Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Beginner’s Guide to ALE and IDocs – a step-by-step approach

Beginner’s Guide to ALE and IDocs – a step-by-step approach

Ratings: (0)|Views: 117|Likes:
Published by Prashanth Darshanam

More info:

Published by: Prashanth Darshanam on Aug 31, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





What is an IDoc?
An IDoc
intermediate document 
Type is SAP's format for data being moved betweenlike electronically. This includes how fields are grouped together (segments), the order and hierarchyof these groupings, and the format of each individual field.If you're familiar with EDI at all, then an IDoc will look very familiar to you. Nearly everything you'reused to is there: from segment name to allowable codesto min/max occurs.It is important to note that an IDoc Type is really just a structure defined on the system and given aname (i.e., ORDERS04). An actual IDoc, however, consists of data, which fits within the definedstructure of the IDoc Type. This IDo
IDoc Structure
The "only once" rule
It is valuable to note that SAP only allows one occurence of each segment type within the IDocstructure. For instance, the E1EDKA1 segment may only exist once withinthe IDoc type.Now, does that mean you can only have one E1EDKA1 segment in an actual IDoc? Of course not.04IDoc.
Generic Structure
Data within an IDoc is divided1.Control Record, which contains (Table EDIDC)1.Key Fields (for inbound)1.Receiving Partner Type/ID (RCVPRT, RCVPRN)2.Logical Message Type3.Test Flag2.Other Fields1.IDoc Number (DOCNUM)2.3.Sending Partner Type/ID (SNDPRT, SNDPRN)4.Status5.Receiver/Sender Port6.Created Timestamp7.Changed Timestamp3.etc.2.Data Records (Table EDID4 in 4.6C)1.Admin Data (39 bytes)
1.IDoc Number (DOCNUM)2.Segment Number3.Segment Name (SEGNAM) (e.g., E1EDK01, E1EDK03, etc)4.etc2.Actual Data (SDATA1,000 bytes)3.Status Records (Table: EDIDS)1.IDoc Number (DOCNUM)2.Counter (COUNTR)3.Status (STATUS)4.etc1.Data record table is version-specific. EDID4 is valid for the current release of SAPR/3 andmay change in future versions.2.for inbound processing.3.EachIDoc may have several data records, which are arranged hierarchically. The data4.Each IDoc may have several status records, which are arranged in sequence.5.Segment Typesbegin with E1. This is the internal SAP format.6.-specic format which denes howthe outside world sees the segment.7.8.Outbound IDocs are created dircontrol. Most outbound documents within OTC are created by message control.9.
Status Codes
Outbound CodesInbound Codes
00Not used, only R/250IDoc added01IDoc created51not posted02Error passing data to port52fully posted03
Data passed to port OK
5304of EDI subsystem54Error during formal
05550656IDoc with errors added07Error during syntax check57Test IDoc: Error during08Syntax check OK58IDoc-Copy from an R/209Error during interchangehandling59Not used10Interchange handling OK60Error during syntax check of IDoc (inbound)11Error during dispatch61Processing despite syntaxerror (inbound)12Dispatch OK6213Retransmission OK63Error passing IDoc to14Interchange Acknowledgement64IDoc ready to be transferred15Interchange Acknowledgement65Error in ALE service1666predecessor IDoc1767Not used18Triggering EDI subsystem OK68Error-no further processing19Data transfer for test OK69IDoc was edited20Error triggering EDI subsystem70Original of an IDoc which wasedited21Error passing data for test71IDoc reloaded from archive22Dispatch OK, acknowledgement72Not used, only R/223Error during retransmission73IDoc archived

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->