
Hi expert,
We need to integrate our PO with our supplier. We are on AX 2012 R3 and our supplier is on SAP using EDI 850 X12 format. Our consultant suggest to hardcode the X12 Format for this particular supplier. They will also customize a field in Vendor Master to allow user to specify whether the particular vendor is "EDI required". So when the PO is being confirm, a routine will check the vendor master and if this field is YES then it will generate the X12 format to a path. (The path is also a customized screen to allow us to key in).
I dont think this is a best practice because it is customization on the EDI process. I was thinking the EDI should be part of AX capability and we just need to worry about the transformation process.
I need some advice here in terms of design perspective, i really want the vendor to use back standard AIF for the job.
Thanks,
Dave
*This post is locked for comments
I have the same question (0)there is no AX EDI module out of the box. that would be jon rivers @ Data Masons (ISV solution) or BizTalk (MS software) are your 2 best options really, considering if you like having error handling, retry, queuing, transactional.......AX AIF has none of that stuff really, and all the other stuff you will be reinventing..costly....If I had only 1 PO 850 file format to send out and the client wanted to save some money I could be talked into your developers pattern and just hack out 1 hardcoded file, maybe provide some parameterized template so it could be somewhat mappable.
With BizTalk or Data Masons this is VERY easy however creating an EDI solution in AX is no easy task, and there is a graveyard of ISV and Partners who have tried and died. I have created a ton of AIF flat files and invariably I end up building out full fledged EDI solutions (Full Fledged may be a stretch!).....good for my billing but not that effective for the $$