While there’s no globally recognized standard cross-reference between SAP IDocs and EDI transaction sets and messages, there are some basic mappings that we can safely make.
ALE, EDI & IDoc Technologies for SAP by Nagpal, Arvind; De Bruyn, Gareth; Lyfareff, Robert and a great selection of related books, art and collectibles available now at AbeBooks.com. For the last five years, he has served as an independent echnical SAP R/3 consultant and has assisted numerous Fortune 500 clients in implementing EDI, ALE, and IDoc technologies in R/3 versions 2.2 through 4.6. He is working closely with Arvind Nagpal, the original author of this best-selling book. Please send me the links and material about ALE/EDI/ ALE, EDI and IDoc Technologies for SAP by Arvind Nagpal is a good book for ALE/IDoc(s). Arvind Nagpal is the author of Ale, EDI, & Idoc Technologies for SAP ( avg rating, 30 ratings, 4 reviews, published ), Ale, Edi, & I Doc Technolo.
The key thing to remember is that the business process drives your mapping.
On the inbound, that means you need to understand what the IDoc is going to do once it hits SAP. Is it creating a specific business document or posting to a particular data object such a customer or material master or an inventory update?
The key question is: what data does it need from the EDI message to post to its SAP business object?
On the outbound, the IDoc is generated with data from an SAP business document or other data object.
The key question for the outbound process is: what data does your trading partner need to receive in the EDI transmission?
The point I’m trying to make here is that literally anything can be mapped to just about anything. But your business process drives your data requirements and your data drives your processing flow, whether you’re dealing with standard or custom functionality.
There is, of course, a starting point. SAP sends and receives IDocs. But SAP is generally introduced into an environment where EDI is already being used. So the EDI transaction sets or messages have already been agreed to with the trading partners and are being used in legacy.
IDocs must therefore be selected that can carry the data in the EDI messages and then post them to a particular transaction in SAP, which is generally done through function modules. You need to understand the business process, but you also need to understand how SAP processes its IDocs in support of that business process.
And remember … if there’s no fit, you can always extend a standard IDoc with custom segments or build a completely new IDoc from scratch. And because the IDoc interface is an open, intelligent data processing API, you can always add your own code to user exits, BADIs, or build a custom function to meet any requirements demanded by the business process.
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 to an EDI transaction or message is a team effort that requires both EDI and SAP skills and input.
If you understand the overall business process, and if you know what EDI transactions or messages are exchanged with your trading partner, you can make an intelligent decision about what IDocs to use or whether you need to do some customization.
There are some commonly accepted pairings between IDocs and EDI transaction sets and messages. OSS note 104606 maps IDocs to X12 transaction sets and 150009 lists IDocs that are commonly used in EDI.
Arvind Nagpal, in his excellent book ALE, EDI, & IDOC Technologies for SAP includes a basic mapping in Table A-2 of his Appendix (page 709 in my copy). But he’s dealing with an earlier version of SAP.
ERP Genie, which has a very useful SAP EDI portal, has published a number of spreadsheets that map IDocs to different EDI standards including EDIFACT, X12, and even VDA.
There have also been some spreadsheets kicking around for a few years from SAP that map IDocs to mostly X12 transactions.
These sources have one thing in common: they’re very basic and only include a handful of transactions. But there are literally hundreds of EDI transaction sets and messages, particularly when you consider all the different versions in use around the world.
It’s literally impossible to map everything. But we can map a lot more IDocs and understand that any mapping is only a beginning, that the business process in the end determines what we actually do.
So I’ve tried to expand on the existing cross-references and included suggested mappings based on IDoc tables and code in SAP and my own project experience and knowledge of EDI, such as it is, tweaked it a little here, and a little there, to come up with a mapping that some may find useful, at least as a starting point.
I used the most recent IDoc versions wherever appropriate. Some of these choices are arbitrary and some you may disagree with. Some pose design issues that you may not want to pursue. Message type TXTRAW, for example, can be mapped to any EDI text report. But would you really want to do it?
Arvind Nagpal Ale Idoc Book Pdf

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 process improvement opportunities circumstance will throw your way.
So without further ado, here is my 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 |
ALE, EDI, & IDoc Technologies for SAP, 2nd Edition (Prima Tech’s SAP Book Series) [Arvind Nagpal, John Pitlak] on *FREE* shipping on. Please send me the links and material about ALE/EDI/ ALE, EDI and IDoc Technologies for SAP by Arvind Nagpal is a good book for ALE/IDoc(s). Arvind Nagpal is the author of Ale, EDI, & Idoc Technologies for SAP ( avg rating, 30 ratings, 4 reviews, published ), Ale, Edi, & I Doc Technolo.
Author: | Mezihn Gardarg |
Country: | Dominican Republic |
Language: | English (Spanish) |
Genre: | Art |
Published (Last): | 22 June 2006 |
Pages: | 478 |
PDF File Size: | 10.71 Mb |
ePub File Size: | 5.36 Mb |
ISBN: | 607-3-39376-741-6 |
Downloads: | 97296 |
Price: | Free* [*Free Regsitration Required] |
Uploader: | Vut |
ALE/EDI/IDOC Material
Tiger woods pga tour 12 for mac free download. Discover Prime Book Box for Kids. Top Reviews Most recent Top Reviews. I found it fairly simple to navigate quickly to my area of interest Read more Read less. From a high level perspective of managers and Project managers, this is a good book to have on hand. Explore the Home Gift Guide. Worth having as a reference book on any shelf.
ALE/EDI/IDOC Material
This book is not yet featured on Listopia. The only thing that I regret is that this technology is quite old and start to be left and replaced by new one.
As if someone wrote about a few of their favorite implementations. And again, I’ll admit to skimming a lot of it that I didn’t have a pressing need to know right now.
Arvind Nagpal (Author of Ale, EDI, & Idoc Technologies for SAP)
The breadth and depth of the material covered in the book has been well balanced. Get to Know Us. There’s a problem loading this menu right now.
Arvind Nagpal Ale Idoc Book 1
I make agvind a point to read the manuals completely and flag the sections that will come in handy later on. Since I’ve worked with SAP EDI for a few years, I didn’t expect a lot of things to be new to me in the first 3 or 4 chapters, but man, there was nothing even moderatly interesting to me in the early part of the book.
Read reviews that mention ale and edi want to learn edi and ale well organized edi and idoc concepts of idocs great book sap system sap edi excellent book pages info reference examples explained presented step bible business chapters.
Now, the Nagpal book starts with quite a few more pages Return to Book Page. Yes, some nnagpal this stuff is ‘light’ too.
I am from the old school and like to have reference manuals available at my fingertips when I need clarification wrvind a particular software feature. I make it a point to read the manuals completely and flag the sections that will come in handy later on. Customers who bought this item also bought. Amazon Rapids Fun stories for kids on the go.
Rakesh rated it really liked it Mar 12, Amazon Renewed Refurbished products with a warranty. Subbu rated it really liked it Oct 25, There are no discussion topics on this book yet.
Gave me the reference I needed for my job. Supriya rated it really liked it Sep 03, Aug 04, Saurabh marked it as to-read.
Open Preview See a Problem? See and apply real-world scenarios. In order to navigate out of this carousel please use your heading shortcut key to navigate to the next or previous heading.
But the iddoc cost of those few possibly valuable pages is quite high!