The Idoc Interface: R/3 Release

The IDoc Interface
Overview
R/3 Release
 SAP AG 1999 IDocEnjoy (Th. Becker) / 1

Introduction/Expectations
 Name
 Expectations from this class
 Any prior experience in ALE/IDOC or other

Interface technologies

Course Objectives
Course Objectives
After completing this course, you will be able to:
 Understand the concept of distributed and it’s pros & cons
 SAP Interface technologies and scenarios
 IDOC and it’s structure
 Detailed overview on ALE/EDI concepts and technology
 Perform simple master data distribution using ALE scenario

Agenda
Agenda
Day 1 – IDOC overview

Distributed Architecture
Business scenarios
IDOC and it’s structures
Interfacing scenarios – Outbound / Inbound

Distributed Applications
One central system is not

always optimal for unifying
business processes with
integrated applications
Org HQ Central Ref

Plant
Sales Center
Distribution Center
2
Why distribute Applications ?
 Technical bottlenecks
 Too much time required for a group-wide implementation of R/3
central systems
 Influences on the market
 Company units become independent
 Optimization of cross-company business processes
 Integrated information exchange across system frontiers
 Profiting from a high degree of freedom in a homogeneous
system environment
 Comprehensible step by step implementation of complex SAP
R/3 projects
3
What is Distributed?
 Master Data
 Control/Customizing Data
 Transaction Data
 Statistical Data (Infosystem)
Master Data
Control Data
(Customizing)
9
Electronic Commerce
Document
IDoc
SAP System R/3 SAP System R/3
IDoc IDoc
Transaction
EDI Subsystem Message EDI Subsystem

EDI Standards in the World
EANCOM
GENCOD
EDIFICE TRADACOMS
EIAJ UCS II, WINS
SEDAS
EDIFER
12
X T
EDIFICE
ELFE
AC
IF
HL7 E D CEFIC
PHOENIX
ARUA
GALIA EANCOM
ODETTE GENCOD
VDA TRADACOMS
UCS II, WINS
SEDAS
BAI, BAI2
ATA SPEC2000 MultiCash
AECMA SPEC2000M S.W.I.F.T.
HBCI
IDOC

Intermediate Document (IDOC)
Why Intermediate Documents ?
 Messages must have a defined structure
 Easy technical handling ( "Data Container" )

 Easy transfer from/to non-SAP systems
 Possibility to build complex data structures
 Possibility for extension
 Possibility for documentation
 Link to standard processing ( EDI )

Intermediate Document (IDOC)
 The key concepts of IDoc (i.e. Intermediate Document) are:

 communication is asynchronous and
 related to one document, i.e. transaction.
 Following these concepts IDoc facilitates distributed processes rather simply

invoking functions.
 IDoc is the SAP standard interface to link application systems via messaging.
Whereas one system is asumed to be SAP system R/3, the other system
could be
 EDI subsystem,
 system R/3,
 system R/2 or
 any third-party application software.
 IDoc is available for system R/3 from release 2.1A on.

 IDoc is available for system R/2 from release 5.0F on.

IDoc Concept
 Asynchronous
 Document-related
System 1 System 2
SAP  Document
Document
IDoc  Transaction
 Message
 R/3 System  EDI subsystem

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

IDOC Structure

IDoc Record Types
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

IDoc Types
Control Record
Data Records
E1HDDOC E1TLSUM
M 1 C 1
E1HDADR E1ITDOC
C 5 M 1
E1ITSCH
Tree of Segments C 99 C 5
Status Records

IDOC Type – MATMAS03

IDoc Data Flow
Outbound Data Inbound
MM
Application SD
Application
...
Message Control Workflow
IDoc Interface & IDoc IDoc Interface &

ALE Services ALE Services
System 2 File System 2

e.g. EDI subsystem tRFC e.g. EDI subsystem
XML
...

Outbound Data Flow
SAP Application
Document
Message Control (NAST)

Document
NAST
Record
IDoc Interface & ALE Services
IDoc
System 2, e.g. EDI subsystem

