BC620 - SAP IDoc Interface (Technology)

BC620
SAP IDoc
Interface
(Technology)
 SAP AG 1999
 SAP AG
Copyright

Copyright 2000 SAP AG. All rights reserved.

Neither this training manual nor any part thereof may
be copied or reproduced in any form or by any means,
or translated into another language, without the prior
consent of SAP AG. The information contained in this
document is subject to change and supplement without prior
notice.

All rights reserved.

 SAP AG 1999
Business Integration Technologies II

Level 2 Level 3
BC619 3 days
Application Link
Enabling (ALE)
Technology
BC620 2 days BC621 1 day
SAP IDoc Interface SAP IDoc Interface - Data Exchange
Technology Development

BC095 3 days CA210 4 days

Business Integration EDI Interface

Technology

CA150 2 days
Building Enterprise BC420 5 days
Solutions with SAP Data Transfer
Components BC415 2 days
Communication
CA925 5 days Interfaces in ABAP Interface
Programming with Programming
BAPIs in Visual Basic CA926 5 days
Programming with
CA927 5 days BAPIs in JAVA
R/3 Interface and BAPI
Programming in C++
 SAP AG 1999
Course Prerequisites

 Recommended:
Basic knowledge of the R/3 System, as gained from
courses SAP20 and SAP50, for example

 SAP AG 1999
Target Group

 Participants:
 Consultants
 Administrators
 Project team
members
 Duration: 2 days

 SAP AG 1999
Course Overview

Contents:

 Course Goals
 Course Objective(s)
 Course Content
 Course Overview Diagram
 Main Business Scenario

 SAP AG 1999
Course Goals

This course will enable you to:

 Understand the possibilities offered by the

IDoc Interface for electronic data transfer

 Use the IDoc Interface

 SAP AG 1999
Course Objective(s)

At the conclusion of this course, you will be

able to:
 Configure the IDoc Interface

 Trace the processing of IDocs in the

system

 Select and use the correct IDoc types for

your business processes

 SAP AG 1999
Course Content

Preface and Introduction

Unit 1 Course Overview Unit 9 General Settings

Unit 2 Basic Principles Unit 10 Further Test Programs
Unit 3 IDocs in Business Process Unit 11 A Process Chain
Unit 4 Documentation Tools Unit 12 Statistics and Monitoring
Unit 5 Port Definition Unit 13 Workflows and IDocs
Unit 6 Partner Profiles Unit 14 Using an EDI Subsystem
Unit 7 The Test Tool Unit 15 Archiving
Unit 8 MC and IDocs

Exercises
Solutions
Appendix

 SAP AG 1999
Main Business Scenario

SmartMart
QuickDeliver

SAP R/3 System SAP R/3 System

IDoc IDoc

Message
EDI Subsystem EDI Subsystem

 SAP AG 1999
Basic Principles

Contents:

 IDoc concept and fundamental terms

 Data flow and process flows when using the IDoc Interface

 SAP AG 1999
Topic Objectives

At the conclusion of this unit, you will be able to:

 Explain the terms IDoc, EDI and ALE

 Identify the basic steps in IDoc processing

 SAP AG 1999
IDoc Concept

System 1 System 2

Document IDoc Document

 Message-oriented
 Asynchronous

 SAP AG 1999
IDoc Applications

Business
R/2 System Connector
Internet
Intranet

ALE

IDoc
EDI
Subsystem
R/3 System

Other
Workflow Systems...
Electronic
Form

 SAP AG 1999
EDI and ALE

Document

IDoc
SAP R/3 System SAP R/3 System

IDoc IDoc

Message
EDI Subsystem EDI Subsystem

 SAP AG 1999
Process Flow: Sending Data

R/3 System
Post document

Generate IDoc

Check partner, find port

Transfer data,
process further

External system

 SAP AG 1999
IDoc Settings: Sending Data

R/3 System
Post document

Archive
Archive IDoc
IDoc ?? Generate IDoc Partner
Partner Profiles
Profiles

Check partner, find port

Port
Port Definition
Definition

External System

Transfer data, Documentation

Documentation
EDI
EDI Subsystem
Subsystem ?? process further Tools
Tools

 SAP AG 1999
