x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 2782 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
124
topics
484
replies
RWorkman

Purchase Order>>Insights>>Explorer>>Purchase Order Lines View - Status Field displaying incorrect information.

SUGGESTED
Posted By

While performing an open PO lines analysis, we filtered the Purchase Order Lines Explorer view to display all lines with a status of Open.  While reviewing the data set that was returned we noticed several lines that had a status of open in the Explorer view were actually closed on the corresponding PO.  These lines were also showing to be closed for receiving and closed for invoicing on the Explorer view.  In summary:

     1.  The PO status is Closed when viewing the PO when the PO is pulled up using Purchase Order>>Activities>>Enter Purchase Orders.

     2. The PO Line status is Closed when viewing the PO when the PO is pulled up using Purchase Order>>Activities>>Enter Purchase Orders.

     3. The PO Line Miscellaneous Tab indicates the line is Closed for Receiving and Closed for Invoicing.

     4. The Closed for Receiving and Closed for Invoicing Fields on the Explorer View are both displaying True.

     5. The Status Filed on the PO Lines Explorer View is showing Open for The PO Line.

Anyone seen anything like this before?  Is there a step we are missing?  The odd thins is it appears to be random...

Thanks,

Rob  

  • 0

    I think that #2 on your list pulls from tpoPOLine.Status in the database while #5 pulls from tpoPOLineDist.Status in the database so it's possible that the two values are different.

    To find out how many lines are in this situation, you could run this query against the database:

    SELECT COUNT(*)
    FROM dbo.tpoPOLineDist
    JOIN dbo.tpoPOLine ON dbo.tpoPOLineDist.POLineKey = dbo.tpoPOLine.POLineKey
    WHERE dbo.tpoPOLineDist.Status<>dbo.tpoPOLine.Status

  • 0

    We have also noticed this problem and yes, it appears to be random.  We have considered asking our reseller to look into it as we thought it might be linked to our add-on "eRequester" which we use to create our PO's and route for electronic signatures.  We use Project Accounting and the biggest problem this creates for us is that the system still sees the PO as "open" and won't allow us to mark the project as complete.  Our work around has been to:

      1.  Reopen the PO and the line(s) with a status of open as viewed through Explore>>PO Lines and SAVE.

      2. Close the PO again.

    Mary

  • 0 in reply to mehavran
    SUGGESTED

    As a workaround I would suggest modify the vdvPurchaseOrderLine view and replace tpoPOLineDist.Status with tpoPOLine.Status.

    Garik Melkonyan

    www.garikmelkonyan.com

  • 0 in reply to garmel

    Thanks for the feedback.  Sounds like a viable workaround.  I checked the source of the Status Field on the Explorer View and it's "tsmlocalString.Local text which is confusing to me, based on this input I would think the source would be tpoPOLineDist.Status..  I'm also curious (inquiring minds want to know :-)) what the difference is between POLineDist.Status and POLineStatus are and why this seems to happen on a random basis.  If there is a something we are missing from a processing standpoint I'd like to educate the End Users so the system produces the desired results as it's designed.

    On a side note, I tried opening one of the PO's that is exhibiting this issue and saving it and it did not resolve the issue in our case.

    Thanks,

    Rob

  • 0 in reply to RWorkman

    You should see a statement in the JOINs where tsmLocalString is joined to tpoPOLineDist on the Status field.

    I've never understood why there are two tables: tpoPOLine and tpoPOLineDist. There should only be one PO Line table in my opinion.

    I'm not sure what causes it, but you could setup a quick email alert to discover when they occur. Then maybe you could discover some kind of pattern. Private message if you're not sure how to do this.

*Community Hub is the new name for Sage City