IDoc View Concept
 An IDoc view is a selection of segments of a given IDoc

type and is compatible with the IDoc type‘s syntax.
 IDoc views are applied in outbound processing of
selected applications.
 Advantages of views:
 Enhancing the performance by restricting the number of
tables read
 Reducing the data volume in internal tables at run time

ALE (Application Link Enabling)
The method and technique for supporting

distributed applications.
ALE enables integrated configurations, in which
applications are loosely coupled, i.e. asynchronously
and not via a common database.
ALE Infrastructure encompasses:

 Message-based Architecture
 Business Scenarios
 Communication Technology
 Tools
 Methodology
4
ALE Objectives
 Integration of distributed applications  Scenarios:

 Consistency and synchronization of distributed data
with respect to available database technology
 Support for the configuration of distributed
 R/3 and R/3
applications
 SAP and
non-SAP systems
 Support for different
application releases
5
ALE Technique
 Using the EDI functionality

 Using IDOCs to define the data to be distributed
 Using aRFC, TCP/IP, EDI subsystem
 Using workflow functions for error handling
 Integration into message control (condition technique)
 Integration into the application
 Integration into customizing
6
Messaging with ALE
BLAORD-
BLAOCH
HEAD QUARTERS
BLAREL •Financials
EKSEKS •Central purchasing
•Purchasing Info. system
FIDCMT
FIROLL
BLAOR Blanket order/changes

BLAREL Release statistics
EKSEKS Purchasing information
PRODUCTION FIDCMT A/C recivable
•Local purchasing, Invoice verification FIROLL G/L rollup
7
Communication between Applications
 ALE handles the communication between business applications, not the

applications processes themselves
 ALE focuses on business requirements, not on technical solutions
8
The Distribution Model
 The model tells the applications which messages are to be sent to which
partner systems.
 SAP supplies a distribution reference model, the documents that may be
distributed
 From the reference model the customer distribution model is derived. This
model defines what will be distributed
 The customer distribution model is created in one R/3 system and distributed
from there to the other systems
 The model directly controls distribution
10
Distribution Reference Model
Filter
Object type Material
Material Div
Div BusArea
BusArea Plant
Plant
Application Inventory
Inventory Inventory
Inventory
type
Controlling
Controlling Management
Management
Function analyse
type change stock
stock change
Message
type INVCON
INVCON
11
Customer Distribution Model
Folsom, CA Tsukuba, Japan
Inventory
Inventory Inventory
Inventory
Control
Control Control
Control
01 1000
Div
Div BusArea
BusArea
KU OR
INVCON INVCON CH
INVCON
Inventory
Inventory Inventory
Inventory Inventory
Inventory
Management
Management Management
Management Management
Management
12
Scenarios supported by ALE
 Distribution of accounting and logistics

 Reallocation between distributed systems
 Seperate sales and shipping
 Purchasing: distributed contacts
 Profitability analysis
 Sales and Operations Planning
 Logistics Information systems
 Warehouse management
 Master data distribution
 Control data distribution
16
ALE Features Summary
 Provides for input and Output Processing

 Provides for Communication Control Mechanism
 Helps Achieve a Virtual View of a Multi-Client Corporation/Enterprise
 Provides Reference Models
 Requires a Completed Detailed Enterprise Design
 Business Segments
 Geographical Area
 Business Function
 Based on Distribution Model
37
Message Handling: Output 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
Segment filter
Field value conversion

Application document
posted simultaneously Version change
with IDOCs
Dispatch
Links
C control C
Database

Input processing
Comm. layer ALE layer Application

posting
C
Version change
asynch. RFC Segment filter

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

Cross-system application links
Sending system Plant 1 Receiving system CRS
ALE layer Application

Application ALE layer
posting
4711 9876
IDOC C IDOC
1234 5678
Source CRS Resultant

Link to application
application appl. doc. 9876
document, Receiver: CRS document
No. 4711 No. 9876
Plant1
Link to CRS Link to Plant1 IDOC: Link to Plant1
1234
appl. doc. 9876 appl. doc. 4711 appl. doc. 4711