Process Flow: Receiving Data

External System

Send data to
R/3 System
transfer

R/3 System

Check port & partner,

Generate IDoc

Post document ok?

No

ok? Error handling

No

 SAP AG 1999
IDoc Settings: Receiving Data

External System

Send data to
EDI
EDI Subsystem
Subsystem ?? R/3 System

Documentation
Documentation
Tools
Tools

Check port & partner, Port

Port Definition,
Definition,
Archive
Archive IDoc
IDoc ?? Partner
generate IDoc Partner Profiles
Profiles

Post document

Error handling

R/3 System

 SAP AG 1999
Basic Principles: Summary

 IDoc is an SAP standard for data transfer between

systems.
 Known implementation areas for IDocs: ALE and
EDI scenarios
 The IDoc Interface facilitates both IDoc processing
and flexible error/exception handling

 SAP AG 1999
IDocs in Business Processes

 IDoc Record Types

 IDoc and IDoc type

 IDoc processing: Inbound and outbound

processing

 SAP AG 1999
IDocs in Business Processes: Course Objectives

At the conclusion of this unit, you will be able to:

 Explain the difference between IDocs and

IDoc types
 Describe the structure of an IDoc
 Determine where in the business process or
the process chain the IDoc was created

 SAP AG 1999
Business scenario

 As a member of the implementation team for

your company (SmartMart or QuickDeliver), you
are responsible for configuring the IDoc
Interface. You must therefore understand the
basic principles behind the interface: the IDoc
format and how to embed the interface in both
outbound processing (SmartMart) and inbound
processing (QuickDeliver).

 SAP AG 1999
IDoc Record Types

Control record

Data records

Status records

 SAP AG 1999
Control record

Control record IDoc ID

Partner
IDoc type and logical message
External structure

 SAP AG 1999
Data Records and Segment Structures

Data record
Control part, contains Application data
segment names Field 1 Field 2 ...

Segment

 SAP AG 1999
Status Record

Status Record IDoc ID

Status information

 SAP AG 1999
IDoc Record Types: Summary

Control record IDoc ID

Partner
IDoc type and logical message
External structure

Data records

Control part Application data

Status records IDoc ID

Status information

 SAP AG 1999
IDoc Types

Control Record

Data records, represented as a segment tree

E1HDDOC E1TLSUM
M 1 C 1
E1HDADR E1ITDOC
C 5 Elternsegment
M 1

E1ITSCH
E1ITSCH
Kindsegment
C 99 C 5

Status Records

 SAP AG 1999
Outbound and Inbound Processing

SAP Application

IDoc Interface/ALE Services

R/3 System

External System

Outbound Processing Inbound

 SAP AG 1999
Outbound Processing using Message
Control

SAP Application

Document

Message Control (MC)

MC
record

IDoc Interface / ALE Services

IDoc

External System

 SAP AG 1999
Direct Outbound Processing using ALE

SAP Application

Master IDoc
IDoc Interface / ALE Services

Comm. IDoc Comm. IDoc Comm. IDoc

External System

 SAP AG 1999
Inbound Processing using Workflow

External System

IDoc

IDoc Interface & ALE Services

IDoc +
process

SAP Business Workflow

Document

SAP Application

 SAP AG 1999
Direct Inbound Processing using ALE

External System

IDoc

IDoc Interface & ALE Services

IDoc

SAP Application

 SAP AG 1999
IDocs in Business Processes: Summary

 Each IDoc in the R/3 database consists of one control

record and several data and status records. Only
control records and data records are exchanged with
external systems.
 There are various IDoc types which are distinguished
by their segments and their order. This information is
stored in the control part of the data records.
 Different processing options are available for IDocs in
both inbound and outbound processing.

 SAP AG 1999
IDocs in Business Processes Exercise
IDocs in Business Processes Solutions
Documentation Tools

 Record types, IDoc types, segments

 Output formats

 SAP AG 1999
Documentation Tools: Unit Objectives

At the conclusion of this unit, you will be able to:

 Use the documentation tools

 Decide in which situations they would be useful

 SAP AG 1999
Overview Diagram (Sending Data)

R/3 System
Post document

