Ale Idoc

Overview of ALE /
EDI / IDOCs
02/06/17 Overview of ALE/IDOCs 1

EDI
What is EDI?
Type of EDI process
Outbound EDI Process
Inbound EDI Process

What is EDI?
EDI is electronic exchange of business documents
between the computer systems of business partner
using a standard format over a communication network
EDI is also called a paperless exchange.

Typical EDI/IDOC Scenario

Outbound Process
With Message Control
Directly -With out Message Control

Inbound Process
With Function Module

EDI Configuration
How to Set Up an RFC Destination in SAP
The Port Definitions
Configure Partner Profile
Configure Message Control

Complete EDI/ ALE scenario

ALE
What is ALE?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Transactions For Monitoring and Processing IDocs.
Questions

ALE Terminology
ALE - Application Linking & Enabling
IDoc - Intermediate Document
EDI - Electronic Data Interchange

ALE Objective

ALE!! What is it ??
It is a set of
Tools,
programs and
data definitions
Provides distribution model and technology

that enables SAP Customer to interconnect
programs across various platforms and
systems.
Features ALE / IDocs
Distributed System yet integrated with SAP R/3
Based on Application-to-Application integration using Message

Architecture
Reliable communication
Data is exchanged using IDocs
Support both R/2, R/3 and External system
If network problem, message is buffered
ALE support backward compatibility
ALE ensure that , data is transferred only once

ALE Scenario
Document
IDoc
SAP System R/3 SAP System R/3
IDoc IDoc
EDI Subsystem EDI Subsystem

Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Trouble Shooting
Questions

Components of ALE
Services:
Application Services
Distribution Services
Communication Services

Services:
This is where the SAP
applications ( SD, FI,
MM etc. ) generate
their data and
documents

