PROJECT ________________________________________________

SAP ABAP ECC 6.0V

Training Manual on IDOC Processing End Users

INDEX

Page No.

Cross Applications.3 IDOC (Intermediate Document). 3

IDOC TYPE Structure 3 Status Codes.. 4 Logical Message Type. 4

ALE (Application Link Enabling).. 5 Outbound Process.5 Inbound Process. 6 IDOC Scenario to send Material
Create Logical system for Client 800. Assign Logical system to Client 800. Create Logical system for Client 810. Assign Logical system to Client 810. Create RFC connection from Client 800 to 810.. Create RFC connection from Cline t810 to 800.. Create Distribution Model. Create Port. Create Outbound Parameter.. Create Inbound parameter.. Send material from one Client to another. Check the IDOC status in Sending System.. Check the IDOC status in receiving System.. Check the Material details in receiving System.

7
10 16 20 27 30 36 43 48 51 61 66 68 71 73

Cross Applications
Cross Application is a communication methodology which is used to transfer the data from SAP to SAP and SAP to NON-SAP systems. Different Cross Applications components are 1) Remote Function Call (RFC) 2) Intermediate Document (IDOC) 3) Application Link Enabling (ALE) 4) Electronic Data Interchange (EDI) 5) Business Application Programming Interface (BAPI)

IDOC (Intermediate Document):

IDOC is an Intermediate Document. IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. In other words it contains business data which is used to exchange between two SAP R/3 systems. Technically an IDOC is an instance of IDOC TYPE where IDOC TYPE describes the behavior of IDOC at runtime. When we execute an outbound ALE or EDI Process, an IDOC is created. In an inbound ALE or EDI process, an IDOC serves as input to create an application document. Client). IDOCs are independent of the sending and receiving systems (SAP-to-SAP as well as Non-SAP).

In the SAP System, IDOCs are stored in database. Every IDOC has a unique number (within a

IDOC TYPE Structure:

IDOC structure has two components, they are

1) Segment: It defines the structure and format of data record which carries the actual
application data that is exchanged between two SAP R/3 systems.

2) Data Element: It is a data type which defines the type and length of the fields of the
segment similar to database table fields.

Structure of an IDOC contains three records.

a) Control Records b) Data Records c) Status Record IDOC Structure Control Record Data Record Status Record Fig: Structure of an IDOC

a) Control Record:
It contains information like IDOC number, sender, recipient information, which port it is using,
Message type etc.

All control record data is stored in EDIDC table. The key to this table is the IDOC Number.
There will be only one Control Record for an IDOC.

b) Data Record:

Data record contains actual application data which is exchanged between two SAP R/3 systems
like employee header info, weekly details, Client details etc. There can be multiple data records in an IDOC.

All data records are stored in a database table EDID4.

c) Status Record:
It contains the information of the IDOC status that is whether it is successfully transferred or not (Acknowledgement). There can be multiple status records in an IDOC.

Status records information is stored in a database table EDIDS.

Status Codes:
0 to 49 50 & Above Outbound Processes (Sending System) Inbound Process (Receiving System)

Logical Message Type:

This interprets or finds the IDOC TYPE with which system generates an IDOC. I.e. exchanged between two SAP R/3 systems. Technically, IDOC is the format of the data; logical message is the business meaning of the data.

Built-In Logical Message Types: 1) MATMAS 2) DEBMAS 3) CREMAS 4) COSMAS : : : : Material Master Data Customer Master Data Vendor Master Data Cost Center Master Data

ALE (Application Link Enabling):

It is a communication technology in which communication is based on application to application integration, which is achieved with the help of messaging architecture where the messages identify the type of information exchange between two SAP R/3 systems. ALE architecture consists of two processes. 1) Outbound Process 2) Inbound Process

1) Outbound Process: It is the process triggered at the sending system and contains the following
steps.

a) The data to be sent is prepared as application document and stored in the database. b) The application document is converted to Master IDOC with the help of ALE outbound program. c) The master IDOC is placed in the ALE service layer which generates communication IDOCs for the receiving systems.

