infor.com
concierge
infor u
developer portal
Home
Groups
Lawson - Supply Chain Management Customer Community [READ ONLY]
Bill Only Matching
dechevar
Running into issues matching EDI Invoices to Bill Only POs due to line numbers mismatch. We have recently changed the MA540 job setting to "Validate Vendor Item" = Y, but are still seeing the problem. I have attached screen shots of our MA540 settings, the PO20, the Invoice Lines in MA54, and the error message. Although the screen shots do not reflect the vendor item #s, I did confirm that the PO and Invoice have the same numbers.
Has anyone else run into this and been able to resolve? Any help would be appreciated.
Dan
Find more posts tagged with
Comments
gtesche
How are you sending your Bill Only POs to the vendor, EDI?
dechevar
Usually Fax or Email to the rep. Some go EDI.
gtesche
We send most of ours via email, so I assumed you probably did too. Unless you ask your sales reps to enter the items on the PO in the same order, I think you may always run into this issue of mismatched line numbers.
jon-athey
You can disable the line number mapping when the 810 is processed for that vendor by adding a record in ED40.
List Name: L1_I_810_LINENUMBERS
Lawson Value: N
External Value: {trading partner ID}
Applies to EDI version 9.0.1.5.9 and higher
VWAG_EDI_Nachrichten_201406.pdf
dechevar
Thanks Jon. We had tried this solutions but apparently had the List Nam as LINE_NUMBERS not LINENUMBERS.
After some research, we found that part of the issue is buyer related. We have a policy when end users order X items in RQC, they place an X in front of the Item number. This prevents them from ordering an item they don't want if the manufacturer number they are ordering as a special happens to match a Lawson item number. Unfortunately, Lawson then copies the Item number into the Vendor Item # field with the X if the end user leaves it blank (which they almost always do because Lawson has it buried). The buyer is supposed to remove the X from the Vendor Item # all specials before transmitting the PO. Unfortunately, we are seeing where this is not occurring as the match lines error put when trying to match on vendor item # now.
jon-athey
I feel your pain. We used a # in front the number for X items since the beginning and have had the same issues with the vendor item number. Only recently we stopped so we could use the option in RQC to bump the item number against Lawson to make sure the item wasn't already in the item master. There's still some issues with this but overall it's reduced the number of X type orders.
Legacy Contributor
In RQC, we have that item master match set to a soft stop - not a hard one. The user just clicks "back" and the system allows it to go through without further attempts to change it to a Lawson item.
We also tell the reps for bill onlys - if they do not confirm errors at point of order - we get to hold the invoice an extra month in dispute. Because of the nature of the bill only process, it should be a "perfect order" - so we make them wait if it isn't. (We're meanies.
)
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
ION Connect
ION Workflow
ION API Gateway
Syteline Development
CPQ Discussion Ask a Colleague
Infor Data Fabric
Infor Document Management (IDM)
LN Development
API Usage
FAQs, How-To, and Best Practices