Services:
Application Services Recipients
Distribution Services Formats and
Filters the data
Creates IDocs
( Intermediate
Documents

Services:
Communication Services TCP/IP
RFC
tRFC
etc

In a Nut Shell
Application Distribution/ALE Communication

Layer Layer Layer
Master
Application
Application IDOC Determine
Determine Filter/Convert
Filter/Convert Comm.
Receipients
Receipients Data,
Data, Create
Create IDOC
IDOC IDOC
Carrier
Carrier
Application
Data Application
Application Filter/Convert
Filter/Convert Comm.
Functions
Functions Data
Data IDOC

Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Trouble Shooting
Questions

IDoc Concept
System 1 System 2
SAP
Document
IDoc
R/3 System EDI subsystem

R/3 System
R/2 System
3rd party software

IDoc Structure
Control Record IDoc-ID
Sender-ID
Receiver-ID
IDoc type and logical message
External structure
Data Record IDoc-ID

Sequence/Hierarchy
Segment Format definition for
header data
item data
Status Record IDoc-ID

Status information

Control record
Data Record
Status Record
IDOC
Intermediate
Document

Control Record The very first record of an IDoc package is always
a control record. The
structure of this control record of the structure
EDIDC and describes the contents of the data
contained in the package. The control record goes to
table EDIDC

Message Type
Message Type indicates How to Know what the data Means
Data Exchanged by IDOC and EDI is known as Messages
Message of same kind belong to the same message type.
Message types are stored in table EDMSG

Data Record All records in the IDoc, which come after the
control record, are the IDoc data. They are all
structured alike, with a segment information part
and a data part, which is 1000 character in
length, filling the rest of the line. Data &
Segment info is stored in EDID4 for release 4.x
and EDID3 for release 2.x and 3.x.

Status Record Information about the IDoc status like:
IDoc identification number
Status number - table verified
IDoc type
Direction
Data and time stamp; Structure:
EDIDS

Status of IDOC
A two-digit status is assigned to an IDoc to allow the processing to
be monitored.
The statuses for outbound IDocs are between '01' and '49', while the
statuses for inbound IDocs begin with '50'.

Idoc Segments
TCODE:
WE31

Idoc Types
TCODE:
WE30

How to Attach Segments

Message Types
WE81
WE82

IDOC Type/ Message Type/ Processing Function
Module
Valid combination of Message type and IDOC type are stored in table
EDIMSG
Combination of message type and IDOC type determine the
processing algorithm. This is usually a function module and is set up in
table EDIFCT.

Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing.
i.Outbound Processing
ii.Inbound Processing

Trouble Shooting
Questions

Outbound Processing

Outbound processing: direct
Application ALE layer Comm. layer
posting
Need to Customer
create IDOC? Distribution Model
asynch. RFC
Create master or
M Receiver determination
IDOC EDI
System call FM
Segment filter
( INBOUND_
IDOC_
Field value conversion PROCESS )
Application document On destination
posted simultaneously Version change
with IDOCs
Dispatch
Links
C control C
Database

Dispatch control
Application ALE layer Comm. layer
posting
Need to Customer
create IDOC? Distribution Model
asynch. RFC
Create master or
M Receiver determination
IDOC EDI RFC
asynch.
- Technical comms parameters are
Segment filter defined or
- EDI or aRFCEDI
(asynch. remote
Field value conversion function call)
- Send immediately or cumulate
Application document
Version change and send via batch job
posted simultaneously
If batch, packet size is
with IDocs
determined
Dispatch
Links
C control C
Database

Scenario analysis
How does the IDOC look like ?
How is data being sent ?
How is the data being received ?

Outbound program development
Program logic
How is the IDOC being created ?
Triggering
How is the IDOC creation kicked off ?

Program logic
IDOC program
Select data from application tables
Fill data into IDOC
Pass IDOC to ALE layer
(Call function MASTER_IDOC_DISTRIBUTE)
Commit Work
MASTER_IDOC_DISTRIBUTE
Receiver determination
Segment filtering
Version Control
Dispatch Control
ALE layer

MASTER_IDOC_DISTRIBUTE
Call function MASTER_IDOC_DISTRIBUTE

Exporting
master_idoc_control: IDOC control record
Tables
communication_idoc_control: returned information
about the distribution
master_idoc_data: IDOC data segments

Filling an EDIDD structure
Header (55bytes) SDATA (1000bytes)
EDIDD . SEGNAM .
Field1 Field2 Field3 Field4

Z1SEG
10 ABC
MOVE Z1SEG to EDIDD-SEGNAM

MOVE 10 to Z1SEG-FIELD1
MOVE ABC to Z1SEG-FIELD2
MOVE Z1SEG to EDIDD-SDATA

General Programming rules
Design Guidelines for creating IDOC data records:
Left-justified filing of IDOC Fields
Replacing SAP codes with ISO codes

currency keys
country keys
unit of measure
shipping instructions
Converting Currency Amounts

Left-justified Filling
All fields must be left-justified
Character fields:
automatic
Non-character fields:
Condense statement must be used
Check IDOC documentation to find out which fields
require a condense
All types unequal to char, cuky, clnt, accp, numc,
dats, tims or unit require a condense

Code Conversions
Replacing SAP codes with ISO codes
Currency keys: currency_code_sap_to_iso
Country keys: country_code_sap_to_iso
Units of measure: unit_of_measure_sap_to_iso
Shipping instructions: sap_iso_package_type_code
Conversion of currency amounts

currency_amount_sap_to_iso

Basic Configuration Elements
Define RFC Destinations
Define Ports
Maintain Customer Model
Create Partner Profiles

Maintaining RFC Destinations
TCODE:
SM59

Displaying and Maintaining Ports
TCODE:
WE21
A port is a logical representation of a

communication channel in SAP with
the data communicated being IDocs.
IDocs

Partner Profiles
TCODE:
WE20

Partner Profiles-Inbound

Partner Profiles-Outbound

ALE For Transactional data ---- Output
Determination
NACE

Output Determination -- Output Types

Output Types -- Details

Inbound Processing

Inbound Processing.
Comm. layer ALE layer Application
posting
C
Version change
asynch. RFC Segment filter

or
EDI Field value conversion
Input
control A
A Serialization Process IDOC
Simultaneously update
IDOC's status
Post application
Database document

Input Control
posting
C
- For each message type and senderVersion change

one can define
asynch. RFCto process
when Segment filter
or(immediate/batch)
whether to call application Field value conversion
EDIdirectly or start customer
workflow
who should get work items in Input
case of error control A
- Incoming IDOC packets are passed to
application A Serialization Process IDOC
IDOC's status
Post application
Database document

Application Input
posting
C
Version change
asynch. RFC Segment filter

or
EDI Field value conversion
- Input
Inbound IDOCs are passed to
the application via a control A
standardized function
A Serialization Process IDOC
interface
IDOC's status
Post application
Database document

Serialization
posting
C
Version change
- When processing the Segment filter

asynch. RFC
inbound IDOC, the
or
application can call an ALE Field value conversion
EDI
API (function module) to
check that the IDOC has not
been overtaken Input
control A
If change No. 1 arrives
after change No. 2, the A Serialization Process IDOC
IDOC containing it has
been overtaken (by the
IDOC containing the IDOC's status
later change) Post application
Database document

FM Assignment to Message Type and
IDoc type
TCODE:
WE57

Process Codes
WE41
WE42

Process Codes in Inbound and Outbound
TCODE:
WE64

FM For Inbound EDI
TCODE:
BD67

Inbound Program Development
ALE configuration
INBOUND_IDOC_PROCESS Partner Profiles
IDOC Version change Process Code
Function module attribute
Segment filter Function module registry
Field conversion
Call function
IDOC_INPUT_<MSGTYPE>
Read IDOC data

Return Variables Post Application data
Send Success info back to ALE layer
If ERROR, trigger
Workflow Task
ALE layer

Basic Scenario
Direct Method
Call Transaction Method

Advanced Scenario
Mass processing
Serialization
Advanced Workflow

Flow Of Program
Read IDOC-Lock IDOC-Call Inbound Program-
Write Status-Commit Work-Unlock IDOC

Interface of Inbound FM
Importing Parameter
-Input Method
-Mass_processing
EXPORT parameter .
-Workflow_result
-Application_variable
-In_Update_task
-Call_transaction_done
Tables parameter :
IDOC_Control
IDOC_DATA
IDOC_STATUS
Return_variable

Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Questions

Monitoring IDocs
The IDoc interface offers 2 different approaches for tracking of data
load and data flow:
Reports for monitoring
Workflow for notifications
Both approaches are based on the concept of status transitions, i.e.
an IDoc changes its status from a given value to another value.

List Of All IDocs Created. (Default, Additional, EDI)-- WE02/
WE05

Selection Program For Issuing Output --
WE15

Test Tool For Idoc Processing (WE19)

Idoc Search For Business Contents
(Database). WE09

Questions

Ale Idoc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ale Idoc

Uploaded by

Copyright:

Available Formats

Overview of ALE /

02/06/17 Overview of ALE/IDOCs 1

02/06/17 Overview of ALE/IDOCs 2

02/06/17 Overview of ALE/IDOCs 3

02/06/17 Overview of ALE/IDOCs 4

02/06/17 Overview of ALE/IDOCs 5

02/06/17 Overview of ALE/IDOCs 6

02/06/17 Overview of ALE/IDOCs 7

02/06/17 Overview of ALE/IDOCs 8

02/06/17 Overview of ALE/IDOCs 9

IDoc - Intermediate Document

EDI - Electronic Data Interchange

02/06/17 Overview of ALE/IDOCs 10

02/06/17 Overview of ALE/IDOCs 11

Provides distribution model and technology

Based on Application-to-Application integration using Message

Data is exchanged using IDocs

Support both R/2, R/3 and External system

If network problem, message is buffered

ALE support backward compatibility

ALE ensure that , data is transferred only once

EDI Subsystem EDI Subsystem

02/06/17 Overview of ALE/IDOCs 14

02/06/17 Overview of ALE/IDOCs 15

02/06/17 Overview of ALE/IDOCs 16

02/06/17 Overview of ALE/IDOCs 17

02/06/17 Overview of ALE/IDOCs 18

02/06/17 Overview of ALE/IDOCs 19

Application Distribution/ALE Communication

02/06/17 Overview of ALE/IDOCs 20

02/06/17 Overview of ALE/IDOCs 21

R/3 System EDI subsystem

02/06/17 Overview of ALE/IDOCs 22

Data Record IDoc-ID

Status Record IDoc-ID

02/06/17 Overview of ALE/IDOCs 23

02/06/17 Overview of ALE/IDOCs 24

02/06/17 Overview of ALE/IDOCs 25

02/06/17 Overview of ALE/IDOCs 26

02/06/17 Overview of ALE/IDOCs 27

02/06/17 Overview of ALE/IDOCs 28

02/06/17 Overview of ALE/IDOCs 29

02/06/17 Overview of ALE/IDOCs 30

02/06/17 Overview of ALE/IDOCs 31

02/06/17 Overview of ALE/IDOCs 32

02/06/17 Overview of ALE/IDOCs 33

02/06/17 Overview of ALE/IDOCs 34

Transactions For Monitoring and Processing IDocs.

02/06/17 Overview of ALE/IDOCs 35

02/06/17 Overview of ALE/IDOCs 36

02/06/17 Overview of ALE/IDOCs 37

02/06/17 Overview of ALE/IDOCs 38

How does the IDOC look like ?

How is data being sent ?

How is the data being received ?

02/06/17 Overview of ALE/IDOCs 39

02/06/17 Overview of ALE/IDOCs 40

02/06/17 Overview of ALE/IDOCs 41

Call function MASTER_IDOC_DISTRIBUTE

02/06/17 Overview of ALE/IDOCs 42

Field1 Field2 Field3 Field4

MOVE Z1SEG to EDIDD-SEGNAM

02/06/17 Overview of ALE/IDOCs 43