Distribution Model: It identifies the SAP R/3 systems and the messages exchanged between
them in the distributed environment. d) Communication IDOC is then sent to Communication Layer which generates port.

Port: It is a medium, which transfers Communication IDOC (Application Data) to the receiving
system.

By default the port ALE uses is TRFC (Transactional Remote Function Call). TRFC: It is an asynchronous process that means it transfers the application document to the
receiving system & will not wait for the acknowledgement to come from receiving system instead it keeps on transferring the communication IDOCs to the receiving system.

2) Inbound Process: Once the Outbound process gets completed then the process triggered is
inbound process at the receiving system & contains the following steps.

a) The communication IDOC receives at the receiving system and it undergoes various checks for
data verification. b) The communication IDOC is then placed in the ALE service layer which converts it to the Master IDOC. c) The master IDOC is then converted to an application document with the help of ALE Inbound Program and is stored in the database from where the user can view with the help of standard transaction.

Process Code: Process Code is an inbound program to which an Inbound Function Module is
attached which takes communication IDOCs & converts it into Master IDOC and then Master IDOC is converted to an application document with the help of ALE Inbound program and stored in the database.

To configure the ALE architecture for transferring the whole document (Material Master Data) from sending system (Client - 800) to receiving system (Client - 810) Login to Client 800 to check the Material details:

Enter the transaction code SE16N in the command field to go with the General Table Display screen and press Enter.

Maintain the following field values on the respective screen fields of above screen: Table Material : : MARA (Contains General Material Data Details) M444 (Material Number, to see the corresponding details of material)

Now click on Online button from standard tool bar or press F8 function key, to see the details of material number M444.

From the above screen you can observe the details of material number M444 in Client 800.

 Login to Client 810 to check the availability of same Material Number M444

Details, which we have already noticed in Client - 800:

Enter the transaction code SE16N in the command field to go with the General Table Display screen and press Enter.

Maintain the following field values on the respective screen fields of above screen: Table Material : : MARA (Contains General Material Data Details) M444 (Material Number, to see the corresponding details of material)

Now click on Online Material Number M444.

button from standard tool bar or press F8 function key, to see the details of

The above error message on status bar describes that there is no material details available in Client 810 with the material number M444.

Now with the help of IDOC processing we are going to transfer Material Number M444 from Client 800 (Sending System) to Client 810 (Receiving System) within the same server.
To Define Logical System for Client - 800 (Sending System), Login to Client - 800:
Logical System: It is a name which uniquely identifies the system in the network.

Enter the transaction code SALE in the command field to deal with the IDOC and ALE development and press Enter.

Expand Basic Settings as shown in the above screen and expand Logical systems and then click on Define Logical System, to create Logical System name for Client 800.

Click on

button as shown in the above screen.

Click on New Entries push button from application tool bar as shown in the above screen.

Maintain the following field values on the respective screen fields of above screen: Log.System Name : : LOG_SYS800 Logical System for Sending System 800 button from standard tool bar, to save the created logical system.

Then click on Save

Click on

button as shown in the above screen.

Click on Create

button to create the own Request number for saving the created Logical System.

Give the Short description as SAP request for sending Logical System, to Create Request and click on Save button from standard tool bar to save the own request number.

Click on

button as shown in the above screen, to save the request number.

After saving request number, the above success message will appear on the status bar, which describes that the data was saved. Then click on Back button from standard tool bar.

From the above screen we can observe the created Logical system name in the marked area. Then click on Save button (optional) from standard tool bar.

After saving logical system, the above success message will appear on the status bar, which describes that the data was saved. Then click on Back button from standard tool bar.

 To Assign Logical System LOG_SYS800 for Client 800 (Sending System), Login to

Client - 800:

Click on Assign Logical System to Client, to assign created Logical System LOG_SYS800 to Client 800.

Click on

button as shown in the above screen.

Double click on Client 800 to assign the logical system LOG_SYS800 to Client 800.

