M 04

Workflow - Inside
Alan Rickayzen
SAP AG
®
 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 1
1. Part Technology for Workflow Debugging
z Events
z Binding
z Methods
z Workflow system
z Agent assignment
z Diagnosis transaction
Page 1
Workflow System
Events
Application
Flow
Dataflow
RFC connections
User assignment
Legacy Systems BOR
®
Debug methods
z Event simulation
z Event log
z RFC queue
z Event creation in SWUE
z Instance linkage
Page 2
Event consequences
z Triggering workflows
z Terminating events
Wait steps
Asynchronous steps
Creating events
z Form inside a SAP user-exit

z Directly in your ABAP program
z Customer status management
z System status management (QM, ECM)
z Change documents
z Message control
z Human Resources tables
z Logistic Information System
Page 3
Event simulation
Events can be
activated
Event items
too
Error codes
Event log - SWEL
Object key
workflow
Not necessarily!
Page 4
Event trigger - SWUE
Set this flag to use

ABAP debugger
Event type linkage - SWE2 SWE_EVENT_MAIL
Avoid modifying
by hand.
Set to ‘NONE’ for synch debugging
Page 5
Event instance linkage
Compare key
with event log ®
Events: Problem avoidance
z Use BOR delegation.

z Document your events.
z Walk through the synchronization scenario.
z Only use parameters with events that you trigger
yourself.
Page 6
Binding
z Workflow step log (error class W8)

z Use the technical trace
Activate for a complete process
Several traces may be active at one time
Automatic retention period
Technical trace
Lines can be
marked permanently
ContBindExecute
shows the binding
The preceeding line

shows the direction®
Page 7
Technical trace: Binding 1
Result of
the binding
Technical trace: Binding 2
Error messages
Binding definition
Page 8
Binding: Problem avoidance
z Avoid automatic binding

(unless the flow is simple)
z Check flow container definition for redundant elements
z Use object attributes where possible
z Double-check multi-line elements.
Methods
z Test with transaction SWUH

z Test with background user
(wf_batch) if possible
z Test with standard user
Page 9
Test method - OSS note 83496
Debug switch
Navigation Input/Export
parameters
Exception
Workitem status
Exception from method

Erroneous
Page 10
Methods: Problem avoidance
z Use parameters,
never use secret container elements.
z Use exceptions wherever possible.
z Avoid standard exception macros other than
exit_return.
z Take care distinguishing between table/single element
items.
swc_get_element, swc_get_table_element, swc_set_element,
swc_set_table_element
Workflow
z View step log

z View workitem history
z View workitem exception
z Object links
Page 11
Workitem technical information
Step log
History
Page 12
Error analysis
Error category
Action to perform
Object link navigation
Application
Application
transaction
transaction
Object
Object links
links
Related
Related Process
Process
workitems
workitems participants
participants
and
and flows
flows
Application
Application Related
Related
transaction
transaction Objects
Objects
Page 13
Object links
Object links
from application
(QM/PM/SM, EC,FI)
®
Flow version: prior to 4.0 OSS Note 125400
Workflow version
visible in the
flow container
Page 14
Flow version: 4.0 onwards
Flow Version
SWI1 started with

‘additional data’ flag
Workflow: Problem avoidance
z Take care with deadlines

z Double-check synchronization
z Define an administrator
z Show step type in description
(b) : background
(pfe): Par for each
(as): Asynchronous
z Highlight BDC methods for upgrade testing
e.g. CreateInBackgroundBDC
Page 15
Agent assignment
z Break-point in function module

z Test role under different users
(including wf_batch)
z Check agent assignment from the workitem
Agent assignment: Problem avoidance
z Avoid general tasks.

z Avoid the flag ‚error on failure‘.
z Don‘t forget to refresh the
organization buffer
and task profile index
when testing
Page 16
Diagnosis Transaction: SWUD
z List of last used workflows

