Toolbox for IT

Topics

SAP

Blogs

SAP EDI Mapping: An IDoc for Every

Interface

Emmanuel Hadzipetros Jul 24, 2009 | Comments (55)

in Share 0

A common request often voiced on list groups and other professional forums is for a standard cross-
reference between SAP IDocs and EDI transaction sets and messages.

Over the years I've seen some spreadsheets that link IDocs to X12 transaction sets and I've built my
share of IDoc to EDI cross-reference spreadsheets that meet the needs of a particular project.

But here's the rub. There's no official standard cross-reference out there. You can literally map anything
to anything. IDocs and EDI transactions are only data structures, after all. The key is what do you do with
their data in the backend SAP system at your site. This is what the business process is all about.

SAP sends and receives IDocs. But SAP is generally introduced into an environment where EDI is
already being used. So the EDI transactions have been already agreed to with the trading partners and
are already being used in legacy. The key is ensuring that you select IDocs that meet the data
requirements of the business process designed in your SAP system and then figuring out how to map
them to your existing, and any new, EDI transactions or messages.

In other words, like everything else you do in SAP, you need to understand the underlying business
process before you can select the appropriate IDoc to map to EDI. The business process drives
everything.

On the inbound, that means understanding what document the IDoc creates when it hits SAP and what
data that document needs. On a deeper technical level, that means knowing the code, the processing
function and the create transaction that the IDoc calls to create the business document. The EDI team
may not need to know this, but somebody on the SAP team does. This knowledge drives the mapping
requirements.

On the outbound, it's all about the business document that generates the IDoc and the configuration
and/or code needed to collect the application data and output the IDoc. In general, but not always, virtuall
all the data in a business document is sent in an outbound IDoc. This data must then be matched up to
the EDI data that is being sent to the trading partner by the legacy system.

A Team Effort

The key take-away in all this is that it's not just about about mapping messages and transactions. It's
about how the data being exchanged is processed and consumed in SAP and by the trading partner.
Selecting the correct IDoc to map is a team effort that requires both EDI and SAP skills and input.

If you understand these pieces, and if you know what EDI transactions or messages you need to
exchange with your trading partner, you can make an intelligent decision about what IDocs to use,
assuming you got out of the right side of your bed that morning or that you don't have a hang-over or
some other self-inflicted malady.

Having said all that, there are some commonly accepted pairings between IDocs and EDI transaction sets
and messages. So I consulted a few sources and came up with a starting point cross-reference for
inbound and outbound interfaces. I began with two OSS Notes from the SAP Support Portal: 104606
maps IDocs to X12 transaction sets and 150009 lists IDocs that are commonly used in EDI.

I also consulted ERP Genie which has a very useful SAP EDI portal with a number of spreadsheets that map
IDocs to different EDI standards. Then I dug through some IDoc tables and code in SAP, ransacked my
own experience and knowledge, such as it is, tweaked a little here, a little there, and came up with a
mapping that I hope you find useful.

I used the most recent IDoc versions wherever appropriate, confirmed by consulting SAP. I'm a firm
believer in using the latest IDoc versions. Some of these choices are arbitrary and some you may not
agree with. Some pose design issues that some may not want to pursue. Message type TXTRAW, for
example, can be mapped to any EDI text report. But would you want to do it?

TXTRAW formats a text message that is distributed through SAPOffice email. I normally handle these
kinds of interfaces in the EDI subsystem, by designing a report with a map and attaching it to an email
sent through the regular email system. But you never know what opportunities circumstance will throw
your way.

If you have any additions to this mapping, or if you object strenuously to some of these choices, I'm all
ears. Feel free to comment or to send me an email.

One last point: this mapping is IDoc centric because SAP is the business system of record. We begin with
the IDoc and map its associated EDIFACT messages and X12 transaction sets. It could just as easily be
displayed from the EDI perspective.

So without further ado, Odysseus is pleased to present this preliminary SAP IDoc to EDI mapping. Enjoy.
Inbound Interfaces

MsgType BasicType Description EDIFACT X12