By default IDES-ALE Logical system name is assigned to Client 800. Then to proceed with the connection process of our requirement, we need to assign our logical system name in the field of Logical system. But it is strongly not recommended to change logical system name.

Assign our Logical System name LOG_SYS800 for Client 800 and click on Save tool bar.

button from standard

Click on Client 800.

button as shown in the above screen to save the assigned logical system LOG_SYS800 for

After saving the assignment of logical system, the above success message will appear on the status bar, which describes that the data was saved. Then click on Back button two times from standard tool bar.

 To Define Logical System for Client 810 (Receiving System), Login to Client - 810:

Enter the transaction code SALE in the command field to deal with the IDOC and ALE development and press Enter.

Expand Basic Settings as shown in the above screen and expand Logical systems and then click on Define Logical System, to create Logical System name for Client 810.

Click on

button as shown in the above screen.

Click on New Entries push button from application tool bar as shown in the above screen.

Maintain the following field values on the respective screen fields of above screen: Log.System Name : : LOG_SYS810 Logical System for Receiving System 810 button, to save the created logical system.

Then click on Save

Click on

button as shown in the above screen.

Click on Create

button to create the own Request number for saving the created Logical System.

Give the Short description as SAP Request for Receiving Logical System to Create Request and click on Save button as shown in the above screen to save the request number.

Click on

button as shown in the above screen.

After saving the request number, the above success message will appear on the status bar, which describes that the data was saved. Then click on Back button from standard tool bar.

From the above screen we can observe the created Logical system name in the marked area then click on Save button (optional) from standard tool bar.

After saving logical system, the above success message will appear on the status bar, which describes that the data was saved. Then click on Back button from standard tool bar.

 To assign Logical System LOG_SYS810 for Client 810 (Receiving System), Login to

Client - 810:

Click on Assign Logical System to Client, to assign created Logical System LOG_SYS810 to Client 810.

Double click on Client 810 to assign the logical system LOG_SYS810 to Client 810.

By default IDES-ALE Logical system name is assigned to Client 810. Then to proceed with the connection process of our requirement, we need to assign our logical system name. But it is strongly not recommended to change logical system name.

Assign our Logical System name LOG_SYS810 for Client 810 and click on Save tool bar.

button from standard

Click on Client 810.

button as shown in the above screen to save the assigned logical system LOG_SYS810 for

After saving the assignment of logical system, the above success message will appear on the status bar, which describes that the data was saved. Then click on Back button two times from standard tool bar.

 To Create RFC connections from Client 800 (Sending System) to Client 810

(Receiving System), Login to Client - 800:

Expand Communication as shown in the above screen and then click on Create RFC Connections, to create remote connection for Clients 800 and 810 in the distributed environment.

Select ABAP Connections and click on Create icon as shown in the above screen, to create Remote Connection between two Clients. That means from Client 800 (Sending System) to Client 810 (Receiving System).

Maintain the following field values on the respective screen fields of above screen:

RFC Destination Description 1

connection)

: connect from Client 800) :

LOG_SYS810 (The Logical System name, to which we are going to RFC Destination for 810 Client (Give the description of your RFC

Target Host:

going to connect)

192.168.1.249 (The IP address of Destination Server/Client, to which we are : 00 (The system number of Destination Client/Server)

System Number

Now click on Logon & Security tab button to enter the logon details of destination Client/Server.

Maintain the following Logon details of Client 810 on respective screen fields, to which we are going to connect as shown in the above screen: Client User Password 810 SAPUSER sap810 icon from standard tool bar.

After entering the Logon details, click on Save

Click on status bar.

button as shown in the above screen, then following success message will appear on the

The above message describes that the Destination connection from Client 800 to Client 810 was saved successfully.

Click on Connection Test push button from application tool bar, to check the RFC connection status of two Clients/Servers.

The above screen depicts the successful connection status between two Clients/Servers. Then click on Back button from standard tool bar.

Click on Remote Logon push button from application tool bar, to remotely login to Client 810 from Client 800.

From the above screen you can observe that we have successfully connected to Client 810 from Client 800.

 To Create RFC connections from Client 810 (Receiving System) to Client 800

(Sending System), Login to Client - 810:

Expand Communication as shown in the above screen and then click on Create RFC Connections, to create remote connection for Clients 810 and 800 in the distributed environment.

Select ABAP Connections and click on Create icon as shown in the above screen, to create Remote Connection between two Clients. That means from Client 810 (Receiving System) to Client 800 (Sending System).

Maintain the following field values on the respective screen fields of above screen:

RFC Destination Description 1

connection)

: connect from Client 800) :

