Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Financial Management
Infor CloudSuite Financials
EDI PO ISSUE
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Rox
Past 24 Hours:
1
Prev. 24 Hours:
1
Overall:
5259
People Online:
Visitors:
324
Members:
0
Total:
324
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3291
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1375
Roger French
1315
mark.cook
1244
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Financial Management
Infor CloudSuite Financials
EDI PO ISSUE
Please
login
to post a reply.
2 Replies
1
Subscribed to this topic
7 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Jimmie
Basic Member
Posts: 22
2/14/2022 8:13 PM
We have come across an error when performing out PO Issue for EDI vendors when we have made a change to the UOM on the Purchase order. The requisition was for a case, but due to supply or substitution we can only order a box. For some reason the application is trying to do math to equate the PO qty to the Requisition Qty. This is causing an error because we do not allow decimals in our qty field. Is anyone else experiencing this? Would anyone else be willing to share their practices on how they adjust UOM's on the PO?
Kat V
Veteran Member
Posts: 1020
2/15/2022 7:34 PM
Split
We 'flip the flag' and set the item to decimals 4 and then once it's done the math and gets a whole number, we flip it back.
You can also on PO20 - go to the more button then the source button and put in the math it says it can't do.
Test them both and then receive them and see what the SOH does.
Jimmie
Basic Member
Posts: 22
2/16/2022 3:32 PM
Split
Thank you Kat V - we had not encountered this error before moving to Cloudsuite so the method to fix this seemed very manual and band-aid like. It sounds like it has always been that way. I appreciate the quick response!
Please
login
to post a reply.