EDI 810 fro Non-PO Vendors

dechevar

Is anyone processing EDI810s for non-PO vendors? Looking for the lessons learned and any advice you can share.

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

unknown

I didn't even know this was possible. How will you translate it? I thought MA540 was PO Match only.

Stace Webley

I didn't know this was possible either.

XA Virtual Summit - Foundation for the future.mp4

kevinwheeler

Hi Kat, we actually bring in appx. 30 invoices a day from our Pharmacy Vendor (McKesson) via GHX. These are Non PO Invoices. We have them come into MA54 as Expense type invoices and the staff from the Pharmacy assigns accounting information and a batch number to each invoice, allowing them to drop for payment. This has been in place for many years and eliminated the 'sneakernetting' that was being done prior.

f10k_error_295451.docx

dechevar

Kevin, Do you have a functional design you can share on set up? Does the pharmacy staff code on MA54?

kevinwheeler

I created a screen in Design Studio for MA54 (carved down version) to keep the entries and tabbing to a minimum, since these users were not Lawson users up to the point where we rolled it out. In AP10, we changed the vendor from 'MAT' to 'EXP', so that this value would not need to be changed in MA54. So basically, the Pharmacy staff receives a Crystal Report following our EDI Inbound (ED502) run, that shows them the 'Pharmacy' invoices that were received for the day. Once they receive this, they go into Lawson Portal (MA54) and add batch number and accounting information to each invoice. One thing that I failed to add earlier, when we went to V10 last year, we found that MA54 will no longer allow Invoice Lines to be present on Expense type invoices. Prior to V10, this was never an issue. Based on this, we needed to write a script that reads the MA540CSV file that is created from ED502 and strip off the invoice lines for these invoices to allow them to continue to process as they had been. I opened a ticket with Infor once we realized this was an issue and they said that is the way it had always been (even prior to V10). I knew differently.........so I had to come up with a solution.

Copyright © 2025 Infor. All rights reserved.