ALE and IDOCs

Introduction to EDI and ALE:

EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the
computer systems of business partners, using a standard format over a communication network.

ALE: (ALE means application linking and enabling). ALE is the tool which will help to transfer the data from one SAP to
another SAP system.

ALE is a tool which will help to transfer the data from one SAP to non SAP system or non SAP system to SAP systems.
Here we required translators.

The translators are:

 PI- Process integration [Latest]

 XI- Exchange of information

 BOOMI

IDOC: (Intermediate document)

 IDOC is a data carrier which is help to carry the data from one system to another system.

 IDOC is a container that can be used to exchange data between any two processes.

 Each IDOC is assigned a unique number for tracking and future reference.

EDI: (Electronic Data Inter change)

 EDI is the tool which will help to transfer the data from SAP to non SAP system or non SAP to SAP system.
Here also we required translators.

Advantages of ALE:

 Reduce Data entry errors

 Reduced processing time
 Availability of data in electronic form
 Reduced paperwork
 Reduced Cost
 Reduced inventories and better planning
 Standard means of communications
 Better business process
Consultant role in ALE IDOCS:
 Consultant has to monitor the IDOC’S i.e. weather the IDOC is transferring successfully or not.
 If data is not successfully transfer then we have to analyse the error and rectify the error and retransfer
the data.
 The common T-code for ALE IDOC & EDI is - WEDI
Structure of IDOC: The IDOC will be classified into 3 types of records. Those are:
 Control record
 Data record
 Status record
CONTROL RECORD:
  Control record consists of sender information (Port information), Receiver information (RFC information),
partner information and medium information.
DATA RECORD:
 Data record consists of actual data which we are transferring from one system to another system.
STATUS RECORD:
 Status record consists of IDOC status information i.e. weather the IDOC is success or fail.
Message numbers:
 Outbound side messages are 0-49 (from which system you sending the data)
 Inbound side messages are 50 above (from which system you receive the data)
Common message numbers:
 03- Success at outbound side.
 27-29 failed at outbound side.
 53- success at inbound
 51- failed at inbound

Track the IDOC:

 We come to know whether the IDOC is success or fail based on message numbers. T-CODE’s are:
o WE02
o WE05
o WE07
o WE09
Track the IDOC T-Code is same for both inbound and outbound side.
 The direction for Outbound is 1
 The direction for Inbound is 2
EDI has two processes:
1. Outbound process
2. Inbound process

Outbound Process Inbound Process

Application document is created. EDI transmission received

IDOC is generated EDI document is converted into an IDOC

IDOC is transferred from SAP to Operating system layer IDOC is transferred to the SAP layer

IDOC is converted into EDI standards The application document is created

Edi document is transmitted to the business partner The application document can be viewed.

The Edi Subsystem report status to SAP

 The T-code to Retransfer the data is - BD87

 The T-code to retransfer the data with different IDOC number is - WE19
o While Retransfer the data if you want to change some information then we use this.
IDOC Message types:

 Customer master DEBMAS

 Vendor master CREMAS

 Material master MATMAS

 Orders (PO-SO) ORDRSP

 Deliveries DESADV

 Invoice INVOIC

 BOM BOMMAS

IDOC type is of 2 types. Those are:

1. BASIC IDOC TYPE [STANDARD]

2. EXTENDED IDOC TYPE [ENHANCEMENT]

Consultant role in EXTENDED IDOC is: we need to MAP the fields in EXCELL file and send this excel file information to
ABAPER. In excel file we mention the field name, length and description.

T-CODES for transfer the data:

 CUSTOMER MASTER BD12

 MATERIAL MASTER BD10

 VENDOR MASTER BD14