Scribd
Upload
70 views4 pages

Cross Aplications - Abap

This document discusses cross-application data exchange in SAP systems using ALE (Application Linking Enablement) and IDOCs (Intermediate Documents). It explains that IDOCs are used to carry data between systems in a format that SAP can understand. It describes the basic components and structure of an IDOC, including control records, data records, status records, and status codes. It also mentions two types of IDOCs: standard and custom.

Uploaded by

Aamrnadh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
70 views4 pages

Cross Aplications - Abap

This document discusses cross-application data exchange in SAP systems using ALE (Application Linking Enablement) and IDOCs (Intermediate Documents). It explains that IDOCs are used to carry data between systems in a format that SAP can understand. It describes the basic components and structure of an IDOC, including control records, data records, status records, and status codes. It also mentions two types of IDOCs: standard and custom.

Uploaded by

Aamrnadh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

CROSS APLICATIONS

Cross application is used to exchange the data among the distribution systems.
ALE (Application linking unit) is an SAP technology to support cross applications.
ALE uses IDOC, to support cross applications.
IDOC INTERMIDATE DOCUMENT
IDOC is the carrier to carry the data from one system to another system.
SAP can understand only IDOC format, when it communicates with other systems.
How the data distributing the data: receivers, senders.

Middleware converts / Translators.


XI EXCHANGE INFRASTRUCTURE
PI PROCESS INTEGRATION

Irrespective of the receivers, the ABAPER job in sender system is to generate the
IDOC.
The process of idoc is nothing but outbound process.
Irrespective of the senders, the ABAPER job is receiver system is to collect the data
from the IDOC.
The process collecting the data from idoc is nothing but in bound process.
RUN TIME COMPONENTS OF IDOC

It generates a unique idoc number, which is 16 digits.


It generates 3 types of records.
1. Control records
2. Data Records
3. Status Records.

1. Control Record :
Control record specifies the sender as well as receiver information.
It generates only one control record
This information will be saved EDIDC table.
2. Data Record:
It specifies the data which is send by the senders system.
It generates any number of records.
This information will be saved in EDIDD table.
3. Status Record:
It generates status codes for each and every stage of transferring the data.
It generates the any number of status records.
This information will be saved in EDIDS table.
Two types of status code
i)
Out bound status codes (0 49 )
ii)
Inbound status codes (50 75)
Out bound success 03
Out bound failure 29
In bound success 53
In bound failure 51
The link between EDIDC, EDIDD, &EDIDS is the IDOC number.

Type of IDOCs
They are two types of IDOCS.
1. BASIC IDOC TYPE
i)
Standard IDOC
ii)
Custom IDOC.

You might also like