Idoc & ALE

[Spoorthi]

Idoc Definition
An intermediate document (IDOC) is a container for distributing R/3 application data among between R/3, R/2 and non-SAP systems




Use
ALE uses IDocs to exchange data between logical systems. Non SAP-systems can use IDocs
as the standard interface for data transfer. IDocs are created by message types and (object)
methods when data is to be distributed. The message type is the format in which the data for a specific business process is transmitted electronically.




Structure
An IDoc represents a configuration of an Idoc Type that determines the IDoc structure. An IDoc consists of a header,
several data segments and status records. The functions of the individual elements of an IDoc are as follows:
• The contents, structure, sender, receiver and current status of the IDoc are defined in the IDoc header.
• Each data segment contains a standard header consisting of a sequential segment number, a description
of the segment type and a 1000 character long string field containing the actual data of the segment.
• The status records show the history of the processing steps applied to the IDoc so far.

[Spoorthi]

Structure of an IDoc



the IDoc contains a header segment that has to be the first segment of the message. Thereafter there must be at least one additional item. The following conditions apply:
•Each item must be followed by at least one sub-item and at most 99.
•Up to 9999 text segments can appear after an item’s sub-items (optional).
•The last segment in a message must be an accumulation segment (ACCUM).

[Spoorthi]

IDoc type




The IDoc type indicates the SAP format that is to be used to transfer the data for a business transaction. An IDoc is a real business process in the form of an IDoc type.
An IDoc type can transfer several message types:
These are the "logical messages" that correspond to different business processes.
An IDoc type is described using the following components:
• a Control record - The format of the control record is identical for all IDoc types.
•one or more Data records - a data record consists of a fixed administration part and a data part (segment).
The number and format of the segments can be different for each IDoc type.
•Status records
the status records describe the processing stages which an IDoc can pass through and have an identical format for each IDoc type.

Example :Purchase order number 4711 was sent to a vendor as IDoc number 0815. IDoc number 0815 is formatted in IDoc type ORDERS01 and has the status records "created" and "sent". The purchase order corresponds to the "logical" message ORDERS.

[Spoorthi]

Application Link Enabling




Application Link Enabling (ALE) refers to the creation and operation of distributed
applications. The basic idea is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.



In the Sending System:
Transaction Code for IDoc list is : WE05
A list of IDocs grouped by status is displayed:
StatusDescription of Status

03, 12, 38 IDoc successfully transferred

02, 04, 05, 25
26, 29 Processing error

30 Waiting status (still processing...)

>=50 Inbound IDoc (not relevant in this context)

Other Not relevant in this context




In the Receiving System
Transaction Code for IDoc list is : WE05
A list of IDocs grouped by status is displayed:
StatusDescription of Status

53 IDoc successfully updated by application

64 Waiting status (still processing...)

<50 Outbound IDoc (not relevant in this context)
51, 56, 60, 61,

63, 65 Inbound error

Other Not relevant in this context

[Spoorthi]

APPLICATION MESSAGE TYPES

CUSTOMER - DEBMAS
VENDOR - CREMAS
MATERIAL - MATMAS
SALES ORDER - ORDRSP
PURCHASE ORDER - ORDERS

T-Code to view the Message Types is : WE81.




TRANSACTION CODES FOR ALE




/N SALE : To Define and Assign Logical Systems .
/N SM59 : To Establish RFC Connection.
/N BD64 : To Create Customer Distribution Model.
/N BD82 : To Generate Partner Profiles.
/N WE05: To View IDoc Lists.
/N BD10: To Send the Material Data. /N BD11: To Receive the Material Data.
/N WE19: To Debug the IDoc.

[wizkid]

tats nice info spoorthi..carry onn