Creating Purchase Orders

Sort:
You are not authorized to post a reply.
Author
Messages
madisg
New Member
Posts: 2
New Member

    We create the vast majority of our Purchase Orders out of PO23.  We are wondering how others manage this; do they build the majority of their purchase orders our of PO100?  There is a stigma by those involved with the onboarding at our organization that the PO23 was referred to as the “scum bucket” and only the trash requisitions end up there.  At the beginning of our Lawson experience PO100 was used some but over time we have gone to almost all PO23 building of POs from requisitions.

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
      Most of our POs are generated via PO100 - we monitor the stat monthly (Who created the PO header) and we are typically at 92 or 93% PO100. And I would say most of the others are some sort of high dollar or project that got manual signatures on a contract or things that were in error and got stuck.

      Are you changing information to get it to a PO? That would be the only reason we'd isolate something and leave it on the pointerfac (PO23) to deal with manually.
      JonA
      Veteran Member
      Posts: 1162
      Veteran Member
        Kat, do you have the PO100 running under a different user id from your buyers? I ask because that's an interesting stat you're collecting, but I have PO100 jobs scheduled to run under each buyer's user id so I wonder how I would determine if the PO was created by PO100 vs out of PO23.
        Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
        Kat V
        Veteran Member
        Posts: 1020
        Veteran Member

          User lawadm runs the PO100 and it is putting the buyer code based on the req loc.  So I can see for buyer code KAT (PO 54) or I can see  how many POs are created from lawadm vs kvila vs jathey based on the POAUDIT table:
          count(AFTER_IMAGE) as "Count", TRIM(USER_ID) as "User"
           from lawson.POAUDIT
          Where AUDIT_TYPE = 'HD' AND AUDIT_ACTION = 'A' 
          AND to_char(UPDATE_DATE, 'YYYYMM') = '202103' 
          group by USER_ID
          order by  count(AFTER_IMAGE) DESC


          That sql gives me 

          Count         User

          10849         lawadm

          245            pegarcia

          156            klaustin

          etc.  I don't go by buyer code - but if you joined it to purchorder, it would be easy enough to do.

           

          You are not authorized to post a reply.