Archive
Archive IDoc
IDoc ?? Generate IDoc Partner
Partner Profiles
Profiles

Check partner, find port

Port
Port Definition
Definition

External System
Documentation
EDI
Transfer data, Tools
EDI Subsystem
Subsystem ?? process further

 SAP AG 1999
Business scenario

 As a member of the implementation team for your

company (SmartMart or QuickDeliver), you are
responsible for configuring the IDoc Interface.
Your EDI subsystem does not yet know the structure
of the IDoc type to be used. The IDoc Interface can
export IDoc type structures in various formats, using
the documentation tools. You must know about this
function, as you can save yourself a lot of
programming work in the EDI subsystem.

 SAP AG 1999
Documentation Tools: Summary

 The documentation tools describe both the

structure and the use of different IDocs.
 The structure is in the structure information.
External structures are always documented,
specifically regarding how they are exchanged
with external systems.
 The output formats can be read by external
systems, so that non-R/3 Systems can quickly
recognize the IDoc structure.

 SAP AG 1999
Documentation Tools Exercise
Port Definition

 Port types and when they are used

 Port definition parameters

 Communication with Older Releases

 SAP AG 1999
Port Definition: Unit Objectives

At the conclusion of this unit, you will be able to:

 Decide which port types should be implemented

for which external systems
 Enter a port definition in the R/3 System
 Determine which additional steps are required for
linking to the relevant external system
 Enter special settings which are required for
communication with older R/3 releases and R/2
Systems

 SAP AG 1999
Overview Diagram (Sending Data)

R/3 System

Post document

Archive
Archive IDoc
IDoc ?? Generate IDoc Partner
Partner Profiles
Profiles

Check partner, find port

Port Definition

External System
Documentation
Documentation
Transfer data, Tools
Tools
EDI
EDI Subsystem
Subsystem ?? process further

 SAP AG 1999
Port Definition: Business Scenario

 As a member of the implementation team for

SmartMart, you are responsible for configuring
the IDoc Interface.
 You must decide which port type is suitable for
the system of your partner company
QuickDeliver.

 SAP AG 1999
IDoc Interface: Port Types

IDoc Interface

IDoc/ IDoc/
IDoc IDoc IDoc IDoc
status status

File XML tRFC Internet CPI-C PI

?
External System R/2 System

 SAP AG 1999
Process Flow: Port Type File (with Triggering)

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

External System

 SAP AG 1999
Port Type XML: Flat File and XML File

EDI_DC40 004000000000030702346B 3013 ORDERS01

...
E2EDP01005 00400000000003070230000210000000200
E2EDP20 00400000000003070230000220000210323
...
E2EDPT1001 004000000000030702300002600002103BESTD
E2EDPT2001 004000000000030702300002700002604This is

 SAP AG 1999
Port Type XML: Flat File and XML File (2)

EDI_DC40 <EDI_DC40 SEGMENT="1"><TABNAM><![CDAT

A[EDI_DC40]]></TABNAM><MANDT>004</MAN
DT><DOCNUM>0000000000307023</DOCNUM>
...
<E1EDP01 SEGMENT="1"><POSEX>00010 </POS
E1EDP01 EX><ACTION>001</ACTION><PSTYP>0</PSTYP
><MENGE>23.000</MENGE>...
...
<E1EDP20 SEGMENT="1"><WMENG>23.000 </W
E1EDP20
MENG><EDATU>19990622</EDATU></E1EDP2>
...
<E1EDPT1 SEGMENT="1"><TDID>BEST</TDID>
E1EDPT1 <TSSPRAS>D</TSSPRAS>...
...
...
<E1EDPT2 SEGMENT="1"><TDLINE>This is the
E1EDPT2
purchase order text.</TDLINE>...
...
</E1EDPT1> </E1EDP01>
 SAP AG 1999
Port Definition - Port Type tRFC

RFC destination
(R/3 connection)

Application server for

receiving system

Port name (assigned automatically)

 SAP AG 1999
Port Definition: CPI-C (R/2 System)

sideinfo-entry

TXCOM entry
Host on R/2

Host destination

RFC destination

Technical parameters
Send status records?

 SAP AG 1999
Process Flow: Port Type PI

IDoc Interface

