Prev
Next
Forums Enterprise Resource Planning & Manufacturing Lawson S3 Procurement

Cost Option 2 (no charge)

 5 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
Lynne
Veteran Member
Posts: 122
Veteran Member
6/4/2015 3:31 PM

    We are attempting to process a no charge item on a PO.  We have it set to cost option 2 on RQ10, but when we run PO100, we get an error that unit cost is required.  How do we get this to work?

    We have PO100 set to process cost option 2 and 3.

    We also have the requester set to allow unit cost overrides.

    Thank you!

     

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
    6/9/2015 2:22 PM
      It's on a PO25 with a cost? If so, you also need to delete the vendor agreement reference. On RQ10, it's on the Purchasing Tab. The rest of what you're doing sounds correct.
      Lynne
      Veteran Member
      Posts: 122
      Veteran Member
      6/9/2015 3:14 PM
        I resolved the unit cost error with a setting on the requester. I see what you're saying about the agreement ref, but we do have it blanked out. It creates the PO via PO23 correctly. Two of the items have zero cost and the third has a cost. If I run PO100 to create the PO, it does not respect the zero override and seems to pull the cost from the contract. I have PO100 set to include cost option 2. All three items end up having a cost. Any other ideas? Thanks!
        Kat V
        Veteran Member
        Posts: 1020
        Veteran Member
        6/9/2015 4:20 PM
          Does it show on the PO100er1? If not, the PO100 isn't seeing it at all and I'd call it into Infor.
          Lynne
          Veteran Member
          Posts: 122
          Veteran Member
          6/9/2015 4:57 PM
            It is not on the po100er1 as all the lines are being created- just w/ the wrong cost. I have logged a case w/ Infor. Thanks.
            Lynne
            Veteran Member
            Posts: 122
            Veteran Member
            8/19/2015 2:36 PM
              FYI- Infor created a JT for my issue and have created a patch that has resolved the issue.