Prev
Next
Forums Enterprise Resource Planning & Manufacturing Lawson S3 Procurement

PO Number Usage

 3 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
R Phillips
Advanced Member
Posts: 42
Advanced Member
5/10/2018 10:23 PM

    This is probably one of those slap your forehead, why didn't I think about that issues. 

    How are PO Numbers used within Lawson and why does it seem like PO Numbers are being skipped? 

    Many years ago they created a PO Number scheme that assigned location A to all POs in the 70000000 range and location B all POs in the 80000000 range. Well, we are now at around 79100000 and are trying to figure out how long before we hit 80000000. We process about 500 POs per day yet the numbers are disappearing faster than that. For example, we started at 79132750 this morning and ended on 79134637 which would be 1,887 POs for today. Is there another process that uses the numbers? 

     

    Thanks for your help!

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
    5/11/2018 12:47 PM

      Starting in v9(? possibly earlier), PO100 creates headers and then attempts to add lines. If it cannot add lines, it deletes the headers.  At one point it was close to 1 deleted to 1 kept, so I feel your pain.

      I don't know what my IT did to fix it, but Infor should be able to assist.

      Assuming you have your audit turned on, PO191 will confirm what is deleting the numbers.  Yesterday we had 498 POs and the number range is 500 - so 2 got deleted.  Attached is my results on PO191.

      Attachments
      JonA
      Veteran Member
      Posts: 1163
      Veteran Member
      5/15/2018 5:52 PM
        I can't say that we had an issue where many PO headers were getting deleted. Our POAUDIT table shows roughly 617,000 PO headers added and 5200 deleted since May 2007. Which translates to 220 POs added and 2 deleted per day on average. I just ran PO191 for year to date and I see just over 100 POs deleted using PO100. Still not too many.

        So if the program was fixed does it still delete the PO header when there are no lines and it's just not as bad as it was in v9? Wonder if it used to create a PO header for every vendor that had an item in PO23 and deleted it if the item(s) couldn't be added. And maybe now it tries to reuse that PO number for the next vendor and ultimately deletes it if no items in PO23 can be added at all. If this is the case I can see that if you had PO100 scheduled to run very often and much of the time there were no lines in PO23 that could be added you might have a lot of deleted PO numbers.
        Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
        R Phillips
        Advanced Member
        Posts: 42
        Advanced Member
        5/16/2018 4:35 PM
          Aha! This was a lot of help. We are still plugging along in v9, so that is our issue.