Message Control
SAP Application Processing
Application data
Output Determination Message proposal

NAST-Record
Processing acc/ TNAPR
Processing Program Output, e.g. as IDoc

e.g. RSNASTED

Message Control - Call Sequence
SAP Applications
communication message
structures default
pass suggest
condition
element evaluate output relation
condition determination
tables write
message trigger and message status

process status
Message table
Control TNAPR
call
formatting program
... printout fax ALE EDI E-mail ...

Message Control - EDI related
Check NAST-Reord R
S
Read Partner Profile
N
A
Call Selection Module
S
(application) T
E
Call ALE Service D
Transfer according
to output mode
Single IDoc Batch of IDocs

by RSEOUT00

Outbound Status Transitions
42
01 37 39 24 04
29
06 05
26
08 07
25
10 09
30
40 41 12 11
03 02
22
18 20
14 15
16 17
31

Inbound Data Flow
System 2, e.g. EDI subsystem
IDoc
IDoc +
Process
SAP Business Workflow IDoc +

Function Module
Document
SAP Application

Inbound Status Transitions
74
50 56
65
Notifications
60 from the
61 EDI subsystem
prior to
64 IDoc creation,
can be received via
66
message TXTRAW.
62 63
52 51
53 68

Process Code, Port and Partner Profile
SAP Application
Process Partner
Port
Code Profile
System 2
e.g. EDI subsystem

Partner Profile
General
Partner
Recipient of notifications
Outbound Inbound
Partner Partner
Logical message Logical message
Port Process code
IDoc type Recipient of notifications
EDI structure
NAST-Key
Recipient of notifications
Partner
Message
Process code
Logical message

Port Types of the IDoc Interface
SAP Application
IDoc & IDoc &

IDoc IDoc IDoc IDoc
status status
File
tRFC CPI-C MIME ABAP XML
+ RFC
EDI ALE EC
R/2 Internet Any
Any Any Any
2.1 on 3.1 on 4.5 on 4.6 on
3.0 on 3.0 on

Triggering with Port Type „File“
IDoc Interface
Write RFC 4 3
1 2 Read RFC
rfcexec startrfc
IDoc file
IDoc file in.script
Status report
out.script status.script
Read Call 1 2
4 3 Write Call
EDI subsystem

Port Type „ABAP“
IDoc Interface
IDOC_INBOUND_ASYNCHRONOUS
Own_function Own_program
?
Port Type „XML“
 The port type XML is

available in release 4.6A.
 The port type
 creates files with data in IDoc/XML format (rendering)
 processes files with data in IDoc/XML format (parsing)
 For documentation of the format and validation by XML parsers
document type definition (DTD) is available for each IDoc type.
DTDs are available by IDoc type documentation, transaction
WE60.
 Measurements for EDI supply-chain messages compared with
port type file
 XML file is 1.5 to 2 times smaller
 XML file inbound to IDoc database is about 10 times slower
 Communication, e.g. via http, is not yet available.

