Mapping a Customers EDI field in to and then out of SAP

Customers that transact Orders to you via an EDI X12 850 often need you to send certain, customer specific, fields back to them on subsequent documents. This is often a requirement at both the header and item levels of the order. A common example of a header field would be the department number. It makes sense for the customer to have the department number returned on subsequent documents but we don't have any use for that number in our SAP system other than to store the details and pass it to subsequent documents.

EDI - IDoc mapping to X12 and EDIFACT

This is an oldie but a goodie!!! A list of the Message Types (an example of the IDoc type) linked to the corresponding EDIFACT and ANSI X12 standard message.

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

SAP EDI Subsystem Certification

Cross Application - Electronic Data Interchange Interface (CA-EDI)

• Certified EDI Subsystems - http://www.sdn.sap.com/irj/sdn/interface-certifications?rid=/webcontent/uuid/3e580672-0501-0010-8aab-8d61c461bbb1
• Search for certified EDI subsystems at http://www.sap.com/ecosystem/customers/directories/SearchSolution.epx

Built into SAP’s applications are interfaces to EDI messages.SAP provides an open, common interface to EDI translators / subsystems (XA-EDI). EDI subsystems assume responsibility for all EDI-oriented tasks:

• Converting data
• Message or interchange handling
• Communication
• Partner profile administration
• Process monitoring

Read the full article on EDIGenie.COM

TIP: ABAP code to add an IDoc to your application object

Sometimes you need to write ABAP code to generate an IDoc. With this new custom IDoc generation you would like to have it link to your SAP application object (E.g. Sales Order, Delivery, …) You would like to see your IDoc linked to the Generic Object Services (GOS) display relationships service. Well here is the code needed to do just that…

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