IDOC – Intermediate Document

IDOC: IDOC is a data container which is use for data transfer from one system to another.
The data transfer can be SAP TO SAP System or SAP to non-SAP

The steps or configuration which is required to enable the system to perform the data transfer
from one SAP system to another is called ALE (Application Link Enabling). ALE IDoc is only for data
transfer from SAP to the SAP system. To transfer data from SAP to a non-SAP system you need EDI
or RFC function module.
The data transferred using IDoc can be Master Data for example Material master, Vendor master,
Customer master, etc, or Transaction Data which can be Purchase order details, Sales order, etc,
or Custom data. Every IDoc has a unique number that is used for tracking.

• SAP to SAP – ALE (Application Linking Enabling) – No flat file involved

• SAP to Non-SAP (vice versa) – EDI (Electronic data interchange) – - Flat file involved.

IDoc Structure & Records

Control Record- contains information such as IDoc no, direction, basic type, message type,
partner, date & time. These records are stored in the transparent table EDIDC.
Data Record- It contains the actual data that is sent to or receive from a partner. Also contains
the details of IDoc segments. IDoc segment has fields that contains the data necessary for posting
the document. Data record information is stored in the data dictionary table EDIDD
Status Record- It defines the processing status of IDoc. This is used to track the IDoc. Status no
represents the IDoc status. The No range 0-49 indicates an outbound IDoc & 50-75 as inbound
IDoc.
03 - Success message – outbound
53 – Success message – inbound

6360959192 www.tagskills.com support@tagskills.com

E2E Configuration Steps (ALE IDOC)
1. SALE – Create Logical System giving name to the sender and receiver
2. SALE – Assign Logical System Logical system gets assigned to client
3. SM59 – Maintain RFC (remote function call) destination Link b/w to application
(RFC destination, IP address)
4. WE21 – Create port Will be done from the sender end (through which the data
passes)
5. BD64 – Maintain distribution model Creation of container (sender, receiver,
message type, triggering – immediate/background job)
6. WE20 - Generate Partner Profiles – (LS – logical system, LI – vendor, KU - customer,
Process codes – MATM, CRE1, ORDE etc)
Example: -

Sender system: 800 Receiver system: 810

Step :1 Create logical system

PATH: T-code: SALE Basic settings Logical system define logical system new entries
Create Log system as ZLS800 Sender logical system and ZLR810 Receiver logical system as shown in bellow fig.

• Click on save button

6360959192 www.tagskills.com support@tagskills.com

Receiver system: 810
Note: no need to create a logical system once again in client 810 because it’s a cross client, the data what we
created above ZLS800 Sender logical system and ZLR810 Receiver logical system it will be reflected in client 810
as shown in below fig.

6360959192 www.tagskills.com support@tagskills.com

Step: 2. Assign Logical System to client in Sender system: Client 800
PATH: T-code: SALE Basic settings Logical system Assign logical system to client
• Double click on 800 client

• Assign logical system = ZLS800 in client 800(Sender logical system assigned to ZLS800 to receiver
system)

• Assign Logical System to client in Receiver system: client 810

PATH: T-code: SALE Basic settings Logical system Assign logical system to client

• Double click on 810 clients

6360959192 www.tagskills.com support@tagskills.com

 • Assign logical system = ZLR810 in client 810(Receiver logical system assigned to ZLR810 to receiver
system)

Step: 3. Maintain RFC in Sender system: Client 800

Path: T-CODE SM59 = select ABAP Connection and click on create button

• Create an RFC destination in sender system

• Input the RFC Destination as ZLR810 and description: Receiver logical system as shown in below fig 1.
• Enter the Logon details as shown in below fig2.
• Click on connection Test as shown in below fig 3.
3

6360959192 www.tagskills.com support@tagskills.com

• Connection test (remote logon should come in yellow colour and no red colour)

• Maintain RFC in Receiver system: client 810

Path: T-CODE SM59 = select ABAP Connection and click on create button

• Create an RFC destination in Receiver system

• Input the RFC Destination as ZLS800 and description: Receiver logical system as shown in below fig 1.
• Enter the Logon details as shown in below fig2.
• Click on connection Test as shown in below fig 3.

3
3
1

6360959192 www.tagskills.com support@tagskills.com

 • Connection test (remote logon should come in yellow colour and no red colour)

Step: 4. Create a port in sender system: 800 clients

• Execute T-code WE21 and select and click on create button and create a own
port name as shown in below fig.

• Enter the description as sender port and RFC destination as ZLR810

• Click on save

6360959192 www.tagskills.com support@tagskills.com

 • Now RFC port as been created Z800_810 as shown in below fig.

• Note: Creation of the port is not required in receiver system client 810.

Step:5. Maintain Distribution Model

• Execute T-code BD64 and click on change view and select the and click on
1

• Enter the details as shown in below fig.

• Click on save

6360959192 www.tagskills.com support@tagskills.com

• Distribution model has been created; it will get updated in last Z800_810

• Select the Distribution model view ZMaterial Z800_810 and click on and input the
details as shown below fig.
• Add message type , MATMAS (Material master) and save

• Once again in same screen select the Distribution model view ZMaterial Z800_810 and click on
and input the details as shown below fig.
• Add message type, SYNCH (ALE Dummy message type) and save

6360959192 www.tagskills.com support@tagskills.com

• select the Distribution model view Zmaterial and click on environment and click on the generate
partner profile as shown in below fig.
2
3

• Click on execute

• Now everything should be in green colour

6360959192 www.tagskills.com support@tagskills.com

• Select the distribution model Zmaterial and click on edit view in header level and Select
and click on
2

3
4

• Select the Receiver logical system and continue

• The model view of target system ZLR810 has been created

Note: no need to create once again in 810 receiver client it is automatically has been created

6360959192 www.tagskills.com support@tagskills.com

Step: 6. Generate partner profile in Sender client 800
• Execute T-code -WE20 and select the partner type LS

• Expand the partner type LS and select Receiver logical system ZLR810 as shown in below fig.
• Double click on MATMAS in outbound parameters

• Check everything and save

6360959192 www.tagskills.com support@tagskills.com

 ➢ Generate a partner profile in Receiver client 810
T-code WE20
• Select the partner type LS and click on create button
2

• Input the partner no has sender logical system ZLS800 and enter the details of TY , user , Lang ,
As shown in bellow fig.
• Click on save

6360959192 www.tagskills.com support@tagskills.com

• In Inbound parameters click on add button

• Enter the Message type as MATMAS and Process code as MATH and save

• Now the data has been saved

6360959192 www.tagskills.com support@tagskills.com

Testing
• Create a material in sender client 800
• T-code MM01 to create a material In sender client 800

• The material 494 has been created in client 800

6360959192 www.tagskills.com support@tagskills.com

In receiver client 810 we can see that material 494 has not bean activated or created

➢ Send the material in T-CODE bd10 in sender client 800

1. Enter the material number 494 and execute

6360959192 www.tagskills.com support@tagskills.com

2.We can see that communication IDOC for message type has been generated in below fig.

➢ WE02 T-Code to see the list of IDOCS

1. Enter the details like created on and execute

2. Now we can see the IDOC number generated

6360959192 www.tagskills.com support@tagskills.com

 3. The status 03 represent the success of this message (data passed to port)

Receiver client 800

1. Check the material in receiver client 810 in t-code MM03 Display

2. All the data related to material has been received in 810 client

6360959192 www.tagskills.com support@tagskills.com

6360959192 www.tagskills.com support@tagskills.com