• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Enterprise Resource Planning & Manufacturing Lawson S3 Procurement

Purchase Order Header Close flag And Close Date

 3 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
JimY
Veteran Member
Posts: 510
Veteran Member
2/6/2017 12:54 PM
In preparation for running PO300 to archive Purchase Orders I ran a query for a particular year that shows the value of the close flag and close date.  I noticed that in several of the records the Header Close flag is set to 'N' , and the close date field has an actual close date.  Also, there are lines for the PO that are still opened.  I would have thought that there would not be a close date if the close flag is N.  Any thoughts ?  Thank you.
Deleted User
New Member
Posts: 0
New Member
2/6/2017 6:00 PM
did you try running the PO199 to see what effect (If any) it would have on the orders you see? I have run into instances where a line is canceled but does not appear to be closed
Kat V
Veteran Member
Posts: 1020
Veteran Member
2/6/2017 8:43 PM
PO190 can be run close the headers. The scenario you describe - close flag = N; close date populated happened when:
(1) large version conversion (7.28 to 8.03) and the flags from the old version didn't align correctly
(2) Buyers had to force a match after the initial close and something has gone astray. You can pull in a field called nbr-closed-lines to see if it matches the actual number of lines. PO190 may also close them correctly.
(3) Bad paint job done to correct one of the above.
JimY
Veteran Member
Posts: 510
Veteran Member
2/7/2017 11:49 AM
I suspect it was a conversion. We have gone from version 7 to 8.0.3 to 9 and now 10 since they were created. I will check out PO190. Thank you for your help.