ALE - IDoC

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 88

Uplatz 1

➢ ALE (Application Link Enabling)


➢ EDI (Electronic Data Interchange)
➢ IDoc (Intermediate Document)
Select Statements of Open SQL

© SAP AG
ALE / EDI / IDOC

Production planning

PP Material management

MM
ALE / EDI / IDOC

HR SD
FI
Human Resource
Sales and Distribution
Finance And Control
ALE / EDI / IDOC

ALE

➢ ALE ( Application Link Enabling ) is


SAP ‘ s technology to support distributed yet
integrated process across several SAP systems .
ALE / EDI / IDOC

➢ Introduction to the Distributed Process

➢ A distributed process is one in which part of a


business process is carried out on one system and part
on another.
ALE / EDI / IDOC

EDI

➢ EDI (Electronic Data Interchange), is the electronic exchange


of structured business data between different applications.
ALE / EDI / IDOC
ALE / EDI / IDOC

EDI Architecture consists of -

➢ EDI-enabled applications :They support the automatic


processing of business transactions.

➢ The IDoc interface: This was designed as an open interface. The


IDoc interface consists of IDoc types and function modules that form
the interface to the application.

➢ The EDI subsystem: This converts the IDoc types into EDI
message types and vice versa. This component of the EDI
architecture is not supplied by SAP.
ALE / EDI / IDOC

Advantages of EDI process

▪ Reduced data Entry Errors


▪ Reduced Processing cycle time
▪ Availability of data electronic form
▪ Reduced Paper Work
▪ Reduced Cost
▪ Reduced Inventories and Better Planning
▪ Standard Means of Communicating
▪ Better Business Processes
▪ Competitive Advantage
ALE / EDI / IDOC

Difference between ALE and EDI ?

ALE is SAP’s technology for supporting a distributed environment


whereas EDI is a process used for exchange of business documents
which now have been given a standard format
ALE / EDI / IDOC

IDOC ( 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.

➢ 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.
ALE / EDI / IDOC

IDOC ( Intermediate Document )

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

➢ IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT.

➢ IDOCs are independent of the sending and receiving systems.


(SAP-to-SAP as well as Non-SAP)
ALE / EDI / IDOC

STRUCTURE OF IDOC

IDOC ( Intermediate Document )

Status Records Data Records Control Record


ALE / EDI / IDOC
IDOC ( Intermediate Document )

➢ Status Records :- With one IDoc many status records are


created , Status Record indicates what is the status of an IDoc, For
example Document sent ,Document Received , Document cant be sent
and many more .

➢ Data Records:- With one IDoc many Data Records are Created.
Data Records are the data of any application which has to be sent from
one system to another system.

➢ Control Record :- With one IDoc only one control Record is


created ,Control Record give information about user name, User details,
sever details , Partner system, port number, System date , time and
many more information
ALE / EDI / IDOC

Message control :-

➢ Message control is a cross-application technology. It


is used in pricing , account determination , material
determination , output determination and many more
information.

➢ Message control component enables you to


encapsulate business rules without having to write ABAP
/ 4 programs.
ALE / EDI / IDOC

 Segments :-

➢ A Segment defines the format and structure of


a data record. Segments are reusable components,
which means they can be used in more than one
IDoc type.

➢ A segment consists of various fields that represent


data in a record.
ALE / EDI / IDOC

 Segment is separated by 3 pieces :-

➢ Segment type.
➢ Segment definition.
➢ Segment documentation.
ALE / EDI / IDOC

IDOC
Data Records contains fallowing segments:-

Data Records Message type :- Specifies information of Business


Details like Person Details, Person Address Details ,
Person Family Details
Message type
IDoc Type:- Specifies order in which the Segment
IDoc type types has to be considered.

Segment Type:- Specifies table and table fields


Segment type to be included.

Table Fields Table Fields:- Specifies Fields of Particular Table


ALE / EDI / IDOC

ALE Benefits in Distributed environment.

➢ Integration with Non-SAP Systems .


➢ Reliable Distribution.
➢ Release Upgrade.
➢ Autonomy.
ALE / EDI / IDOC

Benefits of EDI

➢ Reduced data entry errors.


➢ Reduced processing cycle time.
➢ Availability of data in electronic form.
➢ Reduced paperwork.
➢ Reduced cost.
ALE / EDI / IDOC

Benefits of EDI

➢ Better planning.
➢ Standard means of communication.
➢ Better business process.
➢ Competitive Advantage.
ALE / EDI / IDOC

Message control :-

➢ Message control is a cross-application


technology. It is used in pricing , account
determination , material determination and
output determination .

➢ Message control component enables you to


encapsulate business rules without having to
write ABAP / 4 programs.
ALE / EDI / IDOC

Segments :-

 A Segment defines the format and structure of a


data record. Segments are reusable components,
which means they can be used in more than one IDoc
type.

➢ A segment consists of various fields that represent


data in a record.
ALE / EDI / IDOC

Segment is separated by :-

➢ Segment type.
➢ Segment definition.
➢ Segment documentation.
ALE / EDI / IDOC

Data exchanged through ALE .

➢ Transactional data.
➢ Master Data .
➢ Control Data.
ALE / EDI / IDOC

Transactional Data :-

Transitional data represents day-to-


day business transaction carried out in the
system, Such as purchase orders, sales orders and
invoices.
ALE / EDI / IDOC

Master data :--

➢ Master data is required to support the


creation and interpretation of transactional data
across the systems. Example of master data
include vendor master , customer master , material
master data .

➢ Master data does not change frequently .


ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
ALE / EDI / IDOC
Example Program
ALE / EDI / IDOC
Example Program
ALE / EDI / IDOC
Example Program
ALE / EDI / IDOC
ALE / EDI / IDOC

Transaction Code to View IDocs : -


➢ WE05
➢ WE07
➢ WE02
ALE / EDI / IDOC

Frequent Transaction Code Used in ALE : -


➢ SALE
➢ SM59
➢ WE21
➢ WE20
➢ BD64
➢ PFAL
➢ WE81
➢ WE82
➢ WE31
➢ WE30
➢ BD60
88
Thank You
Upla
tz

You might also like