z 2 main solution strategies
z Test platform
Diagnosis transaction
View flow
directly
Select for
analysis
Page 17
Intelligent Diagnosis
Diagnosis according
to flow definition
Test platform
Appropriate
tools
View components
directly
Page 18
2. Part: Performance Tuning for Workflow
z Workflow performance
z Workflow administration
z Workflow archiving
SAP User Groups

Customers committed to SAP Business Workflow® are
organized in work groups.
Currently those groups exist in the United States and Germany
z American SAP User Group (ASUG)
http://www.asug.com/
z Deutsche SAP Anwender Gruppe (DSAG)
After customer authorization in SAPNet at

http://www.sap.com use the alias
USERGROUPS-DSAG
Get information at bpt@sap-ag.de ®
Page 19
Improving Performance
z Development criteria
z Workflow runtime environment
z Inbox
z Coming up for free (4.5A)
Check data before starting a flow
Check function module
QQWF_EVENT_NOTIF_CREATED
Page 20
Start workflow directly
z Start workflow with a function module rather than via

an event.
sww_wi_start_simple
sww_wi_start
z Consider effects on synchronous chains.
z Document in the workflow how it is started.
Reduce workflow steps
z Use one method in place of many.

E.g. ‘Send mail’ to multiple users
E.g. Merge background steps together
Methods may call other methods
z Use work queues instead of par-for-each.

Background methods
Function group SWZA
Page 21
Avoid terminating events
z Replace asynchronous methods with synchronous

methods
Advantage: less rfc overhead
Disadvantage: Less control over flow
Has the step really finished?
Disadvantage: Synchronization problems.
Disadvantage: Step must be executed from inbox.
Optimize workflow data
z Use BOR attributes instead of container elements

E.g. &PO.purchasegroup.phone&
z Replace reading/calculating background methods with

virtual attributes
z Buffer attributes in BOR definition

E.g. ‘if order_list[] is initial.
Perform get_order_list....
Page 22
Optimize workflow data (cont’d)
z Avoid large structures in containers

Reduces database access (one line per field)
Reduces DDIC overhead
no ABAP code generation
reduced DDIC database queries
z Do not export multiline container elements
Database update instead of a delete + insert
Summary: Improving Performance
z Check data before starting a flow (Check function may

append to the event container).
z Start workflow directly
rather than via an event.
z Use one method in place of many.
z Replace simple background methods
with virtual attributes.
z Reduce container size/access
Page 23
Improving Performance: System
z Switch off event log

(check current installation).
z Archive and delete old workitems.
z Avoid bursts of activity to avoid:
blocking the applications servers
job planning when the RFC queue is full.
Distribute work
z Trigger flows via separate logical destinations.
Process 1
started here
RFC_server1
Application
Server 1
Update Task
Application
Server 2 RFC_server2
Workflow
Process 2
started here
started here
Page 24
Distribute work-processes
z Define separate R/3 RFC destinations

that point to specific servers.
z Assign these RFC destinations to
the main events.
Process 1
RFC_server1 started here
RFC_server2
Process 2 ®
started here
Specify Workflow Server
WS001
RFC_server1 started here
RFC Destination
WS001
RFC_server1 RFC_server2
WS002
started here
Page 25
Isolate Workflow Processes
z Separate application server

z RFC background
destination
(workflow_local_ccc)
routes to one server.
z Ignore
customizing warning.
Workflow
Server
Summary for Improving Performance: System
z Deactivate event log.

z Archive workitems.
z Avoid event bursts.
z Reroute workflows away from
- the update-task server
- the application servers.
z Update database indices periodically.
Page 26
OSS Performance notes
z 98407 Workflow performance tips

z 72032 Database indices
Improving Performance: Inbox
z Avoid general tasks.

z Configure inbox without extra columns
Task, Overdue, Todo-by-date,
Todo-by-time, Group, Object.
z More detailed task assignment in the organizational
model
(use positions instead of jobs if necessary)
Page 27
Workflow Performance: Release 4.0
z Better RFC handling (factor 3)

