IDoc Notification by Workflow

and Monitoring
- The IDoc Interface -

Thomas C. Becker
Business Process Technology
SAP AG
SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 1

Content

z
z
z
z

Layers of Processing
Implementation of Status Report
Notification
Monitoring

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 2

Page 1

Electronic Commerce

Document

IDoc

SAP System R/3

SAP System R/3

IDoc

IDoc

Transaction
Message

EDI Subsystem

EDI Subsystem

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 3

Outbound Data Flow

SAP application
Document

Message Control (NAST)

Document

NAST
Record

IDoc Interface & ALE Services

IDoc

System 2, e.g. EDI subsystem

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 4

Page 2

Outbound Status Transitions

01

37

39

24

04

06

05

08

07

10

09

12

11

29

26
25

30
40
03

41

02
22

18

20
14

15

16

17

31
SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 5

Inbound Data Flow

System 2, e.g. EDI subsystem
IDoc

IDoc Interface & ALE Services

IDoc +
Process

SAP Business Workflow

IDoc +
Function Module

Document

SAP application

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 6

Page 3

Inbound Status Transitions

50

56
65

Notifications
from the
EDI subsystem
prior to
IDoc creation,
can be received via
message TXTRAW.

60
61

64

66

62

63

52

53

SAP AG 1998

51

68

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 7

Notification and Monitoring

z
z

The IDoc interface offers 2 different

approaches for tracking of data load
and data flow:

100
80
60
40
20
0
1.
2.
3. 4.
Qrtl. Qrtl. Qrtl. Qrtl.

Workflow for notifications

Reports for monitoring

Both approaches are based on the concept of status

transitions, i.e. an IDoc changes its status from a given
value to another value.
Status transitions can be triggered by the SAP system
as well as by any subsystem, e.g. EDI subsystem.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 8

Page 4

Content

z
z
z
z

Layers of Processing
Implementation of Status Report
Notification
Monitoring

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 9

Status via File Interface

Status
report

startrfc
startrfc.exe

IDoc Interface

EDI subsystem

IDoc

IDoc

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 10

Page 5

EDI subsystem

IDoc Interface

Status via IDoc Type SYSTAT01

IDoc

IDoc

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 11

Content

z
z
z
z

Layers of Processing
Implementation of Status Report
Notification
Monitoring

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 12

Page 6

Determination of Selected Agents

Organizational plan
Task

Possible agents

Role resolution

Selected agents

Partner profile

Permitted agents

IDoc Interface

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 13

Determination of Permitted Agents

General

Partner and document

related

Determination strategy

Partner related

Administrator
(System profile)

CSR
(Partner profile w/o message)

CSR
(Partner profile w/ message)

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 14

Page 7

Table of Notification Tasks

Process
code

Task

Role
resolution

EDIM
EDIP
EDIO
EDIX
EDII
EDIY

TS30000020
TS60001307
TS00007989
TS00008070
TS00008068
TS00008074

30000001
30000001
00000134
00000134
00000134
00000134

Administrator, system profile

Administrator, system profile
CSR, partner profile
CSR, partner profile
CSR, partner profile
CSR, partner profile

EDIS

TS30000078

30000001

Administrator, system profile

RSEIDOCM
application

TS30200108
TSnnnnnnnn

30200013
00000134

Party from selection screen

CSR, partner profile

All application tasks can be found by the logical message as search term!

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 15

Outbound Data Flow w/ Notification Points

SAP application
Document

Message Control
EDIM

Message

EDIX

IDoc w/
syntax error

NAST
Record

IDoc Interface

EDIO
EDIP

IDoc

IDoc
IDoc batch

EDIS

EDI subsystem

Status report

Customer

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 16

Page 8

Inbound Data Flow w/ Notification Points

TXTRAW

IDoc message

EDI subsystem
IDoc

EDIM

IDoc Interface

EDII

IDoc

IDoc

EDIY

IDoc w/
syntax error

Message

SAP application
Application

IDoc w/o
application document

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 17

Example of an Users Inbox

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 18

Page 9

Workitem: Error in EDI subsystem

A change of status
is triggered by an
EDI subsystem
because of
translation error(s).
Someone has to
take care of the
situation, and is
notified by status
processing.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 19

Workitem: Status Transition Pending

Change of status triggered by

an EDI subsystem is pending
for more time than expected.
Someone has to take care of
the situation, and is notified by
program RSEIDOCM.
SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 20

Page 10

Content

z
z
z
z

Layers of Processing
Implementation of Status Report
Notification
Monitoring

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 21

Monitoring Programs

Statistics
RSEIDOCM
Active monitoring

4711
4712
4713
4718

Lists,
Find

Display

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 22

Page 11

Statistics - Case 1a: Outbound P.O.

Purchase orders were
created, and wait for
their transfer to an
EDI subsystem.
An administrator
monitors the process
by the statistics
transaction WE07.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 23

Statistics - Case 1b: Outbound P.O.

Purchase orders
were transfered to an
EDI subsystem,
some were
confirmed to SAP.
An administrator
monitors the process
by the statistics
transaction WE07.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 24

Page 12

Lists - Case 2a: Outbound P.O.

Purchase orders
were created, and
wait for their
transfer to an
EDI subsystem.
An administrator
monitors the
process by the
lists transaction
WE05.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 25

Lists - Case 2b: Outbound P.O.

Purchase orders were
transfered to an
EDI subsystem, some
were confirmed to
SAP.
An administrator
monitors the process
by the lists transaction
WE05.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 26

Page 13

Display - Case 3: Outbound P.O.

Purchase orders sent, were confirmed
with EDI references by an EDI
subsystem.

An administrator
accesses the IDoc(s) by
selecting with the
interchange and message
references by the display
transaction WE02.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 27

Case 4: Outbound P.O., but Application !

A purchase order was
created, the IDoc(s)
assigned to that P.O. are
seen from the application.

SAP AG 1998

M1 SAPTechEd 98, Karlsruhe (C. Becker) / 28

Page 14