IDoc

Own function module

 SAP AG 1999
Communication with Older Releases

Differences in IDoc record types

4.X
Field 1 Field 3 Field 2

Field 1 Field 2 New field 3 3.0/3.1

Field 1 Field 2
2.1/2.2

 SAP AG 1999
Port Definition: Summary

 IDocs or status records are always exchanged with an

external system via a port.
 In the port definition for the IDoc Interface, users define
the target system and the technical communication
parameters. In addition, users can specify the release
status for the external system via the version entry.
 Additional technical settings must also be entered (also
outside R/3), before a port can be used.
 There are six basic communication techniques for the
IDoc Interface, represented by the six different port
types.

 SAP AG 1999
Port Definition Exercise
Partner Profiles

 Standard partner profiles

 Checking Partner Profiles

 Fast entry

 SAP AG 1999
Partner Profiles: Unit Objectives

At the conclusion of this unit, you will be able to:

 Explain the purpose of partner profiles and

process codes
 Maintain partner profiles

 SAP AG 1999
Overview Diagram (Sending Data)

R/3 System
Post document

Partner Profiles
Archive
Archive IDoc
IDoc ?? Generate IDoc

Check partner, find port

Port
Port Definition
Definition

Documentation
Documentation
Transfer data, Tools
Tools
EDI
EDI Subsystem?
Subsystem? process further

 SAP AG 1999
Partner Profiles: Business Scenario

 SmartMart must define QuickDeliver as a partner.

You have already configured a suitable port in the
port definition.
 In outbound processing, QuickDeliver is the partner
for the purchase order. In outbound processing, it
is the partner for the order acknowledgment.

 SAP AG 1999
Partner Profiles: Outbound Processing I

SAP Application

Document

MC settings
MCMC
settings Document

MC
record

General+outbound
General+outbound
IDoc Interface / ALE Services

IDoc

Receiving System

 SAP AG 1999
Partner Profiles: Outbound Processing II

Partner: QD ; Appl: EF; OtptType : NEW Object type, MC record

language,...

Partner: QD ; Appl: EF; OtptType : NEW Process code: ME10

MC
Message: ORDERS settings

Partner: QD; Output type: ORDERS

Port: SUBSYSTEM
IDoc type: ORDERS01
General
Permitted agent:
Outbound
EDI agent for partner
QuickDeliver (QD) (purchase orders)

 SAP AG 1999
Partner Profiles: Inbound Processing

IDoc type: IDoc

Partner: QD; Message: ORDRSP
ORDERS01 Control Record

Process code:
Partner: QD; Message: ORDRSP
ORDR;
Permitted agents: EDI Inb. Processing
agent for partner
QuickDeliver, order
acknowledgments

 SAP AG 1999
Process Codes I

Partner
Application
Mess.type

Process code

Function module (writes the application

Process code
Example: MC parameters
data in an in partnerIDoc)
outbound profiles

 SAP AG 1999
Process Codes II

Example: Inbound

Partner
Message

Process code

Function module/workflow (reads data from an

Process code
inbound IDoc and processes data further)

 SAP AG 1999
Process Codes III

Documentation via messages

Message

Process code

 SAP AG 1999
Outbound Modes: Port Type File

Partner Description
profile

Transfer single IDoc +

start external system (trigger)

Transfer single IDoc;

no trigger

Transfer multiple IDocs + start

external system (trigger)

Transfer multiple IDocs;

no trigger

 SAP AG 1999
Partner Profiles Output

Display

 SAP AG 1999
Partner Profiles: Summary

 Partner profiles specify which messages are sent to which

users, using which method and how they are processed.
Partners must be entered in the partner profile before IDocs can
be sent successfully.
 The port (the "way") is part of the outbound partner profile.
Technical communication parameters are entered in the port
definition. Inbound ports do not require such parameters - their
technical parameters are defined by the external sending
system.
 Process codes are also part of the partner profiles.
They are used for processing data.
 Process codes which are defined outside the partner profile are
used in error handling.

 SAP AG 1999
Partner Profiles Exercise
The Test Tool

Test Tool Options

 SAP AG 1999
Test Tool Options

 SAP AG 1999
