Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

ALE steps ?

Former Member
0 Kudos

Hello Friends,

Can tell me good websites name i can get the clear steps for IDOC and ALE configuration i have searched lot of sites but i am unable to get the steps with screen shots.

Please can anyone share me the steps to configure IDOC and ALE with screen shots.

Thks helpful answer will be rewarded.


Former Member
0 Kudos

Check these links...


IDOC Convertion



IDOC Creation....

ALE Idoc is method to migrate data between two SAP systems.whereas EDI used to transfer data

between one SAP and other non-SAP systems and vice versa.

IDoc (for intermediate document) is a standard data structure for data migration

between two SAP application carries Business Information.

Business Data is of three types-

1. Control Data - i.e. configuration data (client, company code etc.)

2. Master Data - i.e. Application level data (Material/vendor master etc.)

3. Transactional Data - i.e. also Application level data (Like invoice, billing etc)

For control data IDocs are created once, and after being transferred it can not be changed,

whereas for transactional and master data many IDOCs can be created.

Structure of IDOC-

Message Type- Can contains several segments.

Segment Type- Actual contents of the data contained into the SEGMENT.Segments are the

section of data.Segments containns the fields, it means ields are the

basic building block of any segment.segments are identified by the Sequence no. of the segment i.e. IDOCSYN.

EDIDD,EDIDC,EDID4 are the tables for IDOC data.

Imp. Terms -

Logical System - Logical system is an appropriate name to identify the sender and should be

uniquely binded with a particular client.

CDM (Customer distribution model) - Is responsible for finding out the axact recepient for the IDOC.

Partner Profile - Recipient system should know what type of message it is going to receive from which system,for

this partner profile has to be created,every information related to PORT, RFC, LS, IDOC Type

should be maintained in Partner Profile.

RFC Destination - it will be the other SAP system.

Imp. Tcodes-

WE31 - Creating Segment

WE30 - Creating IDOC Type

WE81 - Creating Message Type

WE82 - Assigning Message type to IDOC

BD64 - Creating CDM

WE20 - Creating Partner Profile

BD82 - Generating Partner Profile Automatically

WE21 - Assign Port to RFC Destination

BD54/SALE - Creating logical System and assign LS to appropriate client.

SM59 - Creating RFC Destination

WE21 - Creating Port and assigning port to RFC destination.

Steps -

1. Create the Logical System.

2. Assign LS to Client.

3. Create RFC Destination.

4. Create PORT.

5. Bind the PORT with RFC dest. to create communication channel.

6. Create Partner Profile.

7. Create CDM.

8. Assign partner profile to CDM.

9. distributing the CDM.

To Create Message type-

10. Create Segment. (WE31)

11. Create IDOC.(WE30)

12. create Message type (WE81)

13. Assign Message type to Idoc Type.

14. Assign the IDOC type to partner profile.

Reward points if useful....

Former Member
0 Kudos

Reward points..

Former Member
0 Kudos

Check the following link:

follow the links



IDOC Convertion



Check this matter.


Electronic Data Interchange

Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.


2) ALE

A means of creating and operating distributed applications.

Application Link Enabling (ALE) guarantees a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications.

Applications are integrated using synchronous and asynchronous communication - not by using a central database.

ALE consists of the following layers:

Application services

Distribution services

Communication services


Check this link

Types of RFC.


Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.

Synchronous RFC:

The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.

Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).

Transactional RFC:

If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.

To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.

Queued RFC:

When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously

For more information on RFC, please go through the link.

In simple words, ALE is used within the organization and EDI is used betn. the business partners.

For eg: in ALE, when you want other branches of your company to have the same data as your main branch. You transport the data through ALE methodology.

Whereas, EDI is used for communication betn ur co. & bank or co. & transport co., etc.

If the other end does not have SAP, then a middle layer like MERCATOR is used to convert SAP data to non-SAP data and vice-versa.

The basic difference is that ALE is the SAP technology for communications and you do not have to depend on 3rd party sofywares for the communication. EDI is the technology which requires you to define/create a sub-system that enables data transfers and these subsystems are 3rd party tools.

THe various types of RFCs used in the technology are

1. Synchronous RFC

2. Asynchronous RFC

3. Transactional RFC (tRFC)

You can refer these links for ALE and EDI.

Please check this PDF documents for ALE and IDoc.

Also check this links for additional information.

Refer the following Websites:

Reward if it Useful.....