Skip to Content
author's profile photo Former Member
Former Member


can any one post wht is header idoc and communication idoc in idoc scenario plzzzzzzzzz and aslo the architecture of ale

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jun 17, 2008 at 07:01 AM


    >> Idoc Headder

    A message comprising a header and body with payload (IDoc XML) is sent to the Integration Server for each IDoc XML. Among other things, the header contains the sender service.

    Adapter-specific identifiers must be assigned to each service for the IDoc adapter in the Integration Directory. The specific identifiers for the IDoc adapter are values from the IDoc control record. The IDoc adapter uses these specifications to specify the sender service in the message header. The receiver service in the inbound channel remains empty.

    Before the message leaves the Integration Server, the message header contains values that are exported and used later to complete the IDoc control record.

    The system calls the IDoc adapter and transfers the IDoc XML, the parameters from the communication channel, and the control record data.

    >> communication idoc and architecture of ale

    ALE allows the user to perform an SAP transaction in the sending system, after which the following steps occur:

    1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent

    These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer

    This layer performs an RFC call using the port definition and RFC destination determined through the customer model

    The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems

    If the receiving system is an SAP system then:

    In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs

    In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. E.g.. A PO is loaded on the sending side, yet a SO is created on the receiving system

    Master data has another difference:

    It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object

    If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system

    In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.


    Aashish Sinha

    PS : reward points if helpful

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 17, 2008 at 07:49 AM

    Hi Akhil,

    About IDOC:


    IDoc is nothing but a container of data.It holds the data which is to be transferred to other system. just like a word document which is used to send data to others, Idoc is used to send Business related data to send data to other system.

    For your understanding,find the difference between Master and Communication IDOC.I am not sure if you are referring the Master IDOC as Header IDOC.

    Master IDOC : This idoc collects all the required data into

    single IDOC and this is temporarily stored in memory.

    Communication IDOC: There can be n number of communication IDOCs generated. This comes into picture after the Master IDOC is validated from the distribution model and this IDOC is stored in database table . you can see this IDOC from we02 transaction code.

    Communication IDOC generation:The final IDoc is generated for a receiver after all the conversions and filtering operations done for an IDoc. One master IDoc can have multiple communication IDocs, depending on the number of receivers identified and the filter operations performed. Communication IDocs are saved in the SAP database. At this point, a tangible IDoc that can be viewed by using monitoring tools has been created in the system.

    The IDoc gets a status record with a status code of 01 (IDoc Created).

    What is ALE?


    ALE stands for Application Link Enabling and is a remote connection technology allowing the decentralization of business processes by connecting decentralized systems together.

    Using ALE, it is fairly easy to synchronize several SAP systems so that they contain the same data objects at anytime. These objects may be master data (customers, vendors, GL accounts, cost centers, ...) or transaction data (FI documents, purchase orders, ...). To enable the synchronization, ALE supports not only mass transfer of data between systems but also selective data transfers of objects changed since the last transfer.

    Viewed from a high level perspective, the process is straight and simple: a sender system selects the data that needs to be distributed, packs it in a standard format and sends it to one or several receiving systems. When a receiving system gets the data, it unpacks the standard format and records the data.

    In fact, 3 layers are involved in this process:

    u2022An application layer which selects and records data in R/3.

    u2022A distribution layer which filters and converts data.

    u2022A communication layer which ensures the actual communication of records generated in a standard format.

    The senders and receivers are determined thanks to a so-called distribution model which defines the transfer rules (who sends what to who?). The definition of the distribution model must be known by all systems involved (either as sender or receiver) and must consequently exist on all those systems.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.