Test Tool Exercise
Message Control and IDocs

 Message determination and message processing

 Condition components

 Dispatch times

 SAP AG 1999
Message Control and IDocs: Unit Objectives

At the conclusion of this unit, you will be able to:

 Explain condition components

 Find examples of condition components in MM
Customizing
 Display and process the proposed message from the
MM application transaction

 SAP AG 1999
Business Scenario

 As a member of the implementation team for

SmartMart, you are responsible for configuring the
IDoc Interface.
A purchase order from SmartMart is firstly created as a
message by the Message Control module, before being
converted into IDoc format. You know that the basic
settings for this module exist in the standard SAP
system, but wish to find out more about other Message
Control functions.

 SAP AG 1999
Outbound Processing using Message
Control

SAP Application

Document
Find proposal

MC Edit

MC
record
Process

IDoc Interface/ALE Services

 SAP AG 1999
Condition Elements

SAP Application
1:n

Procedure

m:n

Output Type
n:1

Access Sequence
m:n
Condition Table

 SAP AG 1999
Message Processing: IDocs

Check MC record R
S
Read partner profile N
A
Call selection module S
(from application) T
E
Call ALE Services
D
Transfer according to
output mode
'1'/ '2' '3'/ '4'

Single IDoc Multiple IDocs

via RSEOUT00

 SAP AG 1999
Dispatch Times in Outb. Procg using MC

Application MC IDoc Interface External System

Post VSZTP = 4 OUTMOD = 1

Real time

Post VSZTP = 1 OUTMOD = 1

Fast batch

Post VSZTP = 1 OUTMOD = 3

Batch

Post VSZTP = 1 OUTMOD = 4

Batch

 SAP AG 1999
Summary

 Message Control is important in IDoc outbound

processing.
 Messages defined in Customizing are examined in a
certain sequence to determine whether or not they
apply to the current application data. This sequence is
defined by the condition components and their
hierarchy.
 IDoc-specific message processing takes place via
program RSNASTED.
 Up to three different dispatch times can be defined for
outbound processing.

 SAP AG 1999
Message Control and IDocs Exercise
Message Control and IDocs: SolutionUnit: Message Control and IDocs
Topic: Condition elements
General Settings

 Number ranges

 Event-receiver linkage

 IDoc administration

 Fast entry

 Long names - short names

 SAP AG 1999
General Settings: Unit Objectives

At the conclusion of this unit, you will be able to:

 Configure the general parameters in the IMG

 Describe when the IDoc Administrator is notified

 SAP AG 1999
Customizing using the IMG

R/3 Customizing IMG

Cross-application
components

IMG documentation IDoc Interface

Project documentation

Project management

Activities

 SAP AG 1999
Number Ranges

IDoc Interface

[…]

 SAP AG 1999
Event-Receiver Linkage

IDoc Interface

Processing

R/3 Application

 SAP AG 1999
IDoc Administration: Global Parameters

 Party to be notified (IDoc Administrator)

 System environment (Basis system?)
 Processing details

 SAP AG 1999
 SAP AG
IDoc Administration: User Parameters

 Tests
 Documentation Tools
 Development

 SAP AG 1999
 SAP AG
Fast entry

Default values

 SAP AG 1999
Long Names - Short Names

Release 4.0 Release 3.X

Type
Type "Short01"
"LongNameXYZ01"

 SAP AG 1999
General Settings: Summary

 General settings are entered via the IMG. In

addition, user-specific parameters can be changed
at any time via the control menu.
 The IDoc Administrator is part of the global
parameters which are maintained in IDoc
Administration. When exceptions occur, the
administrator is always notified if no partner profile
is found.

 SAP AG 1999
General Settings Exercise
Additional Test Programs

 Test layers

 Test programs

 SAP AG 1999
Processing Tests: Unit Objectives

At the conclusion of this unit, you will be able to:

 Use special test programs and determine when to

implement them during processing

 SAP AG 1999
Processing Tests: Business Scenario

 As a member of the implementation team for your

company (SmartMart or QuickDeliver), you are
responsible for configuring the IDoc Interface.
After tests have been completed successfully in
your own system and the EDI subsystem has been
connected, you wish to test data transfer.
The IDoc Interface test programs are to be used for
this purpose and this unit contains information
about using these tools.

 SAP AG 1999
