Amazon Business EDI 850

I would like to start a new thread regarding Amazon Business. I know there are older threads out there touching on this subject but I hope after 3 years there is a better solution. We want to go through punchout with Amazon Business. This set up was fairly easy. However as soon as we switch to the universal EDI method things fall apart. I keep being told by INFOR that they support amazon business, but yet I am finding it's only partially true some of the time. The SupplierAuxID is now populated as expected. This is true for both XML or EDI. However nothing else Amazon requires for EDI is supported. I do not understand this. Has anyone using INFOR prior to cloudsuite set up EDI with Amazon successfully? I have gone through support and gotten the typical submit an enhancement response, but yet on a call with amazon and INFOR I was told - just turn it on, it will work. I do not want to have to customize my EDI scripts for every client. It does not make sense to try and streamline processes using EDI if it requires manual intervention and customization every time. We are anticipating going to cloudsuite within the next 18 months and I fear this process is only going to be more difficult due to a change in our access in the multi tenant environment. This has become very frustrating. We have been trying to implement punchout with EDI with various vendors for over 3 years and have yet to get on vendor in production successfully.

Find more posts tagged with

Infor Lawson Supply Chain Group - Discussion

Accepted answers

All comments

David Wong

Hi, Jimmie.

Has Support provided application patch JT-119815 and EDI patch JT-119819 to you? These are enhancements that were added for Amazon. Here is the description:

>> Why was this change necessary?
ER#22207: The client is implementing punch out and EDI with Amazon. Amazon's EDI requirements are different from GHX's. The Amazon EDI specification is attached. Specifically, they require different values in PO01-06, PO01-08, PO01-10, and PO01-11. In PO01-11 they are looking for the punch out session from the req line/PO line.

>> Describe the changed or new functionality: (for JT-119815)
? Added punchoutID in position 873-936 (after Ser Nbr) in PO120 File Layout reference
? Added a punchout-id field to the end of the line record in the POEDI workfile
? Added a condition in PO120 to write the punchoutID to the EDI output file
o XML
o Sequential File

>> Describe the changed or new functionality? (for JT-119819)
> Added an EDI condition to read punchoutID in position 873-936 in the POEDI file
> In PO01 Segment: mapped the punchoutID to 11th element and a qualifier "OR" in the 10th element

Jimmie Smith

HI there!

Yes! They did provide me with the JT's to get the SPAID to show up for Amazon - the issue then became getting the other EDI sections that Amazon requires to show up. They require the CURR section, N1 - BT and BY sections with 01 thru 04 lines, the AMT section that I think of off the top of my head.

Infor requires an enhancement to support all these sections.

unknown

So is the issue that it doesn't support the Lawson/GHX mapping? Is there another map that populates all the Amazon segments? I have only ever used GHX, but I know we created maps ourselves back in the day. At one point I still had O&M on the MHS map and the rest on GHX.

Jimmie Smith

I tried all delivered maps - with and without substitutions and nothing would get ALL the required segments at once. I don't think there is a base script delivered that has the all the EDI segments. I am told that maybe when we get to cloudsuite we'll have better luck, but they aren't saying it all the sections are there to choose from or not.

Since we will be going to cloudsuite soon the last thing I wanted to do was stand up an EDI punchout and then have cloudsuite not support any customization we did. Additionally I don't think we have should have to maintain custom scripts for every vendor we want to do EDI with. Seems a little silly if EDI is standard format.

0911060553270289.pdf

Copyright © 2025 Infor. All rights reserved.