Prev
Next
Forums Lawson S3 Supply Chain

PO's not flowing to PO23

Sort:
You are not authorized to post a reply.
Author
Messages
Bev Edwards
Veteran Member
Posts: 366
Veteran Member
4/11/2017 5:03 PM

    User reports that she ran a PO100, but saw a message on the report that no data was pulled. The PO100 in the job schedule shows a successful completion but she overwrote the PO100 report after running the job a 2nd time.
    The PO's are not in PO23, however I ran a po254 report and see all of the unreleased PO's there.
    Why would they not flow to PO23 to be managed there? She said the PO100 job she ran has the parameter for auto releasing PO's set to NO.

     

     

    JonA
    Veteran Member
    Posts: 1162
    Veteran Member
    4/11/2017 5:28 PM
      Think of PO23 as a holding area for req lines waiting for their PO assignment. Once the req line has been added to a PO they're no longer in PO23 but in PO20. Your user had Auto Release set to N so they would be in an unreleased status in the PO254 report. It sounds like the first time PO100 ran it picked up the req lines and assigned PO numbers to them. Then the second time she ran it there was nothing left in PO23 to process.
      Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
      Kat V
      Veteran Member
      Posts: 1020
      Veteran Member
      4/12/2017 4:09 PM
        You can use PO66 (PO Audit) to confirm when and who created the headers if need be. Is it possible the user was looking at the .err (error) pieces and that's what reported no data?

        Jon is correct. PO23 is just the holding pen, once they have a PO, you no longer see them.
        You are not authorized to post a reply.