Ale Idoc

Overview of ALE / EDI / IDOCs
10/30/2013
Overview of ALE/IDOCs
EDI
What is EDI? Type of EDI process

Outbound EDI Process Inbound EDI Process
10/30/2013
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.
10/30/2013
Typical EDI/IDOC Scenario
10/30/2013
Outbound Process

With Message Control Directly -With out Message Control
10/30/2013
Inbound Process
With Function Module
10/30/2013
EDI Configuration
How to Set Up an RFC Destination in SAP The Port Definitions Configure Partner Profile Configure Message Control
10/30/2013
Complete EDI/ ALE scenario
10/30/2013
ALE
What is ALE? Components of ALE. Anatomy of an IDoc. ALE Processing Transactions For Monitoring and Processing IDocs. Questions
10/30/2013
ALE Terminology
ALE - Application Linking & Enabling IDoc - Intermediate Document EDI - Electronic Data Interchange
10/30/2013
10
ALE Objective
10/30/2013
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.
10/30/2013
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
ALE
10/30/2013
support backward compatibility

ensure that , data is transferred only once
Overview of ALE/IDOCs 13
ALE Scenario
Document
SAP System R/3

IDoc
IDoc
SAP System R/3

IDoc
EDI Subsystem
EDI Subsystem
14
10/30/2013
Topics to cover
What is ALE ? Components of ALE. Anatomy of an IDoc. ALE Processing Transactions For Monitoring and Processing IDocs. Trouble Shooting Questions
10/30/2013
15
Components of ALE
Services:
Application Services Distribution Services Communication Services
10/30/2013
16
Application Services
Services: Application Services Distribution Services Communication Services
This is where the SAP applications ( SD, FI, MM etc. ) generate their data and documents
10/30/2013
17
Distribution Services
Recipients Formats and Filters the data Creates IDocs ( Intermediate Documents
10/30/2013
18
Communication Services
TCP/IP RFC
tRFC
etc
10/30/2013
19
In a Nut Shell
Application Layer
Master IDOC
Distribution/ ALE Layer
Communication Layer
Application
Determine Receipients
Filter/Convert Data, Create IDOC
Comm. IDOC
Carrier
Application Data
Application Functions
Filter/Convert Data
Comm. IDOC
10/30/2013
20
Topics to cover
What is ALE ? Components of ALE. Anatomy of an IDoc. ALE Processing Transactions For Monitoring and Processing IDocs. Trouble Shooting Questions
10/30/2013
21
IDoc Concept
System 1
SAP Document
System 2 IDoc
R/3 System
EDI subsystem R/3 System R/2 System 3rd party software

22
10/30/2013
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
10/30/2013
23
Control record Data Record Status Record
IDOC Intermediate Document
10/30/2013
24
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
10/30/2013
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
10/30/2013
26
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.
10/30/2013
27
Status Record
Information about the IDoc status like: IDoc identification number Status number - table verified IDoc type Direction Data and time stamp; Structure: EDIDS
10/30/2013
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'.
10/30/2013
29
Idoc Segments
TCODE: WE31
10/30/2013
30
Idoc Types
TCODE: WE30
10/30/2013
31
How to Attach Segments
10/30/2013
32
Message Types
WE81
WE82
10/30/2013
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.
10/30/2013
34
Topics to cover
What is ALE ? Components of ALE. Anatomy of an IDoc. ALE Processing.
i.Outbound Processing ii.Inbound Processing
Transactions For Monitoring and Processing IDocs. Trouble Shooting Questions
10/30/2013
35
Outbound Processing
10/30/2013
36
Outbound processing: direct

Application posting
Need to create IDOC?
ALE layer Customer Distribution Model
Comm. layer
Create master IDOC
Receiver determination Segment filter Field value conversion
asynch. RFC or EDI

System call FM ( INBOUND_ IDOC_ PROCESS ) On destination
Application document posted simultaneously with IDOCs Database
Version change Dispatch control
Links
10/30/2013
37
Dispatch control
Application posting
Need to create IDOC?
ALE layer Customer Distribution Model
Comm. layer
Create master IDOC
Receiver determination
-
Segment filter
-
asynch. RFC or EDI RFC asynch. Technical comms parameters are or defined EDI EDI or aRFC (asynch. remote
function call) Send immediately or cumulate and send via batch job If batch, packet size is determined
Field value conversion Application document posted simultaneously with IDocs Database
-
Version change Dispatch control
Links
10/30/2013
38
Scenario analysis
How does the IDOC look like ?
How is data being sent ? How is the data being received ?
10/30/2013
39
Outbound program development
Program logic How is the IDOC being created ?

Triggering How is the IDOC creation kicked off ?
10/30/2013
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 Receiver determination Segment filtering Version Control Dispatch Control ALE layer
10/30/2013
41
MASTER_IDOC_DISTRIBUTE
Call function MASTER_IDOC_DISTRIBUTE
Exporting
master_idoc_control:
IDOC control record
Tables
communication_idoc_control:
master_idoc_data:
returned information about the distribution

IDOC data segments
10/30/2013
42
Filling an EDIDD structure

EDIDD
Header (55bytes) . SEGNAM . SDATA (1000bytes)
Z1SEG
Field1 10
Field2 ABC
Field3
Field4
MOVE Z1SEG to EDIDD-SEGNAM MOVE 10 to Z1SEG-FIELD1 MOVE ABC to Z1SEG-FIELD2 MOVE Z1SEG to EDIDD-SDATA
10/30/2013
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
10/30/2013
44
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
10/30/2013
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
10/30/2013
46
Basic Configuration Elements

Define RFC Destinations Define Ports Maintain Customer Model Create Partner Profiles
10/30/2013
47
Maintaining RFC Destinations

TCODE:
SM59
10/30/2013
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.
10/30/2013
49
Partner Profiles
TCODE: WE20
10/30/2013
50
Partner Profiles-Inbound
10/30/2013
51
Partner Profiles-Outbound
10/30/2013
52
ALE For Transactional data ---- Output Determination
NACE
10/30/2013
53
Output Determination -- Output Types
10/30/2013
54
Output Types -- Details
10/30/2013
55
Inbound Processing
10/30/2013
56
Inbound Processing.
Comm. layer C
Version change
ALE layer
Application posting
asynch. RFC or EDI
Segment filter Field value conversion Input control
A
Process IDOC
Serialization
Simultaneously update IDOC's status
Database
Post application document
10/30/2013
57
Input Control
Comm. layer C
Version change For each message type and sender one can define Segment filter when to process asynch. RFC (immediate/batch) or whether to call application Field value conversion EDI directly or start customer workflow Input who should get work items in control case of error Incoming IDOC packets are passed to A application Serialization
-
ALE layer
Application posting
A
Process IDOC
Database
10/30/2013
58
Application Input
Comm. layer C
Version change
ALE layer
Application posting
asynch. RFC or EDI

-
Segment filter Field value conversion Input Inbound IDOCs are passed to control the application via a standardized function A Serialization interface
A
Process IDOC
Database
10/30/2013
59
Serialization
Comm. layer C
Version change Segment filter asynch. RFC inbound IDOC, the or application can call an ALE Field value conversion EDI(function module) to API 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
-
ALE layer
Application posting
When processing the
A
Process IDOC
Serialization
Database
10/30/2013
60
FM Assignment to Message Type and IDoc type
TCODE: WE57
10/30/2013
61
Process Codes
WE41
WE42
10/30/2013
62
Process Codes in Inbound and Outbound
TCODE: WE64
10/30/2013
63
FM For Inbound EDI
TCODE: BD67
10/30/2013
64
Inbound Program Development

INBOUND_IDOC_PROCESS IDOC ALE configuration
Partner Profiles Process Code Function module attribute Function module registry
Version change Segment filter Field conversion

Call function
IDOC_INPUT_<MSGTYPE> Return Variables

Read IDOC data Post Application data Send Success info back to ALE layer
If ERROR, trigger Workflow Task ALE layer
10/30/2013
65
Basic Scenario
Direct Method Call Transaction Method
10/30/2013
66
Advanced Scenario
Mass processing Serialization Advanced Workflow
10/30/2013
67
Flow Of Program
Read IDOC-Lock IDOC-Call Inbound ProgramWrite Status-Commit Work-Unlock IDOC
10/30/2013
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
10/30/2013
69
Topics to cover
What is ALE ? Components of ALE. Anatomy of an IDoc. ALE Processing Transactions For Monitoring and Processing IDocs. Questions
10/30/2013
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.
10/30/2013
71
List Of All IDocs Created. (Default, Additional, EDI)-WE02/ WE05
10/30/2013
72
Selection Program For Issuing Output -WE15
10/30/2013
73
Test Tool For Idoc Processing (WE19)
10/30/2013
74
Idoc Search For Business Contents (Database). WE09
10/30/2013
75
Questions
10/30/2013
76

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 / EDI / IDOCs

What is EDI? Type of EDI process

Typical EDI/IDOC Scenario

With Message Control Directly -With out Message Control

With Function Module

Complete EDI/ ALE scenario

Features ALE / IDocs

Distributed System yet integrated with SAP R/3

Based on Application-to-Application integration using Message Architecture

support backward compatibility

SAP System R/3

SAP System R/3

Distribution/ ALE Layer

Filter/Convert Data, Create IDOC

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

IDoc-ID Sequence/Hierarchy Format definition for Segment

IDoc-ID Status information

Control record Data Record Status Record

IDOC Intermediate Document

How to Attach Segments

IDOC Type/ Message Type/ Processing Function Module

Transactions For Monitoring and Processing IDocs. Trouble Shooting Questions

Outbound processing: direct

ALE layer Customer Distribution Model

Create master IDOC

Receiver determination Segment filter Field value conversion

asynch. RFC or EDI

Application document posted simultaneously with IDOCs Database

Version change Dispatch control

ALE layer Customer Distribution Model

Create master IDOC

Version change Dispatch control

Outbound program development

Program logic How is the IDOC being created ?

IDOC control record

returned information about the distribution

Filling an EDIDD structure

General Programming rules

Replacing SAP codes with ISO codes

Converting Currency Amounts

Conversion of currency amounts

Basic Configuration Elements

Maintaining RFC Destinations

Displaying and Maintaining Ports

ALE For Transactional data ---- Output Determination

Output Determination -- Output Types

Output Types -- Details

asynch. RFC or EDI

Segment filter Field value conversion Input control

Simultaneously update IDOC's status

Post application document

Simultaneously update IDOC's status

Post application document

asynch. RFC or EDI

Simultaneously update IDOC's status

Post application document

When processing the

Simultaneously update IDOC's status

Post application document

FM Assignment to Message Type and IDoc type

Process Codes in Inbound and Outbound

FM For Inbound EDI

Inbound Program Development