Ale Idoc

Overview of ALE /
EDI / IDOCs
09/16/15
Overview of ALE/IDOCs
EDI
What is EDI?
Type of EDI process
Outbound EDI Process
Inbound EDI Process
09/16/15
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.
09/16/15
Typical EDI/IDOC Scenario
09/16/15
Outbound Process
With Message Control

Directly -With out Message Control
09/16/15
Inbound Process
With Function Module
09/16/15
EDI Configuration
How to Set Up an RFC Destination in SAP

The Port Definitions
Configure Partner Profile
Configure Message Control
09/16/15
Complete EDI/ ALE scenario
09/16/15
ALE
What is ALE?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Transactions For Monitoring and Processing IDocs.
Questions
09/16/15
ALE Terminology
ALE - Application Linking & Enabling
IDoc - Intermediate Document
EDI - Electronic Data Interchange
09/16/15
10
ALE Objective
09/16/15
11
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.
09/16/15
12
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
09/16/15
13
ALE Scenario
Document
SAP System R/3
IDoc
IDoc
IDoc
EDI Subsystem
09/16/15
SAP System R/3
EDI Subsystem
14
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Trouble Shooting
Questions
09/16/15
15
Components of ALE
Services:
Application Services
Distribution Services
Communication Services
09/16/15
16
Services:
09/16/15
This is where the SAP

applications ( SD, FI,
MM etc. ) generate
their data and
documents
17
Services:
09/16/15
Recipients
Formats and
Filters the data
Creates IDocs
( Intermediate
Documents
18
Services:
TCP/IP
RFC
tRFC
etc
09/16/15
19
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
09/16/15
Application
Application
Functions
Functions
Filter/Convert
Filter/Convert
Data
Data
Comm.
IDOC
20
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Trouble Shooting
Questions
09/16/15
21
IDoc Concept
System 1
SAP
Document
R/3 System
09/16/15
System 2
IDoc
EDI subsystem
R/3 System
R/2 System
3rd party software
22
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
09/16/15
IDoc-ID
Status information
23
Control record
Data Record
Status Record
IDOC
Intermediate
Document
09/16/15
24
Control Record
09/16/15
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
25
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
09/16/15
26
Data Record
09/16/15
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.
27
Status Record
09/16/15
Information about the IDoc status like:

IDoc identification number
Status number - table verified
IDoc type
Direction
Data and time stamp; Structure:
EDIDS
28
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'.
09/16/15
29
Idoc Segments
TCODE:
WE31
09/16/15
30
Idoc Types
TCODE:
WE30
09/16/15
31
How to Attach Segments
09/16/15
32
Message Types
WE81
09/16/15
WE82
33
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.
09/16/15
34
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing.
i.Outbound Processing
ii.Inbound Processing

Trouble Shooting
Questions
09/16/15
35
Outbound Processing
09/16/15
36
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
System call FM
( INBOUND_
IDOC_
PROCESS )
On destination
Segment filter
Field value conversion
Application document
posted simultaneously
with IDOCs
Database
09/16/15
Version change
Links
Dispatch
control
37
Dispatch control
Application
posting
ALE layer
Need to
create IDOC?
Create master
IDOC
Comm. layer
Customer
Distribution Model
-
Segment filter
-

Application document
posted simultaneously
with IDocs
Database
09/16/15
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
38
Scenario analysis
How does the IDOC look like ?
How is data being sent ?
How is the data being received ?
09/16/15
39
Outbound program development
Program logic
How is the IDOC being created ?
Triggering
How is the IDOC creation kicked off ?
09/16/15
40
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
09/16/15
ALE layer
41
MASTER_IDOC_DISTRIBUTE
Call function MASTER_IDOC_DISTRIBUTE
Exporting
09/16/15
master_idoc_control:
IDOC control record
Tables
communication_idoc_control:
returned information
about the distribution
master_idoc_data:
IDOC data segments
42
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
09/16/15
43
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
09/16/15
44
Left-justified Filling
All fields must be left-justified
Character fields:
09/16/15
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
45
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
09/16/15
46
Basic Configuration Elements
09/16/15
Define RFC Destinations

Define Ports
Maintain Customer Model
Create Partner Profiles
47
Maintaining RFC Destinations

TCODE:
SM59
09/16/15
48
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
09/16/15
49
Partner Profiles
TCODE:
WE20
09/16/15
50
Partner Profiles-Inbound
09/16/15
51
Partner Profiles-Outbound
09/16/15
52
ALE For Transactional data ---- Output

Determination
NACE
09/16/15
53
Output Determination -- Output Types
09/16/15
54
Output Types -- Details
09/16/15
55
Inbound Processing
09/16/15
56
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
09/16/15
Post application
document
57
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
09/16/15
Post application
document
58
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
09/16/15
Post application
document
59
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)
09/16/15
Input
control
Serialization
A
Process IDOC
IDOC's status
Database
Post application
document
60
FM Assignment to Message Type and