Port Type „XML“, ORDERS (Header)
<?xml version = "1.0"?> <ORDERS01> <IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM><![CDATA[EDI_DC40]]></TABNAM>
<MANDT>004</MANDT> <DOCNUM>0000000000307013</DOCNUM> <DOCREL>46B</DOCREL>
<STATUS>30</STATUS> <DIRECT>1</DIRECT> <OUTMOD>3</OUTMOD> <IDOCTYP>ORDERS01</IDOCTYP>
<MESTYP>ORDERS</MESTYP> <STD>X</STD> <STDVRS>3/70</STDVRS> <STDMES>850</STDMES>
<SNDPOR>SAPQ99</SNDPOR> <SNDPRT>LS</SNDPRT> <SNDPRN>Q99CLNT004</SNDPRN>
<RCVPOR>WTBXML</RCVPOR> <RCVPRT>LI</RCVPRT> <RCVPFC>LF</RCVPFC> <RCVPRN>WTBLIEF</RCVPRN>
<CREDAT>19990622</CREDAT> <CRETIM>074519</CRETIM> <SERIAL>19990622074509</SERIAL> </EDI_DC40>
<E1EDK01 SEGMENT="1">
<CURCY>DEM</CURCY> <WKURS>1.00000</WKURS> <ZTERM>0001</ZTERM>
<BSART>NB</BSART> <BELNR>4500000328</BELNR> <RECIPNT_NO>WTBLIEF</RECIPNT_NO> </E1EDK01>
<QUALF>014</QUALF> <ORGID>0001</ORGID> </E1EDK14>
<QUALF>013</QUALF> <ORGID>NB</ORGID> </E1EDK14>
<IDDAT>012</IDDAT> <DATUM>19990622</DATUM> </E1EDK03>
<IDDAT>011</IDDAT> <DATUM>19990622</DATUM> </E1EDK03>
<E1EDKA1 SEGMENT="1">
<PARVW>AG</PARVW> <PARTN>WTBKUND</PARTN> <TELF1>06227/341285</TELF1>
<BNAME>Einkaeufer 1</BNAME>
<PAORG>0001</PAORG> <ORGTX>Einkaufsorg. 0001</ORGTX> <PAGRU>001</PAGRU> </E1EDKA1>
<PARVW>LF</PARVW> <PARTN>WTBLIEF</PARTN> </E1EDKA1>
<PARVW>WE</PARVW> <LIFNR>0001</LIFNR> <NAME1>Werk 0001</NAME1> <NAME2>Walldorf</NAME2>
<STRAS>Neurottstrasse 16</STRAS> <ORT01>Walldorf</ORT01> <PSTLZ>69190</PSTLZ>
<LAND1>DE</LAND1> </E1EDKA1>
<QUALF>001</QUALF> <BELNR>4500000328</BELNR>
<DATUM>19990622</DATUM> <UZEIT>074509</UZEIT> </E1EDK02>
 SAP AG<QUALF>001</QUALF> <LKOND>CFR</LKOND>
1999 IDocEnjoy (Th. Becker) / 48 <LKTEXT>Kosten und Fracht</LKTEXT> </E1EDK17>
Port Type „XML“, ORDERS (Item 10)
<E1EDP01 SEGMENT="1">
<POSEX>00010</POSEX> <ACTION>001</ACTION> <PSTYP>0</PSTYP>
<MENGE>7.000</MENGE> <MENEE>PCE</MENEE> <BMNG2>7.000</BMNG2>
<PMENE>PCE</PMENE> <VPREI>17.77</VPREI> <PEINH>1</PEINH> <NETWR>124.39</NETWR>
<NTGEW>5.53</NTGEW> <GEWEI>KGM</GEWEI>
<MATKL>004</MATKL> <BPUMN>1</BPUMN> <BPUMZ>1</BPUMZ>
<WMENG>7.000</WMENG> <EDATU>19990622</EDATU> </E1EDP20>
<QUALF>002</QUALF> <IDTNR>WTBMATERIAL</IDTNR> </E1EDP19>
<QUALF>001</QUALF> <IDTNR>WTBMATERIAL</IDTNR>
<KTEXT>Testmaterial Thomas Becker</KTEXT> </E1EDP19>
<QUALF>001</QUALF> <LKOND>CFR</LKOND>
<LKTEXT>Kosten und Fracht</LKTEXT> <LPRIO>00</LPRIO> </E1EDP17>
<E1EDPT1 SEGMENT="1">
<TDID>BEST</TDID> <TSSPRAS>D</TSSPRAS> <TSSPRAS_ISO>DE</TSSPRAS_ISO>
<TDLINE>Dies ist der Einkaufsbestelltext</TDLINE> </E1EDPT2>
<TDLINE>Ein schoenes deutsches Wort.</TDLINE> </E1EDPT2>
</E1EDPT1>
</E1EDP01>

