Forums
Lawson S3 Procurement
ED40 Outbound UOM
Author
Messages
Alfredo Burdwell
New Member
Posts: 2
11/15/2019 9:46 PM
I am having trouble setting up a substitution table for a vendor to change the UOM from EA to PC when going across EDI. Can someone help me understand? This is how I have it built.
List Name …. GHXROCHE_O_UOM
Lawson Value ….. EA
External Value..... PC
V10 Lawson
John Henley
Senior Member
Posts: 3348
11/15/2019 10:21 PM
moved to procurement forum
JimY
Veteran Member
Posts: 510
11/18/2019 10:59 AM
I know that we change the UOM CA to CS and vice versa using the entries below which changes it for all vendors, but we have never tried it for a specific vendor. You might check with Infor Support to see if it is possible for a specific vendor.
L1_I_UOM CA CS
L1_O_UOM CA CS
JimY
Veteran Member
Posts: 510
11/18/2019 2:42 PM
I found this KB Article, 1206229, on Infor Support that might be useful. It is for older version of EDI, but it did state that it could be used for later versions. Good Luck.
Red
Veteran Member
Posts: 87
12/11/2019 11:27 PM
Alfredo,
Not sure if you have solved for this yet. I can say that we have used this setting at the Trading Partner level (tp_O_UOM) in the past. In the end, I think we put it on our trading partners to make the translation internally. Much like JimY shows, I would think you would want both an outbound and an inbound translation. It seems like not having the inbound portion would lead to matching issues on the Receiver and Invoice.
All this said, this is still not a bulletproof solution. As an example, we had something nearly identical to JimY's lines so that our CA (ANSI standard 'case') became CS (non-ANSI standard, but oh so prevalent 'case'). But, CS is the ANSI abbreviation for 'cassette', so whether appropriately identifying a 'cassette' or mistakenly identifying a 'case', we might have a CS on the PO Line. The ED40 would ignore it going out but change it to a CA coming back in. We had about six such standard translations for case, tray, gross, bottle and a couple of others--each of which was subject to this issue. At the end, you bbuild for your predominant use case, but just something to be aware of.
Good luck,
Red