LOG_SYS800 (The Logical System name, to which we are going to RFC Destination for 800 Client (Give the description of your RFC

Target Host:

going to connect)

192.168.1.249 (The IP address of Destination Server/Client, to which we are : 00 (The system number of Destination Client/Server)

System Number

Now click on Logon & Security tab button to enter the logon details of destination Client/Server.

Maintain the following Logon details of Client 810 on respective screen fields, to which we are going to connect as shown in the above screen: Client User Password 800 SAPUSER ecc123 icon from standard tool bar.

After entering the Logon details, click on Save

Click on status bar.

button as shown in the above screen, then following success message will appear on the

The above message describes that the Destination connection from Client 810 to Client 800 was saved successfully.

Click on Connection Test push button from application tool bar, to check the RFC connection status of two Clients/Servers.

The above screen depicts the successful connection status between two Clients/Servers. Then click on Back button from standard tool bar.

Click on Remote Logon push button from application tool bar, to remotely login to Client 800 from Client 810.

From the above screen you can observe that we have successfully connected to Client 800 from Client 810.

 To Create Distribution Model for Client 800 (Sending System), Login to Client -

800:

Enter the transaction Code BD64 in command filed, to maintain the Distribution Model then press Enter.

Customer Distribution Model: It identifies the systems (Remote Systems) and messages exchanged
in distributed environment. You can specify the relationships between Logical Systems, Message Types, BAPIs and Filters in the Distribution Model.

Click Display/Change model.

button from application tool bar, to go to the change view of Distribution

Click on Create Model View push button from application tool bar, to create Distribution Model.

Maintain the following field values on the respective screen fields of above screen:

Short Text Technical Name

: :

Distribution Model to send material Master Data MODELVIEW1

Then click on

button, to create distribution model with technical name MODELVIEW1.

Select the created distribution Model MODELVIEW1 and click on Add Message type push button from application tool bar, to create message type for the distribution model.

Press F4 function key or click on Search help button as shown in the above screen, to select the Logical systems, which are in the distributed environment.

Double click on our Sender name LOG_SYS800 as shown in the above screen.

Select the Receiver name LOG_SYS810 by press F4 on that filed and give the built-in Logical Message type MATMAS, which is used to transfer Material Master Data.

At the end of the screen, you can observe the created Distribution Model, The sending & Receiving Logical System Names and also the Message type, going to transfer between them. Now click on Save button from standard tool bar, to save the Distribution Model.

After saving the distribution model the above success message will appear on the status bar, which depicts that the distribution model has been saved.

To Create Ports for IDOC Processing in Client 800 (Sending System), Login to

Client - 800:

Enter the transaction code WE21 in the command field to deal with the Ports in IDOC processing and press Enter.

Port: It defines the medium in which communication IDOC (Application Data) is transffered to receiving
system.

Select Transactional RFC from left panel of Ports and then click on Create tool bar as shown in the above screen.

icon from application

Click on radio then click on

button Generate Port Name, then system will automatically generate the port number button as shown in the above screen.

From the above screen you can observe the automatically generated port number A000000059 by system. Maintain the following field values on the respective screen fields of above screen: Description RFC Destination are going to connect) Now click on Save : : Port to send Application Document LOG_SYS810 (Give the destination logical system name, to which we

button from standard tool bar, to save the port details.

After saving the port details, the above success message will appear on the status bar, which describes that the details regarding port was saved.