Port Type „XML“, ORDERS (Item 20 + Trailer)
<POSEX>00020</POSEX> <ACTION>001</ACTION> <PSTYP>0</PSTYP>
<MENGE>17.000</MENGE> <MENEE>PCE</MENEE> <BMNG2>17.000</BMNG2>
<PMENE>PCE</PMENE> <VPREI>18.33</VPREI> <PEINH>1</PEINH> <NETWR>311.61</NETWR>
<NTGEW>1588.65</NTGEW> <GEWEI>KGM</GEWEI>
<MATKL>001</MATKL> <BPUMN>1</BPUMN> <BPUMZ>1</BPUMZ>
<WMENG>17.000</WMENG> <EDATU>19990622</EDATU> </E1EDP20>
<QUALF>002</QUALF> <IDTNR>WTBMATERIAL2</IDTNR> </E1EDP19>
<QUALF>001</QUALF> <IDTNR>WTBMATERIAL2</IDTNR>
<KTEXT>Materialvariante Thomas Becker</KTEXT> </E1EDP19>
<QUALF>001</QUALF> <LKOND>FOB</LKOND>
<LKTEXT>Frei on Board</LKTEXT> <LPRIO>00</LPRIO> </E1EDP17>
<TDID>BEST</TDID> <TSSPRAS>D</TSSPRAS> <TSSPRAS_ISO>DE</TSSPRAS_ISO>
<TDLINE>
Will man das Material bestellen, so wird der Einkaufsbestelltext
</TDLINE> </E1EDPT2>
<TDLINE>sicherlich bei der Entscheidung helfen.</TDLINE>
</E1EDPT2>
<TDLINE>Oder auch nicht!?</TDLINE> </E1EDPT2>
</E1EDPT1>
</E1EDP01>
<E1EDS01 SEGMENT="1">
<SUMID>002</SUMID> <SUMME>436</SUMME> <SUNIT>DEM</SUNIT> </E1EDS01>
</IDOC>
</ORDERS01>

Port Type „XML“, DTD for IDoc type ORDERS01

<!ELEMENT ORDERS01 (IDOC+) >
<!ELEMENT IDOC (EDI_DC40, E1EDK01, E1EDK14*, E1EDK03*, E1EDK04*, E1EDK05*, E1EDKA1*, E1EDK02*, E1EDK17*,
E1EDK18*, E1EDKT1*, E1EDP01*, E1EDS01*) >

<!ELEMENT EDI_DC40 (TABNAM, MANDT?, DOCNUM?, DOCREL?, STATUS?, DIRECT, OUTMOD?, EXPRSS?, TEST?, IDOCTYP,
CIMTYP?, MESTYP, MESCOD?, MESFCT?, STD?, STDVRS?, STDMES?, SNDPOR, SNDPRT, SNDPFC?, SNDPRN, SNDSAD?,
SNDLAD?, RCVPOR, RCVPRT, RCVPFC?, RCVPRN, RCVSAD?, RCVLAD?, CREDAT?, CRETIM?, REFINT?, REFGRP?,
REFMES?, ARCKEY?, SERIAL?) >

<!ELEMENT E1EDK01 (ACTION?, KZABS?, CURCY?, HWAER?, WKURS?, ZTERM?, KUNDEUINR?, EIGENUINR?, BSART?, BELNR?,
NTGEW?, BRGEW?, GEWEI?, FKART_RL?, ABLAD?, BSTZD?, VSART?, VSART_BEZ?, RECIPNT_NO?, KZAZU?, AUTLF?,
AUGRU?, AUGRU_BEZ?, ABRVW?, ABRVW_BEZ?, FKTYP?, LIFSK?, LIFSK_BEZ?, EMPST?, ABTNR?, DELCO?, WKURS_M?) >
...

