idoc notification by workflow and monitoring
TRANSCRIPT
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 1/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 1
Thomas C. BeckerSAP AG
Exception Handling withSAP Business Workflow
Please pay attent ion to
the notes when pr int ingth is document ! The IDoc Interface
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 2/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 2
Agenda
Monitoring and
Notification by Workflow
Processing
Monitor
Notification
Exercises for notification
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 3/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 4
IDoc Data Flow
File
tRFC
XML
...
Application
Message Control
IDoc Interface &
ALE Services
System 2e.g. EDI subsystem
MMSD...
IDoc
Application
Workflow
IDoc Interface &
ALE Services
System 2e.g. EDI subsystem
Outbound Data Inbound
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 4/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 6
Outbound Status Transitions
42
37
29
26
02
20
31
01 39
18
03
30
25
4140 12
10
08
06
24
22
04
11
09
07
05
16
14 15
17
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 5/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 8
Inbound Status Transitions
74
52
66
53
62
51
63
56
65
60
68
50
64
61
Notifications
from the
EDI subsystem
prior to
IDoc creation,can be received via
message TXTRAW.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 6/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 9
Status via File Interface
Status
report
E D I s u b s y s t
e m
1
startrfc
startrfc.exe I D o c I n t e r f a
c e
4
2 3
IDoc
IDoc
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 7/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 10
Status via IDoc Type SYSTAT01
E D I s u b s y s t
e m
I D o c I n t e r f a
c e
IDoc
IDoc
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 8/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 11
Monitoring and Notification
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.
Status transitions can be triggered by the SAP system aswell as by any subsystem, e.g. EDI subsystem.
0
2040
60
80
100
1.
Qrtl.
2.
Qrtl.
3.
Qrtl.
4.
Qrtl.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 9/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 12
Agenda
Monitoring and
Notification by Workflow
Processing
Monitor
Notification
Exercises for notification
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 10/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 13
Monitoring Programs
„RSEIDOCM“
Active Monitoring
Display
4712
4711
4713
4718List
Statistic
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 11/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 14
Scenario for Monitor
7 purchase orders were created and
wait for their transfer to an EDIsubsystem (status „30“).
5 purchase orders were transfered to
an EDI subsystem (status „18“).
3 of the 5 IDocs were confirmed with
positive status by an EDI subsystem
(status „12“).
1 of the 5 IDocs was confirmed with a
negative status by an EDI subsystem
(status „05“).
SAP Application
IDoc Interface
EDI Subsystem
Create
Status Transfer
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 12/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 15
Case 1 - Statistics, after step
7 purchase orderswere created and wait
for their transfer to an
EDI subsystem.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 13/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 16
Case 1 - Statistics, after step
5 purchase orderswere transferred to an
EDI subsystem.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 14/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 17
Case 1 - Statistics, after step
4 purchase orderswere confirmed by an
EDI subsystem via
IDoc msg. STATUS.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 15/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 18
Case 2 - Lists, after step
7 purchase orders
were created and wait
for their transfer to an
EDI subsystem.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 16/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 19
Case 2 - Lists, after step
5 purchase orders
were transferred to an
EDI subsystem.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 17/37 SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 20
Case 2 - Lists, after step
4 purchase orders
were confirmed by an
EDI subsystem via
IDoc msg. STATUS.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 18/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 24
Case 3 - Display, by EDI References (after step )
An EDI administrator searches for IDocs by interchange and message references
reported by an EDI subsystem.
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 19/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 25
Case 4 - Find IDoc by Business Document
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 20/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 26
Agenda
Monitoring and
Notification by Workflow
Processing
Monitor
Notification
Exercises for notification
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 21/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 27
Outbound Data Flow w/ Notification Points
IDoc
NAST
Record
Document
SAP application
Message Control
IDoc Interface
EDI subsystem
EDIM Message
EDIXIDoc w/
syntax error
EDIP
EDIO IDoc
IDoc batch
EDINMessage w/
NAST record
Status report
EDIS
EDIRCustomer
EDILMessage for
Status report
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 22/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 28
Inbound Data Flow w/ Notification Points
EDIM Message
EDII IDoc
EDIYIDoc w/
syntax error
Application IDoc w/oapplication document
TXTRAW IDoc message
SAP application
IDoc Interface
IDoc
EDI subsystem
IDoc
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 23/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 29
Determination of Selected Agents
Role resolution
Task
Partner profile
Possible agents
Permitted agents
Selected agents
O r g a n i z a t i o n
a l P l a n
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 24/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 30
Selected Agents by General Task
Possible agents
Permitted agents
Selected agents Role resolution
General Task
Partner profile
O r g a n i z a t i o n
a l P l a n
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 25/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 31
Selected Agents acc/ Technical & Business Layer
Permitted agents
Selected
technic al agents
Possible agents
- Techn ical Layer -
Possible agents
- Busin ess Layer -
Selected
business agents
Role resolution
Task
Partner profile
O r g a n i z a t i o n
a l P l a n
D i i f P i d A
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 26/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 32
Determination of Permitted Agents
General
Partner
Partner & Process
Administrator(System profile)
Representative(Partner profile w/o message)
Representative(Partner profile w/ message)
D e t e r m i n a t i o n
s t r a t e g y
T bl f N tifi ti T k
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 27/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 33
Table of Notification Tasks
Role
resolution
30000001 Administrator, system profile
70000141 Partner profile, system profile
30000001 Administrator, system profile
30000013 Representative, partner profile30000013 Representative, partner profile
30000013 Representative, partner profile
30000013 Representative, partner profile
00000134 Representative, partner profile
30000001 Administrator, system profile
30000001 Administrator, system profile30000001 Administrator, system profile
30200013 Party from selection screen
Task
TS30000020
TS70008037
TS60001307
TS00007989TS00008070
TS00008068
TS00008074
TSnnnnnnnn
TS70008373
TS30000078TS70008125
TS30200108
EDIM
EDIN
EDIP
EDIOEDIX
EDII
EDIY
application
EDIL
EDISEDIR
RSEIDOCM
Process
code
All application tasks can be found by the logical message as search term!
H t Ch R l R l ti
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 28/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 34
How to Change Role Resolution
Create a new standard role. This
comprises the implementation of a
function module.
Copy the standard task to a new task
for error notification.
Change the default role for agent ofthe new task to the standard role
created in step 1.
Activate the triggering event of the
new task.
Deactivate the triggering event of the
standard task.
Role resolution
E l f U ‘ I b
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 29/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 35
Example of an User‘s Inbox
W kit E i EDI b t
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 30/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 36
Workitem: Error in EDI subsystem
A change of status is triggered
by an EDI subsystem because
of translation error(s).
W kit St t T iti P di
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 31/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 37
Workitem: Status Transition Pending
Change of status triggered by anEDI subsystem is pending for more
than 2.5 hours (end time...). This is
dedected by program RSEIDOCM.
EDI Certification
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 32/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 38
EDI Certification
Certified process
Purchase Order, out
Customer order, in
Order confirmation, out
P.O. Acknowledgement, in
Certified functionality
file interface w/ RFC
outbound IDoc
status report
inbound IDocSystem R/3 System R/3
Document
IDoc
SubsystemSubsystemTransaction
IDoc
Agenda
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 33/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 39
Monitoring and
Notification by Workflow
Processing
Monitor
Notification
Exercises for notification
Agenda
Exercises for Notifications
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 34/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 40
Exercises for Notifications
E D I s u b s y s t e m
I D o c I n t e r f a c e
IDoc outbound
e.g. SYIDOC
Status report
via STATUS
Exercise 1: Start Up
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 35/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 41
Exercise 1: Start-Up
A partner profile to send documentation of IDoc types to user TECHED is maintained.
The partner profile in outbound parameters is set-up for logical message SYIDOC and
IDoc type SYIDOC01. The partner profile in inbound parameters is set-up for logicalmessage STATUS.
All users are assigned to organizational unit EDI department (50010120) for receiving
notifications on status report.
Create documentation for IDoc type TXTRAW01 via transaction WE60, and check with
one of the monitor programs that the IDoc exists (note the IDoc‘s number).
Repeat step 3.
After that exercise there are 2 IDocs in status „03“ on the database for each group.
Exercise 2: Create Status Report
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 36/37
SAP Labs, Inc. 1999 ASUG/EC (Thomas Becker) / 42
Exercise 2: Create Status Report
You plan to simulate the status report by transaction WE19 (the Test Utility).
In WE19 select radio button „via message type“ and enter STATUS. Now select „Create“
and enter the editor. First position to the control record by selecting the top line. Populate the control record
fields as follows:
Receiver: Port = SAP<SID>, Partner number = BC621-nn, Partner type = US
Sender: Port = SUBSYSTEM, Partner number = TECHED, Partnertype US
Message: Message type = STATUS
Next position to the segment by selecting the E1STATS line. Populate the segement
fields as follows:
Table structure = EDI_DS40, Client = <client>, IDoc number = <from exercise 1>
Date and time of status error in format CCYYMMDD and HHMMSS
IDoc status = 05, 07, 09, or 11 for error notification
Additional fields are conditional as well as further status to that IDoc number.
The STATUS IDoc should have reached status „53“.
1 out of the 2 IDocs from exercise 1 got a new status 05, 07, 09, or 11. For that IDoc a
notification can be found in your inbox. Please note that you see all notifications from all
the groups around you!
Exercise 3: Create Alert Notification
8/14/2019 Idoc Notification by Workflow and Monitoring
http://slidepdf.com/reader/full/idoc-notification-by-workflow-and-monitoring 37/37
Exercise 3: Create Alert Notification
You plan to watch IDocs pending in status „03“. For that purpose you schedule report
RSEIDOCM.
Go to transaction SE38, enter the report‘s name RSEIDOCM and choose „Execute“.
On the selection screen you have to enter the following data:
Recipient of notification: Enter your user name BC621-nn and type = US
Calculate the window to be watched by start and end time
The critical IDoc numer
The status group.
If you watch for IDocs in status „03“, the status group code is „3“.
The alert notification can be found in your inbox. By executing the work item you see the
situation as monitored during RSEIDOCM execution. Selecting „refresh“ updates the
situation and allows to branch onto the IDocs.