Click to edit Master title style

IDoc (intermediate
document)

1
Click
What to edit Master title style
is IDOC:

• IDoc (intermediate document) is a standard data

structure used in SAP applications to transfer data to
and from SAP system applications and external
systems.
• The transfer between SAP systems is done through
SAP's Application Link Enabling (ALE) system, while
the transfer from an SAP system to an external system
happens through electronic data interchange (EDI).

2 2
Click
IDOCto edit Master title style
Applications:

Several SAP applications use the robust IDOC interface. Idocs serve the basic purpose of transferring
data from one application to another:

EDI Integration.

ALE integration

Legacy system integration.

Third-party product integration

Workflow Integration.

SAP R/2 integration.

Internet Integration
3 3
Click
IDOCtoApplications:
edit Master title style

EDI Integration

EDI is electronic exchange of business documents between the SAP and NON-SAP systems. Several
applications (purchasing, sales or shipping) in SAP are enabled for EDI.

For transmission of information electronically, two widely used standards are ANSI ASC X12 and
EDIFACT.

ALE integration

Application Link Enabling enables the exchange of data between the SAP systems. It allows SAP
business processes and applications to be distributed across multiple SAP systems. ALE ensures
integration in a distributed SAP environment.

4 4
Click to edit Master title style
Process:

Here we have 2 types of flows in SAP, where data will be flowed into SAP
and other is data transfer out from SAP .
Inbound: When the data is coming in, the process is called Inbound
process and the IDOC is called as Inbound IDoc. Direction key 2, Idoc
status from 50 to75
Outbound: Sending out data from SAP system. The IDOC which is called
Outbound IDOC, Direction key 1, Idoc status from 1 to 49.

5 5
Click to edit Master title style
ALE components

Logical system

Message type

Idoc type & Idoc

Segment type

RFC Destination

Ports

Partner profile

Process codes

Distribution Model
6 6
Click to edit Master title style
ALE components

Logical system
A logical system (LS) is the representation of a R/3 or External system in SAP R/3 for the distribution
of data to and from the R/3 system.
The systems Involved in distributed processing are assigned a logical name, which uniquely identifies a
system in a distributed environment.
The name can have up to 10 alphanumeric characters.
T-code used is BD54 or through SALE.
Message Type
A message type represents the application message exchanged between R/3 systems and R/3 and an
external system. A message type characterizes the data sent across systems and relates to the structure
of the data called an IDOC type.
T code used to view or create message type is WE81.
7
Example : MATMAS – Material master, DEBMAS – Customer master, CREMAS – Vendor master7
Click to edit Master title style
ALE components

Idoc type & Idoc

An Idoc type represents the structure of the data associated with a message type (DEBMAS02 for
message type DEBMAS) while an Idoc is an object containing the data of a particular message type.

T code for IDOC type is WE20

Every Idoc is identified by a 16-digit unique number.

An Idoc structure consists of 3 parts.

1.The administration part(Control Record - EDIDC)- which has the type of idoc, message type, the current
status, sender, receiver etc.
2.The application data (Data Record - EDIDD) – Which contains the data. These are called the data
records/segments.
3.The Status information (Status Record - EDIDS)- These give you information about the various stages the
idoc has passed through.
8 8
You can view an I-DOC using transaction WE02 or WE05
Click to edit Master title style
ALE components
Segment

A segment defines the format and structure of a data record.

Collection of data fields filled with alphanumeric characters.

Non character value must convert to alphanumeric characters.

Fields are aligned left.

Currencies, countries and units of measure must be named in ISO-codes.

The complete data in a segment can have a maximum length of 1000 bytes.

Standard segment type starts with E1, custom-defined segment types begin with Z1.
If a IDOC segment contains its own segments, it is called as Parent segment.

T Code to view or create segment is WE31. 9 9

Click to edit Master title style
ALE components
RFC Destination
Remote function call (RFC) is the standard SAP interface for communication between SAP systems.
RFC destination is a logical name used to define the characteristic of a communication link to a remote
system on which a function needs to be executed.
The parameters of the connection are mentioned in the form of a Destination.
Destination defined the type of connection, the partner program, and the target system.
T code used for configuration is SM59.
Port
A port defines the medium in which data is exchanged between the 2 systems
T code used for configuration is WE21.
tRFC port used for ALE communication, File port used by EDI, Internet ports to connect with internet
applications 1010
Click to edit Master title style
ALE components
Partner profile
A partner profile specifies the Characteristics of data that you exchange with a business partner.
In ALE, a partner is a remote SAP system or legacy system with which you exchange data.
T code used for configuration is WE20.
In EDI, a partner can be a customer, vendor, or any entity with your company does business.
Partner profile of type (LS) is used for ALE communications.
Process code
Process codes are used in ALE and EDI to identify the function modules to be invoked for subsequent
processing.
Inbound interface uses a process code to determine the application module that will process the
Inbound IDOC, stored in table TEDE1.
Distribution Model
Models a distributed environment in which one specifies various messages exchanged between the
sending & receiving systems. 1111

T code used for configuration is BD64.

Click to edit Master title style
ALE Configuration

Define Logical system – BD54.

Assign Logical system to clients – SCC4.

Create RFC Destination – SM59.

Define Port Definition – WE21.

Create Partner Profile – WE20.

Maintain Distribution Model – BD64.

1212
Click to edit Master title style
Test Case
As part of testing, we are sending a material master from 100 client to 800 in EH8
system.
We created below for testing.
1) Logical system 100 : EH8CLNT100
2) Logical system 800 : EH8CLNT800
3) RFC Destination : EH8CLNT800
4) tRFC port : A000000020
5) Model view : MATERIAL
6) Partner profile : EH8CLNT800 & EH8CLNT100
Using standard message type (MATMAS), Extension Idoc type.
Using T code BD10 to generate Material Master IDOC. 1313
Click to edit Master title style

Thank You

14