Prev
Next
Forums Enterprise Resource Planning & Manufacturing Lawson S3 Procurement

PO20 If/when to Issue Final?

 4 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
brupp
Veteran Member
Posts: 165
Veteran Member
8/8/2014 2:08 PM
    Hello - One of our Expeditors asked me about the Issue Final function & the timing of when it should be used.  I believe that we typically Issue Final immediately after releasing a non-EDI PO, but perhaps better practice would be to wait until the confirmation is worked.

    Any information/recommendations would be appreciated!
    Thanks & Happy Friday!
    Beth

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
    8/8/2014 3:48 PM
      Issue Final is the only way to transmit Fax Email or EDI - so we use it in your first "Immediate Release" scenario. Our buyers are actually tracked by length of time from PO Creation to Issue Final and shorter is better. If you wait until confirmation - what do you do with the vendors that do not confirm anything?
      brupp
      Veteran Member
      Posts: 165
      Veteran Member
      8/8/2014 5:52 PM
        Hi Kat - We do not use Lawson's EDI program, but you've answered my question. I was not aware that Issue Final was critical to issue via fax or email. And good point about those wonderful vendors who never confirm...Have you ever had a case where you tried to update the Item Detail field & Replace would not work? We received the error "Cannot Replace item, origin is not RQ". That's what brought up this question to do with Issue Final.
        JonA
        Veteran Member
        Posts: 1163
        Veteran Member
        8/8/2014 5:58 PM
          Our buyers only issue final for POs that they want to print for whatever reason. But for most POs the buyers don't issue at all and the PO120 jobs pick them up for faxing, email or EDI. For the POs for vendors that are set at paper issue I have a PO120 job that runs nightly to issue those. If I remember right, when we were on 8.0.3 the PO audit tracking didn't kick in until after the PO was issued. There's probably no real reason to have that PO120 job anymore. For buyer metrics we track the time from req approval to PO line creation and req to receipt.
          Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
          Kat V
          Veteran Member
          Posts: 1020
          Veteran Member
          8/12/2014 6:36 PM
            "Cannot Replace item, origin is not RQ" - yes - the replace item function was dreamt up by Lawson as an inventory solution. As a result, it will only allow changes to items where the PO Line Source is system code RQ. If the PO line was created on PO20, then it is source "PO" and cannot be changed once you've issued the PO. My buyers have reported that the "first" replace can break the tie to the req and any subsequent changes can generate that error.

            In those instances, we update VEN-ITEM and not Item-Detail - you'll get warnings there, but for the most part it allows the change. The invoice matching is setup to look at VEN-ITEM.

            In Jon's scenario, the PO120 is what is Issuing Final - and you'd have the same issues with updating as you have now without a req number.