<!ELEMENT E1EDP01 (POSEX?, ACTION?, PSTYP?, KZABS?, MENGE?, MENEE?, BMNG2?, PMENE?, ABFTZ?, VPREI?, PEINH?,
NETWR?, ANETW?, SKFBP?, NTGEW?, GEWEI?, EINKZ?, CURCY?, PREIS?, MATKL?, UEPOS?, GRKOR?, EVERS?, BPUMN?,
BPUMZ?, ABGRU?, ABGRT?, ANTLF?, FIXMG?, KZAZU?, BRGEW?, PSTYV?, EMPST?, ABTNR?, ABRVW?, WERKS?, LPRIO?,
LPRIO_BEZ?, ROUTE?, ROUTE_BEZ?, LGORT?, VSTEL?, DELCO?, MATNR?, VALTG?, HIPOS?, HIEVW?,
E1EDP02*, E1EDP03*, E1EDP04*, E1EDP05*, E1EDP20*, E1EDPA1*, E1EDP19*, E1EDP17*, E1EDP18*, E1EDPT1*) >

<!ELEMENT E1EDP02 (QUALF?, BELNR?, ZEILE?, DATUM?, UZEIT?, BSARK?, IHREZ?) >
...

<!ELEMENT MESTYP (#PCDATA) >

<!ELEMENT MFRNR (#PCDATA) >
...
<!ATTLIST IDOC BEGIN (1) #REQUIRED >
<!ATTLIST EDI_DC40 SEGMENT (1) #REQUIRED >
<!ATTLIST E1EDK01 SEGMENT (1) #REQUIRED >
...
<!ATTLIST E1EDP01 SEGMENT (1) #REQUIRED >
<!ATTLIST E1EDP02 SEGMENT (1) #REQUIRED >
...
<!ATTLIST E1EDS01 SEGMENT (1) #REQUIRED >

Error Processing
______________________________

Outbound Data Flow w/ Notification Points
SAP application
Document
Message w/
EDIN NAST record
Message Control
EDIM Message
NAST
Record
IDoc w/
EDIX syntax error
IDoc Interface
EDIO IDoc
IDoc
EDIP IDoc batch
Message for
EDI subsystem EDIL Status report
EDIS
Status report
EDIR
Customer

Inbound Data Flow w/ Notification Points
EDI subsystem TXTRAW IDoc message
IDoc
EDIM Message
IDoc Interface EDII IDoc
IDoc w/
EDIY syntax error
IDoc
IDoc w/o
SAP application Application application document

Table of Notification Tasks
Process Task Role

code resolution
EDIM TS30000020 30000001 Administrator, system profile
EDIN TS70008037 70000141 Partner profile, system profile

EDIP TS60001307 30000001 Administrator, system profile
EDIO TS00007989 30000013 Representative, partner profile
EDIX TS00008070 30000013 Representative, partner profile
EDII TS00008068 30000013 Representative, partner profile

EDIY TS00008074 30000013 Representative, partner profile
application TSnnnnnnnn 00000134 Representative, partner profile
EDIL TS70008373 30000001 Administrator, system profile

EDIS TS30000078 30000001 Administrator, system profile
EDIR TS70008125 30000001 Administrator, system profile
RSEIDOCM TS30200108 30200013 Party from selection screen
All application tasks can be found by the logical message as search term!

Error Processing via Workflow
Application ALE layer Comm. layer

posting
Outbound !?
!?
M C
asynch. RFC
or
EDI
Error-processing
Workflow
Inbound !?
!?
A C

Error Processing
 Errors are processed locally within the system in that the error occurred
 Standard tasks exist for all ALE errors
 If an error occurs, an event triggers the standard task which starts the error
processing workflow
 The responsible people obtain a workitem in their inbox
 The error message attached to the IDOC is displayed

 The IDOC can be resubmitted at the end of error processing
 The standard tasks supplied by SAP have got the default name '<message type>_error'.

Who is responsible?
 The system finds the responsible persons by:

 determination of persons by using the staffing schedule of the organizational unit or position
with which the standard task is linked
 determination of persons defined in the partner profile (by means of their user ID, position or
organizational unit)
 The overlap of the two groups of persons makes up the pool of
employees who receive a work item
Org. unit
Responsible
Responsible
Partner profile

Assigning People to Error Tasks
 Create an organizational unit

 Create a position for the organizational unit
 Assign a user to the position
 Assign the error standard task to the position
Transaction: OOOE

Manual Resubmission
 There also exist a possibility to reprocess IDOCs without using the

workflow
 For this you have to detect the IDOCs that produced an error manually
 You can resubmit IDOCs with
 ALE-outbound errors
 ALE-inbound errors
 Application errors
 For ALE-outbound errors (status:02, 04, 05, 25,29):
Menu: Logistics -> Central functions -> Distribution -> Period.work -> IDoc,
ALE output ->
Process ALE error
 For ALE-inbound errors (status: 56, 61, 63, 65):
Menu:Logistics -> Central functions -> Distribution -> Period.work -> IDoc,
ALE input ->
Process ALE error
 For application errors:
Menu:Logistics -> Central functions -> Distribution -> Period.work -> IDOC,
ALE input -> Edit error

Questions ...

The Idoc Interface: R/3 Release

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

The Idoc Interface: R/3 Release

Diunggah oleh

Hak Cipta:

Format Tersedia

The IDoc Interface

 SAP AG 1999 IDocEnjoy (Th. Becker) / 1

 Expectations from this class

 Any prior experience in ALE/IDOC or other

 SAP AG 1999 IDocEnjoy (Th. Becker) / 2

 SAP AG 1999 IDocEnjoy (Th. Becker) / 3

Day 1 – IDOC overview

 SAP AG 1999 IDocEnjoy (Th. Becker) / 4

One central system is not

Org HQ Central Ref

Why distribute Applications ?

 SAP AG 1999 IDocEnjoy (Th. Becker) / 8

 SAP AG 1999 IDocEnjoy (Th. Becker) / 10

Why Intermediate Documents ?

 Messages must have a defined structure

 Easy technical handling ( "Data Container" )

 Possibility to build complex data structures

 Possibility for extension

 Possibility for documentation

 Link to standard processing ( EDI )

 SAP AG 1999 IDocEnjoy (Th. Becker) / 11

 The key concepts of IDoc (i.e. Intermediate Document) are:

 Following these concepts IDoc facilitates distributed processes rather simply

 IDoc is available for system R/3 from release 2.1A on.

 SAP AG 1999 IDocEnjoy (Th. Becker) / 12

 R/3 System  EDI subsystem

 SAP AG 1999 IDocEnjoy (Th. Becker) / 13

 SAP AG 1999 IDocEnjoy (Th. Becker) / 15

Control Record IDoc-ID

Data Record IDoc-ID

Status Record IDoc-ID

 SAP AG 1999 IDocEnjoy (Th. Becker) / 16

 SAP AG 1999 IDocEnjoy (Th. Becker) / 17

 SAP AG 1999 IDocEnjoy (Th. Becker) / 19

Outbound Data Inbound

Message Control Workflow

IDoc Interface & IDoc IDoc Interface &

System 2 File System 2

 SAP AG 1999 IDocEnjoy (Th. Becker) / 20

Message Control (NAST)

IDoc Interface & ALE Services

System 2, e.g. EDI subsystem

 SAP AG 1999 IDocEnjoy (Th. Becker) / 21

 An IDoc view is a selection of segments of a given IDoc

 SAP AG 1999 IDocEnjoy (Th. Becker) / 22

The method and technique for supporting

ALE Infrastructure encompasses:

 Integration of distributed applications  Scenarios:

 Using the EDI functionality

BLAOR Blanket order/changes

 ALE handles the communication between business applications, not the

Folsom, CA Tsukuba, Japan

 Distribution of accounting and logistics

 Provides for input and Output Processing

 Based on Distribution Model

Application ALE layer Comm. layer

Field value conversion

 SAP AG 1999 IDocEnjoy (Th. Becker) / 33

Comm. layer ALE layer Application

asynch. RFC Segment filter

 SAP AG 1999 IDocEnjoy (Th. Becker) / 34

Sending system Plant 1 Receiving system CRS