z Better Inbox performance
(direct selection)
z Workflow system optimized
Runtime RFC calls
3.0C 3.0D
FI FI Execution
WI
WI Execution
3.0C
WI Confirmation
D 3.1G
BI1
BI Execution
B1 3.0C
BI Confirmation
3.0D
3.0C BI2
B2
BI Execution
3.1G
3.0C BI Confirmation
3.0D
Page 28
Administration
z Customizing in the productive system

z Workflow administration duties
Customizing SWU3
Delete jobs by hand

if necessary
Maintain separate
number ranges in the
production system
Page 29
Deadline Monitoring Exceptions
z Many deadlines
Switch from single case-oriented to permanent
z Several instances of SWWDHEX
Delete all instances with job overview (SM37)
Reschedule using SWU3
z No instances of SWWDHEX
Check selection with job overview (SWU3)
Reschedule using SWU3
Workitem Analysis
Always
Always check
check
Error Deadline that
that your
your
overview overview
deadline
deadline
calculation
calculation is
is 33
SWI2 minutes
minutes in
in
advance
advance ofof sy-
sy-
uzeit!
uzeit!
Create a task group

for your processes
Page 30
Tasks without Agents
SWI4
Workitems without Agents
rhwfotsk
Use the task’s

default role to
return the
workflow
administrator!
Page 31
RFC queue
SM58
Pay special attention

to workflow_local...
Check
Check for
for dumps
dumps for
for
the
the user
user WF-BATCH!
WF-BATCH!
Pay special attention to Batch
Batch items
items Status
Status
wf-batch
‘Started’
‘Started’ (SWI1)
(SWI1)
Workflow table monitor
SMUF
Page 32
Summary: Administrator Duties
z Monitor errors/deadline.
z Workitems without agents.
z Monitor RFC queue and short dumps
(first productive week).
z Monitor workflow table space.
Archiving and Deleting Workflows
z Delete in test system via reports RSWWWIDE and

RSWWHIDE
z Delete in production system only via archiving object
WORKITEM
z Example report to read archive RSWWARCR
z Do not import back into the system
Page 33
Archive - Delete
Report RSWWWIDE Archiving object

WORKITEM
Possible in every status Only possible if status is
COMPLETED or CANCELLED
Immediate start without Authorization check via
authorization check TA SARA
Immediate deletion from Archiving and deletion carried out
the database in two separate steps
Execute in dialog or Execute in batch at
in batch a later time
Log data is not deleted Log data is archived and deleted
(use RSWWHIDE afterwards)
Archiving
SARA
Workitem object
does not archive notes
(but they are deleted)
Page 34
Archiving
SARA
Process-specific archiving
T 00005
Better Processes through Technology

®
Page 35

M 04

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

M 04

Загружено:

Авторское право:

Доступные форматы

Workflow - Inside

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 1

1. Part Technology for Workflow Debugging

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 2

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 3

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 4

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 5

z Form inside a SAP user-exit

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 6

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 7

Event log - SWEL

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 8

Set this flag to use

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 9

Event type linkage - SWE2 SWE_EVENT_MAIL

Set to ‘NONE’ for synch debugging

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 10

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 11

Events: Problem avoidance

z Use BOR delegation.

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 12

z Workflow step log (error class W8)

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 13

The preceeding line

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 14

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 15

Technical trace: Binding 2

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 16

z Avoid automatic binding

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 17

z Test with transaction SWUH

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 18

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 19

Exception from method

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 20

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 21

z View step log

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 22

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 23

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 24

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 25

Object link navigation

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 26

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 27

Flow version: prior to 4.0 OSS Note 125400

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 28

SWI1 started with

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 29

Workflow: Problem avoidance

z Take care with deadlines

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 30

z Break-point in function module

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 31

Agent assignment: Problem avoidance

z Avoid general tasks.

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 32

z List of last used workflows

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 33

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 34

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 35

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 36

 SAP AG 1998 M4 SAPTechEd ’98, Karlsruhe (Alan Rickayzen) / 37