Ale Idoc Edi

IBM Global Services
Overview of ALE / IDOCs

March, 2006
Copyright IBM Corporation 2006
IBM Global Services
Topics to cover
What is ALE?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Transactions For Monitoring and Processing IDocs.
Questions
IBM Global Services
ALE Terminology
ALE - Application Linking & Enabling
IDoc - Intermediate Document
EDI - Electronic Data Interchange
IBM Global Services
ALE Objective
IBM Global Services
ALE!! What is it ??
It is a set of
Tools,
programs and
data definitions
that provides the mechanism for

distributing functionality and data across
multiple system.
IBM Global Services
What Data can be Exchanged ?
Transaction
Data
SD, MM, FI, CO, etc.
Master
Data
Material, Customer, Vendor, etc.
Control
Data
Organizational Reference Information
Plants, Sales Orgs, etc.
Data
required to enable tightly coupled,

distributed applications
Separate HR, Separate Treasury, etc.
IBM Global Services
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
IBM Global Services
ALE Scenario
Document
SAP System R/3

IDoc
EDI Subsystem
IDoc
SAP System R/3

IDoc
EDI Subsystem
IBM Global Services
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Trouble Shooting
Questions
IBM Global Services
Components of ALE
Services:
Application Services
Distribution Services
Communication Services
Tools:
Customizing Tools
Development Tools
IBM Global Services
Services:
Tools:
This is where the SAP