Test Layers: Overview

Application

MC Workflow

WE19 ,
WE15 WE18

IDoc Interface

WE14, WE19 WE16 WE17

External Outbound WE12 Inbound Status

IDoc file IDoc file confirm.
System
File System

WE18

 SAP AG 1999
Test Layers: Outbound Processing

Application

MC
MC

WE15

IDoc Interface

WE14, WE19

External
System

 SAP AG 1999
Test Layers: Inbound Processing

Application

Workflow

WE19

IDoc Interface

WE16

Outbound WE12 Inbound

IDoc file IDoc file File System

 SAP AG 1999
Test Layers: Status Confirmation

Application

Workflow

WE19 ,
WE18

IDoc Interface

WE16 WE17

Outbound WE12 Inbound Status

file with file with confirm.
SYSTAT01 SYSTAT01
File System

WE18

 SAP AG 1999
When to Test Which Function?

 Data exchange with the file system: WE14

(outbound), WE16 (inbound), WE17 (status
confirmation, inbound)
 Processing MC record: WE15
 Data transfer from the IDoc Interface to additional
inbound processing: WE19
 Data transfer to any port: WE14

 SAP AG 1999
Processing Tests: Summary

 Special test programs require MC records, files or

existing IDocs from the database. If necessary,
automatic outbound processing must be stopped via
the output mode from the partner profile and the
dispatch time in the MC condition record.
 The test tool allows general tests for inbound
processing, outbound processing and status
confirmation via SYSTAT01.

 SAP AG 1999
A Process Chain

 Send purchase order

 Post standard order

 SAP AG 1999
A Process Chain: Unit Objectives

At the conclusion of this unit, you will be able to:

 Send a purchase order via IDoc

 Receive a standard order via IDoc
 Explain which EDI-specific master data must be
maintained

 SAP AG 1999
A Process Chain: Business Scenario

 As a member of the implementation team for your

company (SmartMart or QuickDeliver), you are
responsible for configuring the IDoc Interface.
For test purposes, IDocs are to be created by
SmartMart and sent to QuickDeliver.

 SAP AG 1999
EDI-Relevant Master Data in Purchasing

Vendor master record : Data record E1EDKA1 (PARVW = "LF"):

Partner number, type, Partner information
function
Data record E1EDKA1 (PARVW = “AG”):
Vendor master record : Partner information
Vendor account
Data record E1EDP19 (QUALF= “001”):
Material master record: Material number
Material name
Data record E1EDP19 (QUALF= “002”):
Vendor material number: Material number
Material name for vendor
IDoc Type ORDERS01
MC condition record with
transmiss. medium "6" (EDI)
 SAP AG 1999
Standard Order for QuickDeliver

External System = QuickDeliver EDI Subsystem

Send data to
R/3 System

R/3 System

Determine processing for SmartMart data,

generate IDoc

Post standard order ok?

No

ok? Generate work item

No

 SAP AG 1999
EDI-Specific Master Data in Sales

Data record E1EDKA1 (PARVW = “AG”): Customer master record:

Partner information Partner number, type,
function
Data record E1EDKA1 (PARVW = "LF"):
Partner information SD Customizing:
Assigning customer/
vendor to sales
Data record E1EDP19 (QUALF= “002”): organization
Material number
Material master record:
Material name

IDoc
IDoc Type
Type ORDERS01
ORDERS01

 SAP AG 1999
A Process Chain: Summary

 Special EDI parameters must be entered in the

application master data. These include partner
information and transmission medium "6" in the
condition record for outbound processing using
Message Control (MC).

 Outbound processing using Message Control is

always applied for purchase orders from the MM
module.

 SAP AG 1999
Process Chain Exercise
Statistics and Monitoring

 Passive and active monitoring

 Work Item Analysis

 SAP AG 1999
Statistics and Monitoring: Unit Objectives

At the conclusion of this unit, you will be able to:

 Decide when different tools should be implemented

for IDoc monitoring
 Use the individual monitoring transactions

 SAP AG 1999
Business Scenario

 As a member of the implementation team for your

