You are on page 1of 17

ALE IDOC

ALE: It stands for Application Link Enabling. ALE supports the configuration and operation of distributed applications. ALE handles the Message Exchange between Distributed Applications. ALE ensures data is distributed and coordinated using asynchronous communication. ALE uses synchronous connections for reading data. Features of ALE: It supports Distribution of applications between different releases of R/3 Systems. Continued data exchange after a release upgrade without requiring special maintenance. Customer-specific extensions. Communication interfaces that allow connections to non-SAP systems. Coupling of R/3 and R/2 Systems. EDI: It stands for Electronic Document Interchange. EDI is used to transfer data from Non SAP to SAP Systems. Advantages of EDI: It is useful for providing standard means of communication. Reduces Processing time and Cost. Processing of EDI: EDI has two process. 1.Outbound Process. 2.Inbound Process. IDOC: It is an Intermediate Document. IDOC is a container for exchanging data between R/3, R/2 and Non-sap systems. IDoc consists of several segments, and segments contain several fields. IDoc contains three types of records. 1. Control Records. 2. Data Records. 3. Status Records.

Use of IDoc: ALE uses IDOCs to exchange the data between logical systems. Non SAP systems can use IDocs as the standard Interface for Data transfer. IDocs are created by message types and 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 of an IDoc: 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.

Following Tcodes used for IDoc Configuration:

To define Logical System Go to tcode - SALE.

Assign Logical System to client.

For purpose of communication : Create RFC Connection.

Create Ports: (WE21)

Port is used in the outbound process to determine the name of the EDI subsystem program, the directory path where the IDOC file will be created at the operating system level, the IDOC file names and the RFC destinations.

Create Partner Profiles: Partner profile specified the various components used in an outbound process (Partner number, IDOC type, message type, Port, Process code), the mode in which it communicates with the subsystem.

Then go to Tcode: BD64(Distribution Model) To distribute the IDoc (data) from one system to another through this model. First Create Model View and then Add Message type to it.

And select environment tab -> Click on generate partner profiles

In the above screen we have to maintain partner system.

And then Click on edit button -> select model view -> click on distribute (whenever we click distribute the data moved from sender to receiver).

Maintain Same settings as above in Receiver Side also:

For example: ALE configuration for Message type Matmas

Here Sender: 900 Receiver: 800 After done with the above configuration. Now in client 900 go to WE20 and select the inbound system(Receiver side :800) then configure the message type MATMAS in outbound parameters of inbound system .

Then now in 800 client go to we20 select the outbound system(sender side) then configure the Message type MATMAS in Inbound parameters of Outbound System.

Now in client 900 create a material master in mm01.

After creating material in 900 .check it in MM03 display mode whether the material ia available or not.

Then go to tcode BD10 in 900 client .Enter Material No, Message type and Receiver system name. Now click on execute.

Click on Enter after getting below screen.

Now in client 800 check whether the material is available in MM03 or not.

Material Successfully distributed from 900 client to 800 client using ALE.