applications ( SD, FI,
MM etc. ) generate
their data and
documents
Customizing Tools
Development Tools
IBM Global Services
Services:
Tools:
Customizing Tools
Development Tools
Recipients
Formats and
Filters the data
Creates IDocs
( Intermediate
Documents
IBM Global Services
Services:
TCP/IP
RFC
Tools:
Customizing Tools
Development Tools
tRFC
etc
IBM Global Services
Development Tools
Services:
Model Maintenance Tool.
(for configuring the flow of data

between systems )
Shared Master Data(SMD)tools
(for distributing master data )
Customization parameters
(within SAP for IDoc

conversion.
filtering and
Tools:
Customizing Tools
Development Tools
IBM Global Services
Customizing Tools
Services:
Tools:
Customizing Tools
Development Tools
Tools for creating

and modifying
IDocs
IBM Global Services
In a Nut Shell
Application
Layer
Application
Application
Master
IDOC
Distribution/ALE
Layer
Determine
Determine
Receipients
Receipients
Filter/Convert
Filter/Convert
Data,
Data, Create
Create IDOC
IDOC
Communication
Layer
Comm.
IDOC
Carrier
Carrier
Application
Data
Application
Application
Functions
Functions
Filter/Convert
Filter/Convert
Data
Data
Comm.
IDOC
IBM Global Services
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Trouble Shooting
Questions
IBM Global Services
IDoc Concept
System 1
SAP
Document
R/3 System
System 2
IDoc
EDI subsystem
R/3 System
R/2 System
3rd party software
IBM Global Services
IDoc Structure
Control Record
IDoc-ID
Sender-ID
Receiver-ID
IDoc type and logical message
External structure
Data Record
IDoc-ID
Sequence/Hierarchy
Format definition for
Segment
header data
item data
Status Record
IDoc-ID
Status information
IBM Global Services
Control record
Data Record
Status Record
IDOC
Intermediate
Document
IBM Global Services
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
IBM Global Services
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
IBM Global Services
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.
IBM Global Services
Status Record
Information about the IDoc status like:

IDoc identification number
Status number - table verified
IDoc type
Direction
Data and time stamp; Structure:
EDIDS
IBM Global Services
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'.
Status confirmation when using port type 'File':
The external system writes the status records in a status file, which is
read by the R/3 System. In this case, the confirmation always refers to
outbound IDocs.
Status confirmation using IDoc type SYSTAT01:
The system sending the confirmation writes the status records as data
records of IDoc type SYSTAT01. All port types and both directions can
be entered.
IBM Global Services
Idoc Segments
TCODE:
WE31
IBM Global Services
Idoc Types
TCODE:
WE30
IBM Global Services
How to Attach Segments
IBM Global Services
Message Types
WE81
WE82
IBM Global Services
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.
IBM Global Services
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing.
i.Outbound Processing
ii.Inbound Processing

Trouble Shooting
Questions
IBM Global Services
Outbound Processing
IBM Global Services
Outbound processing: direct

Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
asynch. RFC
or
EDI
Receiver determination
Segment filter
Field value conversion
Application document
posted simultaneously
with IDOCs
Database
Version change
Links
Dispatch
control
IBM Global Services
Querying the Model

Application
posting
ALE layer
Need to
create IDOC?
Customer
ALE
supplies APIs (function modules) to
Distribution
Model to query the model
allow applications
-
Is anybody interested in my message type?

Optional: what filter objects are theyasynch.
interested in?
or
Create master
IDOC
Comm. layer
Comm. layer
RFC
EDI RFC
asynch.
or
EDI
Segment filter
with IDocs
Database
Version change
Links
Dispatch
control
IBM Global Services
Handover IDoc to ALE

Application
posting
ALE layer
Need to
create IDOC?
Comm. layer
Customer
Distribution
Model creates the IDOC
- The application
Technically it is stored as an
internal table
- Passed
Receiver
determination
to ALE via an API
(function module)
Segment filter
-
Create master
IDOC
asynch. RFC
or
EDI

with IDocs
Database
Version change
Links
Dispatch
control
IBM Global Services
Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
Segment filter
with IDocs
Database
If the application has no specified

recipients asynch. RFC
ALE refers to the customer
or
distribution model to determine
EDI RFC
them asynch.
Data not relevant
or to receiver
(according toEDI
model) is removed
in ALE layer.
Version change
Links
Dispatch
control
IBM Global Services
Segment filter
Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
-
Segment filter
asynch. RFC
The filter is data-independent

or
IDOC segments that are not
EDI
RFC
required asynch.
can be
removed
or
The filter is message
and receiverspecific
EDI

with IDocs
Database
Version change
Links
Dispatch
control
IBM Global Services

Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
-
Segment filter
with IDocs
Database
asynch. RFC
The contents of individual

or
fields can be
EDI RFC
asynch.
translated
to new values
or
suppressed
EDI
The filter is message and
receiver-specific
Version change
Links
Dispatch
control
IBM Global Services
Version change
Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Comm. layer
Customer
Distribution Model
Segment filter

with IDocs
Database
Version change
Links
Dispatch
control
asynch. RFC
or
EDI RFCto older
asynch.
IDOCs can
be changed
versions
or
Systems with different
release
EDI
levels can communicate
without additional application
logic
IBM Global Services
Make Links
Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
asynch. RFC
or
EDI
Segment filter
Links are written between IDOC

and
Application object contained
in IDOC
Communication-Layer's
Dispatch
"Transaction-ID"
control
C

with IDocs
Database
Version change
Links
IBM Global Services
Dispatch control
Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
-
Segment filter
-

with IDocs
Database
Version change
Links
Dispatch
control
asynch. RFC
or
EDI RFC
asynch.
Technical comms parameters are
or
defined
EDI or aRFCEDI
(asynch. remote
function call)
Send immediately or cumulate
and send via batch job
If batch, packet size is
determined
IBM Global Services
Scenario analysis
How does the IDOC look like ?

How is data being sent ?
How is the data being received ?
IBM Global Services
Outbound program development
Program logic
How is the IDOC being created ?
Triggering
How is the IDOC creation kicked off ?
IBM Global Services
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
Segment filtering
Version Control
Dispatch Control
ALE layer
IBM Global Services
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
IBM Global Services
Filling an EDIDD structure
EDIDD
Z1SEG
Header (55bytes)
. SEGNAM .
Field1
Field2
10
ABC
SDATA (1000bytes)
Field3
Field4
MOVE Z1SEG to EDIDD-SEGNAM

MOVE 10 to Z1SEG-FIELD1
MOVE ABC to Z1SEG-FIELD2
MOVE Z1SEG to EDIDD-SDATA
IBM Global Services
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
IBM Global Services
Left-justified Filling
All fields must be left-justified
Character fields:
automatic
Non-character fields:
Condense statement must be used
All types unequal to char, cuky, clnt, accp, numc,

dats, tims or unit require a condense
Check IDOC documentation to find out which fields

require a condense
IBM Global Services
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
IBM Global Services
Basic Configuration Elements
Create and allocate Logical System

Define Ranges (Idocs, Ports, etc )
Define RFC Destinations
Define Ports
Maintain Customer Model
Create Partner Profiles
IBM Global Services
Logical System
TCODE:
BD54; Stored in
table T000
IBM Global Services
Allocate Logical System to the client
TCODE:
SCC4
SALE > BASIC SETTINGS > SET UP

LOGICAL SYSTEM > ASSIGN LOGICAL
SYSTEM TO THE CLIENT
IBM Global Services
Number Ranges
Maintain number ranges for ports
Maintain number ranges for IDocs

Maintain number ranges for IDoc types and segment version
Maintain number range for change pointers
IBM Global Services
Maintaining RFC Destinations
TCODE:
SM59
IBM Global Services
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
IBM Global Services
Partner Profiles
TCODE:
WE20
IBM Global Services
Partner Profiles-Outbound
IBM Global Services
Partner Profiles-Inbound
IBM Global Services
Distribution Model
TCODE:
BD64
IBM Global Services
Transfer of data
Transfer master data for material, customer, vendor to different client or
system with BALE
IBM Global Services
Filter Objects
BD95
BD59
IBM Global Services
Sending Master Data Idocs

Master
data ?
Y
Only send
objects that have
changed ?
Standalone program
with user-definable
selection criteria
Y
Change
Pointer
available?
Standalone with
custom logic to keep
track of changes
y
Change Pointer
based Program
IBM Global Services
Sending Transactional Data Idocs
Transaction
Data ?
Y
Ensure transactional
Integrity?
N
See Master data
Y
Output
Determinat
ion
available ?
y
Output determination
based Program
User-Exit
available?
hard coded ALE

layer
Modification
Y
Hardcoded ALE layer
no Modification
IBM Global Services
Change Pointers
Application Posting
Post Application document
Batch Program
Master data
Determine IDOC module

Call IDOC module
Create Change Document

Are changes ALE relevant ?
Write Change Pointers
Commit Work
(RBDMIDOC)
ALE configuration
ALE relevant Fields
IDOC Module
(Masteridoc_Create_
SMD_<MSGTYPE>)
Change pointers
Read Change Pointers

Fill IDOC
Call ALE layer
Update Change Pointer
ALE layer
Master_IDOC_DISTRIBUTE
IBM Global Services
Change Pointers
BD61
BD50
IBM Global Services
Change Pointers Continued
BD52
BD60
IBM Global Services
IDOC module
IDOC module has to be implemented as function module
Naming Convention: MASTERIDOC_CREATE_SMD_<msgtype>
Function module reads change pointers information to get data that
needs to go into IDOC
Function module logic:
Read change pointers
Fill IDOC structure
Call ALE layer
Update Change Pointer status
Commit Work
IBM Global Services
ALE Configuration For Change Pointers
Define change pointer creation
Define which change document fields are to be logged
Change pointer activation
Activate generally
Activate per message type
Publish new function module

Link message type to function module
IBM Global Services
ALE For Transactional data ---- Output Determination
NACE
IBM Global Services
Output Determination -- Access Sequence
IBM Global Services
Output Determination -- Output Types
IBM Global Services
Output Types -- Details
IBM Global Services
Output Types -- Partner Functions
IBM Global Services
Output Types -- Processing Routines
IBM Global Services
Output Types -- Procedures
IBM Global Services
Output Types -- Procedures Control
IBM Global Services
Output Types -- Condition records
IBM Global Services
Inbound Processing
IBM Global Services
Inbound Processing.
Comm. layer
ALE layer
Application
posting
C
Version change
asynch. RFC
or
EDI
Segment filter
Input
control
Serialization
A
Process IDOC
Simultaneously update
IDOC's status
Database
Post application
document
IBM Global Services
Input Control
Comm. layer
ALE layer
Application
posting
C
Version change
For each message type and sender
one can define
Segment filter
when
asynch.
RFCto process
or(immediate/batch)
whether to call application Field value conversion
EDIdirectly or start customer
workflow
Input
who should get work items in
control
case of error
Incoming IDOC packets are passed to
A
application
Serialization
-
A
Process IDOC
IDOC's status
Database
Post application
document
IBM Global Services
Application Input
Comm. layer
ALE layer
Application
posting
C
Version change
Segment filter
asynch. RFC
or
EDI

-
Input
Inbound IDOCs are passed
to
control
the application via a
standardized function
A
Serialization
interface
A
Process IDOC
IDOC's status
Database
Post application
document
IBM Global Services
Serialization
Comm. layer
ALE layer
Application
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
If change No. 1 arrives
after change No. 2, the
IDOC containing it has
been overtaken (by the
IDOC containing the
later change)
Input
control
Serialization
A
Process IDOC
IDOC's status
Database
Post application
document
IBM Global Services
FM Assignment to Message Type and IDoc type
TCODE:
WE57
IBM Global Services
Process Codes
WE41
WE42
IBM Global Services
Process Codes in Inbound and Outbound
TCODE:
WE64
IBM Global Services
FM For Inbound EDI
TCODE:
BD67
IBM Global Services
Inbound Program Development

INBOUND_IDOC_PROCESS
IDOC
Version change
Segment filter
Field conversion
Call function
Return Variables
ALE configuration
Partner Profiles
Process Code
Function module attribute
Function module registry
IDOC_INPUT_<MSGTYPE>
Read IDOC data
Post Application data
Send Success info back to ALE layer
If ERROR, trigger
Workflow Task
ALE layer
IBM Global Services
ALE error handling

User action
R/3 action
Error in inbound function module

ALE triggers error event
input Error Occurred
Workitem appears in user's Inbox

Execute Workitem
Display IDoc for user processing
(IDoc method "InputForeground")
Fix error and reprocess IDoc
or
Flag IDoc for deletion
ALE triggers end event
input Finished
Workitem completed
IBM Global Services
ALE error handling
Necessary Steps:
Create new object type in Business Object Repository for IDOC;

object is child of IDOCAPPL
Create new customer task
Create event-couplings linking
Event inputFinished to function module
To support mass processing:
Event inputErrorOccured linked to standard task
Create new object type as child of IDOCPACKET
Maintain process code to refer the above objects and events
IBM Global Services
Advanced Inbound Topics
Data consistency
Serialization
Individual vs. mass processing
Call transaction function modules
IBM Global Services
Data Consistency
Problem:
Ensure transactional integrity
Dont process and IDOC twice
Allow for IDOC reprocessing after rollback of
application document posting
Solution:
Application document must be posted in the same
LUW as the IDOC status records
IDOC function module must not use a Commit Work
IBM Global Services
Data Consistency
ALE Layer
Application
function module
Lock IDoc(s)
Read IDoc(s)
Lock application objects
Optional: Serialization check
Process IDoc data
Write application data to DB
Write IDoc(s) status
Write links
Optional:
Write serialization data
Trigger event(s)
Commit Work
Unlock IDoc(s) and

application objects
IBM Global Services
Serialization
Sender
Object X,
changed twice:
Comm. Layer
First IDOC
overtaken
Receiver
Input from IDOC 1

must be prevented
in order not to lose
information from
IDOC 2
2
1
!?
!?
IBM Global Services
Serialization
Check, if IDOC has been overtaken
Use function module IDOC_SERIALIZATION_CHECK
react to overtaken IDOCs according to your needs
Prerequisite is the definition of a serialization

object
IBM Global Services
Mass Processing
Processing more than one IDOC can improve
throughput:
more than one IDOC is processed per Commit Work
the function can be coded to add multiple entries to a table

with one update command (array insert)
Function module has to be coded in a way that it

supports mass processing
Attribute of delivered function module specifies if
mass processing is supported or not
IBM Global Services
Call Transaction
Pros:
Error reprocessing in foreground
Easy to program
Cons:
Call Transaction has significant performance overhead
Automatic Commit work, no data consistency
Recommendation:
Try to use function modules that update database directly
If you want to use Call transaction, they have been ALEenabled to guarantee data concistency
IBM Global Services
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Questions
IBM Global Services
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.
IBM Global Services
List Of All IDocs Created. (Default, Additional, EDI)-- WE02/ WE05
IBM Global Services
Selection Program For Issuing Output -- WE15
IBM Global Services
Process All Selected IDocs. WE14
IBM Global Services
Test Tool For Idoc Processing (WE19)
IBM Global Services
Select IDocs BD87
IBM Global Services
Idoc Search For Business Contents (Database). WE09
IBM Global Services
Status Conversion With Trfc Execution. BD75
IBM Global Services
Questions
IBM Global Services

Ale Idoc Edi

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 Edi

Uploaded by

Copyright:

Available Formats

IBM Global Services

Overview of ALE / IDOCs

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

that provides the mechanism for

Copyright IBM Corporation 2006

IBM Global Services

What Data can be Exchanged ?

required to enable tightly coupled,

Copyright IBM Corporation 2006

IBM Global Services

Features ALE / IDocs

Distributed System yet integrated with SAP R/3

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

Copyright IBM Corporation 2006

IBM Global Services

SAP System R/3

SAP System R/3

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

This is where the SAP

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Model Maintenance Tool.

(for configuring the flow of data

(for distributing master data )

(within SAP for IDoc

Copyright IBM Corporation 2006

IBM Global Services

Tools for creating

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006

IBM Global Services

Copyright IBM Corporation 2006