company (SmartMart or QuickDeliver), you are
responsible for configuring the IDoc Interface.
The exchange of IDocs between the two
companies is to be monitored. As a result, you
must be familiar with the IDoc monitoring tools
available for the IDoc Interface.

 SAP AG 1999
Monitoring Programs: Overview

Passive monitoring Active

monitoring

Statistics "RSEIDOCM"

4711
4712
List, IDoc 4713
search 4718

Display

 SAP AG 1999
Selection Fields for Monitoring

Control record

Creation Change Partner, EDI

date date message,... References

IDoc statistics
IDoc list
IDoc search
IDoc display
Active
monitoring

 SAP AG 1999
Status Group: Monitor/Statistics
100
80
60
40
20
0
1. 2. 3. 4.
Qrtl. Qrtl. Qrtl. Qrtl.

4 = "IDoc transfer
successful"
13 =
"Send ok" 12 =
Retransmission "Send ok"
ok

39 = "IDoc in
target system (ALE)"

 SAP AG 1999
Work Item Analysis

 Usually refers to exception handling

 Work items which exist in the system are listed
Application for "lost work items", for example (no user
selected)

 SAP AG 1999
Statistics and Monitoring: Summary

 The IDoc data flow can be monitored via four passive

programs and one active program in the IDoc
interface.

 Active monitoring is a function which can be

individually configured for error handling or general
exception handling.

 The level of detail in the passive monitoring programs

goes as far as displaying the individual IDocs. The
least-detailed monitoring tool is the status group
display under IDoc statistics.

 SAP AG 1999
Statistics and Monitoring ExerciseUnit: Statistics and Monitoring
Topic: Passive monitoring
Statistics and Monitoring: Solution
Unit: Statistics and Monitoring
Workflow and IDocs

 Inbound processing

 Exception handling

 Notification concept

 Organizational structure

 SAP AG 1999
Workflow and IDocs: Unit Objectives

At the conclusion of this unit, you will be able to:

 Explain how the agent responsible is informed if

an error occurs during IDoc processing
 Maintain the organizational structure

 SAP AG 1999
Workflow and IDocs: Business Scenario

 As a member of the implementation team for

QuickDeliver, you are responsible for configuring
the IDoc interface.
A purchase order from SmartMart is received by
QuickDeliver as an inbound IDoc of type
ORDERS01. Inbound processing is configured
using a process code as "direct via a function
module", exception handling takes place by means
of workflow. You must configure a party to be
notified if an error occurs.

 SAP AG 1999
Inbound Processing with Workflow

IDoc Interface & ALE Services

IDoc +
process

Review,
edit,
Workflow
forward,
and so on.
Document

SAP Application

 SAP AG 1999
Exception Handling with Workflow

R/3 System
Check partner, generate IDoc

Post document ok?

No Express

ok? Error handling Message

No

 SAP AG 1999
Exceptions in Outbound Processing

SAP Application
or MC Message without IDoc
EDIM
without MC...
Document EDIN ...with MC
or MC
record
Syntax error
EDIX in IDoc

Error during IDoc

EDIO
IDoc Interface processing

Error while processing

EDIP IDoc stack
IDoc

EDIR
External System Status confirmation
EDIS
Customer

 SAP AG 1999
Exceptions in Inbound Processing

TXTRAW Message via IDoc

External System
EDIM Message without IDoc
IDoc
...error during
EDIL status file

Error during IDoc

IDoc Interface EDII processing

IDoc Syntax error

EDIY in IDoc

SAP Application
IDoc with or without
Application application document

 SAP AG 1999
Notification Concept I

Organizational structure
Possible agents

Task

Role resolution Selected agent

Partner profile

Permitted agents
IDoc Interface

 SAP AG 1999
Notification Concept III

reports to/
is superior to

cost center assignment

Organizational unit Cost center

belongs to cost center
assignment
includes

described by belongs to

Job describes Position includes Work center

described by
holds
described by
describes holder
describes

Person/user
Task

 SAP AG 1999
Maintaining an Organizational Structure

 Customizing activities
 Maintenance from the Workflow
menu

 SAP AG 1999
Integrated Inbox

SAPoffice

Message Workflow

Missed deadline

