Showing posts with label EDIGenie. Show all posts
Showing posts with label EDIGenie. Show all posts

Saturday, July 1, 2017

Everything EDI...

We would like to bring your attention to a portal that shares a lot of good information on Electronic Data Interchange (EDI), a technology that has long been thought of as "dying" but is actually growing in its adoption.
Check it out for free mapping templates, links to standards, recruiters, service companies and much more...

Monday, August 10, 2015

Mar-Kov provides Electronic Data Interchange (EDI) Functionality to the Process Manufacturing Industry

Mar-Kov Computer Systems has added EDI functionality to its standard suite including Manufacturing, Purchasing, Receiving, Sales, Shipping, Barcoding, Electronic Batch Recording (EBR), Lot Track/Trace, Recalls - See more at Global News Wire

Wednesday, May 6, 2015

Mapping the SAP IDoc to / from Partner Profile

I have spent many years coming to grips with the relationship between a SAP IDoc, the partner profile and how it relates to EDI. You can see sample mapping templates here and Sample EDI Specs here but this spreadsheet will hopefully make clear how the SAP Partner Profile (WE20) impacts the IDoc control record (EDIDC) and ultimately how it plays a role in selecting the appropriate map to use for translating in to an EDI message (for outbound). 2 Files are also attached to this post to show:
  1. See the 7 key fields used to determine which partner profile to select - See Image and relate to "Partner Profile Key" section 1-7 below
  2. Relating the EDI fields in the Partner profile to the EDI translation tool - See Image and relate to "EDI standard" section 1-3 below
Read the full article on EDIGenie.COM

Friday, May 1, 2015

SAP Best Practice way of handling inbound posting IDoc errors


I often get asked how IDocs and workflow are connected.... The diagram below should clear up the confusion.
Use transaction WE42 to ensure that the relevant IDoc object is linked to the needed events that workflow uses.
INPUTERROROCCURRED is triggered when the IDoc fails to post. It will then search for linked workflows (configured using transaction SWETYPV) to see what workflow to trigger.
There is a standard single step workflow that is provided but most people want a little more functionality than what is provided SAP standard. Read the full article on EDIGenie.COM