How to do mass cost adjustments to PO20

Does anyone in the community have a process for doing mass cost adjustments to PO20? We are trying to avoid doing them manually since we have a large volume of adjustments each month.

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

unknown

You can upload changes to PO20 by mapping:
Company
Procurement Group (Note: Hidden field)
PO number
PO Code (we do not use release, but you would need to map it if you do)
Position To Line Nbr (f29 in the version I'm on it's PT PLI LINE NBR - PT is "Position To")
FC (C)
Unit Cost (VBUY UNIT COST)

unknown

Ok..thanks. When you perform this process for inventory items, have you had any problems with missing cost adjustment account information in the IC50 and IC130? Or do the cost adjustment accounts populate as expected for inventory items?

jon-athey

What is the purpose of doing monthly cost adjustments to the po line?

unknown

We are adjusting the PO cost to reflect the price paid. This happens when we recieve a cost message. If we determine that the invoice price is correct, we go back into PO20 to adjust the cost before closing the cost message in MA64. Doing this manually takes a lot of time.

It would be nice to update cost with add-ins but when we do the adjustment with add-ins, our stock items are missing the cost adjustment accounts, which we can see in IC50 and IC130. We're not sure if we doing something wrong with the add-in or if there is glitch with Lawson

jon-athey

Seems like you're doing more work than necessary. If you just select the adjust action in MA66.3 and release the message you don't have to make any changes to the cost on the PO line. When AP completes the match you will see the CA in IC50 for stock lines.

dechevar

Jon is correct. Accept the price in the invoice matching screens or do a chargeback to only pay your PO price. No need to constantly touch the po lines. Focus on price resolution and updating the PO25 to avoid future price exceptions.

Copyright © 2025 Infor. All rights reserved.