IDoc type
TCODE:
WE57
09/16/15
61
Process Codes
WE41
09/16/15
WE42
62
Process Codes in Inbound and Outbound
TCODE:
WE64
09/16/15
63
FM For Inbound EDI
TCODE:
BD67
09/16/15
64
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
09/16/15
65
Basic Scenario
Direct Method
Call Transaction Method
09/16/15
66
Advanced Scenario
Mass processing
Serialization
Advanced Workflow
09/16/15
67
Flow Of Program
Read IDOC-Lock IDOC-Call Inbound ProgramWrite Status-Commit Work-Unlock IDOC
09/16/15
68
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
09/16/15
69
Topics to cover
What is ALE ?
Components of ALE.
Anatomy of an IDoc.
ALE Processing
Questions
09/16/15
70
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.
09/16/15
71
List Of All IDocs Created. (Default, Additional, EDI)-- WE02/

WE05
09/16/15
72
Selection Program For Issuing Output -WE15
09/16/15
73
Test Tool For Idoc Processing (WE19)
09/16/15
74
Idoc Search For Business Contents

(Database). WE09
09/16/15
75
Questions
09/16/15
76

Ale Idoc

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Ale Idoc

Transféré par

Droits d'auteur :

Formats disponibles

Overview of ALE /

EDI is electronic exchange of business documents

Typical EDI/IDOC Scenario

With Message Control

With Function Module

How to Set Up an RFC Destination in SAP

Complete EDI/ ALE scenario

Provides distribution model and technology

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

SAP System R/3

SAP System R/3

This is where the SAP

The very first record of an IDoc package is always

All records in the IDoc, which come after the

Information about the IDoc status like:

How to Attach Segments

IDOC Type/ Message Type/ Processing Function

Transactions For Monitoring and Processing IDocs.

Outbound processing: direct

Field value conversion

Outbound program development

IDOC control record

IDOC data segments

Filling an EDIDD structure

MOVE Z1SEG to EDIDD-SEGNAM

General Programming rules

Replacing SAP codes with ISO codes

Converting Currency Amounts

Condense statement must be used

All types unequal to char, cuky, clnt, accp, numc,

Check IDOC documentation to find out which fields

Conversion of currency amounts

Basic Configuration Elements

Define RFC Destinations

Maintaining RFC Destinations

Displaying and Maintaining Ports

A port is a logical representation of a

ALE For Transactional data ---- Output

Output Determination -- Output Types

Output Types -- Details

Field value conversion

When processing the

FM Assignment to Message Type and

Process Codes in Inbound and Outbound

FM For Inbound EDI

Inbound Program Development

Read IDOC-Lock IDOC-Call Inbound ProgramWrite Status-Commit Work-Unlock IDOC

Both approaches are based on the concept of status transitions, i.e.

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

Selection Program For Issuing Output -WE15

Test Tool For Idoc Processing (WE19)

Idoc Search For Business Contents

Vous aimerez peut-être aussi