...

 SAP AG 1999
Workflow and IDocs: Summary

 Normal IDoc processing via workflow is only possible for inbound

processing of certain IDoc types.
 Exception handling always takes place via workflow. It is called in
outbound processing in the same way as in inbound processing.
 Errors can be caused by incorrect application data or incorrect
IDoc syntax. In these cases, error handling is different.
 Through the organizational structure, workflow allows users in a
defined task area to be notified, not individual users whose
responsibilities may change.
 Workflow allows incorrect IDocs to be forwarded as work items "in
a controlled manner" from an integrated inbox and even to be
repaired in some cases.

 SAP AG 1999
Workflow and IDocs Exercise
Using an EDI Subsystem

 Converting to another standard

 Required data in control records

 More documentation

 SAP AG 1999
Using an EDI Subsystem: Unit Objectives

At the conclusion of this unit, you will

be able to:
 Recognize the tasks of the EDI subsystem
 Describe the differences between required fields and
optional fields in control records
 Understand the different ways to inform the EDI
subsystem about various IDoc formats

 SAP AG 1999
Business Scenario

 As a member of the implementation team for your

company (SmartMart or QuickDeliver), you are
responsible for configuring the IDoc interface.
You wish to connect your EDI subsystem. You must
find out about the work involved in configuring the
subsystem before carrying out the work.

 SAP AG 1999
EDI Subsystem: Responsibilities

Partner profile Translator Archiving

Addresses Message handling Monitoring

Communication

 SAP AG 1999
Required Fields in IDoc Inb. Processing: Control
Record

(Number, type, function) (Type, code, function) IDoc

Partner Message Test?
control record

Partner Message Test? Inbound

Processing
(partner
Process code; Inbound processing with ALE?; profiles)
Permitted agents; And so on.

 SAP AG 1999
More Documentation

IDoc Interface: Documentation Tools

Begin XML typedef struct z2incodx000

…
…
End z2incodx000

 SAP AG 1999
Using an EDI Subsystem: Summary

 The EDI subsystem is used mainly for converting

the IDoc format into an EDI standard (and vice
versa).
 The EDI subsystem is an interface to external
systems and has its own responsibilities.
 Format definitions can be defined in the EDI
subsystem in a form which can be read by other
systems.

 SAP AG 1999
Using an EDI Subsystem ExerciseUnit: Using an EDI Subsystem
Topic: More Documentation
Archiving

 Archiving object IDOC

 Status transfers

 Archiving status

 SAP AG 1999
Archiving: Unit Objectives

At the conclusion of this unit, you will be able to:

 Archive IDocs
 Describe a status transfer
 Configure the archiving status in the system

 SAP AG 1999
Overview Diagram (Sending Data)

R/3 System
Post document

Archive IDoc? Generate IDoc Partner

Partner Profiles
Profiles

Check partner, find port

Port
Port Definition
Definition

Documentation
Documentation
Transfer data, Tools
Tools
EDI
EDI Subsystem?
Subsystem? process further

 SAP AG 1999
Archiving: Business Scenario

 When the business process has been completed, the

processed IDocs should be deleted from the
database.
 However, you must archive the relevant IDocs before
they are deleted. The IDocs must therefore be
assigned an archiving status. When configuring the
IDoc Interface, you can determine which statuses can
be archived.

 SAP AG 1999
Archiving Object: IDOC

IDoc Interface

Archiving
programs

Possible
Storage

File System

 SAP AG 1999
Status Transfers in Inbound Processing

56 68

65

63
60

74 61 52

66

51

50 64 62 53

70 69 73 71 54 57

Selected statuses can be archived in the SAP

standard system
 SAP AG 1999
Archiving: Summary

 All archiving programs are addressed via the central

archiving transaction SARA. The archiving object is
IDOC.
 IDocs can only be deleted if they have been archived.
The archiving run must be complete.
 IDocs can only be archived if they have been
assigned a status which can be archived. The
statuses suitable for archiving can be configured in
the IDoc interface.

 SAP AG 1999
Appendix

 This section contains supplementary material

to be used for reference
 This material is not part of the standard course
 Therefore, the instructor might not cover this
during the course presentation

 SAP AG 1999
Appendix