ACLPAY ACLPAY01 Freight invoice INVOIC 210
CREADV PEXR2002 Credit advice CREADV 812
CREADV PEXR2002 Extended credit advice CREEXT 812
CREADV PEXR2002 Multiple credit advice CREMUL 812
CREMAS CREMAS04 Vendor/Org info PARTIN 816
DEBADV PEXR2002 Debit advice DEBADV 812
DEBADV PEXR2002 Multiple debit advice DEBMUL 812
DEBMAS DEBMAS06 Customer/Org info PARTIN 816
DELFOR DELFOR01 Delivery schedule DELFOR 830
DELINS DELFOR02 Delivery schedule DELFOR 830, 862
DELJIT DELFOR01 Just in time delivery DELJIT 830, 862
DELORD ORDERS05 Delivery request ORDERS 830, 850
DESADV DELVRY03 Delivery (Despatch Advice) DESADV 856, 940
DIRDEB PEXR2002 Direct debit DIRDEB 828
DIRDEB PEXFI03 Direct debit DIRDEB 828
FINSTA FINSTA01 Financial statement FINSTA 821, 822
GSVERF GSVERF03 Credit memo procedure ORDERS 861
IFTMIN SHPMNT04 Forwarding order IFTMIN 204, 304
INVOIC INVOIC02 Vendor Invoice INVOIC 810, 880
LOCKBX FINSTA01 Lockbox PAYORD 823
MBGMCR MBGMCR03 Post Goods Mvmt & PGI Del RECADV 856, 867, 945
MBGMCR MBGMCR03 Goods Mvmt & Goods Receipt PO RECADV 867, 944
ORDCHG ORDERS05 PO Change Request ORDCHG 860, 876
ORDERS ORDERS05 Customer PO ORDERS 850, 875
ORDRSP ORDERS05 PO confirm ORDRSP 855, 865
PAYEXT PEXR2002 Extended payment order PAYEXT 820
PAYEXT PEXR2002 Multiple payment order PAYMUL 820
PAYEXT PEXR2002 Payment order PAYORD 820
PROACT PROACT01 Inventory Report INVRPT 846, 852
PROACT PROACT01 Sales forecast SLSFCT 852
PROACT PROACT01 Sales report SLSRPT 852
REMADV PEXR2002 Credit advice CREADV 820
REMADV PEXR2002 Payment advice REMADV 820
REQOTE ORDERS05 Response to request for quotation REQOTE 840
SDPICK SDPIID01 Pick/Ship confirm & PGI RECADV 856, 867, 945
SHPADV SHPMNT05 Advanced Ship Notification SHPMNT 856
SHPCON DELVRY03 Ship confirm/PGI RECADV 856, 867, 945
SHPMNT SHPMNT05 Advanced ship noticifaction SHPMNT 856
SHPORD DELVRY03 Delivery despatch order DESADV 830, 850, 856, 940
STATUS SYSTAT01 Acknowledgement CONTRL 997
STATUS SYSTAT01 Functional acknowledgement FUNACK 997
TXTRAW TXTRAW02 Error report (text msg) APERAK 824, 864
TXTRAW TXTRAW02 Error report (text msg) GENRAL 824, 864
WHSCON DELVRY03 Stock confirmation & PGI RECADV 856, 867, 945
WHSORD DELVRY03 Delivery stock order DESADV 940
WMTORD WMTOID02 Transport request (goods movement) RECADV 856, 867, 945
WMMBXY WMMBID02 Post goods receipt (goods movement) RECADV 867, 940, 945

Outbound Interfaces

MsgType BasicType Description EDIFACT X12 Txn

BENREP BENEFIT3 Benefit enrollment N/A 834
CREMAS CREMAS04 Vendor/Org info PARTIN 816
DEBMAS DEBMAS06 Customer/Org info PARTIN 816
DELFOR DELFOR01 Delivery schedule DELFOR 830
DELINS DELFOR02 Delivery schedule DELFOR 830, 862
DELJIT DELFOR01 Just in time delivery DELJIT 830, 862
DESADV DELVRY03 Delivery (Despatch Advice) DESADV 830, 856, 940
DESADV DELVRY03 Delivery (Despatch Advice) IFTMIN 830, 856, 940
EXPINV EXPINV04 Export invoice INVOIC 810, 880
IFTMIN SHPMNT04 Forwarding order IFTMIN 204, 304
IMPINV IMPINV01 Import declaration CUSDEC N/A
INVOIC INVOIC02 Customer Invoice INVOIC 810, 880
MATMAS MATMAS05 Material master/product data PRODAT 832
ORDCHG ORDERS05 PO Change Request ORDCHG 860, 876
ORDERS ORDERS05 Vendor PO ORDERS 850, 875
ORDRSP ORDERS05 PO Response ORDRSP 855, 865
PAYEXT PEXR2002 Extended payment order PAYEXT 820
PAYEXT PEXR2002 Multiple payment order PAYMUL 820
PAYEXT PEXR2002 Payment order PAYORD 820
PRICAT PRICAT02 Price/Sales Catalog PRICAT 832, 879, 888, 889
PRICAT PRICAT02 Product data PRODAT 832, 879, 888, 889
PROACT PROACT01 Inventory Report INVRPT 846, 852
PROACT PROACT01 Sales forecast SLSFCT 852
PROACT PROACT01 Sales report SLSRPT 852
QUOTES ORDERS05 Quotation QUOTES 843
REMADV PEXR2002 Credit advice CREADV 820
REMADV PEXR2002 Debit advice DEBADV 820
REMADV PEXR2002 Payment advice REMADV 820
REQOTE ORDERS05 Request for quotation REQOTE 840
SHPADV SHPMNT05 Advanced Ship Notification SHPMNT 856
SHPCON DELVRY03 Ship confirmation RECADV 856, 867, 945
SHPMNT SHPMNT05 Advanced ship noticifaction SHPMNT 856
SHPORD DELVRY03 Delivery despatch order SHPORD 830, 850, 856, 940
SHPORD DELVRY03 Delivery despatch order DESADV 940
SYIDOC SYIDOC01 EDI/IDoc Guidelines Defintion IMPDEF N/A
SYRECD SYRECD02 EDI/IDoc Guidelines Defintion IMPDEF N/A
WHSCON DELVRY03 Stock confirmation RECADV 856, 867, 945
WHSORD DELVRY03 Delivery stock order DESADV 940