BC601 en 46C FV

6$3%XVLQHVV:RUNIORZ
%XLOGDQG8VH
%&
6$3%XVLQHVV
:RUNIORZ%XLOGDQG
8VH SAP AG 1999
n R/3 System
n Release: 4.6 C
n November 2000
n Material number: 5004 2078
&RS\ULJKW
&RS\ULJKW6$3$*$OOULJKWVUHVHUYHG
1HLWKHUWKLVWUDLQLQJPDQXDOQRUDQ\SDUWWKHUHRIPD\
EHFRSLHGRUUHSURGXFHGLQDQ\IRUPRUE\DQ\PHDQV
RUWUDQVODWHGLQWRDQRWKHUODQJXDJHZLWKRXWWKHSULRU
FRQVHQWRI6$3$*7KHLQIRUPDWLRQFRQWDLQHGLQWKLV
GRFXPHQWLVVXEMHFWWRFKDQJHDQGVXSSOHPHQWZLWKRXWSULRU
QRWLFH
$OOULJKWVUHVHUYHG
SAP AG 1999
7UDGHPDUNV
n Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
n Microsoft, WINDOWS, NT, EXCEL, Word and SQL Server are registered trademarks of
Microsoft Corporation.
n IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390,
AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.
n ORACLE is a registered trademark of ORACLE Corporation, California, USA.
n INFORMIX-OnLine for SAP and Informix Dynamic ServerTM are registered trademarks of
Informix Software Incorporated.
n UNIX, X/Open, OSF/1, and Motif are registered trademarks of The Open Group.
n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide
Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of
Technology, 545 Technology Square, Cambridge, MA 02139.
n JAVA is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA
94303 USA.
n JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
n SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com
Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP
Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit,
SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries
all over the world. All other products mentioned are trademarks or registered trademarks of their
respective companies.
n Design: SAP Communications Media
%XVLQHVV,QWHJUDWLRQ7HFKQRORJLHV,
/HYHO /HYHO

2 days 5 days 3 days
SAP Business SAP Business SAP Business Workflow
Workflow - Introduction Workflow - Workflow - Programming
Build and Use

3 days
SAP ArchiveLink
2 days

3 days ADK - Retrieval
programming Archiving
Data Archiving
2 days
Data Archiving Retention
Tool (DART)

2 days
Web connection
SAP Business Connector
SAP AG 1999
%XVLQHVV,QWHJUDWLRQ7HFKQRORJLHV,,
/HYHO /HYHO

3 days
Application Link
Enabling (ALE)
Technology
6
2 days 1 day /0"&#"&1$+23"%*
SAP IDoc Interface SAP IDoc Interface -
Technology Development
57
3 days 4 days
Business Integration EDI Interface
Technology

5 days
Data Transfer 4 +
2 days
Communication
!#"%$&
5 days Interfaces in ABAP
Programming with 5(( '()+*",,.- *
BAPIs in Visual Basic 5 days
Programming with
5 days BAPIs in JAVA
R/3 Interface and BAPI
Programming in C++
SAP AG 1999
&RXUVH3UHUHTXLVLWHV
l 6$35%DVLV7HFKQRORJ\
l %&%XVLQHVV:RUNIORZ,QWURGXFWLRQ
SAP AG 1999
7DUJHW*URXS
l $XGLHQFH
8 :RUNIORZSURMHFWWHDP
l 'XUDWLRQGD\V
SAP AG 1999
6RXUFHVRI,QIRUPDWLRQ
l 6$3+HOS&'
l $SSOLFDWLRQFRPSRQHQWGRFXPHQWDWLRQ
UHJDUGLQJZRUNIORZWHPSODWHV
l ,'(6GRFXPHQWDWLRQ
l &RPSUHKHQVLYHZRUNIORZWXWRULDOV
l ,QIRUPDWLRQIURP6$3KRPHSDJHRQWKH
,QWHUQHW
l 2662QOLQH6HUYLFH6\VWHP
l 7UDLQLQJ
SAP AG 1999
&RXUVH2YHUYLHZ
&RQWHQWV
l &RXUVH*RDO
l &RXUVH2EMHFWLYHV
l &RXUVH&RQWHQW
l &RXUVH2YHUYLHZ'LDJUDP
l 0DLQ%XVLQHVV6FHQDULR
SAP AG 1999
SAP AG
SAP AG BC601 1-1

&RXUVH2EMHFWLYHV
7KLVFRXUVHZLOOSUHSDUH\RXWR
l *HQHUDWHH[HFXWDEOHZRUNIORZWHPSODWHV
l 0RQLWRUWKHUXQWLPHHQYLURQPHQW
l (QKDQFH6$3VWDQGDUGREMHFWW\SHVIRUVSHFLILF
FXVWRPHUV
l 8VHZL]DUGVWRVXSSRUWWKHGHVLJQSURFHVV
l )RUPVWDWHPHQWVDERXWWKHLQWHJUDWLRQRIWKH
ZRUNIORZLQWKH,QWHUQHW
SAP AG 1999
SAP AG BC601 1-2

&RXUVH2EMHFWLYHV
$WWKHFRQFOXVLRQRIWKLVFRXUVH\RXZLOOEHDEOHWR
l &UHDWHDQRUJDQL]DWLRQDOSODQDQGOLQN
RUJDQL]DWLRQDOREMHFWVWRWDVNVLQWKHZRUNIORZ
l (QKDQFHVWDQGDUGREMHFWW\SHV
l *HQHUDWHWDVNV76
l *HQHUDWHZRUNIORZWHPSODWHV:6
l 0RQLWRUHQKDQFHLQWHUIDFHV FRQWDLQHUV
l 0RGHOGHDGOLQHPRQLWRULQJ
l 'HWHUPLQHDQGDFWLYHO\OLQNDWULJJHULQJHYHQWIRU
DZRUNIORZ
l 7ULJJHUHYHQWVZLWKLQDSSOLFDWLRQV
l 8WLOL]H:RUNIORZ:L]DUGV
l 6WDUWVSHFLILFUXQWLPHUHSRUWV
SAP AG 1999
SAP AG BC601 1-3

&RXUVH&RQWHQW
3UHIDFH
Unit 1 &RXUVH2YHUYLHZ Unit 8 &RQWDLQHUV

Unit 2 ,QWURGXFWLRQ Unit 9 5RXWLQJ
Unit 3 &XVWRPL]LQJ Unit 10 'HDGOLQH0RQLWRULQJ
Unit 4 :RUNIORZ'HILQLWLRQ Unit 11 (YHQWV
Unit 5 %XVLQHVV2EMHFW%XLOGHU Unit 12 :RUNIORZ :L]DUGV
Unit 6 7DVNV Unit 13 :RUNIORZDQGWKH
,QWHUQHW
Unit 7 0RQLWRULQJDQG$QDO\VLV
$SSHQGL[
SAP AG 1999
SAP AG BC601 1-4

&RXUVH2YHUYLHZ'LDJUDP
&RXUVH2YHUYLHZ &RQWDLQHUV
,QWURGXFWLRQ 5RXWLQJ
&XVWRPL]LQJ 'HDGOLQHV
:RUNIORZ'HILQLWLRQ (YHQWV
%XVLQHVV2EMHFW%XLOGHU :RUNIORZ:L]DUGV
7DVNV :RUNIORZDQGWKH,QWHUQHW
0RQLWRULQJDQG$QDO\VLV $SSHQGL[
SAP AG 1999
SAP AG BC601 1-5

0DLQ%XVLQHVV6FHQDULR
l ,QSUHYLRXVVRIWZDUHSURMHFWV\RXKDYHGRQHVRPH
SURJUDPPLQJ1RZ\RXZDQWWRNQRZZKDWLV
QHFHVVDU\WREXLOGDZRUNIORZLQ6$35
l <RXZDQWWREXLOGDZRUNIORZLQ6$35WRVXSSRUW
DPDWHULDOVPDQDJHPHQWEXVLQHVVSURFHVV
l $QRWDEOHIHDWXUHRIWKH6$3%XVLQHVV:RUNIORZLV
WKHFRQQHFWLRQWR\RXURUJDQL]DWLRQDOXQLW
&UHDWHDPDSRI\RXURUJDQL]DWLRQDOSODQ
SAP AG 1999
SAP AG BC601 1-6

,QWURGXFWLRQ
&RQWHQWV
l 5HYLHZRI6$3%XVLQHVV:RUNIORZ
WHUPLQRORJ\
l ,QWURGXFWLRQRIWKHH[DPSOHZRUNIORZ
WKDWZLOOEHFUHDWHGGXULQJWKHFRXUVH
l &UHDWLRQRIDQRUJDQL]DWLRQDOSODQ
SAP AG 1999
SAP AG BC601 2-1

,QWURGXFWLRQ8QLW2EMHFWLYHV
$WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWR
l /LVWZRUNIORZFRPSRQHQWV
l ([HFXWHDSUHGHILQHGZRUNIORZ
l &UHDWHDQRUJDQL]DWLRQDOVWUXFWXUH
SAP AG 1999
n This unit is a short review of BC600 SAP Business Workflow - Introduction
SAP AG BC601 2-2

SAP AG 1999
SAP AG BC601 2-3

0DLQ%XVLQHVV6FHQDULR
l ,QSUHYLRXVVRIWZDUHSURMHFWV\RXKDYHGRQHVRPH
SURJUDPPLQJ1RZ\RXZDQWWRNQRZZKDWLV
QHFHVVDU\WREXLOGDZRUNIORZLQ6$35
l <RXZDQWWREXLOGDZRUNIORZLQ6$35WRVXSSRUW
DPDWHULDOVPDQDJHPHQWEXVLQHVVSURFHVV
l $QRWDEOHIHDWXUHRIWKH6$3%XVLQHVV:RUNIORZLV
WKHFRQQHFWLRQWR\RXURUJDQL]DWLRQDOXQLW
&UHDWHDPDSRI\RXURUJDQL]DWLRQDOSODQ
SAP AG 1999
SAP AG BC601 2-4

:K\6$3%XVLQHVV:RUNIORZ"
6$3%XVLQHVV:RUNIORZ
l ,VDWRROIRUWKHDXWRPL]DWLRQ l ,VWDLORUHGWRFXVWRPHU
RIEXVLQHVVSURFHVVHV QHHGVDQG
GHYHORSPHQWV
l ,VQRWWLHGWRDQ\SDUWLFXODUDSSOLFDWLRQ
l 2SHUDWHVXQLIRUPO\DFURVVDSSOLFDWLRQV
l &RRUGLQDWHVDOOSDUWLFLSDWLQJWDVNV
l 3URYLGHVXVHUVZLWKDFWLYHVXSSRUW
6$3%XVLQHVV:RUNIORZ

5

SAP AG 1999
n You can use the SAP Business Workflow system to support your enterprise processes in R/3.
n The SAP Business Workflow system is able to combine steps from different applications into one
process.
n The SAP Business Workflow system supplies the end user with all the information required for the
next step.
n You can change the SAP workflows provided, or you can build your own workflow definitions.
SAP AG BC601 2-5

(YHQW'ULYHQ:RUNIORZ
Customer
Order
Material
Purchase
order
Vendor
SAP AG 1999
n Workflows can either be started by events, explicitly in start transactions, or by using external forms,
(for example on the Internet).
n A workflow can start another workflow by triggering an event.
n The individual steps of a workflow are represented by tasks (TS).
The tasks are based on methods of business objects that are defined in the Business Object
Repository, and refer to entities and relations in the R/3 data model.
n Steps of a workflow can also be controlling steps, for example, "waiting for an event", "container
operation", "loop", ...
SAP AG BC601 2-6

:RUNIORZ$UFKLWHFWXUH
2UJDQL]DWLRQDOXQLW
3RVLWLRQV :KRLVH[HFXWLQJWKH
5ROHV 8VHU SURFHVVLQJVWHSV"
$FWLYLW\ 2UJDQL]DWLRQ
JURXSV 0DQDJHPHQW
:KLFKVWHSVGRHVWKH
SURFHVVFRQWDLQ"
:RUNIORZ%XLOGHU
0HWKRGV !#"%$ $WWULEXWHV %XVLQHVV

REMHFWW\SHOHYHO
3XUFKDVH
(YHQWV %$3, %XVLQHVV2EMHFW
5HSRVLWRU\
:KDWLVVWDUWHG"
$%$3RI
GLIIHUHQW
DSSOLFDWLRQV
SAP AG 1999
n On the level of the SAP business object type, all services are provided in the form of executable
methods.
Methods can be realized as BAPIs. You can then call them from outside the system.
BAPIs have an established static interface.
Methods are related to functions from applications in the SAP R/3 System.
The tool for maintaining business object types is the BOR (Business Object Repository).
n The process level describes the business process in a sequence of individual steps. All the steps
together form the workflow definition.
An individual step can refer to a method in the BOR, but can also serve to control the process,
for example to allow loop processes or carry out container operations.
The tool for maintaining the process level is the Workflow Builder.
The Workflow Management System evaluates the process level at runtime.
n The organizational level provides the link to the organizational chart.
Each task that can be executed within a workflow has a group fo possible agents,
By making further entries, this group can be reduced to the agent in the workflow step.
The selected agents receive a work item (= representative of the task at runtime)
in their Business Workplace at runtime.
n If the work item is executed, the corresponding method of the business object type is started.
SAP AG BC601 2-7

:RUNIORZ3URMHFW6WHSV
,GHQWLI\WKH%XVLQHVV3URFHVV
,GHQWLI\WKH%XVLQHVV3URFHVV
'RHVDQ6$3
<HV ZRUNIORZDOUHDG\ 1R
H[LVWLQWKH
VWDQGDUGV\VWHP"
8VHWKH6$3ZRUNIORZ &UHDWHWKHZRUNIORZ
,PSOHPHQWWKHZRUNIORZ
7HVWWKHZRUNIORZ
SAP AG 1999
n When you have identified a process in your enterprise that you want to structure using a workflow,
first clarify whether SAP delivers a template for this process.
How to find a template and how to adapt it for execution are covered in the course BC600.
n The course BC600 also covers the changes that are possible within a configuration, without copying
the standard template.
n If you find a template, the process logic must be suitable.
You then require the knowledge from this course. You can use the template as an example after you
have created a copy.
n Only if you do not find a suitable template, do you have to plan and implement the workflow from
beginning to end.
SAP AG BC601 2-8

:RUNIORZ'HVLJQ7RS'RZQ
f g* ''h* )'

@BA ?; C>8D32E-=F9 A ?G?
ij ),
:RUNIORZ
HJI ; 9 I
Workflow

& /')%* +,-* .) %$ E A ?K =>8?;ML;ON(; :P; A ?
"%$ ) Definition Q =SRT=>6 IGUV.A 5-=>E
: IGA ? 9 A 8 U EW; =FX
f%c!#* ),h* )'
ij ),
Y#E A U :A
& (')%* +,-* .)$

H =>EWZ5WN =.[
Task
"%$ )

\ = [^]D6?:

: IGA : U ?Z?
L A_QTA 5<;(8 AGQ X
Object Type
\ =.[^]D6?:`: IGA

=>L a A 9:b:cRbK A
L A_QTA 5<;/8 AGQ X
02143
5768.9:<; =>8? HdI ; 9 I W5 6b8.9:<; =e8?

? I =>6N Q : IGA
] A : I = Q /; 8 V =>N V A X
SAP AG 1999
n You have selected a business process and divided it into individual steps that can be executed in a
workflow.
n Find the suitable object types in the Business Object Repository.
Check that all required methods, attributes and events are available.
If not, you need to enhance the object type.
n Check whether there are already tasks in the system for your desired steps.
If not, you need to define new tasks.
n Organizational level agent assignment:
You have determined organizational responsibilities and found the corresponding entries in your
organizational plan. An agent can be an SAP user, an organizational unit, position, job, or activity.
You may need to create the specific workflow units additionally in your organizational plan, or,
using the organizational management, you may need to create links to existing units.
n Agent assignment:
In the definition of the tasks you have to enter the largest possible agent group (= SRVVLEOHagents).
In the workflow step used by the task, you reduce the possible agents according to demand. The
intersection between the possible agents and those recognized in the workflow step forms the
VHOHFWHG agents.
SAP AG BC601 2-9

'HVLJQWKH9DFDWLRQ$SSURYDO:RUNIORZ
3URFHVV :KDW:KR:KHQ"
:KHQHYHUDQHPSOR\HHFUHDWHV
DQRWLILFDWLRQRIDEVHQFH
Event
7KHKHDGRIGHSDUWPHQWVKRXOGGHFLGH $SSURYH
ZKHWKHURUQRWWRDSSURYHWKHUHTXHVW UHTXHVW
,IDSSURYHGWKHFUHDWRURIWKHUHTXHVW 6HQG0DLO
UHFHLYHVDPHVVDJH
,IQRWDSSURYHGWKHFUHDWRURIWKHUHTXHVW
'HFLVLRQDERXW
LVDVNHGZKHWKHUWKHUHTXHVWVKRXOGEH
UHTXHVW
ZLWKGUDZQRUFKDQJHG
,IWKHUHTXHVWLVWREHFKDQJHG &KDQJH
WKHFUHDWRUUHFHLYHVWKHUHTXHVW UHTXHVW
DJDLQWRPDNHWKHFKDQJHV
5HVXEPLW
7KHVFHQDULRVKRXOGWKHQEHUHSHDWHGLI UHTXHVW
FKDQJHVDUHPDGH
SAP AG 1999
n For each step you should ask yourself:

What work has to be done?
Who is doing the work? (only for dialog steps)
Which message text do you want to send?
n For each event you should ask yourself:
When is this event generated?
Which SAP application generates this event?
SAP AG BC601 2-10

'HILQH9DFDWLRQ$SSURYDO:RUNIORZ
:KHQ"
kT
. l.
l.mm n ,
o ( ,M p
:KDW:KR"
qs
r""%/j
M/l.mn ,
:KR" t
T,
qs
r"
B "%/j p
qr
B"
"%/(j p
7RZKRPH[SUHVV
)pyxr* $
uGnGv o * n* G) w
v T$ ,c/M
%) ' xB
r%* $|n),
:KDWPHVVDJH"
/Ml.mn , ze c { l.mn ,
/2
v $ ,/ %)'
:KDW:KR"
Ml.mn, ze
/{ l.mn,
k l.m n , k .l.mn,
p
$ ,M p o )'' p
{
:KDW"
/RRSXQWLO"
kT}On%m~!#* ,
/l.m n,
t
T
n
f%c!#* ),M
G h7h$
S
G %h7Wh$
,/MM!
4* ) ,M/ p
y
SAP AG 1999
n During the workflow design, it is recommeneded that you write the answers to the questions on the
last slide next to the box. The answers will guide you towards the workflow definition requirements:
1. A triggering event:
request created
2. Three tasks based on methods of object type )250$%6(1&
Approve request
Change request
Delete request
3. A task based on a method of object type 6(/),7(0
Send mail
4. A user decision
5. A loop, which will be controlled by a loop-flag.
SAP AG BC601 2-11

([DPSOHRIDQ2UJDQL]DWLRQDO8QLW'LDJUDP
&RQQHFWH[LVWLQJRUJDQL]DWLRQDO 2UJDQL]DWLRQDOVWUXFWXUH 7KHUHLVRQO\RQH

VWUXFWXUHWRZRUNIORZ DYDLODEOH ZRUNIORZRULHQWHG
$GGLWLRQDO RUJDQL]DWLRQDOVWUXFWXUH
ZRUNIORZVWUXFWXUH LQWKHHQWHUSULVH
(QWHUSULVHVWUXFWXUH
),GHSDUWPHQW
$FFRXQWVSD\DEOH
3RVLWLRQV 'HGLFDWHGJURXSIRU 'HGLFDWHGJURXSIRU
EXVLQHVVSURFHVV EXVLQHVVSURFHVV
$FFRXQWVUHFHLYDEOH 3XUFKDVHUHTXLVLWLRQ $FFRXQWVSD\DEOH
3RVLWLRQV 3RVLWLRQIRU 3RVLWLRQDSSURYDO
&RQWUROOHURI3ODQW$ LQHQWHUSULVH,
&RQWUROOLQJGHSDUWPHQW
'LVWULFW$ 3RVLWLRQIRU 3RVLWLRQDSSURYDO
3RVLWLRQV &RQWUROOHURI3ODQW% LQHQWHUSULVH,,
'LVWULFW%
3RVLWLRQV

SAP AG 1999
n If the agents of the individual workflow steps are determined using the customer-specific
organizational diagram, your agent assignment remains flexible to change.
n You have different options to connect your workflows to the SAP organizational plan.
n ([DPSOH:
There is only one chart for the whole company.
All workflows have to be connected to organizational objects from this structure.
Using this option there are no specific structures just for the workflow.
n ([DPSOH:
HR administrates the general structure for all employees in the enterprise.
For the business process, there is a small specific structure for supporting the workflow.
n ([DPSOH:
There is not (yet) a general HR structure for all employees.
To support the workflows there will be one small structure for each process.
SAP AG BC601 2-12

)HDWXUHVRI6LPSOH0DLQWHQDQFH
PDLQIXQFWLRQV
YE AGU : A =2EC U 8b; U :<; =>8 U 8 Q ?G: U 5h5<;(8 C/[=>EWZ 5PN =.[
&UHDWHRUJDQL]DWLRQDOXQLW
&UHDWHSRVLWLRQ
$VVLJQWDVNV
-g-/
SAP AG 1999
n The maintenance of SAP organizational management is available as a Basis component.

Path: SAP EASY ACCESS - Tools - Business Workflow - Development - Environment -
Organizational Management - Simple maintenance.
n You work with a main window and three main functions. Each function is determined for a
particular group of maintenance activities.
n The "Create Organizational Unit" icon allows you to create and maintain the organizational structure
for your organizational plan.
n The symbol "Create position" allows you to create the positions from new as an element of your
organizational plan. The Tasks function allows you to create, maintain and view task profiles for
jobs, positions, and users.
n &DXWLRQ
+5UHFRJQL]HV6$36\VWHPXVHUVDVZHOODVSHRSOHDVKROGHUVRISRVLWLRQV
7KHZRUNIORZUHFRJQL]HVRQO\6$36\VWHPXVHUVDVYDOLGDJHQWV
,IWKHH[LVWLQJ+5RUJDQL]DWLRQDOVWUXFWXUHLVWREHXVHGIRUWKHZRUNIORZHDFKSHUVRQLQWKH
PDVWHUUHFRUGPXVWKDYHHQWHUHGWKHLQIRW\SHFRPPXQLFDWLRQW\SH6$36\VWHP
XVHU8VLQJWKLVLQIRW\SHDQ6$36\VWHPXVHULVDVVLJQHGWRWKH+5SHUVRQ
7KHHQWULHVDUHPDGHE\PDLQWDLQLQJWKH+5PDVWHUGDWD
6$3($6<$&&(66+XPDQ5HVRXUFHV3HUVRQQHO0DQDJHPHQW$GPLQLVWUDWLRQ+5
0DVWHU'DWD0DLQWDLQ
SAP AG BC601 2-13

3RVLWLRQV
7DVN$SSURYH
YDFDWLRQUHTXHVW l 3RVLWLRQVDUHVSHFLILFWR\RXU
RUJDQL]DWLRQ
l 0XOWLSOHSRVLWLRQVPD\
SHUIRUPVLPLODUMREWDVNV
l (DFKSRVLWLRQW\SLFDOO\
UHSUHVHQWVRQHHPSOR\HHEXW
-RE&KLHI PD\EHSDUWLDOO\ILOOHGE\PRUH
WKDQRQH
3RVLWLRQ 3RVLWLRQ
&KLHI(XURSH &KLHI:HVW5HJLRQ
3RVLWLRQ
&KLHI(DVW5HJLRQ
SAP AG 1999
n A task can be assigned to one or more jobs. Jobs are general activity descriptions.
n Jobs are not designed to be held by employees.
It is the positions in your enterprise that are held by individual people.
n If a position is assigned to a job, the position inherits the tasks of the job, but can also have
additional tasks related to duties performed specifically by that position.
n One position may also be shared by several employees each working less than full time. For
example, two employees can occupy 60% and 40% of a position. The workflow regards both
employees as valid agents and ignores the percentage division of the job.
SAP AG BC601 2-14

&UHDWH2UJDQL]DWLRQDO3ODQ6LPSOH0DLQWHQDQFH
0DQXIDFWXULQJ
0DQXIDFWXULQJ 0H[LFR6DOHV
0H[LFR6DOHV
([HFXWLYH%RDUG
([HFXWLYH%RDUG 5HJLRQ
5HJLRQ
6WHS&UHDWHURRW 6WHS$GGLWLRQDO
RUJDQL]DWLRQDOXQLW RUJDQL]DWLRQDOXQLWV
6WHS 6WHS
$GPLQLVWUDWLYH
$GPLQLVWUDWLYH
DJHQW
&UHDWHSRVLWLRQ &UHDWHMREV
DJHQW $GPLQLVWUDWLYH
$GPLQLVWUDWLYH
0H[LFR6DOHV5HJLRQ
0H[LFR6DOHV5HJLRQ DJHQW
DJHQW
6WHS 6WHS
$VVLJQKROGHUV $VVLJQWDVNV

Februar

%` |yeG.(b_MOyb>..O(T
/LVD7KRPSVRQ
/LVD7KRPSVRQ
DGGMOTGT-M e2.>
SAP AG 1999
n The diagram above shows that the first step in simple maintenance consists of constructing the root
organizational unit. Once one organizational unit has been created, the appropriate organizational
units below it need to be created.
n Organizational units and jobs may be created in any order, but must exist before creating the related
positions.
n Jobs may exist in the job index, or may be created once the model contains an organizational unit.
n Positions are created after the appropriate job(s) are created in the job index.
n Tasks are assigned using jobs and positions.
n Holders are assigned to positions and not to jobs.
n From Release 4.6B onwards, you can only create jobs after positions. Steps 3 and 4 in the diagram
are swapped.
SAP AG BC601 2-15

$VVLJQLQJ:RUNIORZ7DVNV2UJDQL]DWLRQDO2EMHFWV
2UJDQL]DWLRQDOXQLW),GHSDUWPHQW
0DQDJHUMRE 7DVNV
7DVN 3RVLWLRQ),GHSWKHDG
User 1
7DVN 6HFUHWDU\MRE
7DVNV
3RVLWLRQ6HFUHWDU\
User 2
3RVLWLRQ),DGPLQLVWUDWRU
User 3
),HPSOR\HHMRE 7DVNV
3RVLWLRQ),DGPLQLVWUDWRU
User 4
SAP AG 1999
n All necessary tasks are created within the workflow definition, for example approve request, create
order, update customer master, and so on.
n A user is only authorized to process a work item during runtime if he or she is defined as a possible
agent for the task.
n This diagram shows all the basic options available for creating the connection:
Task 1: User 1 (by job)
Task 2: User 1, user 2 (by job)
Task 3: User 1, user 2, user 3, user 4 (by organizational unit)
Task 4: User 1, user 3, user 4 (by position and by job)
Task 5: User 2 (by job)
Task 6: User 3, user 4 (by job)
n The assignment of workflow task to organizational object is best performed using task maintenance
under additional data - maintain agent assignment (see the unit Tasks).
&DXWLRQ
$IWHUFUHDWLQJDQDJHQWDVVLJQPHQWWKHLQGH[IRUDJHQWDVVLJQPHQWPXVWEHUHJHQHUDWHG
%XWWRQ
*HQHUDWHLQGH[
ZLWKLQWDVNPDLQWHQDQFH
SAP AG BC601 2-16

:RUNIORZ&KDQJHWR0DWHULDO0DVWHU
0DWHULDO (QWU\LQ

&KDQJH'RFXPHQW
WDEOH
2OGPDWHULDOQR 2ULJLQDOBSDUW WULJJHUV

1HZBSDUW
/DE 30 (YHQW

=%86
,PSRUWSDUDPHWHUV 2OGB0DWHULDOBFKDQJHG
IRUWKHUROH
VWDUWV
2UJDQL]DWLRQDOXQLW
0DQXIDFWXULQJ
2UJDQL]DWLRQDOXQLW
3URGXFW0DQDJHPHQW :RUNIORZ
:RUNIORZ
3URGXFWPDQDJHUSRVLWLRQ 5ROH
'HWHUPLQH
+ROGHU-RQHV VXSHULRURI
7DVN'LVSOD\
7DVN'LVSOD\
$JHQWUHVSRQVLEOHSRVLWLRQ FKDQJHGRFXPHQWV
FKDQJHGRFXPHQWV
+ROGHU%M|UQ
7DVN'LVSOD\
7DVN'LVSOD\
5ROH
'HWHUPLQHUHVSRQVLEOHXVHUIRUODERUDWRU\30
PDWHULDO
PDWHULDO
SAP AG 1999
n General scenario for this process:

n Smith changes the material master 100-300. He or she enters the new value New_Part in the field
Old material number.
n A change document is generated. The event Material changed is consequently published in the
system. The event is part of the object type BUS1001.
n The published event triggers a workflow.
In the first task, the workflow displays the change document for the changed material to the superior
of the agent who changed the material master. In the second step, the material master is shown to all
who are responsible for the laboratory PM1.
This organizational responsibility is determined within the design process when defining a role.
In this case it is the members of an organizational unit.
SAP AG BC601 2-17

,QWURGXFWLRQ8QLW6XPPDU\
<RXDUHQRZDEOHWR
l %XLOGDQRUJDQL]DWLRQDOVWUXFWXUH
l /LQNZRUNIORZWDVNVWRFRPSRQHQWVRIWKH
RUJDQL]DWLRQDOVWUXFWXUH
l /LVWWKHLPSRUWDQWFRPSRQHQWVRIWKHZRUNIORZ
V\VWHP
l 'HILQHWKHVWUXFWXUHRIDZRUNIORZ
SAP AG 1999
SAP AG BC601 2-18

([HUFLVHV
8QLW,QWURGXFWLRQ
6$3%XVLQHVV:RUNIORZ&RPSRQHQWV
At the conclusion of these exercises, you will be able to:

List workflow components
Execute a predefined workflow
In previous software projects you have done some programming. Now

you want to check what you need to build an individual workflow in SAP
R/3. Your goal is to support a business process in the materials
management application.
As a warm up exercise, you are going to re-build one of the existing
workflow templates. You choose to follow a tutorial from the SAP online
help CD, which provides instructions for building the vacation request
workflow.
To better understand the terminology being used you will first review the
basics from the introduction workflow class.
1-1 You are invited to a meeting about workflows. Many of the other people present
have some misconceptions about workflows. They are relying on you to answer
their questions and concerns.
Below are some of the statements people made in the meeting. Determine which are
true and which are not.
1-1-1 SAP Business Workflow is a tool for automating business processes which
is not tied to any particular application but which operates uniformly across
different applications.
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
1-1-2 SAP Business Workflow coordinates all the participating tasks and provides
the user with active support.
1-1-3 SAP provides several workflow templates that you can use to match your
specific business requirements to a workflow.
SAP AG BC601 2-19

1-1-4 If a template does not exist that represents your business requirements, then
you must contact SAP to develop the requested business scenario.
1-1-5 SAP Workflow provides runtime tools for user interaction, process
characterization and control.
1-1-6 SAP Workflow uses the SAP Business Navigator as a tool for process
modeling and design of workflow definitions.
1-2 A lot of workflow terms were used in the meeting. Some of the people present did
not know the meanings of all of them. As the workflow expert, you must define
these words for everyone.
Using the list of terminology, ensure that everyone knows the appropriate term for
each statement about the workflow.
task standard task single-step task
SAP Workflow multi-step task workflow template
object method object type

work item manager workflow manager Workflow Builder
Business Workplace workflow definition
1-2-1 An__________________________ is the encapsulation of functionality and

behavior for performing defined business tasks.
1-2-2 The_________________________ refers to a generic description of an

object created at runtime. It includes the definition of key fields, methods,
attributes and events.
1-2-3 Any type of related information which can be accessed uniquely under an
identifying key is called___________________________.
1-2-4 ___________________________ refers to an object method or a manual

activity.
1-2-5 ___________________________ is a pre-defined workflow definition

supplied by SAP that defines a specific business scenario.
1-2-6 Interaction between the runtime execution of workflows and users

responsible for carrying out specific work to be done is managed by the
___________________________.
SAP AG BC601 2-20

1-2-7 A single-step task defined by the user or supplied by SAP is called a
___________________________.
1-2-8 A multi-step task defined by the user or supplied by SAP is called a

___________________________.
1-2-9 The ___________________________ is a tool that is used to define, access

and modify workflow definitions in a graphical format.
1-2-10 The technical implementation of a business process is referred to as a

___________________________ which consist of a sequence of connected
steps.
1-2-11 From an organizational perspective, ___________________________ are

the central element in the workflow system. They are used to describe a
business process that may require either a single step or several parallel
steps to be executed. The definition of these processing tasks can be in the
form of either ___________________________ or
___________________________.
1-2-12 Any number of workflows can be derived from a workflow definition as

runtime instances. The ___________________________ is responsible for
controlling and managing the process. By evaluating conditions with object
attributes and taking into account the results of individual steps, it
determines which steps are to be processed next.
1-2-13 Each workflow consists of a sequence of work items which represent the
individual steps of a workflow definition at the runtime of the workflow.
Managing the execution of individual work items, including the assignment
of agents and deadline monitoring, is the task of the
___________________________.
1-3 Prepare for creating a new workflow by refreshing your memory. Execute the pre-
defined workflow definition for the vacation request.
1-3-1 Start the workflow task for vacation request as the employee, user :)
%&&/(5. This is the test logon of the employee who initiates the
vacation request workflow.
Fill in the requested information on the form and save it.
1-3-2 Logon as the manager, using the logon :)%&0*5 to check the
integrated inbox for a work item. Execute the work item by accepting the
vacation request.
1-3-3 Toggle back to the open R/3 session for user :)%&&/(5.(employee)
and check the Business Workplace inbox for a confirmation message
regarding the response of your vacation request from the manager.
SAP AG BC601 2-21

([HUFLVHV
8QLW,QWURGXFWLRQ
7RSLF2UJDQL]DWLRQDO6WUXFWXUH

Describe an organizational structure
As you begin your workflow work, you need to ensure the appropriate
organizational plan exists in your R/3 system.
You need to ensure the IDES organizational structure is defined correctly.
2-1 When a workflow is executed, defined step activities forward work items to agents
for processing. These agents are categorized and defined by the enterprise
departmental hierarchy. The workflow definition is notified of this hierarchy by
way of the organizational structure.
Personnel positions within the organization are assigned as responsible agents to

receive and process work items that result from processing activities of the
workflow definition.
2-1-1 The first step in creating your org plan is to enter the abbreviation
=:)B25*B, and name 2UJDQL]DWLRQDOXQLW for your organizational
unit(## represents your assigned group number).
2-2 Once the unit is defined, you must add staff assignments. You need to begin by
creating a position for the department head. Four steps are required to completely
define positions.
If your organization does not default into the fields, use the [F4] key
and search for the proper organization.
You can enter a full or partial search string using the name of your
organization and the * as a wild card.
2-2-1 First you must define a position, with the abbreviation =SRVBKHDGB, for
department head ##.
SAP AG BC601 2-22

2-2-2 The next step involves creating the position =SRVBHPSOB (employee of
zwf_org_##)
2-2-3 The next action you must take is to assign holders of the positions you
created.
You want to assign the XVHU named %&0*5 to the department head
position and the XVHU named %& to the employee position.
2-2-4 In the last step you define the position of the manager as a chief position
The holder of this position is therefore the superior of all the other positions
in the organizational unit.
SAP AG BC601 2-23

6ROXWLRQV
8QLW,QWURGXFWLRQ
7RSLF6$3%XVLQHVV:RUNIORZ&RPSRQHQWV
1-1 The correct answers are as follows:

1-1-1 7UXH
1-1-2 7UXH
1-1-3 7UXH
1-1-4 )DOVH
1-1-5 7UXH
1-1-6 )DOVH
7KH6$3%XVLQHVV1DYLJDWRULVQRWDGHVLJQWRROOLNHWKH:RUNIORZ
%XLOGHU7KH:RUNIORZJUDSKLFVORRNVLPLODUWRWKH%XVLQHVV1DYLJDWRU
JUDSKLFV
1-2 The appropriate term for each statement is as follows:
1-2-1 AnREMHFW is the encapsulation of functionality and behavior for performing

defined business tasks.
1-2-2 The2EMHFWW\SH refers to a generic description of an object created at

runtime. It includes the definition of key fields, methods, attributes and
events.
1-2-3 Any type of related information which can be accessed uniquely under an
identifying key is called anREMHFW.
1-2-4 0HWKRGV refers to an object method or a manual activity.
1-2-5 6$3:RUNIORZis a pre-defined workflow definition supplied by SAP that

defines a specific business scenario.
1-2-6 Interaction between the runtime execution of workflows and users

responsible for carrying out specific work to be done is managed by the
%XVLQHVV:RUNSODFH
1-2-7 A single-step task defined by the user or supplied by SAP is called a

VWDQGDUGWDVN
SAP AG BC601 2-24

1-2-8 A multi-step task defined by the user or supplied by SAP is called a
ZRUNIORZWHPSODWH
1-2-9 The :RUNIORZ%XLOGHU is a tool that is used to define, access and or modify
workflow definitions in a graphical format.
1-2-10 The technical implementation of a business process is referred to as a

ZRUNIORZGHILQLWLRQ which consist of a sequence of connected steps.
1-2-11 From an organizational perspective, WDVNV are the central element in the
workflow system. They are used to describe a business process that may
require either a single step or several parallel steps to be executed. The
definition of these processing tasks can be in the form of either VLQJOHVWHS
WDVNV or PXOWLVWHSWDVNV
1-2-12 Any number of workflows can be derived from a workflow definition as

runtime instances. The ZRUNIORZPDQDJHU is responsible for controlling and
managing the process. By evaluating conditions with object attributes and
taking into account the results of individual steps, it determines which steps
are to be processed next.
1-2-13 Each workflow consists of a sequence of work items which represent the
individual steps of a workflow definition at the runtime of the workflow.
Managing the execution of individual work items, including the assignment
of agents and deadline monitoring, is the task of the ZRUNLWHPPDQDJHU
1-3 The following are the steps for executing the pre-defined workflow definition for a
vacation request:
1-3-1 ,QWKH6$3(DV\$FFHVVPHQXFKRRVH
7RROV6$3%XVLQHVV:RUNIORZ'HYHORSPHQW(QYLURQPHQW
'RXEOHFOLFN'HPR)LOO2XW)RUP
(QWHUWKHDSSURSULDWHLQIRUPDWLRQLQWKH1DPHDQG$EVHQWGDWHILHOGV
(QWHUDQ\DGGLWLRQDOLQIRUPDWLRQDVUHTXLUHGDQGVHOHFWWKH>6DYH@EXWWRQ
1-3-2 Carry out the following steps to execute the work item as the manager and
accept the vacation request.
,QWKH6$3(DV\$FFHVVPHQXRSHQWKHIROGHU2IILFH
'RXEOHFOLFN:RUNSODFH
2SHQWKH,QER[IROGHUDQGFOLFNRQ:RUNIORZ
3ODFHWKHFXUVRURQWKHDSSURSULDWHZRUNLWHPDQGVHOHFWWKH>([HFXWH@
EXWWRQRUGRXEOHFOLFNWKHLFRQLQWKH([FROXPQ
$SSURYHWKHYDFDWLRQUHTXHVWDQGFOLFNRQWKHEDFNDUURZ<RXZLOO
UHFHLYHDSRSXSZLQGRZWRDSSURYHWKHUHTXHVWH[SOLFLWO\
6HOHFWWKH>&RPSOHWHWKLVZRUNLWHP@EXWWRQ
1-3-3 Return to the open R/3 session for user :)&/(5.(employee) and
check the Business Workplace Inbox for a Notification message regarding
the response of your vacation request from the manager.
SAP AG BC601 2-25

6ROXWLRQV
8QLW,QWURGXFWLRQ
7RSLF2UJDQL]DWLRQDO6WUXFWXUH
2-1 When a workflow is executed, defined step activities forward work items to agents
for processing. These agents are categorized and defined by the enterprise
departmental hierarchy. This hierarchy is defined to a workflow definition by way
of the PD organizational structure.
Personnel positions of the PD Org are assigned as responsible agents to receive and
process work items that result from processing activities of the workflow definition.
2-1-1 The first step in creating your org plan is to enter the abbreviation
=:)B25*B and name 2UJDQL]DWLRQDOXQLW for your organizational
unit (## represents your assigned group number).
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW
'HILQLWLRQ7RROV2UJDQL]DWLRQDO0DQDJHPHQW2UJDQL]DWLRQDO3ODQ
&UHDWH
$FFHSWWKHWLPHOLPLWRIWKH
(QWU\LQGHWDLOVFUHHQ
2UJDQL]DWLRQDOXQLWDEEUHYLDWLRQ=:)B25*B
1DPH2UJDQL]DWLRQDOXQLW*URXS
>6DYH@
2-2 Once the unit is defined, you must add staff assignments. You need to begin by
creating a position for the department head. Four steps are required to completely
define positions.
5HPDLQLQWKHVDPHVFUHHQDVIRUTXHVWLRQ25FKRRVHWKHIROORZLQJSDWK
'HILQLWLRQ7RROV2UJDQL]DWLRQDO0DQDJHPHQW2UJDQL]DWLRQDO3ODQ
&KDQJH
If your organization is not the default entry in the fields, use the [F4]
key and search for the correct organization.
You can enter a full or partial search string using the name of your
organization and the * as a wild card.
SAP AG BC601 2-26

2-2-1 First you must define a position for the department head with the
abbreviation =SRVBKHDGB .
3RVLWLRQWKHFXUVRURQWKHRUJDQL]DWLRQDOJURXS
,FRQ
FUHDWH
!GRXEOHFOLFN
LQFRUSRUDWHSRVLWLRQ
<RXFDQQRZFUHDWHWKHEDVLFGDWDIRUWKHSRVLWLRQLQWKHGHWDLOVFUHHQ
$EEUHYLDWLRQ=SRVBKHDGB
1DPH3RVLWLRQ'HSDUWPHQWKHDG
>6DYH@
2-2-2 The next step is creating the position =SRVBHPSOB
3RVLWLRQWKHFXUVRURQWKHRUJDQL]DWLRQDOJURXS
,FRQ
FUHDWH
!GRXEOHFOLFN
LQFRUSRUDWHSRVLWLRQ
<RXFDQQRZFUHDWHWKHEDVLFGDWDIRUWKHSRVLWLRQLQWKHGHWDLOVFUHHQ
$EEUHYLDWLRQ=SRVBHPSOB
1DPH3RVLWLRQ(PSOR\HH
>6DYH@
2-2-3 Next you need to assign holders to the positions you created. You want to
assign the XVHU %&0*5 to the department head position and the
XVHU %& to the employee position.
&OLFN8VHULQWKHVHDUFKDUHD
1DPH%&0*5!%XWWRQ6HDUFK!8VHULVGLVSOD\HGLQWKH
VHOHFWLRQDUHD
$VVLJQWKHXVHUWRWKHSRVLWLRQXVLQJ'UDJ 'URS
$FFHSWWKHSURSRVHGWLPHOLPLW
>6DYH@
5HSHDWWKLVSURFHGXUHIRUWKHGHSDUWPHQWHPSOR\HHSRVLWLRQ
6DYHWKHDVVLJQPHQWV
2-2-4 In the last step you define the position of the manager as a chief position
The holder of this position is therefore the superior of all the other positions
in the organizational unit.
3RVLWLRQWKHFXUVRURQWKHQDPHIRUWKHGHSDUWPHQWKHDGSRVLWLRQ
&OLFNRQWKHSRVLWLRQ
,QWKHEDVLFGDWDVHWWKHIODJ+HDGRIRZQRUJDQL]DWLRQDOXQLW
>6DYH@
The positions are now completely defined.
SAP AG BC601 2-27

&XVWRPL]LQJ
&RQWHQW
l 6HWWLQJXSWKH6$3%XVLQHVV:RUNIORZ
6\VWHP%DVLF&XVWRPL]LQJ
SAP AG 1999
SAP AG BC601 3-1

&XVWRPL]LQJ8QLW2EMHFWLYHV
l 8QGHUVWDQGWKHVWUXFWXUHRI:RUNIORZ
&XVWRPL]LQJ
l &DUU\RXW&XVWRPL]LQJ
SAP AG 1999
SAP AG BC601 3-2

SAP AG 1999
SAP AG BC601 3-3

&XVWRPL]LQJ%XVLQHVV6FHQDULR
l <RXQRZQHHGWRFDUU\RXWZRUNIORZFXVWRPL]LQJ
IRU\RXUGHYHORSPHQWV\VWHP
l <RXKDYHWRDFWLYDWHWKHZRUNIORZUXQWLPHV\VWHP
IRUHDFK6$35FOLHQWWKDW\RXZDQWWRXVH
l <RXZLOOOHDUQDERXWWKHZRUNIORZDGPLQLVWUDWLRQ
IXQFWLRQV
SAP AG 1999
SAP AG BC601 3-4

:RUNIORZ6\VWHP&XVWRPL]LQJ
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW8WLOLWLHV6:89HULI\&XVWRPL]LQJ
SAP AG 1999
n To find the basic customizing of the workflow, choose

SAP EASY ACCESS - Tools - Business Workflow - Development - Utilities - Verify Customizing
(transaction SWU3)
n A number of system settings and activities need to be carried out for SAP Business Workflow that
are client-dependent. In the online documentation and help, there is a descripton of each
customizing task and its function relative to the SAP Business Workflow environment.
n The function $XWRPDWLF&XVWRPL]LQJ allows you to maintain SAP Business Workflow standard
settings at the "touch of a button.
n Afterwards, using the button "Verification workflow, a first test workflow can be started to check
the settings.
n In the 'Workflow runtime system' section, the traffic light icon should always be green.
n In the 'Workflow development environment' section, an entry with errors in 'Number range for
customer tasks' can be ignored.
n If the error 'PD control tables not completely available' occurs, start the report RHSOBJCH.
n Automatic Customizing does not contain either maintenance of the organizational plan, or task-
specific customizing, (meaning the assignment between tasks and possible agents).
SAP AG BC601 3-5

5)&'HVWLQDWLRQ
7HVW5)&'HVWLQDWLRQ
7HVW5)&'HVWLQDWLRQ $XWRPDWLF&XVWRPL]LQJ 9HULI\ZRUNIORZ

:RUNIORZ5XQWLPH6\VWHP
:RUNIORZ5)&WHVWUHVXOWV
&XVWRPL]LQJ,QFRPSOHWH
3LQJQRWVXFFHVVIXO
&XVWRPL]HWKH5)&GHVWLQDWLRQIRU\RXUZRUNIORZV\VWHP
SAP AG 1999
n If the logical RFC destination "WORKFLOW_LOCAL_xxx" does not already exist, it is created
automatically. The user WF-BATCH is requested (including password). WF-BATCH needs to be
created in the actual client, with the user type "system" for a background user.
Up to and including Release 4.6B, the user type is "background".
n Execute the function "Test RFC dest."
The system tries to log on to the logical destination with the user specified.
If there are password problems, logon is not successful (despite the green check mark in the result
list). A dialog box is displayed to inform you of this.
n Maintain the RFC destination again by double-clicking on the green check mark before the entry
"Workflow RFC destination configuration completed."
n The workflow runtime system always executes tFRC calls in the logical destination
WORKFLOW_LOCAL_<Clnt>. Clnt stands for the 3-figure number of the client.
n The workflow runtime system only uses one client. Assigning a name to a logical destination ensures
that it is unique system-wide.
n No logical destination exists as a default for the tRFC calls of the workflow system.
SAP AG BC601 3-6

/RJLFDO'HVWLQDWLRQ5)&8VHU
SAP AG 1999
n Create a user with the name WF-BATCH, using the user administration function (transaction SU01).
Create this user with the user type system .
In R/3 sub-systems before 4.6C, the correct user type is '
background'
.
Assign this user the authorization profiles SAP_ALL and SAP_NEW .
If you have any doubts regarding the security of SAP_ALL/SAP_NEW, read the note 149344.
n Maintain the user address for this user.

Also maintain a forwarding address in the user master data. (Sender address
when sending an email).
n You need to maintain a logical destination in each client of your system.
n When you execute the function sychronize passwords, the system reads the password in the user
master record and enters it in the workflow destination.
SAP AG BC601 3-7

0DLQWDLQLQJWKH$GPLQLVWUDWLRQ'DWD
'HILQLWLRQRIWKHJHQHUDO
ZRUNIORZDGPLQLVWUDWRU
'HILQLWLRQRIWKHJHQHULF
GHFLVLRQWDVNXVHGGXULQJ
UXQWLPH
SAP AG 1999
n Workflow administrator:
Person responsible for the technical side of the workflow definition (system administrator).
The workflow administrator is notified automatically of errors that occur during the runtime
execution of workflow definitions. The administrator should be able to correct workflows with
errors, or find suitable contact persons who can.
n Note:
Each workflow can have its own administrator.
The administrator of a single workflow is defined in the basic data (responsibilities) of the workflow
template.
n Decision task as default value for user decision:
Task used by the workflow system to execute a user decision in the workflow. When you create a
step of type user decision in a workflow definition, the task entered here is copied to the workflow
definition. If you change the entry here, it will affect all workflow definitions with user decisions
that are created in the future.
n The generic decision task is a task supplied by SAP.
SAP AG BC601 3-8

8VHU'HFLVLRQDV)XOO6FUHHQ
'HFLVLRQ
RSWLRQV
7DVN
GHVFULSWLRQ
$WWDFKPHQWV
8VHUGHFLVLRQVL]H
FDQEHDGMXVWHG
SAP AG 1999
n As of Release 4.5, user decisions are only created as full screens. In Releases prior to 4.5, user
decisions appeared in a dialog box.
n The full screen display of the user decisions has the following advantages:
The user decision display may possibly conceal a secondary method, for example
an object display or the ArchiveLink Viewer. It can, however, be moved. This was
not possible with the dialog box.
The size can be adjusted
Attachments are displayed and can be added interactively on the user decision screen.
SAP AG BC601 3-9

6HW$FWLYH3ODQ9HUVLRQ
&KDQJH9LHZ6HW$FWLYH3ODQ9HUVLRQ2YHUYLHZ
Table view Edit Goto Selection Utilities System Help

!#" $
L =9; 6 &% J-(H'). +GF* G %(KH -, * D % 7F
/E .0 * 7,2G+1G 35I4 H >2?2A@ 6B @ 9;C
'HVWLQDWLRQ
PLOGI

PLOGI 01 Integration plan version / active plan vr

67 $8:9;=< +XPDQ5HVRXUFHV
SAP AG 1999
n In this step, you specify the plan version in which you want to maintain your data. In other words,
the active plan version.
Set an active plan version.
The active plan version is set to "01", provided an active plan version has not already been
maintained.
n Careful consideration is required when deciding which is to be the active plan version, for the
following reasons:
For the purposes of integration, the active plan version in all PD modules is simultaneously the
integration plan version.
Therefore, it is not possible to set a new plan version each time you implement a new application
component.
n Enter the plan version you wish to use as the active one, both for the different PD modules and for
integration purposes, in the field "value of semantic abbreviation" of the parameter group "PLOGI
PLOGI"
SAP AG BC601 3-10

$FWLYDWH'HDGOLQH0RQLWRULQJ
&XVWRPL]LQJVWHS$FWLYDWHGHDGOLQHPRQLWRULQJ-RE6::'+(;
7KH&XVWRPL]LQJDFWLYLW\LVQHFHVVDU\LILQGLYLGXDOWDVNVWHSVVKRXOGKDYH
WKHLUGHDGOLQHVPRQLWRUHGLQ6$3%XVLQHVV:RUNIORZ
SAP AG 1999
n There are two versions for deadline monitoring

n 9HUVLRQ:
Deadline monitoring of work items on an individual basis is performed by a background job that
must be scheduled once when the system is started. This background job schedules itself each time
for the next deadline to be monitored. Scheduling can be carried out using transaction SWWB.
n 9HUVLRQ:
Permanent deadline monitoring of work items means that the scheduled background job is regularly
called at a determined interval, and checks whether deadlines have been missed since its last
activation. Permanent deadline monitoring can be used in each client of your production system,
using transaction SWWA.
n 5HFRPPHQGDWLRQ:
Only select permanent deadline monitoring if there are several deadlines to be monitored per minute.
n You must schedule the job in every client that you want to use in the workflow.
n The job can only be scheduled once for each client.
SAP AG BC601 3-11

6HW0RQLWRULQJRI,QFRUUHFW:RUN,WHPV
6$35
Work item monitoring Edit Goto Environment System Help

MNCO#9;PJ 7$B @ 9;CQ9;CQJR9;C5@ B 9;K@SCTU92OF809KV0@ B 2JQ:8W@ BIXWB J 6 9; 7 ZY

A=9;#
[P\ 7 ?2V]T=9;FC2< 7 C<W8 7 @ B B 6 W9C E Y^
B#7 B < 7B :9O G7 ?VT;P9;FC<0_`9 G

13.06.1998
#B 7 BFB @ JUa92O G7 ?2VT=9;FC2<b_=9 G 10:25:00
SWWERRE
Background job name
10170901
Background job number
Monitoring of work items with temporary errors X
Interval until next rerun 20 (in minutes)
Repeat counter for work items with errors 3
SAP AG 1999
n With this activity, you schedule monitoring and special handling for background work items that
could not initially be executed because of a temporary error in the underlying object method. These
background work items are then restarted automatically.
n Monitoring is deactivated in the standard version.
n The following steps are required to activate monitoring of work items with errors:
Carry out the customizing activity that will invoke transaction SWWD.
Specify whether monitoring should be carried out.
Specify the interval between two monitoring runs.
Specify after how many attempts the background work item should finally be set to status "error".
n Further notes:
If applicable, carry out the customizing activity again in each client of your production system.
If monitoring is not activated or the total number of attempts is reached, the work item is finally
set to status "error". In this status, a work item can be found using the selection report, and the
error can be analyzed.
SAP AG BC601 3-12

7HVW:RUNIORZ
6WDUW9HULILFDWLRQ:RUNIORZ
List Edit Goto System Help

Start Verification Workflow
(YHQWJHQHUDWHG
<RXZLOOILQGDZRUNLWHPLQ\RXULQWHJUDWHGLQER[ZKLFK
UHSUHVHQWVDXVHUGHFLVLRQ:KHQ\RXKDYHH[HFXWHG
WKLVZRUNLWHP\RXZLOOUHFHLYHWZRPDLOV6$3RIILFH
GRFXPHQWV7KH\DUHWKHQRWLILFDWLRQVRIFRPSOHWLRQIRU
WKLVXVHUGHFLVLRQDQGIRUWKHVXEVHTXHQWEDFNJURXQG
VWHS
,QWHJUDWHGLQER[ -
SAP AG 1999
n When starting the verification workflow, the previous customizing activities are tested. This checks
basic functions in the workflow runtime environment.
n A work item is sent to the user who started the verification. This tests the sending of a work item to
be executed in the form of a "User Decision", and the sending of a notification.
n During the execution of the "User Decision" task, several functions at the task level can be tested, for
example: displaying or creating an attachment in the Business Workplace.
SAP AG BC601 3-13

:RUNIORZ'HYHORSPHQW(QYLURQPHQW
&UHDWH3UHIL[1XPEHUVIRU6WDQGDUG2EMHFWV
$QHQWU\LVUHTXLUHG
IRUDOOV\VWHPVDQG
FOLHQWVWKDW\RX
ZDQWWRXVH
SAP AG 1999
n The standard objects, for example, roles, tasks, and workflows, are generated using the prefix of the
entry for system and client.
SAP AG BC601 3-14

3HUVRQDO:RUNIORZ6HWWLQJV%DFNJURXQG
l :K\GRZHQHHGWKHP"
2QHZRUNIORZORJRURQHZRUNLWHPGLVSOD\LVQRWHQRXJK
c
EHFDXVHLWLVXVHGE\GLIIHUHQWXVHUFDWHJRULHVIRUH[DPSOH
w :RUNIORZPRGHOHUVDQGDGPLQLVWUDWRUVUHTXLUHDFFHVVWR
DOOWHFKQLFDOLQIRUPDWLRQVXFKDVFRQWDLQHUVZRUNLWHP
,'VVWHSQXPEHUVDOOVWHSW\SHVHWF
w :RUNIORZHQGXVHUVQRWHFKQLFDOGHWDLOVIRFXVHGRQWKH
FRQWHQWRIWKHZRUNLWHPFRQIXVHGE\WRRPDQ\IXQFWLRQV
HWF
l :KDWIXQFWLRQVDUHLQYROYHG"
w $GPLQLVWUDWRUVHWVWKHGHIDXOWRQDV\VWHPZLGHEDVLV
w (DFKXVHUFDQWKHQPDNHWKHLURZQVHWWLQJV
SAP AG 1999
n User view with ActiveX (32 Bit)

User view of the workflow log, containing no technical information. This view uses ActiveX
controls and is therefore only available on 32 bit platforms.
n User view without ActiveX (32 Bit)
User view of the workflow log, containing no technical information. This view uses the
hierarchical list presentation of the ABAP list viewer (ALV).
n Technical view
In addition to the basic information, the technical view of the workflow log also shows technical
numbers and information, which may not be available in the logon language of the user. The
technical view is intended primarily for system administrators.
n The table SWL_SYSTEM is used to preset personal workflow settings on a system-wide basis.
,PSRUWDQW If a user has already maintained personal workflow settings, these are not
overwritten by new entries in this table.
5HFRPPHQGDWLRQ If you want to make settings that differ from SAP settings, you should do
this when customizing your system before users work with it.
n To maintain your personal settings in the Business Workplace, choose Settings - Workflow Settings -
Personal Settings
SAP AG BC601 3-15

3HUVRQDO:RUNIORZ6HWWLQJV8VHUV
:RUNLWHP
GLVSOD\
:RUNIORZ
ORJ
2WKHUV
7HFKQLFDO %XVLQHVV
XVHUV XVHUV
SAP AG 1999
n Here you can make settings to adapt the display tools (work item display and workflow log) of the
runtime system to your requirements.
n Other settings
'LVSOD\ZRUNLWHPWH[WVLQWKHORJRQODQJXDJH
- Work item texts are always displayed in the logon language of the users integrated inbox. If
the logon language of the user differs from the language in which the work item was
originally created, additional database access is required. This can cause a certain delay
when structuring
the integrated inbox.
(QDEOHPXOWLSOHIRUZDUGLQJRIZRUNLWHPV
- The work item can be forwarded to several agents (organizational unit, job, position, user,
etc.).
'RXEOHFOLFNLQJRQDQREMHFWGLVSOD\VWKHREMHFWLQWKHVDPHZLQGRZ
In the work item display, you can select an object to be displayed. This object is then displayed
in the window of the current session and replaces the work item display. When you exit the
display of the object, you return to the work item display.
If you do not select this check box, a new session is opened to display the object.
SAP AG BC601 3-16

&XVWRPL]LQJ8QLW6XPPDU\
l :RUNIORZFXVWRPL]LQJFDQ
EHFDUULHGRXWXVLQJWKH,0*
RUWKHZRUNIORZGHYHORSPHQW
HQYLURQPHQW
l $QDXWRPDWLFFXVWRPL]LQJIXQFWLRQ
LVDYDLODEOH
SAP AG 1999
SAP AG BC601 3-17

([HUFLVHV
8QLW&XVWRPL]LQJ
7RSLF&XVWRPL]LQJWKH6$3%XVLQHVV:RUNIORZ6\VWHP
At the conclusion of this exercise, you will be able to:

Find documentation on particular topics
Describe the customizing steps for the workflow environment
Carry out the steps required for customizing the SAP Workflow
runtime environment
So far you have worked in a dummy system.
Now you want to follow the normal project implementation model and
start the workflow configuration in the development system.
For each SAP R/3 client, you need to activate the workflow system for
workflow development (for example, to adjust a workflow template).
1-1 The online documentation in the SAP Reference IMG provides a central source of
information related to the various customizing activities.
1-1-1 Call the basic customizing, and use the documentation to find which
transaction can be used to schedule a deadline monitoring job.
____________________________________________________________
1-1-2 What authorizations are required for the USERID necessary for logical
destination WORKFLOW_LOCAL_<Clt.>?
____________________________________________________________
1-1-3 What user type is required for the user ID defined for logical destination
WORKFLOW_LOCAL_<Clt.>?
____________________________________________________________
Note that SAP documentation often has hypertext links to submenus, in

which the terminology of the current topic is explained further.
These links are identified by a change in color, and are often XQGHUOLQHG
The mouse cursor also changes into a pointing index finger to indicate a
submenu.
SAP AG BC601 3-18

1-2 Additional sources of information are the Online Application Help, the SAP Library
and the Documentation CD.
1-2-1 View the list of SAP Business Workflow Scenarios (Templates) to find
which workflow templates are supplied with R/3.
1-2-2 From various screens within the R/3 system, you can use Application Help
to access specific documentation for the task currently being executed. Find
out what Application Help says about task types.
1-3 Even though the Automatic Customizing in SWU3 will do most of the workflow
customizing, you must still maintain the number range settings for the multi-step
tasks and single-step tasks that you create.
1-3-1 Display the number range for all the workflows,

tasks and roles created.
SAP AG BC601 3-19

6ROXWLRQV
8QLW&XVWRPL]LQJ
7RSLF&XVWRPL]LQJWKH6$3%XVLQHVV:RUNIORZ6\VWHP
1-1 The online documentation in the SAP Reference IMG is a central source of
information related to the various customizing activities.
,QWKH6$3(DV\$FFHVVPHQXFKRRVH
7RROV$FFHOHUDWHG6$3&XVWRPL]LQJ
'RXEOHFOLFNWKH(GLW3URMHFWLFRQ
,QWKHVFUHHQ&XVWRPL]LQJ([HFXWH3URMHFWFKRRVHWKHEXWWRQ6$35HIHUHQFH
,0*
1-1-1 Which transaction is used to schedule deadline monitoring?

)URPWKH'LVSOD\,0*VFUHHQ
&KRRVH%DVLV&RPSRQHQWV%XVLQHVV0DQDJHPHQW6$3%XVLQHVV
:RUNIORZ
&DUU\RXW
0DLQWDLQVWDQGDUGVHWWLQJVIRU6$3%XVLQHVV:RUNIORZ
E\
VHOHFWLQJWKH([HFXWHLFRQ
7RUHDGWKHGRFXPHQWDWLRQFOLFNRQWKH,EXWWRQIRUWKHIXQFWLRQ
6FKHGXOHGHDGOLQHPRQLWRULQJ)LQDOO\FOLFNRQ([HFXWHFORFNLFRQ
WRFKHFNWKHVHWWLQJV
6FKHGXOHGHDGOLQHPRQLWRULQJ7UDQVDFWLRQ6::%
1-1-2 What authorizations are required for the USERID necessary for logical
destination WORKFLOW_LOCAL_<Clt.>? (Read about this under RFC
Destination .)
7KHUHTXLUHGDXWKRUL]DWLRQVDUH6$3B$//DQG6$3B1(:
1-1-3 What user type is required for the user ID defined for logical destination
WORKFLOW_LOCAL_<Clt.>?
6\VWHP
SAP AG BC601 3-20

1-2 Additional sources of information are the Online Application Help, the SAP Library
and the Documentation CD.
1-2-1 View the list of SAP Business Workflow scenarios (templates), to find
which workflow templates are supplied with R/3.
)URPWKH6$3PDLQPHQXFKRRVH
+HOS6$3/LEUDU\
([SDQG%&%DVLV&RPSRQHQWV
([SDQG%XVLQHVV0DQDJHPHQW
([SDQG6$3%XVLQHVV:RUNIORZ
([SDQG5HIHUHQFH'RFXPHQWDWLRQ
&KRRVH:RUNIORZ6FHQDULRVLQ$SSOLFDWLRQV
1-2-2 From various screens within the R/3 system, you can use Application Help
to access specific documentation for the task currently being executed. Find
out what Application Help says about task types.
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW'HILQLWLRQ7RROV
7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
3RVLWLRQWKHFXUVRULQWKH7DVNW\SHILHOG
&KRRVH+HOS$SSOLFDWLRQ+HOS
7KHGRFXPHQWDWLRQGLVSOD\HGVKRXOGSURYLGHDQLQGH[IRUWKHRQOLQH
KHOS
1-3 Even though the Automatic Customizing in SWU3 will do most of the workflow
customizing, you must still maintain the number range settings for the multi-step
tasks and single-step tasks that you create.
1-3-1 View the number range for all workflows, tasks, and roles created.
&DOOWKHWUDQVDFWLRQ6:8
([HFXWHWKHLWHP
3UHIL[QXPEHUVIRUVWDQGDUGREMHFWW\SHVPDLQWDLQHG

([HFXWHWKHLWHP0DLQWDLQSUHIL[QXPEHUV
1RWHWKHQXPEHUUDQJHDVVLJQHGWRWKHV\VWHP,'DQGWKHFOLHQW
7KLVQXPEHUUDQJHLVXVHGIRUWKHFUHDWLRQRIZRUNIORZVWDVNVDQGUROHV
6HOHFWWKHJUHHQ%DFNDUURZWRUHWXUQWRWKH'LVSOD\,0*VFUHHQDQG
UHYLHZWKHGRFXPHQWDWLRQIRUWKLVQXPEHUUDQJH
SAP AG BC601 3-21

:RUNIORZ'HILQLWLRQ
&RQWHQWV
l &RPSRQHQWVRI
ZRUNIORZWHPSODWHV
l 6WUXFWXUHRIWKH:RUNIORZ%XLOGHU
SAP AG 1999
SAP AG BC601 4-1

:RUNIORZ'HILQLWLRQ8QLW2EMHFWLYHV
l &UHDWHDZRUNIORZWHPSODWHZLWKDZRUNIORZ
GHILQLWLRQ
l ,GHQWLI\VWHSVLQDZRUNIORZ
l 8VHWKHIXQFWLRQVRIWKH:RUNIORZ%XLOGHU
SAP AG 1999
SAP AG BC601 4-2

SAP AG 1999
SAP AG BC601 4-3

:RUNIORZ'HILQLWLRQ%XVLQHVV6FHQDULR
l <RXKDYHODLGRXWWKHGHVLJQRI\RXUEXVLQHVV
SURFHVV
l <RXQHHGWROHDUQDERXWWKH:RUNIORZ%XLOGHU
l <RXZLOOWKHQEHDEOHWRFRQYHUW\RXUEXVLQHVV
SURFHVVLQWRDZRUNIORZGHILQLWLRQ
SAP AG 1999
SAP AG BC601 4-4

:RUNIORZV([DPSOHV
l &LUFXODUWKDWKDVWREHSURFHVVHGFKHFNHG
DQGDSSURYHG
l &KHFNLQJPDVWHUGDWDDIWHUFKDQJHV
l &URVVDSSOLFDWLRQEXVLQHVVSURFHVVHV
)URPDFKDQJHUHTXHVWWRDSURGXFWLRQRUGHU
%XGJHWPDQDJHPHQWIURPUHTXHVWWKURXJKWR
UHOHDVHRIIXQGV
5HFUXLWPHQWIURPWKHSODFLQJRIWKHMRE
DGYHUWLVHPHQWWKURXJKWRWKHLQWHJUDWLRQRIWKH
QHZHPSOR\HHLQWKHRUJDQL]DWLRQ
SAP AG 1999
n If you want to model a business process using Workflow, always check the SAP R/3 documentation
first and try to use one of the SAP Workflows provided.
n The slide lists examples of workflow templates.
The last three workflows listed are cross-application workflows.
SAP AG BC601 4-5

+RZ$UH:RUNIORZV&UHDWHGLQWKH6\VWHP"
&XVWRPHUGHILQHG
ZRUNIORZWHPSODWH:6
Customer-defined
Reference to the workflow
definition 6$3ZRUNIORZ:6
Client-independent GHOLYHUHGE\6$3
Executable
Reference to the workflow
definition
:RUNIORZWDVN:) Client-independent
XSWR5HOHDVH Cannot be edited
Customer-defined Can be configured
Reference to the workflow Can be used as a template
definition for your own workflows
Client-dependent and time-
dependent
AS OF RELEASE 4.5, DO NOT
USE FOR NEWLY CREATED
TASKS
SAP AG 1999
n Within workflow templates, there is a key with the following structure:

Task abbreviation WS for workflow template
8-character sequence number
n The system recognizes from the structure of the 8-character number whether the template is a
standard template delivered by SAP or one that customers have created.
Customer-defined templates start with the prefix number that was defined in Customizing for the
system and client.
n The system only offers you workflow templates if you want to create a new workflow in the system.
Up to and including Release 4.0, you could also create workflow tasks (abbreviation WF).
Workflow tasks are client-specific and are only valid in a defined time period.
n Existing workflow tasks can still be executed but are not being further developed.
(See also SAPNet Note 114811)
SAP AG BC601 4-6

:RUNIORZ7HPSODWHVDQG:RUNIORZ'HILQLWLRQV
:RUNIORZ
:RUNIORZ
:RUNIORZ'HILQLWLRQ
:RUNIORZWHPSODWH
:RUNIORZWHPSODWH
:RUNIORZWHPSODWH
Reference to
ZRUNIORZGHILQLWLRQ
Specification of
WULJJHULQJHYHQWV
,QLWLDOYDOXH
DVVLJQPHQW
6SHFLILFDWLRQRI
VWDUWWUDQVDFWLRQV
SAP AG 1999
n A workflow template contains:

Basic data of the workflow definition. This includes specifications on buffering reporting data,
on automatic forwarding, and so on.
The specification of triggering events. If the specified event enters the system, the workflow
starts, if the event is actively linked to the workflow.
Initial values
Specifications for the interface (workflow and event container)
A link to the corresponding workflow definition, that is, the specification of the individual
workflow steps that are to be executed.
n The binding marks the relevant data required for the execution of the workflow. It establishes the
connection between the data that is required as input for the execution of a task and the output as the
result of the task, which has to be transferred to the next step in the workflow.
n As of Release 4.5, workflows can be triggered not only by events but also by the maintenance of a
start transaction.
n The view of the workflow definition is without event-driven process chain (standard view as of
Release 4.5).
You can display the workflow definition with event-driven process chain.
To do this, choose Extras -> Options -> Graphic.
SAP AG BC601 4-7

:RUNIORZ'HILQLWLRQ:RUNIORZ%XLOGHU
$UHDVRIWKH:RUNIORZ%XLOGHU
Steps Workflow Definition
Overview
Container
Tasks
Document
Templates
Step Types
Messages
SAP AG 1999
n The workflow definition is created in the Workflow Builder and is displayed graphically in a
network.
n The Workflow Builder is subdivided into the following areas:

Tree structure with sequence of workflow steps. The corresponding step definition can be
called by double-clicking on a step.

Variables of the workflow interface. You can generate, change, display, delete, and
rename container elements from the context menu.

You can display all tasks and workflows that are relevant to your workflow and
transfer them to your workflow definition by double-clicking.
! #"$!
Displays existing document templates.

$)(*
%'& & Display of the whole workflow definition.

+-,
All available step types for Drag&Drop into the workflow definition.
/10
. All messages generated in where-used lists and workflow tests are displayed here.
n The container, task, and document template areas are disjunct in the display. You have to choose
one each time.
SAP AG BC601 4-8

:RUNIORZ'HILQLWLRQ6WHSV
:RUNIORZ'HILQLWLRQ 6WHS
LQ:RUNIORZ%XLOGHU
%XVLQHVVDFWLYLW\
Activity
l $UUDQJHPHQWRIVWHSV
User decision
LQVHTXHQFHRULQ
Document from template SDUDOOHOSURFHVVLQJ
Web activity
l ,IUHTXLUHG
'HDGOLQHPRQLWRULQJIRU
,QWHUQDOSURFHVVFRQWURO LQGLYLGXDOVWHSV
Condition
l &KRRVHDQGQDPH
Multiple condition FRUUHVSRQGLQJRXWFRPH
Event creator IRUHDFKVWHS
Wait steps
Container operation
Loop (UNTIL)
Loop (WHILE)
Fork
SAP AG 1999
n A workflow definition is made up of individual steps in a modular fashion. When creating a step in a
workflow definition, the step type must be specified first.
n The following step types exist:
Steps that relate to business activities: Activity, user decision, document
from template, Web activity
Steps for internal process control and monitoring: Condition, multiple condition, loop,
fork, container operation, event creator, wait step
n The steps can be arranged in series or in parallel processing.
n The processing sequence of the steps depends on the result of the respective preceding step.
n The possible results of a step are usually derived from the underlying business function
and are specfied in the workflow step on the tab page Outcomes.
The system enters another branch to the processing chain for each possible outcome.
n In the graphical display, all steps and events have certain symbols depending on their type.
A legend for the step types is automatically displayed with Release 4.6C.
SAP AG BC601 4-9

:RUNIORZ'HILQLWLRQ)XQFWLRQVRIWKH:RUNIORZ
%XLOGHU
:RUNIORZ'HILQLWLRQ
(YHQW :RUNIORZ%XLOGHU
6WHS 1DYLJDWLRQDQGGLVSOD\DUHD
%ORFNRULHQWHGPRGHOLQJ
7RSGRZQPRGHOLQJLVSRVVLEOH
6SHFLDOIXQFWLRQVVXFKDVFXW
%ORFN
SDVWHPRYHFRS\
3ULQW
&KHFNLQJDQGDFWLYDWLQJ
'UDJ 'URSIXQFWLRQDOLW\
SAP AG 1999
n The Workflow Builder works in a block-oriented way.

Each step is the determining element of its block.
Operations in the individual steps always affect the whole block, that is, you can only delete, cut, and
paste in blocks.
n
2A3 block
4 "$ has a start and includes all actions until a common end is found.
:
Approve leave request step
The step can end with the result approved or rejected .
Both results have follow-up actions.
The follow-up actions still belong to the block Approve leave request and are therefore included in
block operations.
n You can display blocks in the Workflow Builder by choosing Graphic -> Blocks -> Show.
n From the Workflow Builder, you can go to the following processing options:
Event creation (Extras -> Create event)
Business Workplace (Extras -> Business Workplace)
Business Object Repository (Extras -> Business Object Builder).
n Besides the general workflow administrator set in Workflow Customizing, an administrator can be
assigned to each workflow in the basic data: Goto -> Basic data -> Responsibs. tab page.
SAP AG BC601 4-10

'HILQLWLRQ7KH*RDO$SSURYH$EVHQFH
SAP AG 1999
n The slide shows a workflow for approving notifications of absence.

n In the following slides, we will build this workflow to demonstrate the functions of the Workflow
Builder.
SAP AG BC601 4-11

'HILQLWLRQ6FHQDULR
l 6WHS&DOO:RUNIORZ%XLOGHU
5 'HILQHDQHZVHDUFKDUHDIRUWKHDYDLODEOHWDVNV
l 6WHS,QVHUWILUVWVWHSVIURPWKHDYDLODEOHWDVNV
5 ,QVHUWVWHS&UHDWHQRWLILFDWLRQRIDEVHQFH
5 ,QVHUWVWHS$SSURYHQRWLILFDWLRQRIDEVHQFH
l 6WHS,QVHUWPDLOQRWLILFDWLRQRIDSSURYDO
l 6WHS,QVHUWVWHSWRGHOHWHRUUHYLVHOHDYHUHTXHVWLIUHMHFWHG
l 6WHS,QVHUWORRSWRUHSHDWWKHDSSURYDO
5 &UHDWHDORRSDQGFXWDQGSDVWHZKHUHQHFHVVDU\
5 ,QWHJUDWHIXQFWLRQVIRUWHUPLQDWLQJWKHORRS
l 6WHS$VVLJQDJHQW
SAP AG 1999
n You have divided up your process into individual steps.

n You have found or created the required tasks in the system.
The tasks have assigned possible agents.
n You know which agents are to be responsible for individual steps.
SAP AG BC601 4-12

6WHS&DOO:RUNIORZ%XLOGHU
7KHVHDUFKDUHD
KDVWREH
GHILQHGRQFH

6LQJOHFOLFN
6LQJOHFOLFN
SAP AG 1999
n The Workflow Builder is the tool for creating workflow definitions. Call the Workflow Builder
directly using transaction SWDD or choose
SAP EASY ACCESS - Tools - Business Workflow - Development - Definition Tools - Workflow
Builder.
n First, all necessary tasks for the notification of absence have to be added to the area "My workflows
and tasks". Click on the My workflows and tasks button (2) and choose New search range" (3). A
dialog box appears. Switch to "Task groups" and press "F4". Enter "SWD*" in the "Restrict value
range" dialog box and press the return key. Double-click task group "SWD_AF_TG" (TG70000023)
the task group is added to the search area (4). If you close the window to set up the search area, the
content of the task group added is displayed under "Available tasks".
SAP AG BC601 4-13

6WHS,QWURGXFWLRQ
1DYLJDWLRQ
1DYLJDWLRQ
*UDSKLFDOUHSUHVHQWDWLRQ
*UDSKLFDOUHSUHVHQWDWLRQ
RIWKHZRUNIORZ
RIWKHZRUNIORZ
/HJHQG
/HJHQG
&RQWDLQHU *UDSKLFDO
*UDSKLFDO
QDYLJDWLRQ
QDYLJDWLRQ
7RROER[
7RROER[
RIDYDLODEOH
RIDYDLODEOH
WDVNV
WDVNV :RUNIORZ
:RUNIORZ
VWHSV
VWHSV
7HPSODWHV
7HPSODWHV
0HVVDJHOLQHZLWKQDYLJDWLRQRSWLRQ
0HVVDJHOLQHZLWKQDYLJDWLRQRSWLRQ
SAP AG 1999
n The most important improvements to the Workflow Builder

WebFlow integration
The Builder can be called directly without passing over multistep tasks
Improved layout and new symbols
New interaction model: Context-sensitive, few dialog boxes, navigation always possible for
tasks, container elements, and document templates
Amodal display of legend
More detailed checks
Integrated runtime tools, for example, for testing the workflow
Maintenance of triggering events and start transactions is possible
SAP AG BC601 4-14

6WHS,QVHUW&UHDWH1RWLILFDWLRQRI$EVHQFH
&OLFNRQFH
&OLFNRQFH
WRVHOHFW
WRVHOHFW

'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW
SAP AG 1999
n You can now use the "available tasks" as a toolbox for our workflow project. To integrate a step
within the empty workflow, you have to click on the step "Undefined Double-click for new step"
(1) and double-click on a task (2) in the "Available tasks" area.
n The system integrates the step in the workflow definition - see dotted circle (3).
n 1RWH1RFRQWDLQHUHOHPHQWVQRUELQGLQJVKDYHWREHFUHDWHGWKHV\VWHPFUHDWHVWKHPDXWRPDWLFDOO\
SAP AG BC601 4-15

6WHS,QVHUW$SSURYH1RWLILFDWLRQRI$EVHQFH
'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW

SAP AG 1999
n As the second step, we use "Approve notification of absence". Select the undefined step (1) and
double-click the approval task (2).
n You can see the result in the dotted circle. The approval step has three possible results - New (not
required - you can position the cursor on the line and press the "Delete" button), Approved and
Rejected .
SAP AG BC601 4-16

6WHS,QVHUW
6HQG0DLO

'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW

6HOHFW
6HOHFW

6HQGPDLO
6HQGPDLO
SAP AG 1999
n Select the outcome Approved (see screen), click the right-hand mouse button and choose
CREATE (1).
n Choose Send mail (2) to insert a step to send a mail.
SAP AG BC601 4-17

6WHS&UHDWH0DLO6WHS

'HILQH
'HILQH

PDLOUHFLSLHQW
PDLOUHFLSLHQW
'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW
'HILQH
'HILQH
PDLOWLWOH
PDLOWLWOH
'HILQH
'HILQH
PDLOWH[W
PDLOWH[W
SAP AG 1999
n Specify the recipients of the mail - the recipient in the example is the workflow administrator.
n Define the title and text of the mail.
n Choose Back (2) to exit the screen.
n The system creates a task to send the mail. The short text and long text of the task are queried for this
purpose (3).
SAP AG BC601 4-18

6WHS'HOHWHRU1RW"
,QVHUW'HFLVLRQ

&OLFN
&OLFN

&UHDWH

&UHDWH
EXWWRQ
EXWWRQ

&OLFNRQFH
&OLFNRQFH
WRVHOHFW
WRVHOHFW
WKHRXWFRPH
WKHRXWFRPH
SAP AG 1999
n In the dotted circle, the step responsible for sending the notification mail is selected.
n Up to this point, the following has occurred: We can create and approve a notification of absence and
send a mail if the manager decided to approve. Which step comes next? If the manager rejects the
notification of absence, the employee has to be asked if he wants to revise or withdraw the request.
n Proceed as follows: Select the "Rejected" line (1) and click the "Create node" button (2).
n A dialog box (3) appears with all available step and operator types. Choose 8VHUGHFLVLRQ.
n The graphic is now replaced by the detail screen for the user decision (4). Enter at least the two
options (revise and withdraw) and leave the screen by choosing the "Back" button (green arrow to
the left).
SAP AG BC601 4-19

'HOHWHRU1RW"
,QWHJUDWH'HOHWLRQ
&OLFNRQFH
WRVHOHFW

'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW
SAP AG 1999
n Select the undefined step after the "Withdraw" line (1) and double-click on the task "Delete
notification of absence" in the "Available tasks" area (2). The step is integrated in the workflow
definition (3).
n The dotted circle shows which element has been inserted.
SAP AG BC601 4-20

'HOHWHRU1RW"
,QWHJUDWH&KDQJH
&OLFNRQFH
WRVHOHFW

'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW
SAP AG 1999
n Select the undefined step after the "Change" line (1) and double-click the "Change notification of
absence" task in the available tasks area (2). The step is integrated into the workflow definition (3).
n The dotted circle shows which element has been inserted.
SAP AG BC601 4-21

6WHS,QVHUW/RRS
&OLFNRQFH
&OLFNRQFH
WRGURS
WRGURS
VWHS
VWHS
'RXEOHFOLFN
'RXEOHFOLFN
WRFUHDWH
WRFUHDWH
IODJ
IODJ

&OLFNRQFH
&OLFNRQFH
WRGHILQH
WRGHILQH
FRQGLWLRQ
FRQGLWLRQ
&OLFNRQFH
&OLFNRQFH
WRWUDQVIHU
WRWUDQVIHU
LFRQV
LFRQV
SAP AG 1999
SAP AG BC601 4-22

6WHS'HILQH/RRS&RQGLWLRQ

&OLFNRQFH
&OLFNRQFH
WRLQVHUW
WRLQVHUW
'RXEOHFOLFN
'RXEOHFOLFN
WRLQVHUW
WRLQVHUW
IODJ
IODJ
(QWHU
(QWHU
;DVWKH
;DVWKH
FRQVWDQW
FRQVWDQW
SAP AG 1999
n The condition editor appears.

n We want to make sure that the loop is exited when the indicator (Flag) contains the value X .
n Double-click on the entry Flag (1) to create the first part of the condition.
n Click once on = in the "Operators" toolbox (2) to set the operator.
n Enter X in the "Constants" field and press return (3).
n The condition is now consistent. Leave the condition editor and the detail view of the loop to display
the graphic again
SAP AG BC601 4-23

6WHS,QWHJUDWH$SSURYDOLQWR/RRS

&RQWH[WPHQX
&RQWH[WPHQX 6HOHFWVWHS
6HOHFWVWHS
5LJKWPRXVHEXWWRQ
5LJKWPRXVHEXWWRQ &XW
&XW
EXWWRQ
EXWWRQ

SAP AG 1999
n Up to this point, the following has occurred: We have created a loop without content. The approval
step should be able to be repeated as often as necessary. Therefore, we cut the whole part with the
approval and paste it into the loop.
n Double-click on the "Approve notification of absence" step. Click the right mouse button and choose
"Cut block" (1). The whole approval block disappears and is placed on the clipboard.
n Click on the "Undefined" step in the loop (2) and choose the "Paste" function from the menu (3). The
approval sequence is inserted into the loop.
SAP AG BC601 4-24

6WHS([LW/RRS
&OLFNRQFH
&OLFNRQFH
WRLQVHUW
WRLQVHUW
DSSURYDO
DSSURYDO

&OLFNRQFH
&OLFNRQFH
WRVHOHFW
WRVHOHFW
GHVWLQDWLRQ
GHVWLQDWLRQ
SAP AG 1999
n We have created the approval sequence and a corresponding loop. We now have to make sure that
the loop is terminated as soon as the manager has approved the notification of absence or the
employee withdrawn it.
n Click once on the symbol Container operation in the toolbox (1) and on the step that sends the mail,
in order to transfer the container operation (sets the X in the flag to terminate the loop) to the
SendMail step (2).
n Fill out the detail view of the container operation with the following values (3):
Field "Result element": Flag
Field "Expression": X
n This will move the value "X" to the variable "Flag".
n Leave the detail view and return to the graphic.
SAP AG BC601 4-25

6WHS6DYH/RRS

5LJKWPRXVHEXWWRQ
5LJKWPRXVHEXWWRQ
&RQWH[WPHQX
&RQWH[WPHQX
6HOHFWVWHS
6HOHFWVWHS
FKRRVH,QVHUW
FKRRVH,QVHUW

SAP AG 1999
n Now copy this container operation from the "Send mail" to the "Delete notification of absence" step.
n Proceed as follows:
Using the right mouse button, click on the container operation we just created and choose "Copy
block" (1).
Select the "Delete notification of absence" step and choose the "Paste" function from the menu (2).
n The container operation is copied and makes sure that the loop is terminated if the employee
withdraws their notification of absence
n The process is now finished (3): All steps are complete.
SAP AG BC601 4-26

6WHS$VVLJQ$JHQWV
:KRLVUHVSRQVLEOHIRUZKDW"
l Employee:
6 Create notification of absence
6 User decision - change or withdraw
6 Change notification of absence
l Manager
6 Approve notification of absence
6 Create document from template
l Workflow System
6 Send mail
6 Delete notification of absence
SAP AG 1999
n We have created a workflow definition. Up to now, however, only the structure of the workflow has
been determined (which action is followed by what) - the agents still have to be assigned.
n This step can be performed without any problems after the workflow definition has been created.
n At this point, we know exactly which step has to be assigned which agent.
SAP AG BC601 4-27

6WHS$VVLJQ$JHQWV+RZ"

&OLFNRQFH
&OLFNRQFH
WRQDYLJDWH
WRQDYLJDWH
&OLFNRQFH
&OLFNRQFH
WRQDYLJDWH
WRQDYLJDWH
SAP AG 1999
n To assign the agents, we use the navigation tree and double-click first the "Create notification of
absence" step (1) - the detail view appears (2). Choose the initiator from the list window and
navigate further.
n Double-click on the "Approve notification of absence" step (3). The detail screen is called. Assign
the "Superior of workflow initiator" and navigate further.
n Correctly assign the agents in the detail screen.
SAP AG BC601 4-28

6WHS$VVLJQ$JHQWV+RZ"

&OLFNRQFH
&OLFNRQFH
WRQDYLJDWH

WRQDYLJDWH
&OLFNRQFH
&OLFNRQFH
WRQDYLJDWH
WRQDYLJDWH
SAP AG 1999
n Proceed with the steps "User decision", "Delete or revise", and "Revise notification of absence" in
the same way as with the previous two steps.
SAP AG BC601 4-29

&RPSOHWLRQ
SAP AG 1999
n The process created behaves in exactly the same way as the workflow definition demonstrated.
n You can carry out a syntax check, as well as save and execute the process.
SAP AG BC601 4-30

6WDUW7UDQVDFWLRQV%DFNJURXQGDQG8VH
l :K\DUHVWDUWWUDQVDFWLRQVUHTXLUHG"
l :RUNIORZVVRPHWLPHVKDYHWREHVWDUWHGDQG
VXSSOLHGZLWKYDOXHVGLUHFWO\
l 8QWLOQRZDJHQHULFWUDQVDFWLRQ6:86KDVEHHQ
XVHGWRVWDUWZRUNIORZV
l 7KLVWUDQVDFWLRQLVDWHVWWRROQRWDZRUNLQJWRROIRU
XVHUV
l :KRUHTXLUHVVWDUWWUDQVDFWLRQV"
l ,WLVSRVVLEOHWRLQVHUWKHOSWH[WVGLUHFWO\LQWKH
VFUHHQVRIWKHVWDUWWUDQVDFWLRQ
l 8VHUVZKRVWDUWZRUNIORZVGLUHFWO\IURPDUHDPHQX
RU6$3PDLQPHQX!2IILFH!6WDUWZRUNIORZ
l 8VHUVZKRZDQWWRVWDUWZRUNIORZVIURPDVKRUWFXW
RQWKHLU:LQGRZV'HVNWRS
SAP AG 1999
n In the productive system, workflows are usually triggered by events.

n You can start a workflow for testing directly from the Workflow Builder by choosing the icon
"Test". The system goes to the test environment of transaction SWUS.
You can also call this test environment directly by choosing
SAP EASY ACCESS -> Tools -> Business Workflow -> Development -> Runtime Tools
-> Start Workflow (Test Environment).
n A special authorization was assigned to transaction SWUS with Release 4.5. It is no longer
accessible to business users.
Each user who has authorization for this transaction can execute 7898 workflows, even if they are not
actually authorized to do so by the organization model. Therefore, only workflow modelers and
workflow administrators should have this authorization.
n As of Release 4.5, you can define start transactions for workflow templates for special applications
(for example, call centers) or Web activities. These start transactions can be included in personal
favorites of the SAP EASY ACCESS Menu.
n When you create a start transaction for a workflow definition, a screen is displayed that shows all the
input parameters of the workflow and can be adapted as required. This enables you to "tailor" a
screen for the user group.
SAP AG BC601 4-31

6WDUW7UDQVDFWLRQV*HQHUDWLRQ
l +RZDUHVWDUWWUDQVDFWLRQVJHQHUDWHG"
: &XVWRPL]LQJRQHRIIDFWLYLW\
: 'HWHUPLQHQDPHVSDFHRIWUDQVDFWLRQFRGHVDQGPRGXOH
SRROVLQ&XVWRPL]LQJWUDQVDFWLRQ6:87
: *HQHUDWLRQXSWRDQGLQFOXGLQJ%
: ,QWKH6$3%XVLQHVV:RUNIORZ>'HYHORSPHQW@DUHDPHQX
FKRRVH'HILQLWLRQ7RROV!:RUNIORZ6WDUW7UDQVDFWLRQV
: ,QWKH7DVNILHOGVSHFLI\\RXUZRUNIORZWHPSODWH
: (QWHUIRUH[DPSOHDVWKHVFUHHQQXPEHU
: &KRRVHWKH&UHDWHSXVKEXWWRQ!WKHVWDUWWUDQVDFWLRQLV
QRZJHQHUDWHGDXWRPDWLFDOO\
: *HQHUDWLRQDVRI5HOHDVH&
: &DOOWKHZRUNIORZWHPSODWHDQGFKRRVH*RWR!%DVLFGDWDLQ
WKH:RUNIORZ%XLOGHU
SAP AG 1999
n To enable the system to create a unique name for the task-related transactions, you must maintain a
namespace template and a development class.
Customizing activities:
Maintain a two-character namespace template.
Specify the development class to which the task, the generated transaction, and all the required
programs are assigned.
n When generating start transactions, the system creates the following from this information:
The transaction code prefix Y<namespace_template> that all start transactions receive.
The module pool prefix SAPMY< namespace_template > under which the programs and screens
of a start transaction are stored.
n ;<=>
This Customizing is used both for the start transactions and the Web forms.
SAP AG BC601 4-32

6WDUW7UDQVDFWLRQV([DPSOH
.QRZOHGJHRIRSHUDWLQJWKH
JUDSKLFDOVFUHHQSDLQWHULV
Input data for task
WKHRQO\SUHUHTXLVLWH
Decision Edit Goto System Help
Start Deadline Refresh organizational environment

Name
Personnel number
Department
Cost center
Absent from To
Reason
Contact at
Request leave Attachment
1RSURJUDPPLQJ
UHTXLUHG
0DQXDOO\HGLWHGVFUHHQ
<RXFDQDOVRLQVHUWDGGLWLRQDO
KHOSWH[WVKHUH
SAP AG 1999
n The screen created by the system can easily be changed with the graphical screen painter, if you
adhere to the following rules:
Do not delete any fields that are not to be displayed and filled with values. Instead set these fields to
Output only and
Invisible.
The flow logic of the screen therefore does not have to be changed. Note, however, that mandatory
input parameters cannot be hidden'in this manner.
SAP AG BC601 4-33

:RUNIORZ7RROER[
6WDUWZRUNIORZ
6WDUWDQGWHVW
ZRUNIORZ
SAP AG 1999
n Transaction SWUI displays a list of small example workflows.

(Toolbox principle)
n You can start the workflows and test them "live".
n Call the Workflow Builder and look at the technical details for the workflow.
n Transaction SWUI shows each user those workflows for which the user is explicitly specified as the
agent (under Additional data -> Agent assignment) or that have been created as general tasks.
SAP AG BC601 4-34

:RUNIORZ'HILQLWLRQ6XPPDU\
l :RUNIORZWHPSODWHVDUHFOLHQW
LQGHSHQGHQW
l 7KHZRUNIORZGHILQLWLRQLVWKH
GHVFULSWLRQDQGLPSOHPHQWDWLRQ
RIDZRUNIORZSURFHVV
l :RUNIORZGHILQLWLRQLQVWHSW\SHVDQG
WKHLUV\PEROVLQWKH:RUNIORZ%XLOGHU
SAP AG 1999
SAP AG BC601 4-35

?A@CBED1FHGJIK1LNM)OPIQSRATUM)B@CBEDVBIW@
X IZY[BP\WF4]_^WTWK`âBTQSIZMbDVcCTdGJIK1LNM)OPIQSRATUMVBP@CBEDVBIW@

Define the components of a workflow definition.
At the beginning of your workflow project, you laid out the design of
your business process.
In order to design this process with SAP Business Workflow, you want to
learn about the features of the Workflow Builder.
This will enable you to convert your business process into a workflow
definition.
1-1 When editing a workflow template, you create the workflow definition. This is
processed when the workflow is executed. While the basic data of the workflow
represents the external relationship (such as triggering events), the workflow
definition describes the actual implementation of a business scenario as a sequence
of linked steps.
You can define the workflow using the Workflow Builder. Create a workflow
definition using the Workflow Builder and integrate a user decision step.
1-1-1 The first step is to create a workflow egfihZj#kmlonpk+q`j#r#r . Call this task
lms#t#uwvyx{zVt|qb}~zt#utyvyx{zVx{#uw#r#r .
1-1-2 Since no tasks are available yet, incorporate a user decision in your
At the beginning, the Workflow Builder displays an initial workflow
definition with a default structure consisting of:
Two symbols indicating the start and the end of the workflow definition
One undefined step
1-1-2-1 Create the user decision as the first step in the workflow definition
after the workflow is started. Call it hZx/uz)ZPtyzp Include 2
decisions and events, the first to #'#Ext and the other to
npE# .
1-1-2-2 The agent should be lms#uwt`z)z)x{# and the workflow initiator is the
person responsible.
SAP AG BC601 4-36

1-1-2-3 Check the change you made in the Workflow Builder. How has
your workflow definition been modified?
___________________________________________________
___________________________________________________
___________________________________________________
1-1-3 Finally, you must activate your workflow definition.
1-2 Test your workflow and display the work item in a parallel session in the Business
Workplace.
Open another session and go to the Business Workplace.
Arrange the windows so you can see both at the same time.
1-2-1 Go back to the first session and choose the "Test" icon in the Workflow
Builder.
You begin your test in the "Start Workflow (Test Environment)" screen.
1-2-2 After starting the workflow template, you will be presented with the
decision that you specified in your workflow definition. You are asked
whether you want to vy#Ext , z)E# or v`#v`ty , but do not give a decision
yet.
1-2-2-1 Switch to the other session and check the worklist of the Business
Workplace. Does it contain a work item?
___________________________________________________
1-2-2-2 The work item should NOT be listed in the worklist. Return to the
decision step in the other session and specify that the workflow is
to vy#Ex{t .
1-2-2-3 Check your worklist again. Is the previous work item still there?
___________________________________________________
If the work item is still displayed in your worklist, you have to

refresh the worklist. To do this, choose "Refresh".
SAP AG BC601 4-37

1-3 Go from the test environment back to the Workflow Builder in change mode to
extend your workflow definition using another user decision. If you choose
p~#Ext# , a work item is sent to the manager. The work item contains another
user decision.
1-3-1 Insert the step )uV###tuy . This step should be specified for the
undefined step immediately following the '#Px{t event after the first
user decision. Choose the step type User decision again.
Assign ")uEx##vyvytyEt` " as the outcome name.
1-3-2 The agent of the user decision should be the manager, g~#q`P~r#r#
1-4 Finally, you must check, activate, and test your workflow definition.
1-4-1 Check the modified workflow definition with the inclusion of the $)uw
###tuy step. What has changed?
1-4-2 Activate your workflow definition.
You receive the message

:RUNIORZGHILQLWLRQDFWLYDWHGVXFFHVVIXOO\
followed by the message

:RUNIORZGHILQLWLRQVDYHGDQGDFWLYDWHG

1-4-3 Start your workflow and test your modified workflow definition.
After selecting the appropriate response for the decision step

~#Ext , display the Business Workplace of the manager to make
sure that your message was received. Execute the work item and
choose "Information approved".
1-4-4 Check the workflow log for your workflow from the "Workflow Log"
screen and check the execution steps of your workflow.
The :RUNIORZORJ screen contains three tabs -
View: Workflow Chronicle, View: Workflow Agents, View:
Workflow Objects.
View: Workflow Chronicle

This view shows all the steps in a workflow that have already been
processed or are currently pending, as well as subworkflows.
By choosing the 'HWDLOV function for a step, you can find out:
Who carried out which detailed actions on this work item and the
result of the action
When this action was executed
SAP AG BC601 4-38

Which objects were affected
This view is generally used to determine which activities were
carried out.
The $JHQWV function displays the possible and selected agents of a
step.
The *UDSKLF function displays the graphical workflow log.
View: Workflow Agents

This view shows the employees that were involved in this workflow
up to now. A list is displayed for each employee indicating
Which action was carried out for which step
This view primarily indicates the extent to which an employee is
involved in executing a workflow.
View: Workflow Objects

This view lists the objects that are related to the workflow or that
have been addressed up to now when the workflow was executed.
These objects include
The "leading" object of the workflow
Attachments and objects that have been added to individual steps
within a workflow
A list is displayed for each object indicating
Who carried out which detailed action for which task.
When this action was executed.
This view indicates which information has been generated as well as
how it was generated and processed.
Select these tabs and functions to check the details of your workflow.
1-5 Create a new task group Z##_AG.

1-5-1 Assign your newly created workflow template to this task group.
1-6 Generate a workflow start transaction and include this in your favorites
in the SAP EASY ACCESS Menu.
SAP AG BC601 4-39

?A@CBED1FHGJIK1LNM)OPIQSRATUM)B@CBEDVBIW@
X IZY[BP\WF4]_^WTWK`âBTQSIZMbDVcCTdGJIK1LNM)OPIQSRATUMVBP@[BED)BIW@
1-1 Follow the steps below to define your workflow definition.
You can define the workflow using the Workflow Builder. Create a workflow
definition using the Workflow Builder and integrate a user decision step.
1-1-1 The first step is to create a workflow template egfhWj#kmlonpk+q`j#r#r . Call this
task lms#tuvyx{z)t*qb}~ztuHt`vyx{z)x#uw#dr#r .
:RUNIORZ%XLOGHU
&KRRVHWKH6DYHEXWWRQ6DYHWKHZRUNIORZWHPSODWHXQGHUWKH
VSHFLILHGQDPHDQGVWRUHLWLQWKHGHYHORSPHQWFODVV=
hZxty{'t )~#P
Abbr: ZWF_TEST1_##
Name Exercise 1 User decision for group ##
1-1-2 Since no tasks are available yet, incorporate a user decision in your
workflow definition as the first step. To do this, access the Workflow
Builder and insert the step.
1-1-2-1 Create the user decision as the first step in the workflow
definition after the workflow is started. Call it hZx/uzZEt`z)p
Include 2 decisions and events, the first to p'#Px{t and the
other to npE# .
2QWKH:RUNIORZ%XLOGHU&UHDWHVFUHHQGRXEOHFOLFNWKH
ILUVWXQGHILQHGVWHS
,QWKHGLDORJER[FKRRVHWKH8VHUGHFLVLRQEXWWRQ
2QWKH:RUNIORZ%XLOGHU&UHDWH6WHS8VHU'HFLVLRQ
VFUHHQHQWHUWKHIROORZLQJLQIRUPDWLRQRQWKH'HFLVLRQWDE
SDJH
SAP AG BC601 4-40

hZxty{'t )~#P
Title First test
hZx{t`{~tyz
Decision texts Outcome name
)~#P Continue Continue
Stop Stopped
1RSDUDPHWHUVDUHUHTXLUHGIRUWKLVWHVW
1-1-2-2 The agent should be lms#uwt`z)z)x{# and the workflow initiator is the
person responsible.
,QWKH$JHQWVVHFWLRQFKRRVH([SUHVVLRQDQGXVHWKH)
+HOSWRFKRRVHWKHYDULDEOH,QLWLDWRURIDZRUNIORZLQVWDQFH
IURPWKHSXOOGRZQPHQX
5HWXUQWRWKH:RUNIORZ%XLOGHU&UHDWHVFUHHQE\FKRRVLQJ
WKH%DFNEXWWRQJUHHQDUURZ
1-1-2-3 Check the change you made in the Workflow Builder. How has
your workflow definition been modified?
7KHXVHUGHFLVLRQ)LUVWWHVWLVWKHILUVWVWHSLQWKHZRUNIORZ
7KLVLVIROORZHGE\DQH[FOXVLYH25OHDGLQJWRWZRHYHQWV
&RQWLQXHDQG6WRSSHG7KLVLVWKHFKRLFHIRU\RXUGHFLVLRQ
1-1-3 Finally, you must activate your workflow definition.
2QWKH:RUNIORZ%XLOGHU&UHDWHVFUHHQFKRRVHWKH*HQHUDWHDQG
DFWLYDWHUXQWLPHYHUVLRQEXWWRQPDWFKV\PERO



SAP AG BC601 4-41

1-2 To make sure that you have correctly executed all steps when creating new
activities, test your workflow by following the steps below:
&KRRVHWKH7HVWLFRQ
2QWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQFKRRVH
6\VWHP&UHDWHVHVVLRQ
Arrange the windows so you can see both at the same time.
1-2-1 You begin your test on the "Start Workflow (Test Environment)" screen.
Start your workflow template.
6ZLWFKEDFNWRWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVHVVLRQ
&KRRVH(QYLURQPHQW5HIUHVKRUJDQL]DWLRQDOHQYLURQPHQWRUWKH
5HIUHVKRUJDQL]DWLRQDOHQYLURQPHQWEXWWRQ
7KHQXPEHURI\RXUZRUNIORZWHPSODWHVKRXOGEHGLVSOD\HGLQWKH7DVN
ILHOG
&KRRVH7DVN([HFXWHRUWKH([HFXWHEXWWRQ
1-2-2 After starting the workflow template, you will be presented with the
decision that you specified in your workflow definition. You are asked to
decide whether to vy#Ext , zVE# or vy#v1ty and whether you want to keep
the work item in the worklist, but do not give a decision yet.
1-2-2-1 Switch to the other session and check the worklist of the Business
Workplace. Does it contain a work item?
2QWKHLQLWLDOVFUHHQFOLFNRQWKH
6$3%XVLQHVV:RUNSODFH
LFRQRUFKRRVH2IILFH!:RUNSODFH!,QER[DQGGRXEOHFOLFN
RQ:RUNIORZ
<RXZLOOILQGDZRUNLWHP
1-2-2-2 The work item should NOT be listed in the worklist. Return to the
decision step in the workflow session and choose ~#Ext for the
workflow.
1-2-2-3 Check your Business Workplace session again. Is the previous

work item still there?
1R
If the work item is still displayed in your worklist, you have to

refresh the worklist. To do this, choose )ROGHU5HIUHVK
SAP AG BC601 4-42

1-3 Extend your workflow definition by a second user decision that contains only one
outcome. If you choose "'#Px{t ", a work item with user decision is sent to the
manager.
6ZLWFKEDFNWRWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVHVVLRQDQGUHWXUQWR

WKH:RUNIORZ%XLOGHUE\FKRRVLQJWKH%DFNEXWWRQ
1-3-1 Insert the step )uV###tuy . This step should be specified for the
undefined step immediately following the '#Px{t event after the first
user decision. An event should follow this user decision. Call this event
)u#Px{##vyv1tyEt`N .
2QWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQGRXEOHFOLFNWKHILUVW
XQGHILQHGVWHSDIWHUWKHHYHQW&RQWLQXH
,QWKHGLDORJER[FKRRVHWKH8VHUGHFLVLRQEXWWRQ
2QWKH:RUNIORZ%XLOGHU&UHDWH6WHS8VHU'HFLVLRQVFUHHQHQWHUWKH
IROORZLQJLQIRUPDWLRQ
hZxty{'t )~#P
Title Inform manager
hZx{tyd'tyz
Decision texts Outcome name
)~#P Information approved Informed
1RSDUDPHWHUVDUHUHTXLUHGIRUWKLVWHVW
1-3-2 The agent of the user decision should be the manager, g~#q`P~r#r#
,QWKH$JHQWVIUDPHVHOHFW8VHUIURPWKHSXOOGRZQPHQX
3UHVVWKH)NH\LQWKHILHOGQH[WWR8VHU
6HDUFKIRU%&0*5DQGFOLFNWKH&RS\EXWWRQJUHHQWLFN
5HWXUQWRWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQE\FKRRVLQJWKH
%DFNEXWWRQJUHHQDUURZ
1-4 Finally, you must check, activate, and test your workflow definition.
1-4-1 Check the modified workflow definition with the inclusion of the $)uw
###tuy step. What has changed?
8QGHU&RQWLQXHWKHUHLVDQDGGLWLRQDOVWHS,QIRUPPDQDJHUDQGD
QHZHYHQW,QIRUPHG
SAP AG BC601 4-43

1-4-2 Activate your workflow definition.
&KRRVHWKH*HQHUDWHDQGDFWLYDWHUXQWLPHYHUVLRQEXWWRQPDWFK
V\PERORQWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQ



1-4-3 Start your workflow and test your modified workflow definition.
&KRRVHWKH7HVWEXWWRQ
7KHQXPEHURI\RXUZRUNIORZWHPSODWHLVGLVSOD\HGLQWKH7DVNILHOG
&KRRVH7DVN([HFXWHRUWKH([HFXWHEXWWRQ
After selecting the appropriate response for the decision step

~#Ext , display the Business Workplace of the manager to make
sure that your message was received.
/RJRQDVWKHPDQDJHU%&0*5,QWKH6$3(DV\$FFHVV
PHQXFKRRVHWKH:RUNSODFHV\PERO2SHQWKH,QER[IROGHU
DQGFOLFNRQ:RUNIORZ
([HFXWHWKHZRUNLWHPE\GRXEOHFOLFNLQJWKHV\PEROLQWKH
([FROXPQRUVHOHFWWKHZRUNLWHPDQGFOLFNWKH([HFXWH
EXWWRQ
Note that the message is displayed at the bottom right side of the
screen.
Choose "Information approved".
1-4-4 Check the Workflow log for your workflow on the "Workflow Log" screen
and check the execution steps of your workflow.
6ZLWFKEDFNWRXVHU%&DQGFKRRVHWKH:RUNIORZORJEXWWRQRQ
WKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQ
&KHFNWKHH[HFXWLRQVWHSVLQWKH6WDWXVFROXPQ
SAP AG BC601 4-44

The "Workflow log" screen contains three tabs -
View: Workflow Chronicle, View: Workflow Agents, View:
Workflow Objects.
View: Workflow Chronicle
This view shows all the steps in a workflow that have already been
processed or are currently pending, as well as subworkflows.
By choosing the 'HWDLOV function for a step, you can find out:
Who carried out which detailed actions on this work item and the
result of the action
This view is generally used to determine which activities were
carried out.
The $JHQWV function displays the possible and selected agents of a
step.
The *UDSKLF function displays the graphical workflow log.
View: Workflow Agents

This view shows the employees that were involved in this workflow
up to now. A list is displayed for each employee indicating:
Which action was carried out for which step
This view mainly indicates which role an employee has played in
executing a workflow.

This view lists the objects that are related to the workflow or that
have been addressed up to now when the workflow was executed.
These objects include:
Attachments and objects that have been added to individual steps
within a workflow
A list is displayed for each object indicating:
Who carried out which detailed action for which task
This view indicates which information has been generated as well as
how it was generated and processed.
Select these tabs and functions to check the details of your workflow.
SAP AG BC601 4-45

1-5 Create a new task group Z##_AG.
7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
2QWKH7DVN0DLQWDLQVFUHHQHQWHUWKHIROORZLQJLQIRUPDWLRQ
hZxty{'t )~#P
7DVNW\SH 7DVN*URXS
7DVN =B$*
&KRRVHWKH&UHDWHEXWWRQ
2QWKH
7DVN*URXS$GGVFUHHQDVVLJQWKHQDPH7DVNJURXS*URXS

6DYHWKHWDVNJURXSDVDORFDOREMHFW
1-5-1 Assign your newly created workflow template to this task group.
7DVNV7DVN*URXSV
'RXEOHFOLFN&KDQJH
hZxty{'t )~#P
7DVNW\SH 7DVN*URXS
7DVN =B$*
&KRRVHWKH&KDQJHEXWWRQ
2QWKH
7DVN*URXS&KDQJHVFUHHQFOLFNRQWKH:)7HPSODWHWDE
SDJH
8QGHU2EM,'HQWHUWKHQXPEHURI\RXUQHZO\FUHDWHGZRUNIORZWHPSODWH
IRUH[DPSOHRUVHDUFKIRULWXVLQJWKH)+HOS]ZI
6DYH\RXUHQWULHV
SAP AG BC601 4-46

1-6 Generate a workflow start transaction and include this in your favorites
in the SAP EASY ACCESS Menu.
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW'HILQLWLRQ7RROV:RUNIORZ
6WDUW7UDQVDFWLRQV
hZxty{'t )Z'#E
7DVN 7KHQXPEHURI\RXUZRUNIORZ
WHPSODWH
&RQILUPE\SUHVVLQJWKH5HWXUQNH\
&KRRVH&RQWLQXHIRUDOOZDUQLQJV
0DNHDQRWHRIWKHWUDQVDFWLRQFRGHLQWKH7UDQVDFWLRQFRGHILHOGDQGUHWXUQWR
WKH6$3($6<$&&(660HQX
3RVLWLRQWKHFXUVRURQWKH)DYRULWHVIROGHU
&OLFNWKHULJKWPRXVHEXWWRQDQGFKRRVH,QVHUWWUDQVDFWLRQ
(QWHU\RXUJHQHUDWHGWUDQVDFWLRQFRGH
3RVLWLRQWKHFXUVRURQWKHWUDQVDFWLRQ
&OLFNWKHULJKWPRXVHEXWWRQDQGFKRRVH&KDQJHIDYRULWHV
&DOOWKHWUDQVDFWLRQ0DWHULDOZRUNIORZ*URXS
SAP AG BC601 4-47

%XVLQHVV2EMHFW%XLOGHU
&RQWHQWV
l 7HUPLQRORJ\
l (QKDQFLQJDQREMHFWW\SH
SAP AG 1999
SAP AG BC601 5-1

%XVLQHVV2EMHFW%XLOGHU&RXUVH2EMHFWLYHV
l 'HILQHFRPSRQHQWVRIDEXVLQHVVREMHFWW\SH
l &KHFNDQGHQKDQFHDEXVLQHVVREMHFWW\SH
l 'HVFULEHWKHSXUSRVHRIGHOHJDWLRQRIREMHFWW\SH
EHKDYLRU
SAP AG 1999
SAP AG BC601 5-2

SAP AG 1999
SAP AG BC601 5-3

%XVLQHVV2EMHFW%XLOGHU%XVLQHVV6FHQDULR
l 'XULQJWKHILUVWZRUNIORZGHVLJQDFWLYLWLHV\RX
GLVFRYHUWKDW6$3GRHVQRWVXSSRUWDOOUHTXLUHG
IXQFWLRQDOVWHSVZLWKVWDQGDUGWDVNV
l 7REXLOG\RXURZQWDVN\RXZDQWWRNQRZPRUH
DERXWWKHEDVLFFRPSRQHQWVRIDWDVN
l ,Q6$3%XVLQHVV:RUNIORZDQREMHFWW\SHLVWKH
EDVLVIRUDOOVLQJOHVWHSWDVNV
l &KHFNDQGHQKDQFHWKHPDWHULDOPDVWHUEXVLQHVV
REMHFWW\SH%86
SAP AG 1999
n For this course, sub-types of the object type BUS1001 have already been created.
You will be working with the object types Y##MARA.
SAP AG BC601 5-4

%XVLQHVV2EMHFW7\SH
,QWHUIDFH
,QWHJULW\ $FFHVV
XVLQJ
Attributes
%XVLQHVV Consistency
2EMHFW requirements
COM/DCOM
NHUQHO (object-
related) %$3,V
0HWKRGV
Representative is part of
CORBA
is a
Business ABAP (RFC)

rules
Internal Structure Events
(environment-
Specialization related)
SAP AG 1999
n The internal structure of a business object is hidden using several layers.

n A business object is described by the following elements:
n Object ID Unique identifier
n Key field Unique identification option of the object
n Object name Unique semantic designation
n Components Differentiated internal structure elements of the object
relationship type: "Is a part of"
n Subtypes Specialization of an object
relationship type: "Is a"
n Attribute Entered by, entry date, approved by, etc.
n Methods Implementation of the methods applicable to the object
n Events Events that generate the object depending on its object status
n Information about the different access options for data in the R/3 system is covered in the overview
course BC095, and also the specific courses on BAPI programming CA925/CA926/CA927
SAP AG BC601 5-5

%XVLQHVV2EMHFW5HSRVLWRU\%25
%XVLQHVV
:RUNIORZ
%2
%2
%2
%2
%2
%2 %2
%2
%25
$UFKLYH/LQN %2
%2 %2
%2
%2
%2
%$3,

%2
%2
%2
%2

%2
%2

0RGHOLQJ
SAP AG 1999
n Object types are developed from the applications and stored in the Business Object Repository
(BOR)
n To find the BOR, choose
SAP EASY ACCESS - Tools - Business Workflow - Development - Definition Tools - Business
Object Builder
n The Business Object Repository button enables you to carry out a specific search by application
component
n The business object type is implemented using an ABAP program.
n Object types and their components are each assigned one of 4 statuses:
Modeled: A program does not yet exist for the object type
Implemented: The program for the object type can be called, but the implementation is not yet
fully completed
Released: The program for the object type can be called by anyone
Obsolete: The object type is being replaced by another object type in the long term.
SAP AG BC601 5-6

2EMHFW7\SHDQG,QVWDQFH
6
&ODVV 6SHFLDOL]DWLRQ &ODVV 2EMHFWW\SH
,QVWDQFLQJ 6LQJOHREMHFW ,QVWDQFH
2EMHFW
$LUFUDIW
&DUJRSODQH 3DVVHQJHUSODQH
&KDUWHUSODQH 6FKHGXOHGSODQH
7879$: ;<=)>
#$&%(') *+ D79DE FD)
? -. ,-. , -.
/)@ +0"2A:222B3C !" ))!" ))!G
/!) +012435 /@) +0.22435
SAP AG 1999
n In SAP terminology, object classes are described as object types and a single business object is
described as an instance.
n Object types (classes) describe an abstract business object, the data that belongs to it, methods, and
so on.
n Object types can be inherited. Inherited object types contain all the methods and data fields of the
original, and additional specific data and methods.
n This enables polymorphism, which combines the same attributes from different, specialized objects.
Implementing defined interfaces (attributes and methods) from objects has the same effect.
n In this example, charter and scheduled planes are specific instances of a passenger plane. They are
polymorphs relating to the object type class Passenger plane.
n Multiple inheritance is currently not directly supported by SAP business objects. An object can
implement several interfaces.
n Instances of business objects contain actual data, for example, a customer order. There can be any
number of instances of an object type.
SAP AG BC601 5-7

([DPSOHVRI2EMHFW7\SHV
l 6$3REMHFWW\SHV
,QYRLFH %6(*B00,9
H
6DOHV2UGHU %86
H
'HOLYHU\QRWH /,.3
H
0DWHULDO %86
H
%LOORIPDWHULDO %86
H
l ([WHUQDOGRFXPHQWV
$UFKLYHGGRFXPHQWV 72$9
H
3XUFKDVHRUGHU,GRF ,'2&25'(56
H
SAP AG 1999
n SAP Business Workflow represents the concept and implementation of an object-oriented approach.
n The object type Notification of absence is, for example, described by the following data:
Key: Number of the notification of absence
Attributes: Created by, entry date, status
Methods: Create, approve, edit, delete
n Objects are concrete instances of an object type that can be identified by a unique key, for example,
the notification of absence with the number 2000, or the notification of absence with the number
2010.
n Access to the method is implemented in an ABAP program.
You can view the program. Use the Program button in the display function of the object type in the
BOR
SAP AG BC601 5-8

2EMHFWVLQ:RUNIORZ
Event
Triggering
event
Workflow
Workflow
definition
Workflow manager
Terminating
event
Task Work item
Work item manager

2EMHFWW\SH 2EMHFWW\SH
Executing an
Attribute Method object method
ABAP
Dictionary Database
External
SAP AG 1999 SAP functions applications
n The actions in a workflow are described by tasks. These tasks are based on the methods of object
types.
n The definition of objects can be changed without having to modify workflow definitions or
organizational structures.
n The definition of an object type in the BOR also includes events that describe status changes of the
object type.
These events can have a triggering effect on workflows as well as terminating effects on individual
tasks within the workflow.
SAP AG BC601 5-9

0DWHULDO:RUNIORZ%&
0DWHULDO 7DEOHRIFKDQJHGRFXPHQWV
2OG0DWHULDO 2ULJLQDOBSDUW WULJJHUV

1HZBSDUW
/DE 30 (YHQW

=%86
&KHFN ,PSRUWSDUDPHWHU
2OGB0DWHULDOBFKDQJHG
WDEOH IRUUROH
7/
VWDUWV
2UJ3ODQ
(QJLQHHULQJXQLW
5ROH
'HWHUPLQH
3URGXFW0DQDJHPHQWXQLW :RUNIORZ
VXSHULRURI
3URGXFW0DQDJHUSRVLWLRQ
+ROGHU-RQHV 7DVN'LVSOD\
$JHQW FKDQJHGRFXPHQWV
+ROGHU5DQGRO
7DVN'LVSOD\
5ROH
'HWHUPLQHUHVSRQVLEOHXVHUIRUODERUDWRU\30
PDWHULDO
SAP AG 1999
n BOR - Workflow linkage

n First, the system searches for a standard object type for material using the structure search (Business
Object Repository button in transaction SWO1)
n After this, check the attributes, methods, and events of the standard object type
n If your workflow requires additional elements, you need to create a subtype.
n The dummy workflow in the course BC601 uses a method Display change documents and an event
Material changed. Neither of these is available in the standard object type BUS1001.
SAP AG BC601 5-10

2EMHFW7\SH'HILQLWLRQRID6XEW\SH
6XSHUW\SH 6XEW\SH
%86 =%86
0DWHULDO 0\B0DWHULDO
.H\ILHOGV Materialno .H\ILHOGV Materialno
$WWULEXWHV MaterialType $WWULEXWHV MaterialType

MaterialGroup
MaterialGroup Division
Division OldMaterial
OrderUnit
OldMaterial
BasicMaterial
0HWKRGV Edit
0HWKRGV Edit
Create
Create Display
Display Report1
(YHQWV
Created
Created (YHQWV
Changed
SAP AG 1999
n The analysis of an existing object type can result in a need for additional attributes, methods, and
events.
Adjustment of the standard object type is then carried out using the definition of a subtype.
The subtype inherits all properties, methods and events of the supertype and is open for new
customer-specific attributes, methods and events.
n You can only make changes directly in an object type provided by SAP if the change is described in
a SAPNet note.
n When creating a subtype, proceed as follows:
Position the cursor in the BOR on the standard object type
Button Create subtype
Enter the required names in the subsequent dialog box. When assigning names use the customer
namespace. By defining a sub-object type you are creating a new ABAP program.
n This is reflected in the program name
The object type must be assigned when saving a development class. Otherwise it is not possible
to release the object type.
Enhance the object type according to your requirements
Set the whole object type to status implemented and then to released, and then set the
individual
components to 'implemented'and ' released'
.
SAP AG BC601 5-11

'HOHJDWLRQ
([DPSOHVFHQDULR
8VLQJWKH6$3$UFKLYH/LQNLQWHUIDFHDSDSHUGRFXPHQWLVWREHFRPHDQREMHFWRI
W\SH(..2SXUFKDVLQJGRFXPHQWWKDWLVWREHVXEVHTXHQWO\VWRUHGLQDQ
H[WHUQDODUFKLYH
,QWKLVVFHQDULR6$3$UFKLYH/LQNFDOOVWKHPHWKRG&21),50LQWKHREMHFWW\SH
(..2LVHQKDQFHGZLWKDVXEREMHFWW\SH=(..2IRUDVSHFLILFFXVWRPHU
(..2 =(..2
QRPHWKRG 1RGHOHJDWLRQ PHWKRG
HNNRFRQILUP ]HNNRFRQILUP
7KHDSSOLFDWLRQ6$3$UFKLYH/LQNRQO\NQRZVWKHREMHFWW\SH(..2
(..2GRHVQRWKDYHWKHPHWKRG&21),50
6XEVHTXHQWVWRULQJIDLOVDWUXQWLPHZLWKWKHHUURUPHVVDJH
0HWKRG&21),50QRWLPSOHPHQWHG
SAP AG 1999
n Testing delegations:
I?JLK)JNM?OQP?RSNT)URBVRW!RX)K)J0Y!TZ\[
Display the required supertype in the Business Object Builder and choose the icon Test
You will not see any attributes, events and methods defined in the subtype
I?JLK)JNM?OQKSNJNRU]VRW@RX)K)J0Y!T)ZQ[
Display the required supertype in the Business Object Builder and choose the icon Test
You will see all the attributes, events and methods defined in the subtype and you can test the
elements
n To set up a delegation, you use the Business Object Builder:
Object Builder - Settings - Delegate - System-wide
Change mode - Button New entries
Object type: Supertype entry
Delegation type: Subtype entry
Person responsible: Person who entered the delegation and is therefore responsible for the
Customizing.
^ TJNR
:
The GUI-specific checkbox must remain empty
SAP AG BC601 5-12

'HOHJDWLRQ
([DPSOHVFHQDULR
8VLQJWKH6$3$UFKLYH/LQNLQWHUIDFHDSDSHUGRFXPHQWLVWREHFRPHDQREMHFWRI
W\SH(..2SXUFKDVLQJGRFXPHQWWKDWLVWREHVXEVHTXHQWO\VWRUHGLQDQ
H[WHUQDODUFKLYH
,QWKLVVFHQDULR6$3$UFKLYH/LQNFDOOVWKHPHWKRG&21),50LQWKHREMHFWW\SH
(..2LVHQKDQFHGZLWKDVXEREMHFWW\SH=(..2IRUDVSHFLILFFXVWRPHU
'HOHJDWLRQVHWXS =(..2
(..2
QRPHWKRG 0HWKRG
HNNRFRQILUP ]HNNRFRQILUP
7KHDSSOLFDWLRQ6$3$UFKLYH/LQNRQO\NQRZVWKHREMHFWW\SH(..2
(..2GRHVQRWKDYHWKHPHWKRG&21),50
7KHUHLVQRGHOHJDWLRQEHWZHHQ(..2DQG=(..2ZKLFKPHDQVWKHPHWKRGVIURP
=(..2DUHXVHGDWUXQWLPH
=(..2NQRZVWKHPHWKRG&21),50
6XEVHTXHQWVWRULQJLVSRVVLEOH
SAP AG 1999
n Summary of the basic procedure:

Creating a subtype
Enhancing an object type
Delegation from a supertype to a subtype.
n CAUTION:
If a subtype is created and a delegation set up, everything that you subsequently define in the
workflow (triggering events, defining tasks, entering links) will only be executed in association with
the supertype.
In the system, the subtype only appears in the BOR and in the delegation.
At runtime, however, the components of the subtype are used instead of those of the supertype.
n The key fields of the supertype and the subtype must be identical.
n In the basic data for an object type you can find whether it is a supertype or a subtype.
n Any amount of subtypes can be created for one supertype,
but only one of these subtypes can be selected as a delegation type.
SAP AG BC601 5-13

2EMHFW7\SHV(OHPHQWV
2EMHFWW\SH
3URJUDP
.H\ILHOGV
7UDQVDFWLRQ
)LHOGUHIHUHQFH
$WWULEXWHV
2EMHFW
UHIHUHQFH )XQFWLRQ
PRGXOH
([SRUWLPSRUW 5HSRUW
SDUDPHWHU
0HWKRGV
5HVXOW $%$3FRGLQJ
(YHQWV
SAP AG 1999
n Possible status changes to an object type are defined in events.

For example, the event "material changed" should occur if a material master is changed using the
transaction MM02.
n The creation of an event for the object type in the BOR does not mean that it is automatically
triggered at the appropriate time.
The application must publish the event specifically in the system.
In the "Events" unit, you will see how to make applications publish events, if they do not do it as
standard.
n Attributes can refer to fields in the Dictionary and therefore to a database table, as well as to other
object types. For example, the attribute "Order" in the object type "Material" refers to the object type
"Order" (BUS2012). For example, at runtime all orders are available for the material "P-100", and
their attributes can be evaluated. You can also access the methods of the object type order.
n Methods can refer to all functions stored in R/3.
A method can call a report, a transaction, a function module, or any ABAP Coding that is stored or
that can be customer-specific.
SAP AG BC601 5-14

2EMHFW7\SH'HILQLWLRQ
%DVLFGDWD Object
l *HQHUDO5HODWLRQVKLSVWRVXSHULRU
W\SHUHOHDVHJHQHUDWLRQ
l &KDQJLQJDQGWUDQVSRUWLQJGDWD
l 'HIDXOWV)RUPHWKRGVDQGDWWULEXWHV
l &XVWRPL]LQJ'LVSOD\SHUVRQVUHVSRQVLEOHGHOHJDWLRQ
.H\ILHOGV
l ,GHQWLILFDWLRQRIDQREMHFW
l 'DWDW\SHUHIHUHQFH
H
Dictionary field: Only character-based data types,
up to 70 characters total
SAP AG 1999
n The basic data of an object type is in Business Object Repository Maintenance (SWO1), under the
icon Basic data (hat icon)
n To find out whether a supertype exists, see the tab page '
General'in the basic data.
On the tab page Customizing , you can see whether a delegation type has been created
n The person who last changed the object is also stored in the basic data.
n Entry default method: This method is selected if no there are no further specifications when
accessing an object of this object type.
Example: Executing an object by double clicking in a display list.
n Key fields act as the unique identification of a concrete object
n The key fields of supertypes and subtypes must be identical
SAP AG BC601 5-15

2EMHFW7\SH'HILQLWLRQ$WWULEXWHV
l $WWULEXWHVGHVFULEHWKHIHDWXUHVRIDQREMHFWW\SH
l 5HTXLUHGHQWULHV
l 'HVFULSWLRQWH[WV
l +RZWKHYDOXHRIWKHDWWULEXWHDWUXQWLPHLVGHFLGHG
,QIRUPDWLRQVRXUFH
'DWDEDVHILHOG
H
9LUWXDO
H
l :KDWWKHDWWULEXWHUHIHUVWRGDWDW\SHUHIHUHQFH
$%$3'LFWLRQDU\ILHOG
H
2EMHFWW\SH
H
l $WWULEXWHSURSHUWLHVLIQHFHVVDU\
SAP AG 1999
n Attributes are available as interface elements and can be incorporated into workflow texts. Attributes
are also used in the workflow definition when formulating conditions, which means they can be used
within process control
I?TM?U_R
n :
ABAP Dictionary field: At runtime, the value of the attribute is taken from a field in an R/3
database table
Example: Material short text from BUS1001 - Refers to the field MAKTX in the table MAKT
Virtual: The value of the attribute must be determined dynamically at runtime according to the
values of the object type
Example: All existing orders for a material
KJNKaJNb)cR]URSNRURZ?_R
n ` :
Reference to a dictionary field - Example: see material short text above
Reference to an object type - Example: see all existing orders above
n If an attribute refers to another object type, its attributes and methods are also available at runtime in
the program
n For virtual attributes, coding must be implemented in the program of the object type.
n Attribute properties: An attribute can have multiple lines (all orders), and/or can be obligatory (must
always have a value), or instance independent (value does not depend on a concrete object, for
example, all IDOC message types in R/3)
SAP AG BC601 5-16

2EMHFW7\SH'HILQLWLRQ0HWKRGV
l 3HUPLWWHGIXQFWLRQIRUDQREMHFW
l 3URSHUWLHV
5HIHUHQFHWR6$3IXQFWLRQV
H
'LDORJPHWKRG
H
'LDORJPHWKRGFKDQJHPDWHULDOFUHDWHVDQH[HFXWDEOHZRUNLWHP
IRUWKHVHOHFWHGDJHQWV
1RGLDORJPHWKRG
H
7KHEDFNJURXQGPHWKRG'HOHWHUHTXHVWFUHDWHVDZRUNLWHPDQG
DXWRPDWLFDOO\H[HFXWHVLW
6\QFKURQRXVPHWKRGVFDQKDYHDGHWHUPLQHGUHVXOWRU
H
H[SRUWSDUDPHWHU
6\QFKURQRXVPHWKRGVFDQGHILQHH[FHSWLRQVIRUHUURUKDQGOLQJ
H
3DUDPHWHUVFDQEHWUDQVIHUUHGWRPHWKRGVZKHQFDOOHG
H
SAP AG 1999
n Methods encapsulate the functions that are available and are permitted for an object
n It can be necessary to enter import parameters at runtime for methods to work correctly (defined in
the interface for the method)
n Synchronous methods can return values to the calling program in the form of
Export parameters (defined in the interface of the method)
Result parameter
- The possible values of the result are stored in a check table
- They are then recognized in the workflow definition, and are automatically inserted as the
possible outcomes of the workflow step the method has called Example: APPROVE
method of the object type FORMABSENC
n The opposite of synchronous methods are asynchronous methods. Asynchronous methods can have
import parameters, but no export parameters, result parameters, or exceptions.
Reason: Asynchronous methods do not send a response to the calling program.
n To implement the method in the object type, proceed as follows:
Select a method, button Create , enter the basic data
Select the new method, button Program
The system will implement the method in the program on demand, as far as possible.
SAP AG BC601 5-17

6\QFKURQRXVDQG$V\QFKURQRXV0HWKRGV
l 7DVNVFDQKDYHWHUPLQDWLQJHYHQWV
l 6\QFKURQRXVPHWKRG
7KHPHWKRGLVFDOOHGDVVXPHV
H
SURFHVVFRQWURODQGVHQGV dfeFgh:
7DVN Ci
FRQILUPDWLRQWRWKHFDOOHUDIWHU
SURFHVVLQJ
H
2SWLRQDO,PSRUWSDUDPHWHU 6\QFKURQRXV
6\QFKURQRXV
REMHFWPHWKRG
REMHFWPHWKRG
2SWLRQDO5HVXOW
H
H[SRUWSDUDPHWHUH[FHSWLRQV
l $V\QFKURQRXVPHWKRG
7KHPHWKRGLVFDOOHGLVH[HFXWHG
H
dfeF:fg
ZLWKRXWFRQQHFWLRQWRWKHFDOOHU 7DVN Ci
DQGGRHVQRWVHQGDFRQILUPDWLRQ
DIWHUSURFHVVLQJ
H
2SWLRQDO,PSRUWSDUDPHWHU $V\QFKURQRXV
$V\QFKURQRXV
REMHFWPHWKRG
REMHFWPHWKRG
SAP AG 1999
n Synchronous methods return control to the calling program when the method is complete. The work
item underlying the method is then completed by the system.
n Asynchronous methods do not return confirmation.
The work item generated remains in the inbox of the agent because it is not known when the called
method is completed.
n To terminate work items for asynchronous methods, the application executed by the work item must
trigger a terminating event.
n The terminating event is specified when defining the standard task.
Menu path: SAP EASY ACCESS - Tools - Business Workflow - Development - Definition Tools -
Tasks/Task Groups
Create/Change - Enter "standard task" in the "Task type" field and click on the tab page
"Terminating events"
n A terminating event always refers to exactly 1 work item, which means that the work item ID must
be entered as a variable when defining the terminating event. The variable is always called
_WI_OBJECT_ID, and is always entered under ELEMENT.
SAP AG BC601 5-18

2EMHFW7\SH'HILQLWLRQ(YHQW
6\VWHPZLGH (YHQWVDUHRQO\GHILQHG
QRWLILFDWLRQUHJDUGLQJ LQWKHREMHFWW\SH
FKDQJHVWRWKHREMHFW
VWDWXV
Object
7KH6$3DSSOLFDWLRQ (YHQWSDUDPHWHUV
PXVWDFWLYDWHWKH WUDQVIHULQIRUPDWLRQ
HYHQWQRWWKHREMHFW IURPHYHQWFUHDWRUWR
W\SH HYHQWUHFHLYHU
SAP AG 1999
n Published event: System-wide message about change in status of an object

Kmnc?W!RO
n jlk :
Sales order created
Customer master changed
Invoice booked
Material deleted
n Events are only defined for object types in the Business Object Repository
n The workflow can only work with the event if the relevant application triggers the event at the
correct position at runtime.
SAP AG BC601 5-19

6SHFLILF2EMHFW7\SHV
0HWKRG([DPSOHV
2IILFHGRFXPHQW 62)0 Send SAPoffice document
6$36FULSW
67'B7(;7 Replace text symbols and display text
VWDQGDUGWH[W
&DOOH[WHQGHG
+(/3 Display help object
KHOS
7UDQVDFWLRQ 767& Execute transaction
$%$3
75',5
SURJUDP
Execute program
SAP AG 1999
n The object type SOFM is intended for SAP experts who want to program functions for the SAP
office folders and documents.
n The object type STD_TEXT can be used to integrate SAPscript text into a mail sent out by
workflow. (Although the SELFITEM approach is easier.)
n Use the object type TSTC to execute a transaction in a workflow step.
n Use the object type TRDIR to execute a report in a workflow step.
SAP AG BC601 5-20

%XVLQHVV2EMHFW%XLOGHU8QLW6XPPDU\
l :RUNIORZDUFKLWHFWXUHLVEDVHG
RQREMHFWW\SHV
l 2EMHFWW\SH.H\ILHOGVDWWULEXWHV
PHWKRGVHYHQWV
l %XVLQHVV2EMHFW5HSRVLWRU\%25
&ROOHFWLRQRI6$3DQGRZQREMHFW
VXEW\SHV
SAP AG 1999
SAP AG BC601 5-21

oqpsrutvxwzys{)rLps|E{{~}|8tFwzyBru|
z=r8vwzyB{rp]| {{~}|ts|s{rtFq|tCrLpFyssts| {

Define the components of a business object type
Check and enhance a business object type
Describe the purpose of object type delegation
During your first workflow design activities, you establish that SAP does
not support all of your required functional steps with predefined
standard tasks.
In order to build your own task, you need to know more about the basic
components of a task.
In SAP Business Workflow, an object type is the basis for all tasks.
In this scenario you will check and enhance the material master business
object type Y##mara (derived from BUS1001).
1-1 The Business Object Repository is the basis for all workflows. To better understand
these workflows, you need to become familiar with navigation in the Business
Object Repository (BOR), and the different statuses of object types.
Note: For these exercises you need to enter a development class.

Enter the development class 4 , and create a new correction
request with the title z9~\uC . ## is your
assigned group number.
Do use the option LOCAL OBJECT, because this will not allow
you to release your object types. The workflow will only recognize
released object types.
1-1-1 Find your team s business object type Y##MARA.
What is the current status of this object type?
____________________________________________________________
1-1-2 List all the possible statuses for an object type, and their icons:
____________________________________________________________
____________________________________________________________
____________________________________________________________
SAP AG BC601 5-22

1-1-3 Check the functions of the inherited method ExistenceCheck by testing on
valid and invalid material numbers. Use material number x for a
positive test and 4 for a negative test.
For a positive test, the object type methods, events, and attributes
triggered are displayed. After executing ExistenceCheck, you will
receive a success notification S 000.
For the negative test, you will receive an exception error message
stating that the object does not exist.
1-1-4 Test the Edit method for your material u (## is your group
number), and check Basic data 1 and Basic data 2 . Change the value of
the fields Old Matl Number (Basic data 1) and Basic Material (Basic
data 2) Choose your G## for the Lab./office field (Basic data 1 - Entry:
G##)
1-2 To meet specific business requirements, you may sometimes need to enhance object
types for your workflows. In the following exercises, you will create your own
subtype for doing this.
After each implementation step, note any relevant changes in color keys, symbols,
and status. Create a subtype of your material object type.
1-2-1 Go to the screen Business Object Builder: Initial Screen .

1-2-2 Enter your object type, and create a new subtype called xxx
Enter the following:

Supertype: Y##mara
Subtype: Ymara##
Object name: Material_group_##
Name: Material, Group ##
Description: Material, Group ##
Program Ymara##
Application: S
The object type and program fields both need to be in the Customer
Namespace (should start with a Z or Y).
The Object type , Object name and Program fields must be
filled.
1-2-3 Change your material object type to meet the requirements of the following
steps. After each step, examine the object type program to see if anything
has changed.
SAP AG BC601 5-23

1-2-4 For this workflow exercise, one event is needed as a triggering event. Create
the new event Old_Material_Changed for your object type x .
Define the event, then change the status of the event to implemented .
1-2-5 Allow access to the field Basic material from Basic data 2 in the
material master. Create a new attribute BasicMaterial , based on the same
ABAP Dictionary table used to implement the object key (use field
WRKST).
1-2-6 In the Create Attribute dialog box, answer the question Create with
ABAP Dictionary field attributes? with<HVThen enter the table name
MARASelect your field WRKST and define the attribute. Finally,
change the status to implemented.
1-2-7 For the new task in the workflow definition, a user must display a change
log of the material master. Create a new method Display_Changes . In
dialog mode, and using the ABAP transaction MM04, define the method as
synchronous. In the Create Method dialog box, answer the question
Create with function module as template? with 1R
Then implement the program for this method. This will be generated by the
system.
Finally, change the status of the method to implemented .
1-2-8 Change the status of your object type to implemented and then to
released . Click away any warnings that may appear. Then change the
status of all new events, attributes and methods to released .
1-2-9 Finally, regenerate your object type.
SAP AG BC601 5-24

z=r8vQ|80|Q8t5r8p
2-1 Before you create a delegation, check the object type Y##MARA. This test
environment provides an overview of the situation before and after delegation.
2-1-1 Display the object type Y##MARA, choose test with Material T-BBD## ,
and find its events and methods.
Can you see your new event?

_____________
2-2 Define SYSTEM WIDE DELEGATION in the Business Object Repository.
The object type will be your supertype Y##MARA . Enter your name as the
responsible person and choose your sub- object type YMARA## as the
delegation type.
You may be asked to enter a Change request. Choose the Own

request button, and select the change request number created in the
previous exercise. Continue by choosing the Continue Enter
button.
2-3 You will now see the new event, the new method and the new attribute that you
have defined.
2-4 Test the Display_Changes method.
2-5 Why don t you see your new event and your new method when displaying the
methods and events of the object type Y##Mara?
SAP AG BC601 5-25

z=r8vwzyB{rp]| {{~}|ts|s{rtFq|tCrLpFyssts| {
1-1 The Business Object Repository is the basis for all workflows. To better understand
these workflows, you need to become familiar with navigation in the Business
Object Repository (BOR), and the different statuses of object types.
Note: For these exercises you need to enter a development class.

Enter the development class 4 , and create a new correction
request with the title z9~\uC . ## is your
assigned group number.
Do use the option LOCAL PRIVATE OBJECT, since this will
not allow you to release your object types. The workflow will only
recognize released object types.
1-1-1 Find your team s business object type Y##MARA.

What is the current status of this object type?
____________________________________________________________
'RXEOHFOLFN%XVLQHVV2EMHFW%XLOGHU
,QWKH%XVLQHVV2EMHFW%XLOGHU,QLWLDO6FUHHQHQWHUWKHIROORZLQJ
LQIRUPDWLRQDQGFKRRVH'LVSOD\
=h
9x? Qu
Object type/interface type Y##MARA
1-1-2 List all the possible statuses for an object type, and their icons:
____________________________________________________________
____________________________________________________________
____________________________________________________________

6HOHFW2EMHFW7\SH'LVSOD\
,QWKH'LVSOD\2EMHFW7\SHVFUHHQFKRRVH8WLOLWLHV&RORUOHJHQGRU
FKRRVH(GLW&KDQJHUHOHDVHVWDWXV2EMHFWW\SH
SAP AG BC601 5-26

1-1-3 Check the functions of the inherited method ExistenceCheck by testing on
valid and invalid material numbers. Use material number x for a
positive test and 4 for a negative test.
)URPWKH'LVSOD\2EMHFW7\SHVFUHHQ
FOLFNRQWKH3/86VLJQLQIURQWRI0HWKRGV3RVLWLRQWKHFXUVRURQ
([LVWHQFH&KHFN
&KRRVH(GLW7HVWH[HFXWHRUWKH7HVWH[HFXWHLFRQ
&OLFNWKH&UHDWH,QVWDQFHEXWWRQDQGHQWHUPDWHULDOQXPEHU7%%'
6FUROOGRZQDQGFKRRVHWKHPHWKRG(;,67(1&(&+(&.
&KRRVHWKH([HFXWH0HWKRGLFRQ
For a positive test, you receive a success notification S, and the

return code 000
5HSHDWWKHVDPHSURFHGXUHIRUWKHQHJDWLYHWHVWEXWHQWHUPDWHULDO===
For the negative test, you will receive an exception error message
stating that the object does not exist.
1-1-4 Test the Edit method for your material and check Basic data 1 and Basic
Data 2 .
&KRRVH(GLW7HVWH[HFXWHRUWKH7HVWH[HFXWHLFRQ
&OLFNWKH&UHDWH,QVWDQFHEXWWRQDQGHQWHUPDWHULDOQXPEHU7%%'
6FUROOGRZQDQGVHOHFWPHWKRG(',7
&KRRVHWKH([HFXWH0HWKRGLFRQ
6HOHFW%DVLFGDWDDQGFOLFNWKH&RQWLQXH(QWHUEXWWRQ
Change the value of the fields Old Matl Number (Basic data 1) and Basic
Material (Basic data 2) Choose your G## for the Lab./office field
(Basic data 1 - Entry: G##) ## is your group number.
&KRRVHWKH6DYHEXWWRQ
5HWXUQWRWKH7HVW2EMHFW7\SHVFUHHQE\VHOHFWLQJWKH%DFNEXWWRQ
1-2 To meet specific business requirements, you may sometimes need to enhance object
types for your workflows. In the following exercises, you will create your own
subtype for doing this.
After each implementation step, note any relevant changes in color keys, symbols,
and status. Create a subtype of your material object type.
SAP AG BC601 5-27

1-2-1 Go to the screen Business Object Builder: Initial Screen .
'RXEOHFOLFN%XVLQHVV2EMHFW%XLOGHU
1-2-2 Enter your object type, and create a new subtype called xxx
,QWKHVFUHHQ%XVLQHVV2EMHFW%XLOGHU,QLWLDO6FUHHQHQWHUWKH
IROORZLQJLQIRUPDWLRQ
=h
9x? Qu
Object type/interface type Y##MARA
&KRRVHWKH&UHDWHVXEW\SHLFRQ
,QWKH&UHDWH2EMHFW7\SHGLDORJER[HQWHUWKHIROORZLQJLQIRUPDWLRQ
=h
9x? Qu
Supertype Y##MARA
YMARA##
Object type
Object name Material_Group_##
Name Material, Group-##
Description Material, Group-##
Program YMARA##
Application S
&KRRVHWKH&RQWLQXH(QWHUEXWWRQ
,QWKH&UHDWH2EMHFW'LUHFWRU\(QWU\GLDORJER[HQWHU=DVWKH
GHYHORSPHQWFODVV
&KRRVHWKH6DYH(QWHUEXWWRQ
,QWKH(QWHU&KDQJH5HTXHVWGLDORJER[FKRRVHWKH&UHDWHUHTXHVW
EXWWRQ
,QWKH&UHDWHUHTXHVWGLDORJER[HQWHUWKHIROORZLQJLQIRUPDWLRQ
=h
9x? Qu
Short description Group##, do not transport
&KRRVHWKH6DYH(QWHUEXWWRQ
SAP AG BC601 5-28

The object type and program fields both need to be in the Customer
Namespace (should start with a Z or Y).
The Object type , Object name and Program fields must be
filled.
1-2-3 Change your material object type to meet the requirements of the following
steps. After each step, examine the object type program to see if anything
has changed.
1-2-4 For this workflow exercise, one event is needed as a triggering event. Create
the new event Old_Material_Changed for your object type xx .
,QWKH&KDQJH2EMHFW7\SHVFUHHQSRVLWLRQWKHFXUVRURQ(YHQWVDQG
&KRRVH(GLW&UHDWHRUWKH&UHDWHEXWWRQ
,QWKH&KDQJH2EMHFW7\SHGLDORJER[HQWHUWKHIROORZLQJLQIRUPDWLRQ
=h
9x? Qu
Event Old_Material_Changed
Name Old material changed
Description Old material changed
&KRRVHWKH6DYHEXWWRQ
Then change the status of the event to LPSOHPHQWHG.
&OLFNRQWKH3/86VLJQLQIURQWRI(YHQWV
3RVLWLRQWKHFXUVRURQ0DWHULDOB*URXSB2OGB0DWHULDOB&KDQJHG
6HOHFW(GLW&KDQJHUHOHDVHVWDWXV2EMHFWW\SHFRPSRQHQW7R
LPSOHPHQWHG.
1-2-5 Allow access to the field Basic material from Basic data 2 in the
material master. Create a new attribute BasicMaterial , based on the same
ABAP Dictionary table used to implement the object key (use field
WRKST).
3RVLWLRQWKHFXUVRURQ$WWULEXWHV
&KRRVH(GLW&UHDWHRUFKRRVHWKH&UHDWHEXWWRQ
SAP AG BC601 5-29

1-2-6 In the Create Attribute dialog box, answer the question "Create with
ABAP Dictionary field attributes?" with<HVThen enter the table name
MARA Choose your field WRKST and define the attribute.
&KRRVHWKH&RQWLQXH(QWHUEXWWRQDIWHUVHOHFWLQJWKH:5.67ILHOG
,QWKH&UHDWHGLDORJER[FKRRVHWKH&UHDWH(QWHUEXWWRQWRFUHDWH
WKHQHZDWWULEXWH%DVLF0DWHULDO
The attribute is already implemented.
1-2-7 For the new task in the workflow definition, a user must display the change
log of the material master. Create a new method Display Changes In
dialog mode, and using the ABAP transaction MM04, define the method as
synchronous.
3RVLWLRQWKHFXUVRURQ0HWKRGVDQGFKRRVH(GLW&UHDWHRUWKH
&UHDWHEXWWRQ
In the Create Attribute dialog box, answer the question Create with
function module as template? with 1R
,QWKH&KDQJH2EMHFW7\SHGLDORJER[HQWHUWKHIROORZLQJLQIRUPDWLRQ
=h
9x? Qu
Method Display Changes
Name Display Changes
Description Display Changes
2QWKH*HQHUDOWDESDJHVHOHFWWKH'LDORJDQG6\QFKURQRXVFKHFN
ER[
*RWRWKH$%$3WDESDJHDQGVHOHFWWKH7UDQVDFWLRQUDGLREXWWRQ
(QWHUWUDQVDFWLRQ00LQWKH1DPHILHOG
,QWKH&KDQJH2EMHFWW\SHVFUHHQ
&OLFNRQWKH3/86VLJQLQIURQWRI0HWKRGVDQGVHOHFW\RXUQHZ
PHWKRG'LVSOD\&KDQJHV
Then generate the program for this method.
&KRRVH*RWR3URJUDP
$QVZHU<HVWRWKHJHQHUDWLQJTXHVWLRQ
&KRRVHWKH6DYHEXWWRQRQWKH2EMHFW7\SH(GLWRUVFUHHQ
5HWXUQWRWKH&KDQJH2EMHFW7\SHVFUHHQE\VHOHFWLQJWKH%DFNEXWWRQ
SAP AG BC601 5-30

Finally, change the status of the method to implemented .
3RVLWLRQWKHFXUVRURQ0DWHULDOB*URXSB'LVSOD\&KDQJHV
6HOHFW(GLW&KDQJHUHOHDVHVWDWXV2EMHFWW\SHFRPSRQHQW7R
LPSOHPHQWHG.
1-2-8 Change the status of your object type to implemented and then to
released .
&KRRVH(GLW&KDQJHUHOHDVHVWDWXV2EMHFWW\SH 7RLPSOHPHQWHG
&KRRVH(GLW&KDQJHUHOHDVHVWDWXV2EMHFWW\SH 7RUHOHDVHG
&OLFNDZD\DQ\PHVVDJHVWKDWPD\DSSHDU
Now change the status of all new events, attributes and methods to
released .
,QWKHVFUHHQ%XVLQHVV2EMHFW%XLOGHU,QLWLDO6FUHHQFKRRVH
2EMHFWW\SH&KDQJHRUFKRRVHWKH&KDQJHEXWWRQ
&OLFNRQWKH3/86VLJQLQIURQWRI(YHQWV
3RVLWLRQWKHFXUVRURQ0DWHULDOB*URXSB2OGB0DWHULDOB&KDQJHG
&KRRVH(GLW&KDQJHUHOHDVHVWDWXV2EMHFWW\SHFRPSRQHQW7R
UHOHDVHG.
5HSHDWWKHDERYHVWHSVWRFKDQJHWKHVWDWXVRI\RXUQHZ0HWKRG
0DWHULDOB*URXSB'LVSOD\&KDQJHVDQG\RXUQHZ$WWULEXWH
0DWHULDOB*URXSB%DVLF0DWHULDOWRUHOHDVHG
1-2-9 Finally, regenerate your object type.
,QWKH&KDQJH2EMHFWW\SHVFUHHQFKRRVH
2EMHFWW\SH*HQHUDWHRUWKH*HQHUDWHEXWWRQ
SAP AG BC601 5-31

z=r8vQ|80|Q8t5r8p
2-1 Before you create a delegation, check the object type Y##MARA. This test
environment provides an overview of the situation before and after delegation.
2-1-1 Display the object type Y##MARA, choose test with Material T-BBD## ,
and check its events and methods.
Can you see your new event and your new method?
_____________
2-2 Define SYSTEM WIDE DELEGATION in the Business Object Repository.

5HWXUQWRWKHVFUHHQ%XVLQHVV2EMHFW%XLOGHU,QLWLDO6FUHHQ
&KRRVH6HWWLQJV'HOHJDWH6\VWHPZLGH
The object type will be your supertype Y##MARA . Enter your name as the
responsible person and choose your sub- object type YMARA## as the
delegation type.
,QWKHVFUHHQ'LVSOD\9LHZ&XVWRPL]LQJ2EMHFW7\SHV2YHUYLHZ
&KRRVHWKH'LVSOD\!&KDQJHEXWWRQSHQFLOLFRQWRVZLWFKWR&KDQJHPRGH
7DEOHPD\EHORFNHGE\DQRWKHUFRXUVHSDUWLFLSDQW2QO\RQHXVHUFDQXSGDWH
WKLVWDEOHDWDWLPH
&KRRVHWKH1HZHQWULHVEXWWRQ
,QWKHVFUHHQ1HZ(QWULHV'HWDLOVRI$GGHG(QWULHVHQWHUWKHIROORZLQJ
LQIRUPDWLRQ
=f
9 \x
Object type Y##MARA (supertype)
Person responsible BC601-##
Delegation type YMARA## (subtype)
&KRRVHWKH6DYHEXWWRQDQGH[LWWRDOORZWKHQH[WSDUWLFLSDQWWRFUHDWHDWDEOH
HQWU\
SAP AG BC601 5-32

You may be asked to enter a Change request. Choose the Own
request button, and select the change request number created in the
previous exercise. Continue by choosing the Continue Enter
button.
2-3 Return to the Object Builder.

Display the object type Y##MARA.
Create a test instance, for example using material P-100.
Can you see the new event, the new method and the new attribute?
<HV
2-4 Test the Display_Changes method.
<RXFDQVHHWKHFKDQJHGRFXPHQWDERXWWKHFKDQJH\RXKDYHPDGH
2-5 Why don t you see your new event and your new method when displaying the
methods and events of the object type Y##Mara?
7KHPHWKRGDQGWKHHYHQWDUHQRWGHILQHGIRUWKHREMHFWW\SH<0$5$
<RXZLOORQO\EHDEOHWRDFFHVVWKHPWKURXJKWKHGHOHJDWLRQ
SAP AG BC601 5-33

7DVNV
&RQWHQWV
l %DVLFVIRUGHILQLQJDWDVN
l (QKDQFHGFRPSRQHQWVIRU
GHILQLQJDWDVN
l 7DVNJURXSV
l %XVLQHVV:RUNIORZ([SORUHU
SAP AG 1999
SAP AG BC601 6-1

7DVNV8QLW2EMHFWLYHV
l &UHDWHDWDVN
l 'HILQHWKHEDVLFFRPSRQHQWVRIDWDVN
l 'HILQHWKHHQKDQFHGFRPSRQHQWVRIDWDVN
l 'HILQHDQGXVHWDVNJURXSVIRUVWUXFWXULQJ
WDVNV
l 8VHWKH%XVLQHVV:RUNIORZ([SORUHU
SAP AG 1999
SAP AG BC601 6-2

SAP AG 1999
SAP AG BC601 6-3

7DVNV%XVLQHVV6FHQDULR
l <RXQRZNQRZWKDWLQDZRUNIORZRQO\DWDVNEULQJV
DERXWIXQFWLRQDOLW\
l <RXZDQWWRFUHDWHDQHZWDVN'LVSOD\PDWHULDO
FKDQJHGRFXPHQWWRIXOILOOWKHUHTXLUHPHQWVRI
\RXUEXVLQHVVSURFHVV
l <RXKDYHWRNQRZDOOWKHFKDUDFWHULVWLFVRI\RXU
WDVNWRFRUUHFWO\LQWHJUDWHLWLQWR\RXUZRUNIORZ
GHILQLWLRQ
l ([LVWLQJWDVNVDUHWREHJURXSHGLQWRDWDVNJURXS
l <RXZDQWWRPDQDJHWDVNVXVLQJWKH%XVLQHVV
:RUNIORZ([SORUHU
SAP AG 1999
SAP AG BC601 6-4

7DVN7\SHV:6DQG76
:RUNIORZWHPSODWH
Workflow
7DVNW\SHV
Definition
:RUNIORZWHPSODWH
:6
7DVNV

Task 76

Object type
Attribute Method
6$3IXQFWLRQV
SAP AG 1999
n There are 2 main types of tasks:

Tasks - abbreviation TS, reference one method of an object type and represent one step in the
business process
Workflows - abbreviation WS, represent the business process and consist of a sequence of
individual tasks and control steps
n The following questions have to be asked for a new task:
Who will carry out this work?
What work has to be done?
What should the notification text look like?
Do I need additional flags or settings?
For example, "Terminating events".
SAP AG BC601 6-5

7DVNV
7DVN
6WDQGDUGWDVN
76
Reference to object
method or
manual activity
:RUNIORZ
:RUNIORZWHPSODWH
Reference to :6
workflow definition
SAP AG 1999
n From an organizational perspective, tasks are the central element in the workflow system.
n Tasks are used to describe a business process. Tasks can be executed one after the other in the
business process. Parallel steps can, however, also be defined.
n Tasks are designed as client-independent and time-independent, reusable modules.
n Tasks are generally executed in the context of a workflow definition.
In exceptional cases, they can also be explicitly triggered without being included in a workflow.
n Like tasks, workflow templates are also client-independent and time-independent.
n You may find workflow tasks (WF) and customer tasks (T ) in your system. They are client-specific
and have a validity period.
Up to and including Release 4.0, WF and T could be created with the same authorizations as WF
und TS.
As of Release 4.5A, when you create new workflows and tasks, the system only offers you WS
and TS.
WF and T are not being further developed.
Existing WF and T are still executable.
n 1RWH: You cannot include customer tasks (T ) in a workflow template.
SAP AG BC601 6-6

([DPSOHRID7DVN
0DWHULDO 0\BSDUW :ULWH

FKDQJH
2OGPDWHULDO 2ULJLQDOBSDUW GRFXPHQW
1HZBSDUW 7ULJJHUV
(YHQW
=%86
2UJDQL]DWLRQDOSODQ 2OGB0DWHULDOB&KDQJHG
'HVLJQGHSDUWPHQW :+2"

'HVLJQHUSRVLWLRQ
+ROGHU0DU\
=%86'LVSOD\ :KDW"
Task
$WWULEXWHVDQGNH\ :RUNLWHP Display material
RI=%86 DQG (Confirm end of
ORQJWH[WV processing)
SAP AG 1999
n )LUVW: Assign the method of a business object type to your task.

Entries in the Object type/Methods fields.
n 6HFRQG: Assign the maximum number of possible agents.
Maintain entry under Additional data -> Agent assignment.
It can concern a group of organizational elements.
Create: Select the task, menu option Agent assignment -> Create, choose and specify the
required organizational object.
The task can also be a general task, that is, every SAP user is a possible agent.
Create: Select the task, button Properties, flag General task.
n 7KLUG: Define the work item text and the long text of the task.
You can insert variables of the workflow interface that are expanded with current data at
runtime.
Entry in Work item text field.
Entry on Description tab page.
SAP AG BC601 6-7

'HILQLQJD'LDORJ7DVN2YHUYLHZ
2UJDQL]DWLRQDO
6WDQGDUGWDVN
SODQ
2EMHFWW\SHZLWK What is to
Who is
REMHFWPHWKRG execute
responsible
for the
the task? task?
&KDUDFWHULVWLFV
*HQHUDOWDVN
DOO6$3XVHUV
7H[WV (YHQWV
Work item text: Title of work
item in inbox Terminating Events
Long texts: Triggering events
! Description Only if the task is not
! Notification used in a workflow
! Missed deadlines
SAP AG 1999
n A task refers to a method of an object type.

n A task has to have possible agents referring to the organizational model or all SAP users (general
task).
n The work item text will show up in the "Description" column of the Business Workplace.
n The task description can be used to inform the user about the work that has to be done.
n If tasks are controlled with simple deadline monitoring, individual message texts have to be defined
for all types of missed deadlines.
n The variable parts of all those texts are automatically replaced at runtime by accessing the attributes
of the processed objects.
n If an asynchronous method call is used for the task, the method does not return confirmation of
completion to the calling system.
The work item is also not completed.
An asynchronous method has to make the notification of completion known using an event.
This event has to be entered as a terminating event for the task.
n Triggering events are only required if the task is to be started independently of the workflow
definition.
Such events can be found in R/3 in error handling of IDOCs, for example.
In customer-specific scenarios, SAP recommends that tasks are always included in workflows, even
if the whole business process could be modeled in a task.
SAP AG BC601 6-8

6HWWLQJVIRUD7DVN
l %DFNJURXQG
" %DVHGRQWKHREMHFWPHWKRGWKHWDVNFDQEHIODJJHGDVD
EDFNJURXQGWDVN
l &RQILUPHQGRISURFHVVLQJ
" 'XULQJUXQWLPHWKHXVHUFDQFUHDWHDQDWWDFKPHQWDIWHUWKH
ZRUNLWHPKDVEHHQH[HFXWHG
" 7KHXVHUH[SOLFLWO\H[SODLQVWKDWWKHZRUNLWHPGRHVQRWKDYH
WREHSURFHVVHGDQ\ORQJHU
l 6$3SKRQH
l )RUP6$3IRUPVLQGLFDWRU
SAP AG 1999
n SAPphone Scenario customer service

A customer service employee wants to call to a customer.
The workflow dials the telephone number that is linked to the current customer object of the
workflow.
After the connection is established, the customer service employee can talk to the customer while
viewing the important customer data on the screen.
n SAPphone Scenario customer service
A customer is calling your enterprise. A telephone service tool asks the customer to enter the
customer contract number.
The SAP System collects the important customer data and starts a workflow.
The next available customer service employee starts the work item.
Their telephone is now connected to the customer and the customer data is displayed on their
screen.
n SAPforms enables occasional users of the R/3 System and the SAPGUI to start workflows and
execute workflow tasks.
For example, a user can fill out a Visual Basic or Outlook form on their PC and then send it to an R/3
System. A workflow is then started in R/3. Conversely, a user can receive a work item in their mail
inbox. If they execute the work item, a form starts. For more information, see the SAPforms
documentation.
SAP Library -> Basis Components -> Business Management -> SAP Business Workflow ->
Reference Documentation -> Form Integration with SAPforms.
SAP AG BC601 6-9

:RUN,WHP7H[W
l :RUN,WHP7H[W
" 7LWOHRIZRUNLWHPLQWKH%XVLQHVV:RUNSODFH
" )LUVWFUHDWHWKHZRUNLWHPWH[WDQGSRVLWLRQWKHFXUVRUWRLQFOXGHD
YDULDEOH
" &KRRVHWKH
,QVHUWYDULDEOH
LFRQXQGHUWKHZRUNLWHPWH[W
" 7KHREMHFWDWWULEXWHVIURPWKHWDVNLQWHUIDFHDUHWKHQDYDLODEOH
([DPSOH
3URFHVVUHTXHVWIURP B:,B2EMHFWB,'&UHDWHG%\
SAP AG 1999
n The long texts of tasks use the same concept for variables.
You maintain long texts in the task on the Description tab page.
You include variables by choosing Insert -> Expression .
n Example of a task description for the "Approval step
Employee &_WI_Object_ID.CreatedBy& created a notification of absence under the number
&_WI_Object_ID.Number& on &_WI_Object_ID.CreateDate&. Decide whether to approve.
SAP AG BC601 6-10

7DVNVZLWK7HUPLQDWLQJ(YHQWV
l 7DVNVEDVHGRQDV\QFKURQRXVPHWKRG
FDQKDYHWHUPLQDWLQJHYHQWV
l 7DVNVEDVHGRQDQDV\QFKURQRXV
PHWKRGPXVWKDYHDWOHDVWRQH
WHUPLQDWLQJHYHQW
" 7KHDV\QFKURQRXVPHWKRGLVRQO\ 6LQJOHVWHS
6LQJOHVWHS
WDVN
VWDUWHGE\WKHZRUNIORZV\VWHP
" 7KHDV\QFKURQRXVPHWKRGFDOOV
DWUDQVDFWLRQRIDQ6$3DSSOLFDWLRQ $V\QFKURQRXV
$V\QFKURQRXV Terminating
REMHFWPHWKRG
REMHFWPHWKRG
" 7KHDSSOLFDWLRQWKHQDFWLYDWHVWKH
event
WHUPLQDWLQJHYHQW
" 7KHWDVNLVHQGHGZKHQWKHWHUPLQDWLQJ
HYHQWLVDFWLYDWHG
SAP AG 1999
n The terminating events are published events of the business object type on which the task is based.
n You have to assign terminating events to each asynchronous task. The system recognizes by the
triggering event that the method call is completed.
n ([DPSOH: The asynchronous task "Delete leave request" has to have at least one terminating event,
usually the event "Deleted".
The application triggers the event in the context of the method "Delete leave request" and the
associated work item can be completed.
n ([DPSOH: The synchronous task "Approve application" can have a terminating event. The event
may be an enterprise-wide recruitment freeze.
n Synchronous tasks need terminating events if it is not guaranteed that the processing on which the
work item is based is executed by the workflow system exclusively.
n If a task is to be able to be completed by a business event exclusively, this task has to contain an
asynchronous method.
SAP AG BC601 6-11

7HUPLQDWLQJ(YHQWV
l 7HUPLQDWLQJHYHQW (OHPHQWRIWKHWDVN
FRQWDLQHUZKLFKUHIHUVWR
WKHWULJJHULQJREMHFWW\SH
RIWKHHYHQW
Task container
#$&%'#)(*)+ ,.-0/1#2%43
#$&%'#56-/ 7.891#.5;:.,<;/
Terminating events
(OHPHQW Object
D (EF5)=G?H@
Object type
type Notification
Notification of
of absence
absence
B:,B2EMHFWB,'RI Event C.?.I?.A?C Deleted
WDVNFRQWDLQHU
Event Deleted
Element
Element #$&%1#)(=>?.@AB#2%C
B:,B2%-(&7B,'
B:,B2%-(&7B,'
VWDQGVIRUWKHDIIHFWHGZRUNLWHP
VWDQGVIRUWKHDIIHFWHGZRUNLWHP
DWUXQWLPH
DWUXQWLPH
SAP AG 1999
n A terminating event applies to one instance of a task only, that is, to one specific work item. The key
of the work item, therefore, has to be given to the terminating event.
n ([DPSOH:
A head of department has four work items for leave request.
They have the work item numbers 1, 2, 3, 4.
The person making request number 3 deletes their request. The work item in the inbox is then no
longer needed and has to be deleted.
The terminating event "Request deleted" now has to be generated for work item 3.
The object reference is given to the terminating event for this purpose.
n The object reference for a task is always in the variable _WI_OBJECT_ID.
n A terminating event for a task is, therefore, specified as follows:
Object type for which the event is defined
Name of event
Container element _WI_OBJECT_ID
SAP AG BC601 6-12

7DVNZLWK6\QFKURQRXV0HWKRG
l 7KHWDVNLVFRPSOHWHG
ZKHQWKHPHWKRGUHWXUQV
ILQDOFRQILUPDWLRQ
WRWKHZRUNIORZV\VWHP Terminating
7DVN
l 7KHWDVNLVDOVRFRPSOHWHG
event
LIWKHDSSOLFDWLRQ
WULJJHUVWKHWHUPLQDWLQJHYHQW
6\QFKURQRXV
6\QFKURQRXV
REMHFWPHWKRG
REMHFWPHWKRG
l 6\QFKURQRXVWDVNVFDQ
KDYHH[SRUWSDUDPHWHUVDQGUHVXOWV
SDUDPHWHUV
'DWDH[FKDQJHRFFXUV
LQERWKGLUHFWLRQV
SAP AG 1999
n Since a synchronous method can return values to the calling system, synchronous methods can have
export parameters or results parameters.
n Example of results parameters:
The method Approve leave request is to be completed with Approved (A), Rejected (R) and
New (N).
The values A, R and N are stored as fixed values in a domain.
The relevant value is transferred to the workflow in a special attribute.
n The definition of results parameters can be exemplified using the method Approve notification of
absence (Formabsenc.Approve).
General definition: Results parameter flag set
Under Result type, you find the reference field for the respective value (= PROCSTATE) and the
reference table SWXFORMAB.
In the ABAP Dictionary, the field PROCSTATE is of the field type SWX_PROCST. This field
type is assigned a domain SWX_PROCST. The domain contains the fixed values A, R, N.
n If you incorporate a task that links to a method with results parameters into a workflow definition,
the Workflow Builder automatically generates outcomes corresponding to the defined fixed values.
n If a task is to be able to be completed by a business event exclusively, this task has to contain an
asynchronous method.
SAP AG BC601 6-13

2EMHFW7\SH1RWLILFDWLRQRI$EVHQFH
'\]^4QK `
_ba XcPed)f2Zhghi
J 4LKNM O
Number
Number 1XPEHU
P UQVR S WT4
ApprovDate
ApprovDate $SSURYDOGDWH
ApprovBy
ApprovBy $SSURYHGE\
CreateDate
CreateDate &UHDWLRQGDWH
CreatedBy
CreatedBy &UHDWHGE\
X 4WYO
Display
Display 'LVSOD\QRWLILFDWLRQRIDEVHQFH Dialog Synchronous
Create
Create &UHDWHQRWLILFDWLRQRIDEVHQFH Dialog Synchronous
Delete
Delete 'HOHWHQRWLILFDWLRQRIDEVHQFH Asynchronous
Update
Update 8SGDWHQRWLILFDWLRQRIDEVHQFH Dialog Synchronous
Approve
Approve $SSURYHQRWLILFDWLRQRIDEVHQFHDialog Synchronous Result
Z[ Q
Created
Created 1RWLILFDWLRQRIDEVHQFHFUHDWHG
Deleted
Deleted 1RWLILFDWLRQRIDEVHQFHGHOHWHG
SAP AG 1999
n The object type notification of absence (FORMABSENC) is used as an example demonstrating the
attributes, methods, and events above.
SAP AG BC601 6-14

6WDQGDUG7DVN$SSURYH1RWLILFDWLRQRI$EVHQFH
$)BDSSURYH
2EMHFWW\SH FORMABSENC Notification of absence

2EMHFWPHWKRG Approve Synchronous method; Method with dialog
Definition in task B:,B5HVXOWis created automatically
container
5HODWLRQVKLS Position: Head of department
7HUPLQDWLQJHYHQWV Not applicable
&KDUDFWHULVWLFV Confirm completion of processing
:RUNLWHPWH[W Approve notification of absence from &

Assign container elements Use &_WI_Object_Id.CreatedBy&
/RQJWH[W
SAP AG 1999
n A results parameter is defined for the method APPROVE. The results parameter refers to a result
type that references a table field (PROCSTATE in SWXFORMABS).
n From the entries in the dictionary, it becomes clear that the result type refers to fixed values of the
domain SWX_PROCST. The fixed values are A (Approved), R (Rejected) and N (New).
n If the method APPROVE is incorporated in a workflow step, the system always generates possible
outcomes for the 3 values automatically.
SAP AG BC601 6-15

6WDQGDUG7DVN'HOHWH1RWLILFDWLRQRI$EVHQFH
$)BGHOHWH
2EMHFWW\SH FORMABSENC Notification of absence

2EMHFWPHWKRG Delete Asynchronous method
Definition in task container Not necessary
5HODWLRQVKLS Not applicable
7HUPLQDWLQJHYHQWV Event: DELETED (Notification of absence deleted)
Container element B:,B2%-(&7B,'
&KDUDFWHULVWLFV Background processing
:RUNLWHPWH[W Not applicable
Assign container elements

/RQJWH[W Not applicable
SAP AG 1999
n Example of a background task.

There are no possible agents for this task and no agents are selected in the workflow step.
n Example of an asynchronous method. The existing work item is automatically completed if the event
Deleted is triggered in the system. The event has to refer to the object on which the work item is
based.
The object is specified in the element _WI_OBJECT_ID.
SAP AG BC601 6-16

,QWHJUDWLQJD7DVNLQD:RUNIORZ
&DOOWKH:RUNIORZ%XLOGHU $FWLYLW\VWHSW\SHLQD
&KRRVHWKH$FWLYLW\VWHSW\SH ZRUNIORZ
l ,QWKHZRUNIORZVWHSHQWHU
UHIHUVWRDWDVN
l $WDVNDEEUHYLDWLRQRU
Activity 1
l $ZRUNIORZDEEUHYLDWLRQ
l 6SHFLI\QDPHVIRUWKHRXWFRPHVRIWKH
VWHS
+RZGRHVWKHWDVNZRUNIORZHQG
Multiple outcomes
l (QVXUHELQGLQJIRUGDWDH[FKDQJHEHWZHHQ
WDVNFRQWDLQHUDQGZRUNIORZFRQWDLQHU
UHIHUVWRDZRUNIORZ
l 'HILQHDJHQWV
l 'UDZXSDGHDGOLQHHVFDODWLRQZKHQ Activity 2
UHTXLUHG
Multiple outcomes
SAP AG 1999
n A step in a workflow can refer to an activity.

An activity with a single triangle links to a task
An activity with three triangles links to a workflow (the associated workflow is called a
"subworkflow")
n The binding defines the data exchange between the different containers in a workflow.
Every time you integrate a task into a workflow, you have to make sure that the correct data is
transported into the task container when the work item is started and back to the workflow
container when the work item is completed.
n You determine the work item recipients for this step in the section "Agents".
If they can execute the underlying tasks, these recipients receive the work item in their
Workplace.
On the "Notification" tab page, you can specify a recipient who receives a message when the
step is completed. The notification text is defined in the underlying task.
n There are two main deadline escalation procedures, simple and modeled deadlines.
You can define special recipients for the simple deadlines.
SAP AG BC601 6-17

7DVN*URXSV
Task group 1
Workflow template 1 Only standard objects

(workflow templates
Workflow template n and standard tasks)
Standard task 1

Standard task n
Task group 2 It is possible to have

task groups within
Workflow template 1 task groups

Workflow template m
Standard task 1

Standard task m
Task group 3
SAP AG 1999
n Logically connected tasks are grouped together in task groups. Note also that task groups can have a
description text. The use of the task group can therefore be precisely documented.
n Hence, it is possible, for example, to:
Place workflow templates that only communicate with each other using events together in a task
group. As a result, you obtain a better overview.
Bundle tasks (workflow templates and standard tasks) that belong to one work area in order to
increase reusability.
n Task groups are also useful for defining the search range for the Business Workflow Explorer. The
Business Workflow Explorer can then display the tasks in these task groups.
n Important note: Task groups can only contain the task types workflow template and standard task.
Workflow tasks and customer tasks are no longer supported.
SAP AG BC601 6-18

7DVN*URXSV,QKHULWDQFH
7DVNJURXS 866&+0,'73$3DWULFN6PLWK
:RUNIORZWHPSODWH[
)RUZDUGVWR
)RUZDUGVWR
866&+0,'73$3DWULFN6PLWK DJHQW
DJHQW
DVVLJQHG
DVVLJQHG
6WDQGDUGWDVN[ 866&+0,'73$
866&+0,'73$
866&+0,'73$3DWULFN6PLWK
:RUNIORZWHPSODWH\
866&+0,'73$3DWULFN6PLWK )RUZDUGVWR

)RUZDUGVWR
DJHQW
DJHQW
6WDQGDUGWDVN\ DVVLJQHG
DVVLJQHG
866&+0,'73$
866&+0,'73$
866&+0,'73$3DWULFN6PLWK
SAP AG 1999
n Tasks pass on their characteristics to the collected tasks and task groups.
n This inheritance also continues through any assigned task groups. As shown in the graphic, the tasks
in a task group also inherit the characteristics of the task group highest in the hierarchy.
n With very extensive inheritance hierarchies, undesired agent assignments can be made if an
organizational object is assigned to the highest task group. Therefore, ensure that the change of
responsibility for the task group is also desired for the assigned tasks and task groups.
SAP AG BC601 6-19

%XVLQHVV:RUNIORZ([SORUHU
l 2QHPHGLXPIRUPDQDJLQJWDVNVDQGZRUNIORZV
l )XQFWLRQVDYDLODEOHLQFOXGH
" &UHDWH
" &KDQJH
" 'LVSOD\
" &RS\
" $JHQWDVVLJQPHQW
" $QGVRRQ
l 1RKHOSYDOXHVUHTXLUHG$OOUHOHYDQWWDVNV
DUHGLVSOD\HGGLUHFWO\
SAP AG 1999
n The Business Workflow Explorer facilitates the management of workflow projects. All tasks can be
assigned to a task group. The relevant employees incorporate this task group into the search range of
the Business Workflow Explorer.
n The functions mentioned here can always be accessed from context menus (right mouse button). The
following functions are also possible:
Display current workflows of task
Quick overview of most important task attributes
n The Business Workflow Explorer always uses a defined search area. This area can be defined
interactively by the user. Note, however, that calling the Business Workflow Explorer takes longer
than accessing the largest chosen search range since all tasks have to be imported with their
attributes. Therefore, ensure that the chosen search range is not unnecessarily large.
n Parts of the Business Workflow Explorer can be used within the Workflow Builder.
SAP AG BC601 6-20

%XVLQHVV:RUNIORZ([SORUHU8VH
Business Workflow Explorer

Task Edit Goto View System Help
Query
Task Abbreviation Name Task Abbreviation Name
All tasks for notifications of absence WS9990003 Notification of absence (productive)

Available objects
Multistep tasks TS9990003 Create notification of absence
WS9990000 Notification of absence (test) TS9990007 Approve notification of absence
WS9990003 Notification of absence (productive) TS9990012 Display notification of absence
TS9990003 Create notification of absence TS9990015 Delete notification of absence

TS9990007 Approve notification of absence
TS9990012 Display notification of absence
TS9990015 Delete notification of absence
Single-step tasks
All single-step tasks
TS9990003 Create notification of absence are displayed
TS9990007 Approve notification of absence
TS9990012 Display notification of absence
TS9990015 Delete notification of absence
Multistep tasks: All single-

step and multistep tasks
are displayed
SAP AG 1999
n The search range of the Business Workflow Explorer can be defined with the following objects:
7DVNJURXSV: This is the preferred option since granularity is optimized. In principle, every
workflow modeler can create one or more task groups to organize their tasks.
$SSOLFDWLRQFRPSRQHQWV
This key is not a very precise sort key and is probably not relevant for customer projects.
2WKHU
- 6$3SKRQHWDVNV: Tasks suitable for telephone integration (inbound calls and/or outbound
calls).
- /RFDOREMHFWV: All local tasks in the system. Only your own local tasks (user-specific).
n The tasks used in a workflow definition can be displayed in more detail by choosing View->Details.
The Explorer then displays more information about the tasks in additional columns (object type,
method, agent assignment, background task, and so on.).
n If you click on a multistep task in the left-hand tree, the most recent (and not the active) version is
read and displayed in detail in the right-hand tree.
SAP AG BC601 6-21

7DVNV8QLW6XPPDU\
l 7ZRW\SHVRIWDVNV6LQJOH
VWHSWDVNVDQGZRUNIORZV
l 6LQJOHVWHSWDVNVUHIHUWRREMHFW
PHWKRGV
l :RUNIORZVUHIHUWRVLQJOHVWHSWDVNV
DQGRURWKHUZRUNIORZV
l 6LQJOHVWHSWDVNVWKDWDUH
" V\QFKURQRXVFDQKDYHWHUPLQDWLQJHYHQWV
" DV\QFKURQRXVPXVWKDYHDWOHDVWRQH
WHUPLQDWLQJHYHQWV
l <RXFDQFUHDWHDQGPDLQWDLQ7DVN*URXSV
l <RXDUHQRZIDPLOLDUZLWKWKH%XVLQHVV
:RUNIORZ([SORUHU
SAP AG 1999
SAP AG BC601 6-22

([HUFLVHV
8QLW7DVNV
7RSLF%DVLFVIRU7DVN'HILQLWLRQ

Define standard tasks
Standard tasks are based on the methods of object types. These tasks can
be used as stand alone single-step tasks or as steps in a workflow
definition.
1-1 Familiarize yourself with the different tasks in the SAP workflow concept.
1-1-1 List all the task types that you can create by default in Release 4.6, along
with their abbreviation and their usage method:
_________________________________________________________
_________________________________________________________
_________________________________________________________
1-1-2 Check the standard task AF_approve.

What is the number of this task? __________________
Which object type method is used as a basis for this task?
___________________________________________
What is the shortest way to display that object type? _____________

What is the key field of that object type? ______________________
Check the "possible agents" of this task.
_________________________________________________________
_________________________________________________________
_________________________________________________________
What is the work item text of this task?

_________________________________________________________
How do you find the task description?

_________________________________________________________
SAP AG BC601 6-23

1-2 Define the two tasks as standard tasks. Do not enter a work item text yet.
1-2-1 Create the first task.

,QWKH7DVNW\SHILHOGVHOHFWWKHRSWLRQ6WDQGDUGWDVN
Abbr: "Z##_TS_1"
Name: "Change documents for material, group ##".
Object type: "Y##MARA"
Method: "Display_Changes"
Use the input help to find this entry.
Make a note of your task number:BBBBBBBBB
You may be prompted to specify a development class. Enter the

development class =, and create a new &KDQJHUHTXHVW with the
title *URXSGRQRWWUDQVSRUW. (## is your assigned group
number.)
Define the task as a "general" task.

Exit the window.
1-2-2 Create a second task.

,QWKH7DVNW\SHILHOGVHOHFW6WDQGDUGWDVN
Abbr: "Z##_TS_2"
Name: "Display material master, group ##".
Object type: "Y##MARA"
Method: "Display"
Use the input help to find this entry.
Make a note of your task number:BBBBBBBBB
Define the task as a "general" task.
Exit the window.
SAP AG BC601 6-24

1-3 Test your two tasks "Change documents for material" and "Display material
master".
1-3-1 Update the organizational buffer.
Enter TS and the number of your "Change documents for material" task, for
example, "
Provide input data by choosing7DVN,QSXWGDWD
In the "Initialize Container" dialog box, use the input help in the "Value"
field to enter your material 7%%'.
Go back and start the task "Change documents with material".
Repeat the test with the task "Display material master".

Do not forget to specify the material in the input data.
1-4 You have demonstrated the tasks to your users and they have asked for some
enhancements. They would like the completion of the task to be explicitly
confirmed and would like to add some meaning to the message text in the worklist.
Adjust the task "Change documents for material" to the user requirements.
1-4-1 Select "Confirm end of processing".

This changes the runtime behavior of the work item for this task.
1-4-2 Change the work item text for the task "Change documents for material".
The work item text appears in the worklist of the recipients.
On the "Basic data" tab page, enter your text, for example "Display changes
of material" in the "Work item text" field.
Position your cursor after "material" and insert the material number variable
by choosing the "Insert variables" button.
In the "Please Choose an Expression" dialog box, click on the plus sign next
to the object type "Y##MARA" (may also be displayed as
BUS1001_Groupnr_## or _WI_OBJECT_ID).
Double-click the "Material" field.
The work item text now contains the value
&_WI_OBJECT_ID.MATERIAL& after "material".
Save your task.
(Note: The & sign is a placeholder for the variable.)
Make sure that there is at least one space before the first & sign and one
space after the second & sign.
SAP AG BC601 6-25

1-4-3 Create a task description for the task "Change documents for material".
This will send special help information to the recipient of this work item at
runtime.
Enter your text, for example, "Display changes of requested material ",
and insert the parameter value &_WI_OBJECT_ID.MATERIAL& after the
word "material".
Again, make sure that there is at least one space before the first '
&'sign and
one space after the second '
&'sign.
1-4-4 Save the task "Change documents for material" again.
1-4-5 Test your task again. Open another session and go to the Business
Workplace.
Write down your work item text:
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
The task description of your work item is displayed in the lower part of the
screen. Afterwards end that session.
To complete this work item, click on the "Complete processing of step"
button in the "This Work Item Has To Be Completed Explicitly" dialog box.
Why was this additional dialog box displayed?
________________________________________________
1-5 Change your workflow.
1-5-1 Insert your task "Change documents for material" as the new first step in
your workflow.
Call the Workflow Builder.
Your workflow template is displayed.
Integrate the task directly after the step "Workflow started".
Accept the question about the workflow <-> task container binding. This
point will be covered later.
As the agent of this step, choose the "expression" &_WF_INITIATOR&.
On the "Outcomes" tab page for "Step executed", enter a text, for example
"Change documents displayed".
Exit the screen and activate your workflow again.
SAP AG BC601 6-26

1-5-2 Change the task "Change documents for material" again.
Up to now, your workflow has been defined without import parameters. But
the task you have just inserted into the workflow requires an import. For test
purposes, you can specify an initial value.
Display your task z##_TS_1 and create an initial value in it. Use the F4
Help for the "Expression" and enter your material number in the
"BUS1001_Groupnr_##" window.
Exit the window and save your task again.
1-5-3 Test your workflow.

Why did the workflow not require you to enter a material?
1-6 Enter your tasks in your task group Z##_AG.
SAP AG BC601 6-27

6ROXWLRQV
8QLW7DVNV
7RSLF%DVLFVIRU7DVN'HILQLWLRQ
1-1 Familiarize yourself with the different tasks in the SAP workflow concept.
1-1-1 List all the task types that you can create by default in Release 4.6, along
with their abbreviation and their usage methods.
6$3($6<$&&(66!7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW
'HILQLWLRQ7RROV7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
&KRRVHWKH)+HOSIRUWKH7DVNW\SHILHOG
76 Standard task, stand-alone or as a step in a workflow
:6 Workflow template, stand-alone or as a subworkflow
7* Task group
1-1-2 Check the standard task "AF_approve".
6$3($6<$&&(667RROV%XVLQHVV:RUNIORZ'HYHORSPHQW
'HILQLWLRQ7RROV7DVNV7DVN*URXSV
2QWKH7DVN'LVSOD\VFUHHQHQWHUWKHIROORZLQJLQIRUPDWLRQ
)LHOG1DPH ,QSXW'DWD
Task type Standard task
Task AF_approve
&KRRVHWKH'LVSOD\EXWWRQ
2QWKH6WDQGDUGWDVNGLDORJER[GRXEOHFOLFN$)BDSSURYH
What is the number of this task? .

Which object type method is used as a basis for this task?
)250$%6(1&$33529(
SAP AG BC601 6-28

What is the shortest way to display that object type?
'RXEOHFOLFNRQWKHREMHFWW\SH
What is the key field of that object type?
2QWKH'LVSOD\2EMHFW7\SHVFUHHQ
FOLFNRQWKHSOXVVLJQQH[WWR.H\ILHOGV
$EVHQFH)RUP1XPEHU
Check the "possible agents" of this task.
&KRRVHWKH%DFNEXWWRQWRUHWXUQWRWKH6WDQGDUG7DVN'LVSOD\
VFUHHQ
2QWKH6WDQGDUG7DVN'LVSOD\VFUHHQFKRRVH
$GGLWLRQDOGDWD $JHQWDVVLJQPHQW 'LVSOD\
What is the work item text of this task?

2QWKH%DVLFGDWDWDESDJHWKHZRUNLWHPWH[WLVGLVSOD\HGLQWKH
:RUNLWHPWH[WILHOG
How do you find the task description?

2QWKH6WDQGDUG7DVN'LVSOD\VFUHHQFKRRVHWKH'HVFULSWLRQWDE
SDJH
7KHWDVNGHVFULSWLRQLVGLVSOD\HGLI\RXVHOHFWWKHRSWLRQ7DVN
GHVFULSWLRQLQWKH7H[WW\SHILHOG
5HWXUQWRWKH6$3(DV\$FFHVVPHQXE\VHOHFWLQJWKH%DFNEXWWRQ
JUHHQDUURZ
1-2 Define the two tasks as standard tasks. Do not enter a work item text yet.
1-2-1 Create the first task.

,QWKH6$3(DV\$FFHVVPHQXGRXEOHFOLFN&UHDWHLQWKH7DVNV7DVN
*URXSVIROGHU
)LHOG1DPH ,QSXW'DWD
Task Blank
SAP AG BC601 6-29

2QWKH%DVLFGDWDWDESDJHHQWHUWKHIROORZLQJLQIRUPDWLRQ
)LHOG1DPH ,QSXW'DWD
Abbr: Z##_TS_1
Name Change documents for material,

group ##
Object type Y##MARA
Method Display_Changes
&KRRVHWKH6DYHEXWWRQ

number.)
Make a note of your task number: _________

Define the task as a "general" task by choosing:
$GGLWLRQDOGDWD$JHQWDVVLJQPHQW0DLQWDLQ
3RVLWLRQ\RXUFXUVRURQWKHWDVNKLJKOLJKWHGLQOLJKWJUHHQDQGFKRRVH
(GLW $WWULEXWHVRUWKH$WWULEXWHVEXWWRQ
,QWKH7DVNZLQGRZVHOHFW*HQHUDOWDVNDQGFKRRVHWKH
7UDQVIHUEXWWRQ
([LWWKHZLQGRZDQGVDYH\RXUWDVNDJDLQ
1-2-2 Create a second task.

,QWKH6$3(DV\$FFHVVPHQXGRXEOHFOLFN&UHDWHLQWKH7DVNV7DVN
*URXSVIROGHU
SAP AG BC601 6-30

)LHOG1DPH ,QSXW'DWD
Task Blank
)LHOG1DPH ,QSXW'DWD
Abbr: Z##_TS_2
Name Display material master, group ##
Object type Y##MARA
Method Display
&KRRVHWKH6DYHEXWWRQ
$QVZHU<HVWRWKHSURPSW7UDQVIHUPLVVLQJHOHPHQWVIURPWKHREMHFW
PHWKRG"

number.)
Make a note of your task number: _________

Define the task as a "general" task by choosing:
$GGLWLRQDOGDWD$JHQWDVVLJQPHQW0DLQWDLQ
3RVLWLRQ\RXUFXUVRURQWKHWDVNKLJKOLJKWHGLQOLJKWJUHHQDQGFKRRVH
(GLW $WWULEXWHVRUWKH$WWULEXWHVEXWWRQ
,QWKH7DVNZLQGRZVHOHFW*HQHUDOWDVNDQGFKRRVHWKH
7UDQVIHUEXWWRQ
SAP AG BC601 6-31

1-3 Test your two tasks.
First test "Change documents for material".
,QWKH6$3(DV\$FFHVVPHQXFKRRVH7RROV!%XVLQHVV:RUNIORZ!
'HYHORSPHQW!5XQWLPH7RROV
'RXEOHFOLFN6WDUW:RUNIORZ7HVW(QYLURQPHQW
2QWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQH[HFXWHWKHIROORZLQJVWHSV
)LHOG1DPH ,QSXW'DWD
Task Blank
3UHVVWKH)NH\WRVWDUWWKHVHDUFK
2QWKH6HDUFKDQG)LQG7DVNVVFUHHQHQWHU\RXUJURXSQXPEHUIRUH[DPSOH
= DQGFKRRVHWKH)LQGEXWWRQ
$OLVWRIDOOFRUUHVSRQGLQJWDVNVLVGLVSOD\HG7UDQVIHU\RXUVWDQGDUGWDVN&KDQJH
GRFXPHQWVIRUPDWHULDOE\GRXEOHFOLFNLQJRQLW
Update the organizational buffer.

2QWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQFKRRVH
(QYLURQPHQW5HIUHVKRUJDQL]DWLRQDOHQYLURQPHQWRUWKH5HIUHVK
RUJDQL]DWLRQDOHQYLURQPHQWEXWWRQ
Provide input data by choosing7DVN ,QSXWGDWD(or the "Input data" button).

In the "Initialize Container" dialog box, use the input help to enter your material 7
%%'
Choose "Back" and start the task by choosing:

7DVN([HFXWHRUWKH([HFXWHEXWWRQ
2QWKH9LHZ6HOHFWLRQVFUHHQFKRRVH%DVLFGDWDIROORZHGE\WKH
&RQWLQXH(QWHUEXWWRQ
7KHFKDQJHVRIPDWHULDO7%%'DUHGLVSOD\HG
5HSHDWWKLVSURFHGXUHZLWKWKHWDVN'LVSOD\PDWHULDOPDVWHU
SAP AG BC601 6-32

1-4 You have demonstrated the tasks to your users and they have asked for some
enhancements. They would like the completion of the task to be explicitly
confirmed and would like to add some meaning to the message text in the worklist.
Adjust the task "Change documents for material" to the user requirements.
'HYHORSPHQW!'HILQLWLRQ7RROV!7DVNV7DVN*URXSV
'RXEOHFOLFN&KDQJH
2QWKH7DVN0DLQWDLQVFUHHQHQWHU\RXUWDVNQXPEHUDQGFKRRVH7DVN!
&KDQJHRUWKH&KDQJHEXWWRQ
1-4-1 In the "Execution" frame, set the &RQILUPHQGRISURFHVVLQJflag. This

changes the runtime behavior of the work item for this task.
1-4-2 Change the work item text. The work item text appears in the recipients
worklist.
2QWKH%DVLFGDWDWDESDJHHQWHU\RXUWH[WIRUH[DPSOH*URXS
'LVSOD\FKDQJHVRIPDWHULDOLQWKH:RUNLWHPWH[WILHOG
3RVLWLRQ\RXUFXUVRUDIWHUWKHZRUGPDWHULDODQGFKRRVHWKH,QVHUW
YDULDEOHVEXWWRQ
,QWKH3OHDVH&KRRVHDQ([SUHVVLRQGLDORJER[FKRRVHWKH6ZLWFK
GLVSOD\7HFKQLFDOQDPH'HVFULSWLRQEXWWRQWRGLVSOD\WKHGHVFULSWLRQRI
WKHH[SUHVVLRQ
&OLFNRQWKHSOXVVLJQQH[WWR\RXUREMHFWW\SH,WLVGLVSOD\HGDV
<0$5$RUDV%86B*URXSQUBRULWLVDIWHUB:,BB2%-(&7B,'
'RXEOHFOLFNWKH0DWHULDOILHOG
The value &_WI_OBJECT_ID.MATERIAL& has been inserted after your
work item text "Display changes of material".
(Note: The & sign is a placeholder for the variable.)
Make sure that there is at least one space before the first & sign and one
space after the second & sign.
SAP AG BC601 6-33

1-4-3 Create a task description for the task "Display changes".
This sends special help information to the agent of this work item at
runtime.
2QWKH6WDQGDUG7DVN&KDQJHVFUHHQFKRRVHWKH'HVFULSWLRQWDE
SDJH
&KRRVH7DVNGHVFULSWLRQDVWKHWDVNW\SHDQGFOLFNWKH&KDQJHWH[W
EXWWRQ
Enter your text, for example "Display changes for requested material...".
Position the cursor after "material" and choose:
,QVHUW([SUHVVLRQ
&OLFNRQWKHSOXVVLJQQH[WWR\RXUREMHFWW\SH<0$5$GLVSOD\HGDV
%86B*URXSB
'RXEOHFOLFNWKH0DWHULDOILHOG
7KHSDUDPHWHUYDOXH B:,B2%-(&7B,'0$7(5,$/ KDVEHHQ
LQVHUWHGDIWHU\RXUGHVFULSWLRQWH[W
&KRRVHWKH%DFNEXWWRQWRUHWXUQWRWKH6WDQGDUG7DVN&KDQJH
VFUHHQ
Again, make sure that there is at least one space before the first & sign and
one space after the second & sign.
1-4-4 Save the task again by choosing:
6WDQGDUGWDVN6DYHRUWKH6DYHEXWWRQ
1-4-5 Test the task "Change documents for material" again. Open another session
and go to the Business Workplace.
Write down your work item text:
________________________________________________
The task description of your work item is displayed in the lower part of the
screen. Afterwards end that session.
To complete this work item, click on the "Complete processing of step"
button in the "This Work Item Has To Be Completed Explicitly" dialog box.
Why was this additional dialog box displayed?
<RXKDYHVHWWKH&RQILUPHQGRISURFHVVLQJIODJ
5HWXUQWRWKH6$3(DV\$FFHVVPHQXE\FKRRVLQJWKH%DFNEXWWRQ
JUHHQDUURZ
SAP AG BC601 6-34

1-5 Change your workflow.
1-5-1 Insert your task "Display changes" as the new first step into your workflow.
7RROV!%XVLQHVV:RUNIORZ!'HYHORSPHQW!'HILQLWLRQ7RROV!
:RUNIORZ%XLOGHU
<RXUZRUNIORZWHPSODWHLVGLVSOD\HG
2QWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQVHOHFWWKHHYHQW:RUNIORZ
VWDUWHG
7KHQFKRRVH(GLW&UHDWHRUWKH&UHDWHEXWWRQ
&KRRVHWKH$FWLYLW\EXWWRQDQGHQWHU\RXUWDVNQXPEHUIRUH[DPSOH
76LQWKH7DVNILHOG
As the responsible agent of this step, choose the "expression"

&_WF_INITIATOR&.
,QWKH$JHQWILHOGVHOHFWWKHZRUNIORZLQLWLDWRUXVLQJWKH)+HOS
On the "Outcomes" tab page, enter a text for "Step executed".

2QWKH:RUNIORZ%XLOGHU&UHDWH6WHS$FWLYLW\VFUHHQFKRRVHWKH
2XWFRPHVWDESDJH
,ISURPSWHGDFFHSWWKHFKHFNTXHVWLRQDERXWWKHZRUNIORZ!WDVN
FRQWDLQHUELQGLQJE\FKRRVLQJWKH&RQWLQXH(QWHUEXWWRQ7KLVSRLQW
ZLOOEHFRYHUHGODWHU
(QWHUWKHIROORZLQJLQIRUPDWLRQ
)LHOG1DPHV
Outcome Name
,QSXW'DWD Step executed Changes displayed
Exit the screen and activate your workflow again.

2QWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQFKRRVHWKH*HQHUDWHDQG
DFWLYDWHUXQWLPHYHUVLRQEXWWRQPDWFKV\PERO
SAP AG BC601 6-35

1-5-2 Change the task "Display changes" again.
8SWRQRZ\RXUZRUNIORZKDVEHHQGHILQHGZLWKRXWLPSRUWSDUDPHWHUV
%XWWKHWDVN\RXKDYHMXVWLQVHUWHGLQWRWKHZRUNIORZUHTXLUHVDQLPSRUW
)RUWHVWSXUSRVHVZHVSHFLI\DQLQLWLDOYDOXH
&DOOWKHWDVN=B76B
,QWKH:RUNIORZ%XLOGHUFOLFNRQWKHVWHS'LVSOD\FKDQJHVZKLFK
FRQWDLQVWKHWDVNIRUGLVSOD\LQJFKDQJHGRFXPHQWV
'RXEOHFOLFNRQWKHWDVN,'IRUH[DPSOH76WRJRWRWKH
VWDQGDUGWDVN
2QWKH6WDQGDUG7DVN&KDQJHVFUHHQFKRRVH*RWR$VVLJQLQLWLDO
YDOXHV
8VHWKH)+HOSIRU([SUHVVLRQDQGHQWHU\RXUPDWHULDOQXPEHU7
%%'LQWKH%86B*URXSQUBZLQGRZ
5HWXUQWRWKHEDVLFVFUHHQRIWKH:RUNIORZ%XLOGHU
1-5-3 Test your workflow.

,QWKH:RUNIORZ%XLOGHUFKRRVHWKH7HVWLFRQZKLFKWDNHV\RXWRWKH
ZRUNIORZWHVWHQYLURQPHQW
7KHQXPEHURI\RXUZRUNIORZWHPSODWHKDVEHHQHQWHUHGDXWRPDWLFDOO\
&KRRVHWKH6WDUWZRUNIORZEXWWRQ
7KHFKDQJHGRFXPHQWVIRU\RXUPDWHULDODUHGLVSOD\HG
([LWWKHPDWHULDOGLVSOD\E\FKRRVLQJWKH%DFNEXWWRQ
Why did the workflow not require you to enter a material?
7KHPDWHULDOQXPEHUZDVDOUHDG\SURYLGHGDVDQLQLWLDOYDOXHDWWKHWDVN
OHYHO
1-6 Enter your tasks in your task group.

3DWK7RROV!%XVLQHVV:RUNIORZ!'HYHORSPHQW!'HILQLWLRQ7RROV!
7DVNV7DVN*URXSV
'RXEOHFOLFN&KDQJH
7DVNW\SH7DVN*URXS
&KRRVHWKH&KDQJHEXWWRQ
6HDUFKIRUWKHWDVNJURXSZLWKWKHDEEUHYLDWLRQ=B$*
&KRRVHWKH6WDQGDUGWDVNVWDESDJHDQGVSHFLI\\RXUVWDQGDUGWDVNVXVLQJWKH
)+HOS
6DYH\RXUWDVNJURXS
SAP AG BC601 6-36

0RQLWRULQJDQG$QDO\VLV
&RQWHQWV
l 5HSRUWLQJ6\VWHP
l :RUN,WHP$QDO\VLV
l 7HVW8WLOLWLHVIRUWKH
'HVLJQHU
SAP AG 1999
SAP AG BC601 7-1

0RQLWRULQJDQG$QDO\VLV8QLW2EMHFWLYHV
l ([HFXWHUXQWLPHUHSRUWVIRUWKHGHVLJQHU
l ([HFXWHUXQWLPHUHSRUWVIRUWKH
DGPLQLVWUDWRU
l ([HFXWHUXQWLPHUHSRUWVIRUWKHHQGXVHU
l (YDOXDWHWKHZRUNIORZORJYLHZVDQG
RSWLRQV
SAP AG 1999
SAP AG BC601 7-2

&RQILJXUDWLRQ 'HDGOLQHV
SAP AG 1999
SAP AG BC601 7-3

0RQLWRULQJDQG$QDO\VLV%XVLQHVV6FHQDULR
l <RXEXLOW\RXUILUVWZRUNIORZ
l <RXZDQWWRVHHDOOLQIRUPDWLRQVWRUHGLQ6$35
DERXW\RXUZRUNIORZ
l $QDO\]HWKHZRUNIORZUXQWLPHGDWDXVLQJWKH
VWDQGDUGGHOLYHUHGZRUNIORZUHSRUWV
SAP AG 1999
SAP AG BC601 7-4

5HSRUWLQJ6\VWHP
:RUNIORZORJ :RUNIORZ :RUNLWHP

GLDJQRVLV DQDO\VLV
7DVN ,QIRUPDWLRQ
:RUNIORZ
DQDO\VLV V\VWHP
RXWER[
2EMHFWVSHFLILF :RUNORDG
HYDOXDWLRQ DQDO\VLV
SAP AG 1999
n There are different report for information purposes available.

n If you have problems with one specific workflow, then use the workflow diagnosis.
SAP AG BC601 7-5

(YDOXDWLQJ:RUN,WHPV:RUN,WHP$QDO\VLV
0RQLWRULQJSHULRG :RUNLWHPW\SH 7DVNILOWHU
:RUNLWHPV
:RUNLWHPVSHUWDVN
3URFHVVGXUDWLRQ
0LVVHGGHDGOLQHV
SAP AG 1999
SAP AG
n To find the work item analysis, choose

SAP EASY ACCESS - Tools - Business Workflow - Development - Reporting - Work Item
Analysis.
You can then display the work items per task, work items with monitored deadlines, or work items
by processing duration.
n Work items per task:
You can enter a time span and choose to view selected tasks.
If you want to display the work items that together represent a workflow, set the flag (sub-)
workflow.
n Work items with monitored deadlines:
To restrict the choice to a particular process, enter the individual task.
For work items with monitored deadlines for approval of vacation, you would enter
TS30000016 in the "Task" field.
n The work item analysis provides a good overview for workflow administrators and managers who
are responsible for this business process.
SAP AG BC601 7-6

,GHQWLI\LQJ:RUN,WHPV:RUN,WHP6HOHFWLRQ
6HOHFWLRQUHSRUWFULWHULD
Work item ID
Work item type
Work item status
Task-ID
:RUNLWHPV
&KDQJHZRUNLWHP
'LVSOD\ZRUNLWHP 'LVSOD\DJHQW
'LVSOD\FRQWDLQHUHWF
'LVSOD\ZRUNIORZORJ
SAP AG 1999
n To find the work item selection, choose

SAP EASY ACCESS - Tools - Business Workflow - Development - Reporting - Utilities - Work
Item Selection.
n Work item selection is probably the fastest way for a workflow designer to access the workflow log
of any workflow.
n 6HOHFWLRQFULWHULD:
Task ID or task group (for example, WS99900012/TS30000016)
Work item type
Date created/time created
Work item status
Priority
Specific entry of the work item key
n If you set the Additional data flag, the display will include the number and version of the workflow
or task, the system administrator, and the user who executed the work item.
n Depending on your selection criteria, the report might display a list of work items. By double
clicking, you can display these work items to obtain detailed information.
n You can only execute or change these work items if you are a SRVVLEOHagent of those work items.
SAP AG BC601 7-7

:RUN,WHP7\SHV
l 'LDORJZRUNLWHP :
l 0LVVHGGHDGOLQHZRUNLWHP '
l :RUNIORZZRUNLWHP)
l %DFNJURXQGZRUNLWHP %
l :DLWVWHSZRUNLWHP (
SAP AG 1999
n Work item types and their meanings:

W: Dialog work item
- Runtime representation for a task with user dialog
D: Missed deadline work item
- The message recipient for missed deadline is informed.
F: Workflow work item
- Runtime representation of a workflow. The processing status of the overall workflow can be
assessed using the status of this workflow work item.
B: Background work item
- Runtime representation of a task executed in the background.
E: Wait step work item
- Runtime representation of a wait step in the workflow definition.
SAP AG BC601 7-8

:RUNORDG$QDO\VLV
8VHU
%HUQHU
(GLWHGZRUNLWHPV
3RVLWLRQ RIDXVHU
6 RIDSRVLWLRQ
RIDMRE
RIDQRUJDQL]DWLRQDOXQLW
'HDGOLQHFDQEHVSHFLILHG
-RE
&
:RUNLWHPVVWLOOWRHGLW
LQLQER[
8VHU RIDXVHU
0LOOHU RIDSRVLWLRQ
RIDMRE
RIDQRUJDQL]DWLRQDOXQLW
2UJXQLW
2
SAP AG 1999
n To find the workload analysis, choose

SAP EASY ACCESS - Tools - Business Workflow - Development - Reporting - Workload Analysis.
n You can only execute the Workload Analysis if you have administrator authorization.
n From Workload Analysis you can go directly to the relevant inbox.
SAP AG BC601 7-9

:RUNIORZ2XWER[LQ:RUNSODFH
%XVLQHVV:RUNSODFH ,QWKH%XVLQHVV:RUNSODFH
RXWER[HYHU\XVHUFDQ
JDLQDQRYHUYLHZRIWKH
,QER[ ZRUNWKH\KDYHFDUULHGRXW
LQZRUNIORZSURFHVVHV
2XWER[
6WDUWHGZRUNIORZV
ZRUNIORZZRUNLWHPIRU:6
([HFXWHGZRUNLWHPV
ZRUNLWHPIRU76
ZRUNLWHPIRU76
ZRUNLWHPIRU76
)RUZDUGHGZRUNLWHPV
ZRUNLWHPIRU76
SAP AG 1999
n The functions for displaying executed and forwarded work items are available from Release 4.6
onwards.
n These functions are in the Business Workplace Outbox folder.
SAP EASY ACCESS - SAP Business Workplace, or Office - Workplace.
SAP AG BC601 7-10

,QIRUPDWLRQRQ2EMHFW7\SHVDQG2EMHFWV
:KLFKWDVNVDQGZRUNIORZVXVH
WKHREMHFWW\SH1RWLILFDWLRQRIDEVHQFHLQWKHLU
GHILQLWLRQ"
2EMHFWW\SH
1RWLILFDWLRQRI
DEVHQFH :KLFKLQVWDQFHVDUHWKHUHIRUWKHZRUNIORZVDQG
WDVNVWKDWXVHWKHREMHFWW\SH
1RWLILFDWLRQRIDEVHQFHLQWKHLUGHILQLWLRQ"
2EMHFW
:KLFKZRUNLWHPUHIHUVWRWKHREMHFW
1RWLILFDWLRQRI
RIWKHREMHFWW\SH1RWLILFDWLRQRIDEVHQFH
DEVHQFH
DQGZKLFK%XVLQHVV:RUNSODFHLVLWLQ"
QXPEHU

SAP AG 1999
n Which tasks and workflows use a particular object type:

Object Builder - Enter the required task and choose the icon "Where-used list"
n Which instances exist for an object type:
SAP EASY ACCESS - Tools - Business Workflow - Development - Runtime Tools - Workflows For
Object Type.
You can decide between completed or active instances.
n Which work item relates to a particular object of an object type:
SAP EASY ACCESS - Tools - Business Workflow - Development - Runtime Tools - Workflows For
Object.
SAP AG BC601 7-11

7HVW8WLOLWLHVIRUWKH'HVLJQHU
l &RQVLVWHQF\FKHFN
7DVNGHILQLWLRQ
&XVWRPL]LQJRIWKHZKROHZRUNIORZV\VWHP
l (YHQW
6LPXODWLRQ
(YHQWWULJJHUSURYLGHLQSXWGDWD
(YHQWWUDFHVZLWFKRIILQSURGXFWLRQ
l 5)&/RJV
l 0DQXDOVWDUWRIDWDVNRUZRUNIORZ
)LUVWUHIUHVKWKHRUJDQL]DWLRQDODVVLJQPHQW
DQGWKHQSURYLGHLQSXWGDWD
SAP AG 1999
n Before you process a workflow in the development system, you should see only green lights on the
screen for Customizing of the whole workflow system. Always check SWU3 if you suspect an error
in the workflow system.
n The event simulation is a what if'game.
The system will inform you about the consequences of such an event, without actually triggering it.
If there are errors in event linkage you will receive a list of identified problems.
To find event simulation, choose Utilities - Events - Simulate Event
n The event trigger will ultimately trigger the event. You can use this to test whether your workflow
works properly without having to create the event in the application.
To find event triggering, choose Utilities - Events - Create Event
n In the development system, the event trace should be switched on.'
Periodically, the workflow system administrator should remove this physical file.
In the productive system, the event log should be switched off for performance reasons.
To find the event trace, choose Utilities - Events - Event Trace
n The RFC log provides an overview of RFC problems.
To find the RFC log, enter transaction SM58.
n You can start a task or a workflow manually for test purposes using the transaction SWUS, or from
the Workflow Builder using the test icon.
SAP AG BC601 7-12

:RUNIORZ/RJ6HWWLQJ2SWLRQVLQWKH:RUNIORZ(GLWRU
7KHIROORZLQJVWHSVDUHILOWHUHGRXWLQWKHGLVSOD\IRUEXVLQHVVXVHUV
&RQWDLQHURSHUDWLRQ
(YHQWFUHDWRU
3URFHVVFRQWURO
8QGHFLGHGVWHSV
$FWLYLW\DQGXVHUGHFLVLRQ
DVORQJDVWKH\DUHPDUNHGZLWKWKHRSWLRQ1RWLQ
ZRUNIORZORJ
7KHGLVSOD\LVQRWILOWHUHGIRUWHFKQLFDOXVHUV
SAP AG 1999
n The workflow log provides different modes for various information requirements. Each mode
answers particular questions and is aimed at a particular user group. The following modes are
available:
Modes for agents with no technical information.
Modes with technical details, as required, for example, by a workflow administrator.
n The standard display is the log for the business user.
n Your personal display depends on the mode you have chosen in your personal workflow settings. If
you have chosen the technical mode there, the display is not filtered.
n Workflow administrators should activate the technical view, so that they do not get any simplified
views. (This could mean viewing a workflow in a workflow log, but not seeing all the steps, and
therefore possibly making an incorrect diagnosis.)
SAP AG BC601 7-13

:RUNIORZ/RJ*UDSKLFDO1HZ9LHZ
5HTXHVWFUHDWHG
$SSURYH
UHTXHVW

Approved
Rejected $JHQWDQGZRUN
8VHU LWHPVWDWXV
GHFLVLRQ 6HQG
PDLO
Delete request "!$#&%"#
'
(
:LWKGUDZ &KDQJH
DSSOLFDWLRQ UHTXHVW 6WDUWHGDQG
H[HFXWHG
VWHSVDQG
Request deleted Request changed Yes
ZRUNIORZV
5HVXEPLW
UHTXHVW
No
:RUNIORZ
WHUPLQDWHG
SAP AG 1999
n The graphical workflow log supplements the information in the text. The flow of workflow steps that
have already been processed is marked by the green line in the graphical representation of the
You can tell at first glance which "route" a workflow instance has taken, and which activities are
processed in parallel to your own activities within a business process.
In contrast to the workflow log in text form, the graphical workflow log also shows the future steps
of a workflow instance. You can therefore see how a process is continued after executing your
activity.
n The technical basis of the graphical workflow log is the graphical workflow editor. To display the
graphical workflow log, the relevant workflow definition is read and combined with the runtime
information.
n The graphical workflow log in the view without event-driven process chains (EPCs) has the same
advantages as the graphical workflow editor:
Space-saving presentation
Improved clarity
n Work items that have already been processed or are currently being executed are marked with their
status icon. In addition, the current agents and the work item status are shown below a node.
SAP AG BC601 7-14

:RUNIORZ/RJ*UDSKLFDO8VLQJ(3&
+,"-,.& #
/ "0

**)
"-,." #
& " IJ & "
+14325( / 6(" *)
7 #
/8 # 8 9 0 8 $JHQWDQGZRUN
3 "!$#&%&#
:;1
6( >=< 0 I' LWHPVWDWXV
"&-,." # "-,." #
?@0 8 A# &
8 < 0 ! < 0
"-,. # &-,." #
+;1"&-,.& # +,"-,." # &RORUFRGLQJRI

( / < 0 &" VWDUWHGDQG
H[HFXWHGVWHSV
+;&B # .*C 8 DQGHYHQWV
&-,." #
D E #
F 6 8 &0"
!GH &!
!
( ( 8 0 (
SAP AG 1999
n The graphical workflow log is also available in the "event-driven process chains" view: Up to and
including Release 4.0, this was the only possible form of representation.
Yellow and crossed-out nodes show which steps have already been executed or are currently
being processed.
The current agent and the work item status are shown below a node.
n To call the view using EPC, choose the following:
Workflow Builder - Extras - Options - Graphic,
or from the graphic log using Extras - Options - Graphic
SAP AG BC601 7-15

:RUNIORZ/RJ*UDSKLFDO,PSRUWDQW
l ,PSRUWDQW7KHJUDSKLFDOZRUNIORZORJGLVSOD\VWKHZRUNIORZ
GHILQLWLRQDQGDOVRWKHUXQWLPHGDWD
l ,IDYHUVLRQRIDZRUNIORZGHILQLWLRQLVFKDQJHG
FRQVLGHUDEO\DQGLQFRPSDWLEO\E\
$GGLQJVWHSV
'HOHWLQJVWHSV
0RYLQJEORFNVFXWWLQJSDVWLQJHWF
DQGQRQHZYHUVLRQLVFUHDWHG
l WKHJUDSKLFDOZRUNIORZORJPD\QRORQJHUUHSUHVHQWZKDW
RFFXUUHGSUHYLRXVO\
SAP AG 1999
n This problem will occur mainly in the development and test phase, if a workflow definition is
changed, executed, changed and executed again, and so on.
n While the workflow log in list form only formats past values from the workflow runtime tables in a
list, the graphical workflow log shows the version of the workflow executed as it is currently
defined.
n If the version has been notably changed, the graphic displays the changed workflow definition, but
the workflow process differs from this. The graphical workflow log therefore tries to enter
information from the runtime tables into a workflow definition that looks totally different. How can
you identify this problem?
Steps seem to have been skipped (particularly apparent in a sequence)
All steps are shown as "executed", even those in an alternative (not loop)
The workflow is terminated, but you cannot determine a direct consequence of the workflow
execution.
SAP AG BC601 7-16

:RUNIORZ/RJ:RUNIORZ&KURQLFOH9LHZ
1RWLILFDWLRQRIDEVHQFH
:RUNLWHPVWDWXV
&UHDWHUHTXHVW &RPSOHWHG
$SSURYHUHTXHVW &RPSOHWHG
$FFHVVWR
6HOHFWHGDJHQWV
3RVVLEOHDJHQWV
$FFHVVWRZRUN ([FOXGHGDJHQWV
LWHPKLVWRU\
$FFHVVWRJUDSKLFDO
ZRUNIORZORJ
K=LMNO KQP&OSRST NMUM"P V*OMW ZX Y OM [\R ]M ^_4`M&P"O Î_4ÀMP"O*NY]'M

aI. 'bZ"# # : 8 0 # ( / 0& (& c degf\c e f
hh"ijf
k*l m"i*l k&h
aI. 'bZ"# #on .& %p# " c degf\c e f
hh"ijf
q*l c"c*l q&qsr ( 8 / p / . & n ." % 6f\e e e
aI. b1 # # H 8 ( t # ) 6,,( / #"# 8 " c d"e f\c e f
h&h"iuf
ql c"cl q q
aI. vb1 # #xw / .
8 # (0 (& c d"e f\c e f
h&h"iufAylSf
ql m k
aI. vb1 # #{z,( / #&# 8 " / '
(" c d"e f\c e f
h&h"iufAylSf
ml q k D 8 8 / 0
8 0C # / c"c&c c
c c&c"k\y*m
SAP AG 1999
n The "Workflow chronicle" tab page in the workflow log (ActiveX) shows a hierarchical display of
all the steps of the workflow that have already been processed or are due to be processed. If the
workflow has a structure of (sub-)workflows, these are also displayed.
n The function "Details" lists the following details for one step in the lower part of the screen:
Who carried out what detailed action with what result on these work items.
Which objects were involved.
n The function "Agents" shows:
Selected agents
Possible agents
Excluded agents for a step
n The function "Graphic" leads to the graphical workflow log.
n The different views (Workflow chronicle, Workflow agents, Workflow objects) are also available in
the workflow log in the user view (without ActiveX), using the "Views" menu.
SAP AG BC601 7-17

:RUNIORZ/RJ:RUNIORZ2EMHFWV9LHZ
3DWULFN6FKPLGW
1RWLILFDWLRQRIDEVHQFH 6XEZRUNIORZFUHDWHG

&UHDWHUHTXHVW 'LDORJVWHSFUHDWHG
&UHDWHUHTXHVW :RUNLWHPH[HFXWHGDXWRPDWLFDOO\
&UHDWHUHTXHVW :RUNLWHPSURFHVVLQJFRPSOHWHG
+XJR%RVV
$SSURYHUHTXHVW 'LDORJVWHSFUHDWHG
$SSURYHUHTXHVW 4XHU\VHQW
$SSURYHUHTXHVW :RUNLWHPSURFHVVLQJFRPSOHWHG
:RUNIORZ6\VWHP
6HQGPDLO %DFNJURXQGZRUNLWHPFUHDWHG
6HQGPDLO :RUNLWHPSURFHVVLQJFRPSOHWHG
SAP AG 1999
n The tab page "Workflow agents" of the workflow log (ActiveX) displays the employees involved in
this workflow so far. The following entries are contained for every employee:
Which action was executed in which step
When was this action executed.
Which objects were involved.
n This view mainly indicates which role an employee has played in executing a workflow.
SAP AG BC601 7-18

:RUNIORZ/RJ:RUNIORZ2EMHFWV9LHZ
1RWLILFDWLRQRIDEVHQFH
1RWLILFDWLRQRIDEVHQFH 6XEZRUNIORZFUHDWHG

&UHDWHUHTXHVW 'LDORJVWHSFUHDWHG
:,IRUVHOIPHWKRG
$SSURYHUHTXHVW 'LDORJVWHSFUHDWHG
SAP AG 1999
n The "Workflow objects" tab page lists the objects that are connected with the workflow or that have
been called by the workflow execution so far. These objects are:
Attachments and objects that have been added in the individual steps of the workflow.
n The following are listed for each object:
Who carried out what detailed action in what task.
n This view therefore shows what information was created and processed in what way.
SAP AG BC601 7-19

:RUNIORZ/RJ:LWK7HFKQLFDO'HWDLOV ([SHUW0RGH
|~}1
4 } ;*,J}Z
}
|~}1
4 }S5H* ;*,J}Z
}
S5H;H **
56;,5 H *H 5 H(5 1Hj1I
56H4 ' ;S*; * G,(,*;(4* S;6};
|~}1
4 }t,}1; ;
5}Z 64* |$}1 6 };HH ,*;

5}Z pHH G* }Z*H* *5 '
* ,*H}1& }
; * H , g}I }6* * ,S,
;* H ||Z, * ,S,
; , 61}'
= ;H , 6Z*646}1 G>'SZH
;* H H },'H'5* * ,S,
;* H |}Z " }, * ,S,
SAP AG 1999
n The workflow log (non-ActiveX version) can be switched to an expert mode that displays technical
details. This includes:
All steps: Hidden steps are also displayed.
All information, warnings and errors that appeared during execution.
Access to the workflow container and the relevant work item containers (container display
extended to display the attributes for object container elements).
Display of work item IDs.
n In addition, all the functions and information of user mode are available.
n From the standard log, you can go to the technical display by choosing Goto - List with technical
details - Goto.
SAP AG BC601 7-20

0RQLWRULQJDQG$QDO\VLV8QLW6XPPDU\
l 7RDQDO\]HWKHDFFXPXODWHG
ZRUNIORZUXQWLPHGDWDWKHUH
DUHDORWRIVWDQGDUGGHOLYHUHG
UHSRUWV
l <RXFDQPDQXDOO\VWDUWDWDVN
RUZRUNIORZDQG\RXFDQ
PDQXDOO\WULJJHUHYHQWVIRU
WHVWLQJ
SAP AG 1999
SAP AG BC601 7-21

([HUFLVHV
8QLW0RQLWRULQJDQG$QDO\VLV
7RSLF:RUNIORZ5HSRUWV

Run workflow reporting and analysis tools for monitoring and
managing the workflow environment
SAP Business Workflow provides several reporting and analysis tools

for monitoring processes in the workflow runtime system.
Reports help workflow developers to enter information that can be
used for debugging program errors in workflow definitions.
For the following reports, use as many options as you like. See the
solutions for help.
1-1 Runtime Tools

1-1-1 Workflow Outbox
The work items representing "your" tasks are displayed in the workflow
outbox with date, time, and current status.
Display the workflow outbox.
1-1-2 WorkItem Analysis
Using the work item analysis, you can carry out VWDWLVWLFDOHYDOXDWLRQVRI
ZRUNLWHPV. The work items to be analyzed can be restricted according to
time, their type, and their task.
The evaluation results displayed represent runtime information.
1-1-3 Workload Analysis
Using the workload analysis, you can determine the workload of individual
employees, positions, jobs, or organizational units.
1-1-4 Task Analysis

The task analysis allows you to display an overview of defined WDVNVwith
their dependencies and relationships.
SAP AG BC601 7-22

1-1-5 Workflows for object
This report allows you to display the workflow step log for a certain object.
1-1-6 Work item selection

This report allows you to display all work items created after a certain date.
1-1-7 RFC Monitor

If you checked that the triggering event for a workflow has actually
occurred, but the workflow was never started, then use this RFC monitor to
locate the error.
1-1-8 Diagnosing workflows with errors

In some situations you may only want to see workflows that have errors.
Use this report to display only the errors and to call the workflow log.
If an error has occurred, display the work item with the error. For more
information, double-click the work item.
SAP AG BC601 7-23

6ROXWLRQV
8QLW0RQLWRULQJDQG$QDO\VLV
7RSLF:RUNIORZ5HSRUWV
1-1 Runtime Tools

1-1-1 Workflow Outbox
The work items representing "your" tasks are displayed in the workflow
outbox with date, time, and current status. Work items are displayed:
For tasks you started in dialog (transaction SWUS, menu path %XVLQHVV
:RUNIORZ 'HYHORSPHQW 5XQWLPH7RROV 6WDUW:RUNIORZ7HVW
(QYLURQPHQW
For tasks which were started using a triggering event, and in whose
event parameter container your user name is specified as B(YWB&UHDWRU
Access the workflow outbox from the Business Workplace area menu:
2SHQWKH2XWER[IROGHU
There are three categories for displaying work items in the Workflow
Outbox.
Started workflows
Work items executed by me
Forwarded work items
It is possible to configure the Workflow Outbox, as you can the worklist.

(See:&RQILJXULQJWKHZRUNOLVWLQWKH6$3/LEUDU\
From the Started workflows overview area, you can select a GLDORJ
ZRUNLWHP or a EDFNJURXQGZRUNLWHP from the work item list. The
work item steps are displayed below in the Detail area. To go to the
workflow log, choose any of these steps followed by the Workflow
log button.
There are three views in the workflow log display: View: Workflow
Chronicle (what was processed when), View: Workflow Agents (who
processed what), and View: Workflow Objects (what was processed).
SAP AG BC601 7-24

In the Workflow Log screen, choose and check the following options:
On the tab page View: Workflow Chronicle :
2SHQWKH:RUNIORZIROGHUDQGFKRRVHWKHLFRQLQWKH'HWDLOV
FROXPQ7KHGHWDLOHGDFWLRQVIRUDVWHSDUHGLVSOD\HGDWWKHERWWRPRI
WKHVFUHHQ
&KRRVHWKHLFRQLQWKH*UDSKLF FROXPQWRGLVSOD\WKHJUDSKLFDO
ZRUNIORZORJ
&KRRVHWKHLFRQLQWKH$JHQWFROXPQWRGLVSOD\WKH3RVVLEOHDQG
([FOXGHG$JHQWV
<RXFDQVKRZRUKLGHFROXPQVIRU3URFHVVLQJWLPHDQG:RUNIORZ,'V
XVLQJWKHDSSURSULDWHRSWLRQLQWKH([WUDVPHQX
On the tab page View: Workflow Agents :
2SHQWKHIROGHUIRUDQDJHQWWRYLHZWKHWDVNVH[HFXWHGE\WKDWDJHQW
&KRRVHWKLVWDESDJHWRYLHZWKHREMHFWVUHIHUUHGWRE\DWDVNDQDJHQW
H[HFXWHGDFWLRQGDWHDQGWLPH
Technical workflow log
,QWKH:RUNIORZ/RJVFUHHQFKRRVH
*RWR/LVWZLWKWHFKQLFDOGHWDLOV
Work item display
,QWKH:RUNIORZ/RJVFUHHQVHOHFWDVWHSIURPWKH2YHUYLHZDUHD
WKHQFKRRVH*RWR/LVWZLWKWHFKQLFDOGHWDLOV
<RXFDQDOVRVHOHFWWKH/LVWZLWKWHFKQLFDOGHWDLOVEXWWRQDQG
GRXEOHFOLFND:RUNIORZVWHS7KLVGLVSOD\VWKH'LVSOD\:RUNLWHP
VFUHHQ
To obtain further information for the displayed work items, choose the
relevant function from the Display work item screen:
Agent info
*RWR$JHQW3RVVLEOHDJHQWV
Containers
([WUDV&RQWDLQHUV
Object links
:RUNLWHP2EMHFW'LVSOD\
1RWH: Before you can execute one of the above functions, you must
position the cursor on the respective work item.
SAP AG BC601 7-25

1-1-2 WorkItem Analysis
Using the work item analysis, you can carry out VWDWLVWLFDOHYDOXDWLRQV
RIZRUNLWHPV. The work items to be analyzed can be restricted
according to time, their type, and their task.
The evaluation results displayed represent runtime information.
7RVWDUWZRUNLWHPDQDO\VLVFKRRVHWKHIROORZLQJIURPWKH6$3(DV\
$FFHVVPHQX
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW5HSRUWLQJ :RUN
,WHP$QDO\VLV.
6HOHFWWKHGLIIHUHQWZRUNLWHPDQDO\VLVW\SHV
Work items per task:
'RXEOHFOLFN:RUNLWHPVSHUWDVN.
,QWKH:RUN,WHPV3HU7DVNVFUHHQVHOHFWWKHIROORZLQJUDGLR
EXWWRQV:
,QWKH0RQLWRULQJSHULRGIUDPH
7KHZRUNLWHPHYDOXDWLRQVDOZD\VUHIHUWRDPRQLWRULQJSHULRG
6HOHFW7RGD\.
,QWKH:RUNLWHPW\SHIUDPH
<RXFDQVSHFLI\WKHZRUNLWHPW\SHDVDQRWKHUVHOHFWLRQFULWHULRQIRU
WKHZRUNLWHPVWREHDQDO\]HG.
&KRRVH'LDORJ6XE:RUNIORZRU%DFNJURXQG
<RXFDQPDNHPRUHWKDQRQHVHOHFWLRQ<RXPXVWVHOHFWDWOHDVWRQH
ZRUNLWHPW\SH
Make sure that the entries for the task filter and work item types are not
mutually exclusive.
,QWKH7DVN)LOWHUIUDPHRSWLRQDO
<RXFDQOLPLWWKHZRUNLWHPVWREHDQDO\]HGE\VSHFLI\LQJWKH
XQGHUO\LQJWDVN.7KLVLQIRUPDWLRQLVRSWLRQDOEXWUHFRPPHQGHGIRU
WKLVH[HUFLVHWRUHVWULFWWKHGLVSOD\HGRXWSXWRI\RXUH[HFXWHGZRUNIORZ
WDVN
SAP AG BC601 7-26

(QWHUWKH7DVN,'LQWKH7DVNILHOG7KHWDVN,'EHJLQVZLWKWKH
WDVNW\SHIROORZHGE\DQGLJLWQXPEHU8VH76[[[[[[[[VWDQGDUG
WDVN:6[[[[[[[[ZRUNIORZWHPSODWH
,QWKH:RUN,WHPV3HU7DVNVFUHHQFKRRVH
$QDO\VLV([HFXWHRUWKH([HFXWHEXWWRQ
The work items of the specified type, or for the specified tasks in the
specified monitoring period are displayed. The list is sorted according to
WDVN.
Repeatedly double-clicking an entry displays the following information:
Detailed information for a shorter period (only for monitoring periods
of more than one day.)
List of all work items for a task with GDWH, VWDWXV, and possibly the
DJHQW.
Work item display for work items of single-step tasks; workflow log
for workflow work items.
Work items with monitored deadlines:
'RXEOHFOLFN:RUN,WHPV:LWK0RQLWRUHG'HDGOLQHV.
5HSHDWWKHFKRLFHVRXWOLQHGDERYHLQWKH:RUN,WHPV:LWK0RQLWRUHG
'HDGOLQHVVFUHHQ
&KRRVH$QDO\VLV([HFXWHRUWKH([HFXWHEXWWRQ
If the work items of the specified type or specified tasks were subject to
deadline monitoring, information is given on how often these deadlines
were exceeded within the specified monitoring period. The list is sorted
according to WDVN.
Work items by processing duration:
'RXEOHFOLFN:RUNLWHPV%\3URFHVVLQJ'XUDWLRQ.
5HSHDWWKHFKRLFHVRXWOLQHGDERYHLQWKH:RUN,WHPV%\3URFHVVLQJ
'XUDWLRQVFUHHQ
&KRRVH$QDO\VLV ([HFXWHRUWKH([HFXWHEXWWRQ
Specifies the process duration of work items of the specified type or for
the specified tasks. The list is sorted according to task.
SAP AG BC601 7-27

1-1-3 Workload Analysis
Using the workload analysis, you can determine the workload of
individual employees, positions, jobs, or organizational units.
6WDUW:RUNORDG$QDO\VLVIURPWKH5HSRUWLQJIROGHU
'RXEOHFOLFN:RUNORDG$QDO\VLV
Enter the organizational entity (PD) for which the workload is to be

determined, in the field Responsibility .
Describe the organizational entity (PD) by its type and 8-digit number
(ID).
,QWKH:RUNORDG$QDO\VLVVFUHHQHQWHUWKHIROORZLQJLQIRUPDWLRQ
,QWKH5HVSRQVLELOLW\IUDPH
)LHOG1DPH ,QSXW'DWD
Type O (Organizational unit)
ID 8 digit number (ID)
(The organizational unit created in

the PD Organizational Structure
exercise). Note: Use the F4 key for
input help.
To enter a user, enter the identifier US in the Type field

and the user name in the ID field. Use the F4 key for
input help.
,QWKH3HULRGIUDPH
&KRRVHWKHSHULRGIRUZKLFK\RXZDQWWRGHWHUPLQHWKHZRUNORDGE\
VHOHFWLQJWKH7REHSURFHVVHGE\UDGLREXWWRQ
&KRRVH:RUNORDG([HFXWHRUWKH([HFXWHEXWWRQ
A list of work items is displayed which must be processed by the

specified date by members of the organizational entity.
A work item must meet the following criteria to be displayed in this
list:
SAP AG BC601 7-28

The work item must be a W\SH:ZRUNLWHP(dialog work item).
The work item must have the status ZDLWLQJ, UHDG\, LQSURFHVV, UHVHUYHG,
or H[HFXWHG.
(For more information on work item statuses, see 6WDWXVHV)
1-1-4 Task Analysis

The task analysis allows you to display an overview of defined WDVNVwith
their dependencies and relationships.
Task analysis returns information from the environment of the task and
workflow definition. It does not provide runtime information.
6WDUW:RUNORDG$QDO\VLVIURPWKH5HSRUWLQJIROGHU
)URPWKH7DVN$QDO\VLVIROGHU
'RXEOHFOLFN7DVNVLQ:RUNIORZV
7\SHRI(YDOXDWLRQ
:KHUHXVHGOLVW
IRUWDVNVLQZRUNIORZGHILQLWLRQV
IRUREMHFWW\SHVLQZRUNIORZGHILQLWLRQV
)URPWKH7DVN$QDO\VLVIROGHU
'RXEOHFOLFNWKH7DVNV3URILOHLFRQ
7\SHRI(YDOXDWLRQ
$XWKRUL]DWLRQWRH[HFXWHDQGVWDUWWDVNV
1RWH'RXEOHFOLFNWKHWDVNVGLVSOD\HGLQWKHLQGLYLGXDODQDO\VHVWR
GLVSOD\WKHLUGHILQLWLRQ
SAP AG BC601 7-29

1-1-5 Workflows for object
This report allows you to display the workflow log for a certain object.
This report provides runtime information about one object.
6WDUWWKLVUHSRUWIURPWKH6$3(DV\$FFHVVPHQX
2SHQWKH5XQWLPH7RROVIROGHU
'RXEOHFOLFN:RUNIORZV)RU2EMHFW
,QWKH&KRRVH,QIR+HOSGLDORJER[FKRRVHWKH,QIRV\VWHPEXWWRQ
(QWHU LQWKH2EMHFWW\SHILHOGDQGFKRRVHWKH([HFXWH(QWHU
EXWWRQ
)URPWKH%XVLQHVVREMHFWVVHOHFW)250$%6(1&)RUP: 1RWLILFDWLRQ
RIDEVHQFH
&KRRVHWKH>$FFHSW(QWHU@EXWWRQ.
(QWHUWKHQXPEHURI\RXUODVW1RWLILFDWLRQRIDEVHQFHUHTXHVW
$IWHUZDUGV\RXFDQGLVSOD\DEUHDNGRZQRIWKHZRUNIORZORJIRUWKLV
ZRUNIORZDQGFKHFNZKLFKDJHQWVKDYHEHHQLQYROYHGLQWKHSURFHVVVR
IDU
1-1-6 Work item selection

This report allows you to display all work items created after a certain
date.
Use this report to display work items that were recently started .
6WDUWWKH:RUN,WHP6HOHFWLRQUHSRUWLQWKH6$3(DV\$FFHVVPHQX
2SHQWKHIROGHU8WLOLWLHV
'RXEOHFOLFNWKH:RUN,WHP6HOHFWLRQLFRQ
,QWKH6HOHFWLRQ5HSRUWIRU:RUN,WHPVVFUHHQ\RXZLOOQRZH[HFXWH
WKLVUHSRUWXVLQJWKHGHIDXOWRSWLRQV
$IWHUZDUGVXVHDQRWKHUVHWWLQJIRUH[DPSOH7\SH)DQG6WDWXV
&RPSOHWHG8VHWKH)NH\IRULQSXWKHOS%HIRUH\RXVWDUWWKH
UHSRUWGHOHWHWKH7LPHFUHDWHGHQWU\DQGFKRRVH3URJUDP
([HFXWHRUWKH([HFXWHEXWWRQ
7KLVUHSRUWVHWWLQJZLOOJLYH\RXDOLVWRIDOOZRUNIORZVFRPSOHWHGWRGD\
'LVSOD\WKHZRUNIORZORJWRILQGWKHDJHQWZKRSDUWLFLSDWHGLQWKLV
SURFHVV
SAP AG BC601 7-30

1-1-7 RFC Monitor
If you checked that the triggering event for a workflow has actually
occurred, but the workflow was never started, then use this RFC monitor to
locate the error.
Also use transaction SM58 with the user name to obtain a longer list.
6WDUWWKH5)&PRQLWRUIURPWKH6$3(DV\$FFHVVPHQX
2SHQWKH(YHQWVIROGHU
'RXEOHFOLFNWKH:RUNIORZ5)&0RQLWRULFRQ
In case of errors, double click the status text to obtain more information.
1-1-8 Diagnosing workflows with errors

In some situations you may only want to see workflows that have errors.
Use this report to display only the errors and to call the workflow log.
Use this report to list only work items with errors.
5XQWKHGLDJQRVLVRIZRUNIORZVZLWKHUURUVUHSRUWE\FKRRVLQJ
$GPLQLVWUDWLRQ:RUNIORZ5XQWLPH
'RXEOHFOLFN'LDJQRVLV2I:RUNIORZV:LWK(UURUV
If an error has occurred, display the work item with the error. For more
information, double-click the work item.
SAP AG BC601 7-31

&RQWDLQHUV
&RQWHQWV
l &RQWDLQHUV
l &RQWDLQHUELQGLQJV
SAP AG 1999
SAP AG BC601 8-1

&RQWDLQHUV8QLW2EMHFWLYHV
l &UHDWHDZRUNIORZFRQWDLQHUHOHPHQW
l &UHDWHDWDVNFRQWDLQHUHOHPHQW
l 8QGHUVWDQGDQGFKHFNFRQWDLQHUELQGLQJV
l &UHDWHFRQWDLQHUELQGLQJVE\GHPDQG
SAP AG 1999
SAP AG
SAP AG BC601 8-2

SAP AG 1999
SAP AG BC601 8-3

&RQWDLQHUV%XVLQHVV6FHQDULR
l 7KHPDWHULDOEXVLQHVVSURFHVV\RXZDQWWRVXSSRUW
ZLWKZRUNIORZKDVGLDORJVWHSV
l ,QIRUPDWLRQSDVVHGLQWRDWDVNLVLPSRUWHGDWWKH
EHJLQQLQJRIWKHZRUNIORZRUSURGXFHGE\SULRUVWHSV
l <RXZDQWWRNQRZKRZGDWDLVVWRUHGLQFRQWDLQHUV
DQGFDQEHXVHGLQODWHUVWHSV
SAP AG 1999
SAP AG
SAP AG BC601 8-4

&KDQJLQJ:RUNIORZ0DWHULDO0DVWHU&RQWDLQHU
$FKDQJHWRWKHPDWHULDOPDVWHUWULJJHUV
HYHQWROGBPDWHULDOBFKDQJHG Data transferred to event container
0DWHULDOREMHFW3
/DVWFKDQJHGE\8VHU-RQHV
starts
:RUNIORZ3URFHVVFKDQJHWRPDWHULDOPDVWHUGDWD
(YHQWFRQWDLQHU
-RQHV B(97B&5($725
3 B(97B2%-(&7
7DVN &RQWDLQHUWDVN :RUNIORZFRQWDLQHU

'LVSOD\FKDQJH 0DWHULDOPDVWHU
GRFXPHQWV B:,B2%-(&7B,' 0DWHULDOPDVWHU
=%86
0HWKRGFRQWDLQHU
7DVN &RQWDLQHUWDVN
'LVSOD\PDWHULDO 0DWHULDOPDVWHU
PDVWHU B:,B2%-(&7B,'
5ROHFRQWDLQHU
2UJREMHFW B:)B,1,7,$725
SAP AG 1999
n User Jones changes the material master P-100 and therefore triggers the event
old_material_changed.
The event triggers the workflow "Change material master".
n In the event container, the object reference and the person who triggered the event are transferred
from the event.
The variable for the person who triggered the event is _EVT_CREATOR, the variable for the object
reference is _EVT_OBJECT.
n Both values are transferred from the event container into the workflow container.
The person who triggered the event becomes the workflow initiator (_WF_INITIATOR).
The object reference variable depends on the object used.
n The workflow container variables are available throughout the workflow runtime.
n The task containers are created from the workflow container.
Caution: The task containers do not know your variables
Each task container must be provided from the workflow container.
n In each task container there is a variable _WI_OBJECT_ID for the object reference.
The task recognizes the object reference, because the object type must be specified when defining the
task.
n The changed material master flows from container to container as follows:
First it is an event object, then it is stored as ZBUS1001 in the workflow container, and from there
enters the different task containers.
SAP AG BC601 8-5

%LQGLQJ
l 4XHVWLRQDWGHILQLWLRQWLPH
:KDWGDWDKDVWREH
Definition of modeling and
WUDQVIHUUHGWRVXSSRUWWKH
SURFHVV"
assignment rules which are
implemented at runtime for
w 7UDQVIHUULQJGDWDIURP
RQHFRQWDLQHUWRDQRWKHU
FRQWDLQHU :RUNIORZ 7DVN
FRQWDLQHU FRQWDLQHU
w $VVLJQLQJLQLWLDOYDOXHV
WRVRPHFRQWDLQHU
HOHPHQWV
l 5XQWLPH
Binding definition is executed at
runtime
w 7KLVPHDQVGDWDLVPRYHG
IURPRQHFRQWDLQHUWR
DQRWKHU
SAP AG 1999
n Binding definition - Definition of modeling and assignment rules introduced at runtime for
Transferring the data from one container to another container
Assigning values to container elements.
n The workflow container is on the left hand side in the Workflow Builder.
n When defining the tasks, choose the "Container" button for the task definition.
n The binding definition is always executed with reference to the elements of a container. This means
that an expression is assigned to the container element or the container element is assigned to an
expression.
n At definition time the system automatically generates a proposal for the required bindings.
Each binding generated must be checked for correctness.
n When entering the task, choose the "Binding" buttton to find the binding between the workflow and
task containers in the workflow step.
For the binding to the role container, choose the button "Binding" in the box "Agent".
In the workflow basic screen, the binding from the event to the workflow container is on the
"Triggering events" tab page.
SAP AG BC601 8-6

&RQWDLQHU'HILQLWLRQ5XQWLPH
l 7DEOHOLNHGDWDVWUXFWXUHXVHGIRU
)LHOGYDOXHV
2EMHFWUHIHUHQFHV Runtime: Object reference to object type
in accordance with data type reference
(OHPHQW 'HVFULSWLRQ'DWDW\SHUHIHUHQFH 9DOXH

Object type Table field
)RUP Notification of
absence)250$%6(1&
$JHQW Agent in :)6<67$*(17
workflow
Data type reference to field Runtime: Value has data type

in ABAP Dictionary in accordance with
data type reference
Data type reference to object type
in Object Repository
Definition Runtime
SAP AG 1999
n Containers are table-like data structures.

n Containers are exclusively used for accepting attribute values, constants, and object references for
control and monitoring, for the workflow process and the execution of work items.
n Container definitions are created by the workflow system as standard.
The tasks and methods used in the workflow are the basis for the defined fields.
n As a customer, you can enhance container definitions at any time.
In the Workflow Builder, you can process the container definition using the context menu.
n Container definition in the workflow:
Description of elements to be stored in the container, with element name, description, and data
type reference
The description can refer to a field in the ABAP Dictionary, to an object type,
or can represent any field with a known data type
n Container instance
Table-like runtime structure from the container definition.
The name of an element is entered in a line together with its value.
The data type of this value must agree with the data type reference established at definition.
SAP AG BC601 8-7

3URFHVVLQJ%LQGLQJLQWKH:RUNIORZ%XLOGHU
:6%LQGLQJLQZRUNIORZVWHS$SSURYHQRWLILFDWLRQRIDEVHQFH
'LVSOD\RIDOOSRVVLEOHYDULDEOHV
XVLQJ6KRZOLQHV
7DVN
7DVN :RUNIORZ
:RUNIORZ
6WDQGDUGVFUHHQLQFKDQJHPRGH
SAP AG 1999
n The upper part of the screen shows the binding from the workflow container into the task container.
The lower part of the screen shows the binding from the task container back into the workflow
container.
n Not all container elements are visible by default. You can use the "Show lines" icon to make them
visible for processing.
n Use the input help (F4) for values.
SAP AG BC601 8-8

&RQWDLQHUDQG%LQGLQJ'LUHFWLRQV
:RUNIORZ WDVN
:RUNIORZ Event container

FRQWDLQHU Task container
5ROH (YHQW 0HWKRG
Role Event Method

parameter parameter parameter
container container container
SAP AG 1999
n The WDVNFRQWDLQHUalways contains an element that can store the reference to the object to be
processed in the respective single-step task (_WI_Object_ID). It also contains the element
"_WI_Actual_Agent". This is the agent who actually executed the work item. For synchronous tasks
with a defined result parameter, the _WI_Result'element can store
the result of the underlying object method.
n The ZRUNIORZFRQWDLQHUalways contains an element that can store the user name of the initiator
of the current workflow (_WF_Initiator). For most workflows you have to create a new element in
the workflow container. To do this you can either go along with the SAP proposals, or you can create
your own element. For example, you have to provide a storage element for the main object of your
process.
n The HYHQWFRQWDLQHUalways contains an element that can store the (object) reference to the object
whose change of status is announced using the event '_EVT_Object' . It also always contains an
element with the name of the user responsible for changing the status of the object ('
_EVT_Creator' ).
n The UROHFRQWDLQHUcontains the elements required as input in connection with the role resolution to
be run at runtime.
If a default role is defined for the entry, the binding can also begin from the entry in the role.
n The PHWKRGFRQWDLQHUcontains elements which are import parameters in connection with the
method execution.
SAP AG BC601 8-9

'HPR([DPSOH%LQGLQJ'HILQLWLRQ
Submit notification of absence
Notification of
absence created
QRWLILFDWLRQRIDEVHQFH
5HIHUHQFHWRREMHFWW\SH
Approve notification
of absence
approved rejected
Change notification
6HQGPDLO of absence ?
No Yes
Delete notification
mail sent of absence
deleted revised
Yes
Re-submit
for
No
:RUNIORZ
approval ?
Complete
FRQWDLQHU
workflow
Workflow
completed
SAP AG 1999
n Element in the workflow container: Object notification of absence

The element is created with a data type reference to the object type FORMABSENC.
n The event "Notification of absence created" triggers the workflow "Notification of absence".
SAP AG BC601 8-10

Notification of
absence created
Change notification
of absence
approved rejected
Change notification
No Yes
Delete notification
deleted revised
Yes
Re-submit
for
No approval ?
Complete
workflow
:RUNIORZ
Workflow FRQWDLQHU
SAP AG 1999
completed
n The binding is always at the appropriate place in the workflow definition.

The system generates bindings automatically. You must check the definition
n The binding Event -> Workflow container is on the "Triggering Event" tab page in the workflow
template.
n When entering a task, the binding Workflow container - Task container is on the "Control" tab page.
n The binding Workflow container - Role container in the workflow step is on the "Control" tab page
and is shown if the routing should occur using a role.
n To find the binding to the method container choose Goto - Binding - Object method in the task
definition
n Binding
Event -> Workflow container
&_EVT_CREATOR& -> &_WF_INITIATOR&
&_EVT_OBJECT& -> &Vacation request&
n Binding
Workflow container -> Task container
&Vacation request& -> &_WI_OBJECT_ID&
n Each task must be individually provided from the workflow container.
SAP AG BC601 8-11

Notification of
absence created
3HUVRQVXEPLWWLQJQRWLILFDWLRQRIDEVHQFH
Change notification
of absence
approved rejected
Change notification
No Yes
Delete notification
deleted revised
Yes
Re-submit
for
No approval ?
Complete
:RUNIORZ
workflow
Workflow FRQWDLQHU
SAP AG 1999
completed
n If the role resolution of a workflow step requires an import parameter, then those values have to be
provided from the workflow container.
n Binding
Workflow container -> Role container
&_WF_INITIATOR& -> &ORG_OBJECT&
SAP AG BC601 8-12

%LQGLQJDQG&RQWDLQHUV
(YHQWFRQWDLQHU
B(97B&5($725
B(97B2%-(&7
:RUNIORZ
FRQWDLQHU &+$1*(7DVN
FRQWDLQHU
(YHQW B:)B,QLWLDWRU B:,B2EMHFWB,G
B:,B$FWXDOB$JHQW
&KDQJH 0$7(5,$/
PDWHULDO 5ROHFRQWDLQHU

&KDQJHGBE\
6XSHULRU 'LVSOD\ 25*B2%-(&7

RI PDWHULDO

',63/$<7DVN
FRQWDLQHU
B:,B2EMHFWB,G
=BFKDQJHGBE\
SAP AG 1999
n The workflow container contains two customer-defined elements:

The material based on Business Object BUS1001
"Changed-By" is based on the ABAP Dictionary field WFSYST-AGENT.
n The event transfers the material reference and the initiator to the workflow container.
n The "CHANGE" task is provided from the workflow container with the object reference (Binding
Workflow container -> Task container), and returns the actual agent of the work item from the
variable &_WI_ACTUAL_AGENT& into the variable &CHANGEDBY& of the workflow
container (Binding Task container -> Workflow container).
n The task "DISPLAY" is transferred to the object reference and to the variable "Changed_by". The
"Z_changed_by" can now, for example, be used as a variable in the work item text of the display
task.
"Z_changed_by" can also be used as a new agent.
n The workflow initiator is entered in the "find supervisor" role. It is assumed that the supervisor of the
initiator processes the step "Display material".
SAP AG BC601 8-13

([DPSOHRID&RQWDLQHU2SHUDWLRQ
6XSSO\LQJD&XVWRPHU2EMHFW5HIHUHQFH
6FHQDULR,QDZRUNIORZIRUSURFHVVLQJRUGHUV\RXZDQWWRSURYLGHDQREMHFW
UHIHUHQFHWKDWUHIHUVWRWKHVROGWRSDUW\WKHFXVWRPHU
9DOXHIURP
6HOI RUGHU
GHILQHG WUDQVIHUUHG
REMHFW IURPWKH
UHIHUHQFH HYHQW
WRFXVWRPHU
SAP AG 1999
n Container elements can also be specifically provided by a workflow step. This involves the container
operation step.
Container operations are necessary, for example, if you want to execute a secondary method in
addition to the main method.
n The binding entered in the workflow step usually only provides the main method.
Secondary methods must be provided using a container operation with valid values.
n If it does not already exist, you must first create the object reference in the workflow container.
For example, you can create an element CUSTOMER in the workflow container that refers to the
object type KNA1 (customer).
n You must then insert the container operation step into the workflow.
Your workflow processes a customer order.
n In the container operation you provide the Customer element with the ordering party value
(ORDERINGPARTY) from the order (Element CUSTOMERORDER) in the workflow container
n &DXWLRQ:
The customer number (database key field) must not be transferred.
You must enter the reference to the whole object "ordering party" (object reference).
SAP AG BC601 8-14

+RZ'RHV'DWD5HDFKWKH&RQWDLQHUV"
l :RUNIORZFRQWDLQHU
)URPWKHFRQWDLQHUHOHPHQWVRIWKHWULJJHULQJHYHQW
)URPWKHH[SRUWSDUDPHWHUVRUUHVXOWVRIDWDVN
)URPDFRQWDLQHURSHUDWLRQVWHS
%\HQWHULQJLQLWLDOYDOXHV
l 7DVNFRQWDLQHU
)URPDWHUPLQDWLQJHYHQW
)URPPHWKRGSDUDPHWHUV
%\HQWHULQJLQLWLDOYDOXHV
SAP AG 1999
n How containers are assigned values at runtime is shown in workflow runtime reporting.
n 7DVNFRQWDLQHU:
Display work item (type W) that belongs to the task
Goto ,Technical work item display
Extras Container
n :RUNIORZFRQWDLQHU:
Display work item (Type F), that represents the whole workflow to which the task belongs
Goto - Technical work item display
Extras Container
n The simplest way to view the type F work item (workflow work item):
From the work item display, go to the log and double click the highest level.
The workflow work item is displayed.
SAP AG BC601 8-15

:KHUH&RQWDLQHU(OHPHQWV$UH8VHG
l :RUNLWHPWH[W
l 7DVNGHVFULSWLRQ
l 0LVVHGGHDGOLQHWH[WV
GHDGOLQHODWHVWVWDUWGHVLUHGHQG
l 1RWLILFDWLRQWH[W
l ([SRUWLQWHUIDFHWRWKHREMHFWPHWKRG
l ([SRUWLQWHUIDFHWRWKHWDVN
l ([SRUWLQWHUIDFHWRWKHUROH
l &RQWDLQHURSHUDWLRQV
l 6HFRQGDU\PHWKRGV
l &RQGLWLRQ(GLWRU
l 6WDUWFRQGLWLRQVIRUHYHQWV
SAP AG 1999
SAP AG BC601 8-16

&RQWDLQHUV8QLW6XPPDU\
l &RQWDLQHUVDUHWDEOHOLNHGDWD
VWUXFWXUHV
l &RQWDLQHUVFRQWDLQFRQWURO
LQIRUPDWLRQIRUWKHZRUNIORZV\VWHP
l &RQWDLQHUVDUHXVHGIRUILHOGYDOXHV
DQGREMHFWUHIHUHQFHV
l 'XULQJUXQWLPHWKHGLIIHUHQW
FRQWDLQHUVSURYLGHHDFKRWKHU
ZLWKQHFHVVDU\LQIRUPDWLRQ
ELQGLQJGHILQLWLRQWUDQVIHUV
GDWDIURPRQHFRQWDLQHUWRDQRWKHU
SAP AG 1999
SAP AG BC601 8-17

([HUFLVHV
8QLW&RQWDLQHUV

Understand the containers concept
When you create your own workflow, you also have to think about the
data flow. Within a workflow, data is transferred from one container to
the next. You prepare this data flow by defining the binding between
different containers.
1-1 Familiarize yourself with containers in the SAP Workflow system at runtime.
1-1-1 Which workflow components have their own containers?

____________________________________________
____________________________________________
____________________________________________
____________________________________________
____________________________________________
____________________________________________
1-1-2 Name at least 2 possible ways to reach the starting point for a runtime
evaluation of a workflow or a task container?
____________________________________________
____________________________________________
1-1-3 You have a work item in your worklist. How do you display the associated
task container?
____________________________________________
SAP AG BC601 8-18

1-1-4 How can you use the Work item selection report to display the workflow
container?
____________________________________________
____________________________________________
____________________________________________
____________________________________________
1-1-5 You see a particular workflow container. Who is the initiator of this
workflow?
____________________________________________
1-1-6 Looking at the work item for your "Z##_T_1" task, where could you have
used an imported container element?
____________________________________________
____________________________________________
____________________________________________
____________________________________________
____________________________________________
SAP AG BC601 8-19

([HUFLVHV
8QLW&RQWDLQHUV3DUW

Check the binding in the workflow after inserting a single step task
When you create your own workflow, you also have to think about the
data flow. Within a workflow, data is transferred from one container to
the next. You prepare this data flow by defining the binding between
different containers.
1-1 Call your material master workflow in the workflow editor
1-2 After the Display material change documents task, insert the Display material
master task
1-3 Name the manager of your organizational unit as the agent for this step.
Choose this person using their position.
1-4 Check the binding between the two tasks.
1-4-1 How does the first task know which material to work with?
1-4-2 How is the object transferred to the second task?
1-5 Activate the workflow and choose the Test button in the Workflow Builder.
In the first step, the change documents are displayed to the workflow initiator.
After the first step has been processed, the manager BC601-MGR## receives a
work item to display.
If you are executing the test as a manager, you will immediately see the material
displayed.
Otherwise, change to a mode in which you are registered as a manager, and execute
the work item to be sure that your material was correctly transferred. If you have
problems executing the work item, use Refresh in the inbox of your
organizational chart.
SAP AG BC601 8-20

([HUFLVHV
8QLW&RQWDLQHUV$GGLWLRQDOH[HUFLVH
7RSLF8VLQJDGRFXPHQWWHPSODWHLQ
ZRUNIORZ

Create a document template in the workflow template
Insert a step in your workflow for displaying or changing a
document.
Until now you have created and tested a workflow. You now want to edit,
save, and release some of the workflow runtime data and additional user
data in your own document. The SAP Workflow development
environment provides the following document processing functions for
doing this.
1-1 Make a copy of your material display workflow
1-1-1 In your copied workflow, create a document template in the form of a

Word document
1-1-2 Enter the following text:
Material workflow group ##
Person triggering the workflow: <variable workflow initiator>
Material: <variable material number>
Save the template under ' ZDOC_##' .
1-2 Processing the document template
1-2-1 After the step Display material changes ,

enter a new step Document from template .
The agent for the step should be the workflow initiator.
Enter a new step description for each of the starting points Step
executed or Document could not be created .
1-2-3 Which element was created from new in the Workflow Container?
1-2-4 Insert a new activity after the starting point Step executed
This involves the activity Edit document , task
TS71007944.
All tasks for processing document templates can be found in
the task group TG71000004.
Check the binding in both directions.
The agent is the user BC601-MGR##.
1-3 Activate and test your workflow
SAP AG BC601 8-21

6ROXWLRQV
8QLW&RQWDLQHUV
1-1 Familiarize yourself with containers in the SAP Workflow system at runtime.
1-1-1 The workflow components with their own containers are:
Workflow
Task
Event
Role
Object method
1-1-2 To get to the starting point for a runtime evaluation of a workflow or a

task within the workflow development area, you can use the following
different reports:
5XQWLPH7RROV%XVLQHVV:RUNSODFH2XWER[
5XQWLPH7RROV%XVLQHVV:RUNSODFH,QER[
5HSRUWLQJ'RXEOHFOLFN:RUN,WHP$QDO\VLV
8WLOLWLHV'RXEOHFOLFN:RUN,WHP6HOHFWLRQ
8WLOLWLHV 'RXEOHFOLFN'LDJQRVLV
1-1-3 From a work item in your worklist you can choose

'LVSOD\WKHQVHOHFW*RWR7HFKQLFDOZRUNLWHPGLVSOD\([WUDV
&RQWDLQHU
to see a runtime snap shot of the associated task container.
1-1-4 After you have started the Work item selection report, select Type '
F'
on the Selection Report for Work Items screen. Then choose
3URJUDP([HFXWHRUFKRRVHWKH([HFXWHEXWWRQ
to start the report. Finally, position the cursor on your type F work item,
and choose
*RWR&RQWDLQHU
SAP AG BC601 8-22

1-1-5 You see a workflow container. Who is the initiator of this workflow?
&KHFNWKHYDOXHLQWKHYDULDEOHB:)BLQLWLDWRU
1-1-6 Looking at the work item for your "Z##_T_1" task, where could you
have used an imported container element?
:RUNLWHPWH[W
7DVNGHVFULSWLRQ
0LVVHGGHDGOLQHWH[WV
1RWLILFDWLRQWH[W
([SRUWLQWHUIDFHIRUREMHFWPHWKRGIRUWDVNIRUUROH
&RQGLWLRQ(GLWRU
6HFRQGDU\PHWKRGV
6WDUWFRQGLWLRQVIRUHYHQWV
&RQWDLQHURSHUDWLRQ
SAP AG BC601 8-23

SAP AG BC601 8-24
6ROXWLRQV
8QLW&RQWDLQHUV3DUW
&KHFNLQJ%LQGLQJ
1-6 Call your material master workflow in the workflow editor
6$3($6<$&&(66!7RROV!%XVLQHVV:RUNIORZ!'HYHORSPHQW!
'HILQLWLRQ7RROV!:RUNIORZ%XLOGHU
1-7 After the Display change documents of material task, insert the task Display
material master
'RXEOHFOLFNWKHXQGHFLGHGWDVNDIWHU\RXUWDVN&KDQJHGRFXPHQWVIRU
PDWHULDODQGFKRRVHWKH$FWLYLW\EXWWRQ
(QWHU76DVWKHWDVNDQGWKHQXPEHURI\RXUVLQJOHVWHSWDVN'LVSOD\PDWHULDO
PDVWHU8VHWKHLQSXWKHOS)LI\RXQRORQJHUNQRZWKHQXPEHU
1-8 Name the manager of your organizational unit as the agent for this step.
Choose this person using their position.
<RXDUHVWLOOLQWKHWDVNVWHS'LVSOD\PDWHULDO
&KRRVH3RVLWLRQLQWKH$JHQWVER[DQGXVHWKHLQSXWKHOSWRVHDUFKIRUWKH
PDQDJHUSRVLWLRQRI\RXURUJDQL]DWLRQDOXQLW
&KHFNWKHELQGLQJEHWZHHQWKHWZRWDVNV
+RZGRHVWKHILUVWWDVNNQRZZKLFKPDWHULDOWRZRUNZLWK"
7KHWDVN'LVSOD\FKDQJHGRFXPHQWVNQRZVWKHPDWHULDOIURPWKHLQLWLDOYDOXH
HQWHUHGLQWKHVLQJOHVWHSWDVN
,WGRHVQRWNQRZLWIURPWKHZRUNIORZFRQWDLQHU
+RZLVWKHREMHFWWUDQVIHUUHGWRWKHVHFRQGWDVN"
'LVSOD\WKHELQGLQJE\GRXEOHFOLFNLQJWKHLFRQ%LQGLQJH[LVWV
7KHVHFRQGWDVNPXVWKDYHWKHPDWHULDOLQWKHWDVNFRQWDLQHULQWKHYDULDEOH
B:,B2%-(&7B,'7KLVYDULDEOHPXVWEHILOOHGGXULQJELQGLQJLQWKHVWHSIURP
WKHZRUNIORZFRQWDLQHU
%LQGLQJZRUNIORZFRQWDLQHU!7DVNFRQWDLQHU
SAP AG BC601 8-25

,QWKHZRUNIORZFRQWDLQHU\RXPXVWVHOHFWWKHYDULDEOHIRUWKHPDWHULDOREMHFW,W
FDQEHWKHYDULDEOH 0$7(5,$/B*5283B
RU =PDUD
1RUPDOO\DZRUNIORZLVVWDUWHGXVLQJHYHQWVDQGWKHREMHFWLVWUDQVIHUUHGLQWRWKH
ZRUNIORZFRQWDLQHUE\WKHHYHQWPDQDJHU
%HFDXVHWKHZRUNIORZLVQRW\HWVWDUWHGZLWKHYHQWV\RXPXVWHQVXUHWKDWWKH
ZRUNIORZFRQWDLQHUYDULDEOHLVILOOHGFRUUHFWO\IURPWKHILUVWWDVNRQZDUGV
5HWXUQWRWKHVFUHHQ:RUNIORZ%XLOGHU]ZIBWHVWBFKDQJH
'RXEOHFOLFNWRGLVSOD\WKHZRUNIORZVWHS&KDQJHGRFXPHQWVIRUPDWHULDO
'LVSOD\WKHELQGLQJE\GRXEOHFOLFNLQJWKHLFRQ%LQGLQJH[LVWV
&KHFNWKHELQGLQJ7DVNFRQWDLQHU!:RUNIORZFRQWDLQHULQWKHORZHUSDUWRIWKH
VFUHHQ
<RXPXVWHQVXUHWKDWRQWKHZRUNIORZFRQWDLQHUVLGHDYDULDEOHLVVSHFLILHGWKDW
FDQLQFOXGHWKHHQWU\LQ:,B2%-(&7B,'
8VHWKHLQSXWKHOS)IRUWKLVDQGVHOHFW\RXUPDWHULDOYDULDEOH
1-10 Activate the workflow and choose the Test button in the Workflow Builder.
5HWXUQWRWKHVFUHHQ:RUNIORZ%XLOGHU]ZIBWHVWBFKDQJHDQGFKRRVHWKH
LFRQ&UHDWHDQGDFWLYDWHUXQWLPHYHUVLRQ
7KHQFKRRVHWKH7HVWLFRQ
([HFXWHWKHZRUNIORZWHPSODWH
In the first step, the change documents are displayed to the workflow initiator.
After the first step has been processed, the manager BC601-MGR## receives a
work item to display.
If you are executing the test as a manager, you will immediately see the material
displayed.
Otherwise, change to a mode in which you are registered as a manager, and execute
the work item to be sure that your material was correctly transferred.
If you have problems executing the work item, use Refresh in the inbox of your
organizational environment.
7RGRWKLVFKRRVHWKHIROORZLQJLQWKH%XVLQHVV:RUNSODFHVFUHHQ
6HWWLQJV!:RUNIORZVHWWLQJV!5HIUHVKRUJDQL]DWLRQDOHQYLURQPHQW
SAP AG BC601 8-26

6ROXWLRQV
8QLW&RQWDLQHUVDGGLWLRQDOH[HUFLVH
7RSLF8VLQJDGRFXPHQWWHPSODWHLQZRUNIORZ
1-1 Make a copy of your material workflow
6$3($6<$&&(667RROV%XVLQHVV:RUNIORZ'HYHORSPHQW
'HILQLWLRQ7RROV7DVNV7DVN*URXSV&RS\
(QWHUWKHQXPEHURI\RXUPDWHULDOZRUNIORZ,IQHFHVVDU\XVHWKHLQSXWKHOS
)WRILQGWKLVQXPEHU
8QGHU&RS\HQWHUWKHDEEUHYLDWLRQ=GRFXB'HVFULSWLRQ'RFXPHQW
WHPSODWH*URXS
1-1-1 Create a new document template
5HWXUQWRWKHWDVNPHQXDQGFKRRVH
&KDQJHWDVN
7KHZRUNIORZQXPEHUKDVDOUHDG\EHHQHQWHUHG
&KRRVHWKH&KDQJHLFRQDQGVWDUWWKH:RUNIORZ%XLOGHUXVLQJWKH
:RUNIORZ%XLOGHULFRQ
,QWKHQDYLJDWLRQDUHDFOLFNWKH'RFXPHQWWHPSODWHVEDU
'RXEOHFOLFNRQWKHDUHD'RXEOHFOLFNWRFUHDWH
6HOHFWWKH:RUGGRFXPHQWE\GRXEOHFOLFNLQJ
$:RUGGRFXPHQWLVVKRZQLQWKH:RUNIORZ%XLOGHU
1-1-2 Enter the following text:

Material workflow Group ##
Person triggering the workflow: <variable workflow initiator>

Material: <variable material number>
7RLQVHUWWKHYDULDEOHVSRVLWLRQWKHFXUVRULQWKHGHVLUHGSODFHDQGVHOHFW
WKHDSSURSULDWHYDULDEOHIURPWKHYDULDEOHGLVSOD\RQWKHOHIWKDQGVLGHRI
WKH:RUNIORZ%XLOGHU
1-1-3 Save the template
5HWXUQWRWKH:RUNIORZ%XLOGHUVWDQGDUGGLVSOD\
7KHV\VWHPZLOODVNLI\RXZDQWWRVDYHWKHWHPSODWH
6DYHLWXQGHU
='2&B

7KHGRFXPHQWWHPSODWHLVYLVLEOHLQWKHQDYLJDWLRQDUHDXQGHUGRFXPHQW
WHPSODWHV
SAP AG BC601 8-27

1-2 Insert a new step Document as template
Process the document template
6HOHFWWKHRXWFRPHRIWKHVWHS'LVSOD\PDWHULDOFKDQJHGRFXPHQWV
&KRRVHWKH&UHDWHLFRQDQGVHOHFWWKH'RFXPHQWDVWHPSODWHVWHS
,QWKHZRUNIORZVWHSGLVSOD\HGFOLFNLQWKHHPSW\ILHOG'RFXPHQW
WHPSODWHVQH[WWRWKH&UHDWHLFRQ
$QLQSXWKHOSEXWWRQDSSHDUV
8VHWKHLQSXWKHOSWRVHOHFW\RXUGRFXPHQWWHPSODWH
(QWHUWKHZRUNIORZLQLWLDWRUDVDJHQW
1-2-2 Enter a step description on the Outcomes tab page.
&KRRVHWKH2XWFRPHVWDESDJHDQGDVVLJQQDPHV
1-2-3 Which element was created from new in the Workflow Container?
,QWKHQDYLJDWLRQDUHDFOLFNRQWKH:RUNIORZFRQWDLQHUEDU
<RXZLOOVHHWKHHOHPHQW:)B'RFXPHQWBWKDWZDVXVHGLQWKH
ZRUNIORZVWHSXQGHU(OHPHQWIRUGRFXPHQW
1-2-4 Insert a new activity in the outcome Step executed
6HOHFWWKHRXWFRPH6WHSH[HFXWHGIRUWKHDFWLYLW\\RXKDYHMXVWFUHDWHG
&KRRVHWKH&UHDWHEXWWRQDQGWKHQFKRRVH$FWLYLW\
(QWHUWKHWDVN76(GLWGRFXPHQW
$OOWDVNVIRUGRFXPHQWWHPSODWHVDUHLQWKHWDVNJURXS7*
&KHFNWKHELQGLQJLQERWKGLUHFWLRQV7KHZRUNIORZFRQWDLQHUYDULDEOHLV
:)B'2&80(17B
&KRRVHWKHXVHU%&0*5DVWKHDJHQW
1-3 Activate and test the workflow
,QWKH:RUNIORZ%XLOGHUFKRRVHWKHLFRQ&UHDWHDQGDFWLYDWHUXQWLPHYHUVLRQ
&KRRVHWKH7HVWLFRQLQWKH:RUNIORZ%XLOGHU
SAP AG BC601 8-28

5RXWLQJ
&RQWHQWV
l 5ROHV
5HVWULFWLQJSRVVLEOHDJHQWV
'HILQLWLRQZLWKUHVSRQVLELOLWLHV
$G+RFZRUNIORZDQGDJHQW
DVVLJQPHQW
5ROHUHVROXWLRQDQGELQGLQJ
SAP AG 1999
SAP AG BC601 9-1

5RXWLQJ8QLW2EMHFWLYHV
l 'HVLJQDWHUHVSRQVLEOHDJHQWV
l 8VHUROHV
SAP AG 1999
SAP AG BC601 9-2

SAP AG 1999
SAP AG BC601 9-3

5RXWLQJ%XVLQHVV6FHQDULR
l ,QWKHPDWHULDOEXVLQHVVSURFHVV\RXZDQW
WRUHVWULFWWKHQXPEHURISRVVLEOH
DJHQWVLQRUGHUWRREWDLQWKRVHXVHUVWKDWDUH
UHVSRQVLEOHIRUWKLVVWHSDFFRUGLQJWR
UXQWLPHGDWD
SAP AG 1999
SAP AG
SAP AG BC601 9-4

:RUNIORZ6WHS$JHQW$VVLJQPHQW2SWLRQV
3URFHVV 2UJDQL]DWLRQ
ZRUNIORZGHILQLWLRQ Business
2UJXQLW
2UJXQLW Workplace
-RE
:RUNOLVW
3RVLWLRQ
3RVLWLRQ
Prio Tasks Date
8VHU,'
1 Approve Form Mar 1
Responsibility 2 Post Invoice Mar 25
5ROH
5ROH 3 Post Invoice Apr 5
IXQFWLRQ
3UHYLRXV
ZRUNIORZ
Your worklist can display
DJHQWV all work items for which
you are a recipient
SAP AG 1999
n Using the agents in the workflow step, and the possible agents for the task, the runtime system
determines the current valid agent for the workflow step.
n All responsible agents, who are also possible agents for the task, will become recipients of the work
item.
n The workflow system only enters this work item once in the work item list.
n All recipients can view this work item by refreshing their worklist.
n You have the option to make fixed agent assignments. These include
Members of organizational units
Owners of positions
Owners of positions who have inherited tasks from job assignment
SAP users
n They can refer to variables (output) of the workflow container.
For example, you can save the agent for the 1st workflow step in a variable of the workflow
container and enter this variable in the 5th step of the workflow as the agent for that step.
n Another possibility are agents who are found dynamically at runtime using a role.
According to runtime entries that are transferred into the role container, a role function module
determines responsible users, for example, the superior of the workflow initiator.
SAP AG BC601 9-5

5ROH'HILQLWLRQ
l 5ROHW\SHVFDQEH
5HVSRQVLELOLWLHV
w 'DWDIURPWKHZRUNIORZFRQWDLQHULVDVVLJQHGWRDJHQWV
w 1R$%$3&RGHMXVWFRQILJXUDWLRQ
2UJDQL]DWLRQDOGDWD
w 6$32UJDQL]DWLRQDO2EMHFW7\SHVDUHXVHGWRDVVLJQ
DJHQWV
w 1R$%$3&RGHMXVWFRQILJXUDWLRQ
)XQFWLRQPRGXOH
w $%$3&RGH
<RXDUHIUHHWRGHYHORSHYHU\IXQFWLRQPRGXOH\RXQHHG
SAP AG 1999
n There are 3 different role types.

Two of these only require system settings, the third variant requires a customer-specific function
module to be stored in R/3.
n 2UJDQL]DWLRQDOGDWD:
Roles using organizational data require an SAP organizational object type in the system.
Table T7791 contains the SAP organizational object type and the information about which object
types can be linked to them.
Within the object type processed by the workflow, one element must refer to this SAP
organizational object type.
The SAP organizational object type is linked to agents through organizational units, positions or
jobs.
For more information, see the appendix of this file or the workflow documentation, key word
"Organizational object"
n 5HVSRQVLELOLWLHV:
From Release 4.0 onwards, you can define roles using responsibilities.
In the workflow container, you store variables that are filled with values at runtime.
You also store value ranges for these variables and assign agents to the different values.
n Developing customer-specific function modules for role resolution is the topic of course BC610.
SAP AG BC601 9-6

2SWLRQVIRU'HILQLQJD5ROH

:LWK6$3 :LWKRXW6$3
2UJDQL]DWLRQDO6WUXFWXUH 2UJDQL]DWLRQDO6WUXFWXUH
- Particular groups - Fixed user assignment
or positions - Role with responsibilties
- SAP role, for example, Manager for user
- Responsibilities Workflow container element,
for example, workflow initiator
- SAP Org. Objects or last agent
- BBP Manager - SAP Office distribution list
Ad Hoc Selection - New step for the free
- New step for the free selection of the next
selection of the next recipient
recipient - Own ABAP function with
customer tables or SAP tables
- Own ABAP programs
with evaluation path
or self-created
function
SAP AG 1999
n During implementation the self-defined ABAP solutions take the longest.

The roles based on responsibility can be implemented within minutes.
n In general, role definitions with fixed agent assignment are not recommended.
This is because the agent assignment does not change automatically if an employee in the enterprise
takes over a new task, and is no longer available for the task assigned in the workflow.
n From Release 4.0 onwards, roles can generally be defined by responsibilty instead of by SAP
organizational objects. Roles by responsibilties are more flexible and easier to use.
SAP AG BC601 9-7

([DPSOH5ROH6XSHULRU
l 5ROH Possible
Possible agents:
agents:
Restriction of possible agents Group of all
Group of all
according to organizational model managers
managers
l 6WDQGDUG7DVN'HILQLWLRQ
Approve notification of absence

Linked to job: Head of department
l 5ROHDJHQW Superior...

Parameter for role: Employee Responsible
Responsible agent:
agent:
l :RUNLWHPDFWLYLW\DWUXQWLPH
Approve notification of absence 4712
Employee: Marcus Adams
Evaluation of organizational plan
Superior: David Boss
SAP AG 1999
n The role Superior... can be used to route a notification of absence to the responsible superior.
n In this case, Adams wants to go on vacation and only David Boss should receive this work item.
No other possible agents should receive this notification of absence.
SAP AG BC601 9-8

([DPSOH5ROH,QYRLFH9HULILFDWLRQ&OHUN
l 5ROH Customer names Invoice verification clerk

Restriction of possible agents A-G
according to organizational model
l 3RVVLEOH$JHQWVRI7DVN
Post document
Linked to job:
Invoice verification clerk
l 5ROH)LQGLQYRLFHYHULILFDWLRQFOHUN
2 Parameters: Customer
- Customer name names
- Invoiced amount H-N
Customer names
l :RUNLWHPDFWLYLW\DWUXQWLPH O-Z
Post document 4712
Customer - Manley Corp. Invoiced amount: < $ 50,000
Invoiced amount - $ 258,300
Invoiced amount: > $ 50,000
SAP AG 1999
n Example of how role resolution could be used in an invoice verification workflow.

n Design requirements -
All clerks working in this unit are assigned to a special customer group. At runtime they should
only receive invoices from those customers.
Each clerk has a pre-defined personal transaction limit. If the invoice is above this limit, this
clerk is not allowed to process the invoice.
n Runtime -
The two import parameters for the role resolution (Manley Corp. and $ 258,300), determine
that the work item should be sent to the three agents circled in red.
Only those three recipients will receive this work item in their worklist.
- The first user to execute the work item at runtime will block access to this work item. No
other user can access it. The work item will actually disappear from the worklist of the other
two users, when they refresh their worklist.
- After the "first agent" has completed the work item, it will disappear automatically from their
worklist after the next refresh.
SAP AG BC601 9-9

&XVWRPHU6SHFLILF5ROHIRU0DWHULDO&RQWUROOHU
l 0DWHULDO0DVWHUFKDQJHGE\6FKPLG
0DWHULDO 0\BSDUW &KDQJHGRFXPHQWV
2OGPDWHULDO 2ULJLQDOBSDUW
1HZBSDUW
&U
HD Design department
WH CAD engineer position
=%86
G Owner: Schmid Possible 2OGB0DWHULDOB&KDQJHG
E\ 3URGXFWPDQDJHPHQW agents
GHSDUWPHQW
3URGXFWPDQDJHUSRVLWLRQ
7DVN
Owner: Jones
'LVSOD\PDWHULDO
0DWHULDO&RQWUROOHU3RVLWLRQ Selected
Owner: Meier
agents 5ROH
)LQG&RQWUROOHU
,PSRUWSDUDPHWHUV
SAP AG 1999
n Acceptance for this example of a business process:The creator of the material master basic view is
considered to be the material controller.
n Design-Procedurefor the Material Controller Role:
n First - Assign the possible agents to the task.
n Second - Create a role that returns the controller for a given material. You will probably have to
create this role yourself:
Copy an existing role function module (ABAP-program).
Change this program to find the creator of the imported material master.
n Third - Assign this role to your step definition and provide the import parameter. If you use the task
stand alone, you can assign the role directly to the task.
n During runtime this role resolution will return a special user ID. This user becomes a recipient if he
or she is also a possible agent for this task.
SAP AG BC601 9-10

&UHDWLQJD'LVWULEXWLRQ/LVW
l %XVLQHVV:RUNSODFH
6KDUHGIROGHUVULJKWPRXVHEXWWRQ
w &UHDWHQHZVXEIROGHU
1DPH:)B9HUWHLOHU
%XWWRQ'LVWULEXWLRQOLVWV
w &UHDWHEXWWRQ
1DPH:)B9/,67(
7LWOH$Q\WLWOH
)ROGHU:)B9HUWHLOHU
w 7DESDJHGLVWULEXWLRQOLVWFRQWHQW
(QWHUUHFLSLHQW6$3XVHU,'
w 6DYH
SAP AG 1999
SAP AG BC601 9-11

5ROH5HVROXWLRQ:LWK'LVWULEXWLRQ/LVW
l :RUNIORZ%XLOGHU
3URFHVVGLDORJVWHS
$JHQWDVVLJQPHQW
5ROHVZ[BUHDGBGOL
%LQGLQJ:)B9/,67(
(QWHUQDPHRIGLVWULEXWLRQOLVWDVFRQVWDQW
$FWLYDWHZRUNIORZ
l 6WDUWZRUNIORZ
l &KHFNZRUNLWHPUHFLSLHQW
SAP AG 1999
SAP AG BC601 9-12

5ROH'HILQLWLRQ:LWK5HVSRQVLELOLWLHV%DFNJURXQG
l :K\GRZHQHHGWKLVW\SHRIUROH"
7KHDSSOLFDWRQRIWHQUHTXLUHVWKHDVVLJPHQWRI
UHVSRQVLELOLWLHVWREXVLQHVVREMHFWVVXFKDVIRUH[DPSOH
ZKRLVUHVSRQVLEOHIRUPDWHULDOJURXS[\"
l :KDWLVDUROHRIWKLVW\SH"
$UROHWKDWGRHVQRWKDYHWREHSURJUDPPHG
-XVWFRQILJXUDWLRQQR$%$3FRGH
l +RZDUHWKHVHUROHVGHILQHG"
'HILQLWLRQRIUROHSDUDPHWHUVFRQWDLQHU
5HVSRQVLELOLWLHVSRVLWLRQVRUJDQL]DWLRQDOXQLWVXVHUVHWF
FDQEHGHILQHGIRUYDOXHVRUYDOXHUDQJHVRIWKHSDUDPHWHU
SAP AG 1999
n This type of role can help the application to solve problems, such as finding the person responsible
for a material, without separate tables and role function modules.
n An assigment table is evaluated for role resolution, in which the various instances of the role
parameters are assigned to objects of organizational management (jobs, positions, users,
organizational units).
n If you create a role of this type, you must:
Maintain the elements in the role container
Maintain the responsibility for each possible value/value interval of the role parameter(s) in the
assignment table
Assign responsible agents to the values/value intervals
n Advantages of role definition with reponsibilities:
If an organizational object is deleted, the roles of this type are also updated
Where-used lists for organizational objects also find these roles
No ABAP programming is required
SAP AG BC601 9-13

5ROH'HILQLWLRQ:LWK5HVSRQVLELOLWLHV([DPSOH
5HSRQVLEOHIRU
(PSOR\HHQDPHV$.
%HUQ 7KRP
'UHLHU
&ODVV
0U6PLWK 0V-RQHV
3HWHUV $GDPV
3RVLWLRQ 6FKXO] 3RVLWLRQ
$GPLQLVWUDWRU /\QQ $GPLQLVWUDWRU
LQ+5GHSW LQ+5GHSW
5RVW
.HUQHU
'UHLHU
$QGUHZV =\OLQN
5HSRQVLEOHIRU
(PSOR\HHQDPHV/=
SAP AG 1999
n The two administrators are responsible for employee queries in a medium-sized business:
Mr. Smith for employees from A to K,
Ms Jones for employees from L to Z.
SAP AG BC601 9-14

5ROH'HILQLWLRQ:LWK5HVSRQVLELOLWLHV,QWURGXFWLRQ
5ROHFRQWDLQHUGHILQLWLRQEDVLVIRUFRPSDULVRQ
&RQWDLQHUHOHPHQW 'DWDW\SH 1DPH
(OHPHQW &KDU )LUVWOHWWHURIVXUQDPH
$UHDRIUHVSRQVLELOLW\ILUVWOHWWHURIVXUQDPH
9DOXHIURP 9DOXHWR 1DPH
$ . (PSOR\HHVIURP$WR. 0U6PLWK
/ = (PSOR\HHVIURP/WR= 0V-RQHV
:KLFKYDOXH :KLFKDJHQW
SAP AG 1999
n To create a role with responsibilites, you must make the following entries.
n 1. Role container
The first letter of the surname is transferred at runtime, so here you are creating an element that is
character long.
n 2. The areas that can be assigned to agents must be defined.
In this case, the areas are "Employees from A to K" and "Employees from L to Z".
n 3. The area "Employees from A to K" is defined by the interval into which the values must fall at
runtime, in order to belong to this area of responsibility.
Likewise for area "Employees from L to Z".
n 4. Finally, the persons responsible are assigned: Use the "Insert agent assignment" button.
n What happens at runtime:
The role just defined is called, and receives a value for "element".
If the current value is between A and K, Mr Smith is the selected agent. If the current value is
between L and Z, Ms Jones is the selected agent.
SAP AG BC601 9-15

5ROH5HVROXWLRQDQG%LQGLQJ
5ROHSDUDPHWHUVUXQWLPH
Role parameters (definition)
,QSXW
!"
%LQGLQJIURPWDVN

%LQGLQJIURPWDVN
FRQWDLQHURUZRUNIORZ

FRQWDLQHURUZRUNIORZ
FRQWDLQHU
FRQWDLQHU
5ROHUHVROXWLRQ 0DVWHUGDWD
0DVWHUGDWD
2UJDQL]DWLRQDOSODQ
2UJDQL]DWLRQDOSODQ
Function module for &XVWRPL]LQJGDWD
&XVWRPL]LQJGDWD
role resolution Rules
Org. 5HVXOWRI
Org. unit
unit Person
Person UROHUHVROXWLRQ
Job
Job Position
Position
User
User
SAP AG 1999
n SAP provides standard roles.

n To find these roles, see
SAP EASY ACCESS -> Tools -> Business Workflow -> Development -> Definition Tools ->
Standard Roles.
n You can display all the standard roles using the input help (F4).
n A role is identified by a unique name.
A role container is defined for each role. The role parameters establish which information is required
for the role resolution to be executed at runtime.
n If an error occurs during role resolution, the termination flag setting for role resolution will
determine how the workflow continues:
Flag is selected - the workflow will stop and a message is sent to the workflow administrator.
Flag not selected - the workflow will route this work item to ALL possible agents.
SAP AG BC601 9-16

6HOHFW5HFLSLHQWDW5XQWLPH
:RUNIORZ'HILQLWLRQ
Task
displays
list Task
Select Container:
of
recipient Import: Workflow
possible
agents
for next step TaskID 76[\ Container
Task Export:
of
76 6HOHFWHG2EMHFW/LVW $JHQWBOLVW
TS500000xy
on the
screen.
Recipient
Next Responsible agent
chooses
dialog step Expression:
valid
agents
Task $JHQWBOLVW
76[\
as
selected
object list
SAP AG 1999
n Your workflow is very dynamic, and in some steps the responsible agent cannot be determined at the
design stage. Within the workflow, however, each user knows who will execute the next step.
n You can use the task TS30200146 to enable manual selection of the responsible agent for one of the
following steps. This task generates an on-screen list of the possible agents for the subsequent task.
n At runtime, the user who executes the work item for the first step may choose from the list of
possible agents for task TS500000xy.
n All those manually selected responsible agents are transferred to the agent list for the next step.
n The work item of the next step is now available for all users who have a connection to the elements
of the agent list.
n Until Release 4.5, the task for the subsequent step ( TS500000xy ) may not be defined as a general
task.
n Using the wizard "Select agent", you can enter the dispatcher task TS30200146 into your workflow
definition, as well as the subsequent task.
n In Releases before 4.5 this wizard does not exist, and you should use task TS30200141.
With this task you can only select one agent.
SAP AG BC601 9-17

$G+RF:RUNIORZ)XQFWLRQV
l 6WDQGDUGIXQFWLRQVLQWKHZRUNIORZLQER[
$GGDWWDFKPHQW
#
)RUZDUGZRUNLWHP
#
6HQGPDLO
#
&KDQJHZRUNLWHPSULRULW\
#
'HOHWHZRUNLWHPGHDGOLQH
#
l &RQILJXUDEOHRSWLRQV
(LWKHUWKHZRUNIORZLQLWLDWRUDORQHFDQHQWHUQHZDJHQWVRU
#
$QDGGLWLRQDOZRUNIORZVWHSDOORZVVRPHERG\WR
#
GHWHUPLQHWKHQH[WDJHQWDGKRF
SAP AG 1999
n Order of development steps in the Workflow Builder:

Specific Workflow Design: Ad hoc steps can only have possible agents
Menu option: Extras - Ad hoc functions - Enable ad hoc agent assignment
Menu option: Extras - Ad hoc functions - Test ad hoc agent assignment
SAP AG BC601 9-18

'HYHORSLQJ$G+RF:RUNIORZV
)LQDOO\DFWLYDWH )LUVWDVVLJQDOOSRVVLEOHXVHUVWRHDFKGLDORJVWHS
WKHZRUNIORZ
)RUDOODGKRFVWHSVGRQRWDVVLJQDQDJHQWLQWKHDFWLYLW\GHILQLWLRQ
SAP AG 1999
n You can develop a workflow very quickly with the use of task groups.
n After the workflow has been activated, call the function:
Extras - Ad hoc functions - Enable ad hoc agent assignment.
SAP AG BC601 9-19

$G+RF:RUNIORZ&RQWDLQHU(OHPHQWV
The menu option

Extras - Ad hoc functions - Allow ad hoc agent assignment
generated the AGENT_00xy container elements, and correspondingly assigned the
agent definitions in the activities with no agents.
SAP AG 1999
n The menu option "Extras - Ad hoc functions - Enable ad hoc agent assignment"
has also changed the workflow basic type:
See the "Technical Information" tab page in the workflow basic data.
Menu: Workflow Builder - Goto - Basic data
Tab page: Technical information
-> Type of workflow definition: "Ad hoc"
n 1RWH: Ad hoc workflow agent assignment will only work with this ad hoc definition type.
n Finally, reactivate the workflow.
n Next configuration step: "Extras - Ad hoc functions - Test ad hoc agent assignment"
SAP AG BC601 9-20

$G+RF7HVW$JHQW$VVLJQPHQW
6$3HQDEOHV\RXWRVHOHFW
IURPDOOSRVVLEOH
)LQG DJHQWVRIWKHWDVN
DJHQWV

6HOHFWRQH
RUPRUH
DJHQWV

&RS\VHOHFWLRQ
6WDUWWHVW
SAP AG 1999
n The workflow developer tests the ad hoc functions.
SAP AG BC601 9-21

&KDQJH$G+RF$JHQWLQ7HVW
VWRSWLRQ
&KDQJHWKHDJHQWIRUWKHFXUUHQWZRUNLWHPDIWHUWKHVWDUWRIWKHZRUNIORZLQVWDQFH
&KDQJHDJHQW
QGRSWLRQIRUFKDQJLQJWKHDJHQW
)LUVWILQGDQGVHOHFW
7KHQVDYH
SAP AG 1999
n Consequence: The work item is immediately removed from the workflow inbox of the current agent
SAP AG BC601 9-22

$G+RF$JHQWIRU6HYHUDO6WHSV
6HOHFWWKHZRUNLWHPIURPWKHRXWER[RIWKHZRUNIORZLQER[
&KDQJHDJHQW
(QWHUDJHQWIRUDOO
DGKRFVWHSVQRW
\HWFRPSOHWHG
SAP AG 1999
n This is the first of two options for changing the agent at runtime.
SAP AG BC601 9-23

$G+RF:RUNIORZ6WHS
Task TS70007966 from task group TG70000003
1RWHV'RQRWIRUJHWWKHDJHQWDVVLJQPHQWIRUWKLVWDVN
7KHELQGLQJIRUWKLVWDVNUHPDLQVXQGHILQHG
SAP AG 1999
n This is the second option for changing the agent at runtime.

n At runtime, the recipient of this work item can select the agents for all ad hoc steps in the workflow
that have not yet been completed.
n 1RWH:
Changing an ad hoc agent has immediate effect.
If user "A" is processing an ad hoc-compatible work item, and user "B" changes the ad hoc user of
the work item from user "A" to user "C", the work item is immediately taken away from user "A",
even if he is working on it at the time.
User "C" then sees the work item in his or her inbox.
SAP AG BC601 9-24

6HOHFWLRQ3URFHGXUHIRU:RUN,WHP5HFLSLHQW
)LUVW 6HFRQG
)LQGSRVVLEOHDJHQWV
(YDOXDWHWKH6WHS
)RUDJHQHUDOWDVNHYHU\
5ROH5HVROXWLRQ
XVHULVDSRVVLEOHDJHQW
7KLUG )RXUWK
(YDOXDWHWKHWDVN 'HOHWHDOOH[FOXGHG
VWDQGDUGUROHLI DJHQWVIURPWKH
QRVWHSUROHH[LVWV UHFLSLHQWOLVW
,IDXVHULVGHWHUPLQHGE\WKH
UROHDQGLVDOVRDSRVVLEOH
DJHQWWKLVXVHULV
DUHFLSLHQW
,IDXVHULVGHWHUPLQHGE\WKH
UROHDQGLVQRWDSRVVLEOH
DJHQWDOOSRVVLEOHDJHQWV
UHFHLYHWKHZRUNLWHP
SAP AG 1999
n Only recipients who are still on the list after the fourth step can execute a work item.
n Most common error situation:
The dialog task has no possible agents assigned to it (this means that there can never be a recipient).
You have to assign possible agents to all dialog tasks, even to those in workflow templates.
n If no agent assignment is entered in the workflow step, the system checks whether a default role is
saved in the workflow step task.
The default role is on the "default roles" tab page in the task definition.
Tasks/Task Groups
SAP AG BC601 9-25

5RXWLQJ9DULDQWV
9DULDQW
$
3RVVLEOHDJHQWVIRUWKHWDVN3RVLWLRQ
$JHQWVLQWKHZRUNIORZVWHS0LOOHU3RVLWLRQ-RQHV3RVLWLRQ
!0LOOHUUHFHLYHVDZRUNLWHP
9DULDQW
$
3RVVLEOHDJHQWVIRUWKHWDVN*HQHUDOWDVN
$JHQWVLQWKHZRUNIORZVWHS0LOOHU-RQHV
!0LOOHU-RQHVUHFHLYHDZRUNLWHP
9DULDQW
$
3RVVLEOHDJHQWVIRUWKHWDVN3RVLWLRQ
$JHQWVLQWKHZRUNIORZVWHS6PLWK%HUQ3RVLWLRQ
!$OOHPSOR\HHVLQSRVLWLRQUHFHLYHDZRUNLWHP
9DULDQW
$
3RVVLEOHDJHQWVIRUWKHWDVN*HQHUDOWDVN
7KHUROHLQWKHZRUNIORZVWHSGRHVQRWGHWHUPLQHDQDJHQW
7HUPLQDWHLIUROHUHVROXWLRQKDVQRUHVXOWIODJVHW:RUNIORZHUURU
7HUPLQDWHLIUROHUHVROXWLRQKDVQRUHVXOWIODJQRWVHW$OOXVHUVUHFHLYHZRUNLWHP
9DULDQW
$
3RVVLEOHDJHQWVIRUWKHWDVN2UJDQL]DWLRQDOXQLW
1RDJHQWDVVLJQPHQWLVVSHFLILHGLQWKHZRUNIORZVWHS
!$OOHPSOR\HHVLQRUJDQL]DWLRQDOXQLWUHFHLYHDZRUNLWHP
SAP AG 1999
SAP AG BC601 9-26

5RXWLQJ8QLW6XPPDU\
l 5ROHVDUHXVHGIRUILQGLQJWKH
UHVSRQVLEOHDJHQWV
l 'XULQJUXQWLPHWKHUROHUHVROXWLRQ
ZLOOGHWHUPLQHRQHRUPRUH
UHVSRQVLEOHDJHQWVIRUDZRUN
LWHP
l 6RPHUROHVDUHVXSSOLHGE\6$3
l <RXFDQFUHDWH\RXURZQUROHV
l 5ROHVGHILQLWLRQXVLQJ
6$3RUJDQL]DWLRQDOREMHFWV
5HVSRQVLELOLWLHV
SAP AG 1999
SAP AG BC601 9-27

([HUFLVHV
8QLW5RXWLQJ
7RSLF&UHDWLQJ5ROH5HVROXWLRQ8VLQJ5HVSRQVLELOLWLHV

Define a role resolution using responsibility
This procedure will enable you to create a role resolution based on your
own requirements, without writing ABAP code.
By assigning responsibilities to specific field values, you can use a role to
map those responsibilities to your organizational chart.
In this scenario we assume that particular people are responsible for
material groups. If a material is changed, the role will find who is
responsible for that material group and notify them of the change.
1-1 Create a standard role ZMat_group## , and specify the role type as Responsibility. The
role should terminate if no agent can be found.
1-2 Create container entries with ABAP Dictionary field proposals for the table name MARA,
field MATKL. Use the default element name Material Group .
1-3 Define a responsibility and assign a name for this responsibility, such as Matl_grp_001 .
The material group should be 001.
1-4 Define the organizational unit ZWF_ORG_## as the agent for the responsibility.
1-5 Simulate the role for test purposes.
1-6 Update your workflow definition with this new role:

1-6-1 Call the Workflow Builder with your workflow template for the material master
zwf_test1_##.
SAP AG BC601 9-28

1-6-2 Select the step Display material master , and change the responsible agent in
Role assignment .'
1-6-3 Enter your role number, for example 99100131.
1-6-4 Next, accept the current binding.

Finally, change the binding to integrate the material group for your object (the
material group of your object type Y##MARA) into the binding.
1-6-5 Activate your workflow.
1-6-6 Test your workflow. To do this, log on as user WF-BC-MGR' (password

Welcome), and start your workflow in the test environment.
In the first step, the change documents are displayed to the workflow initiator,
WF_BC_MGR.
The work item of the second step is routed to BC601-MGR## and BC601-##.
Check the Business Workplace inbox for both users.
&DXWLRQ5HPHPEHUWRVHWWKHPDWHULDOJURXSLQ\RXUWHVWPDWHULDO
DSSURSULDWHO\IRUWHVWLQJWKHUROHUHVROXWLRQ
7HVWWKHVXFFHVVIXOFDVHPDWHULDOJURXSDQGWKHHUURUFDVHPDWHULDO

JURXSQRW
SAP AG BC601 9-29

([HUFLVHV
8QLW5RXWLQJ$GGLWLRQDOH[HUFLVH
7RSLF&KRRVH6HOHFWHG8VHUDW5XQWLPH

Create a task with an agent list
Define a workflow to route a work item to an agent selected from a list
during runtime
Your workflow is very dynamic, and in some steps the recipient cannot
be determined at the design stage. Within the workflow, however, each
user knows who will execute the next step.
1-1 Create a standard task that has a specific agent list.

Assume we are working with a task that displays the changes to a material (Task:
z##_choosag, Description and work item text: Dynamic agent selection, Method:
Display_Changes, Object type: Y##MARA).
There are three users on the list of possible agents: BC601-##, BC601-MGR##, and
WF-BC_MGR.
Remember to refresh the index in the agent assignment.
1-2 Create a workflow "WS##_SEL_AGENT".

Go to the Workflow Builder, and use a Wizard to include the Choose agent
function at runtime.
In the Enter task screen, enter the number of the task z##_chooseag.
Enter "Agent chosen at runtime/Display change documents" as the title of the
selection window.
Set the flag Several agents can be selected .
Execute the first step. This will provide a list of possible agents for the following
step. Select one or more agents, and the work item will be routed to them.
SAP AG BC601 9-30

([HUFLVHV
7RSLF$G+RF:RUNIORZ)XQFWLRQV
At the conclusion of this exercise, you will be able to

include ad hoc agent assignment
in your workflow template
Until now you have created and tested a workflow with fixed role
assignment. Now you want to make sending the work item at runtime
more flexible. The SAP Workflow development environment provides the
ad hoc functions for doing this.
1-1 Make a copy of your material display workflow.

Name your new workflow Z_Ad_Hoc_## .
1-2 Start the Workflow Builder and open your

Z_Ad_Hoc_## workflow in change mode.
Process all the dialog steps in your workflow, and delete the agent assignment for
each one.
1-3 Also change the possible agents of the corresponding single-step tasks.
Deactivate the assignment general tasks ,
and enter four user IDs as possible agents. Use your
own IDs and those of your neighboring group.
1-4 Now call the ad hoc function in the Workflow Builder that prepares the dialog steps
in the workflow for ad hoc processing.
What has changed in your workflow after doing this?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
1-5 Activate your workflow.
1-6 Insert a new step for the single-step task TS70007966

at the beginning of your workflow.
Define the workflow initiator as agent.
The binding for this task remains undefined.
SAP AG BC601 9-31

1-8 Change the possible agents for your dialog tasks for material display. These tasks
should now be redefined as general tasks .
1-9 Test your workflow again after you have refreshed the organizational environment.
Has the runtime procedure changed?
_____________________________________________________________
_____________________________________________________________
SAP AG BC601 9-32

6ROXWLRQV
8QLW5RXWLQJ
7RSLF5ROH5HVROXWLRQ8VLQJ5HVSRQVLELOLWLHV
1-1 Create a standard role ZMat_group## , and specify the role type as Responsibility.
0HQXSDWK7RROV!%XVLQHVV:RUNIORZ!'HYHORSPHQW!'HILQLWLRQ7RROV!
6WDQGDUG5ROHV!&UHDWH,FRQ&UHDWH
%DVLFGDWD
$EEUHYLDWLRQ=0DWBJURXS
1DPH0DWHULDO*URXS
5ROHGHILQLWLRQ
5ROH7\SH5HVSRQVLELOLWLHV
6HWWKHIODJ7HUPLQDWHLIUROHUHVROXWLRQKDVQRUHVXOW
1-2 You want to query the material group in the role.

To do this, you need to create an entry for the element Material group in the
container.
7DESDJH&RQWDLQHU
,FRQ,QVHUWFRQWDLQHUHOHPHQW
$QVZHUWKHTXHVWLRQ&UHDWHZLWK$%$3'LFWLRQDU\ILHOGSURSRVDOV"ZLWK<HV
(QWHU0$5$DVWKHXQGHUO\LQJWDEOH
6HOHFW0$7./%XWWRQ&RQWLQXH%XWWRQ&UHDWH
%DFNLQWKHVFUHHQ6WDQGDUG5ROH$GG
VDYHWKHGDWDDQGVDYHWKHUROHLQWKHGHYHORSPHQWFODVV]
1-3 In the next step, you define the variants that should be in the responsibility,
meaning which agents have which different material group values
&OLFNRQWKH5HVSRQVLELOLWLHVWDESDJH
,FRQ&UHDWHUHVSRQVLELOLW\
2EMHFWDEEUHYLDWLRQ0DWOBJUSB
1DPH0DWHULDOJURXS
(QWHU
6FUHHQ5HVSRQVLELOLW\&KDQJHIRU6WDQGDUGUROH
1DPH0DWHULDOJURXS
2I7R
6DYHWKHUHVSRQVLELOLW\
SAP AG BC601 9-33

1-4 Return to the screen "Standard Role: Change", and enter your organizational unit
ZWF_ORG_## as the agent.
3RVLWLRQWKHFXUVRURQ0DWHULDOJURXS
,FRQ,QVHUWDJHQWDVVLJQPHQW
'RXEOHFOLFN2UJDQL]DWLRQDOXQLW
6HDUFKWHUP<RXURUJDQL]DWLRQDOXQLW]ZIBRUJB
&KRRVH&UHDWH
1-5 You can simulate the role for test purposes.
Choose the icon "Simulate role resolution" in the upper part of the screen, or use
Shift+F8
Enter 001 as the input value for the material group in the Role container for
runtime , and choose Continue
Your organizational unit should be displayed as the result of the role resolution
1-6 Update your workflow
1-6-1 Open the Workflow Builder and display your workflow for processing the
material master.
If it is not automatically displayed, choose the menu options:
Workflow Other workflow/version, and enter the number of your
workflow template from zwf_test1_##, or find it using the input help.
Go to the change mode
Double-click the step Display material master
1-6-2 In the screen "Workflow Builder: Change step: Activity": Make sure
that you are on the Control tab page.
Select Role from the pulldown menu in the Agents frame.
1-6-3 Enter your role number in the field next to Role , e.g. 99100131.
1-6-4 The input parameter for the role must be the material group of the object.
In the Binding Responsibility for.. window, use the input help (F4) and
select the Material group attribute from your object type.
1-6-5 Leave the window and re-activate your workflow by selecting the Generate
and activate runtime version button.
SAP AG BC601 9-34

1-6-6 Log on as user WF-BC-MGR (password Welcome), and start your
workflow in the test environment
Caution: Remember to adjust the material group in your material master

according to the role resolution.
SAP EASY ACCESS -> Tools -> Business Workflow -> Development ->
Runtime Tools -> Start Workflow (Test Environment)
Afterwards, check the inboxes for BC601-MGR## and BC601-##.

Both inboxes contain a reference to the same work item for displaying
change documents
Caution: Set the material group in the material master to the correct test
value.
SAP AG BC601 9-35

6ROXWLRQV
7RSLF&KRRVH6HOHFWHG8VHUDW5XQWLPH
1-1 Create a single step task that has a specific agent list.
Assume we are working with a task that displays the changes to a material (Task:
z##_choosag, description and work item text: Dynamic agent selection, method:
Display_Changes, Object type: Y##MARA).
There are three users on the list of possible agents: BC601-##, BC601-MGR##, and
WF-BC_MGR.
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW'HILQLWLRQ7RROV7DVNV7DVN
*URXSV
'RXEOHFOLFN&UHDWH
)LHOG1DPH ,QSXW'DWD
&KRRVH7DVN&UHDWHRUFKRRVHWKH&UHDWHEXWWRQ
)LHOG1DPH ,QSXW'DWD
Abbr: z##_chooseag
Name Dynamic agent selection
Object type Y##mara
Method Display_Changes
6DYHWKHVWDQGDUGWDVNV
&KRRVH$GGLWLRQDOGDWD$JHQWDVVLJQPHQW0DLQWDLQ
3RVLWLRQWKHFXUVRURQWKHOLQHZLWK\RXUWDVNQDPHDQGFKRRVH$JHQW
DVVLJQPHQW!&UHDWH
SAP AG BC601 9-36

,QWKH&KRRVHDJHQWW\SHGLDORJER[VHOHFW8VHUWKHQFKRRVHWKH&RQWLQXH
(QWHUEXWWRQ
$VVLJQWKHDSSURSULDWHXVHUVLQWKH&KRRVH8VHUGLDORJER[
5HSHDWWKHSURFHVVXQWLODOOWKUHHXVHUVKDYHEHHQDVVLJQHG
7RJHQHUDWHWKHQHZLQGH[SRVLWLRQWKHFXUVRURQWKHWDVNQDPHDQGFKRRVHWKH
5HIUHVKLQGH[LFRQ
:KHQDOOXVHUVKDYHEHHQDVVLJQHGDQGWKHLQGH[KDVEHHQUHIUHVKHGUHWXUQWR
WKH6WDQGDUG7DVN&UHDWHVFUHHQ
&KRRVHWKH6DYHEXWWRQ
&KRRVHWKH%DFNEXWWRQWRUHWXUQWRWKH7DVN0DLQWDLQVFUHHQ
1-2 Create the workflow WS##_SEL_AGENT. Use the Wizard to integrate the
Choose agent function at runtime.
&KRRVH
'HILQLWLRQ7RROV!7DVNV7DVN*URXSV!&UHDWH
)LHOG1DPH ,QSXW'DWD
Task type Workflow template
&KRRVH7DVN&UHDWHRUFKRRVHWKH&UHDWHEXWWRQ
)LHOG1DPH ,QSXW'DWD
Abbr: WS##_Sel_Ag
Name Dynamic agent selection
6WDUWWKH:RUNIORZ%XLOGHU
6HOHFWWKHXQGHILQHGVWHSDQGFKRRVH:L]DUGV!,QFOXGH&KRRVHDJHQW
SAP AG BC601 9-37

5HDGWKHGHVFULSWLRQRQWKH6WDUWVFUHHQ
&KRRVHWKHEXWWRQ&RQWLQXH
)ROORZWKHLQVWUXFWLRQVLQWKHZL]DUG
,QWKH6SHFLI\WDVNVFUHHQHQWHU76[[[[[[[[RIWDVN]BFKRRVHDJ
(QWHU$JHQWFKRVHQDWUXQWLPH'LVSOD\FKDQJHGRFXPHQWVDVWKHWLWOHRIWKH
VHOHFWLRQGLDORJER[
6HWWKHIODJ6HYHUDODJHQWVFDQEHVHOHFWHG
&KRRVHWKHEXWWRQ&RPSOHWH

Execute the first step. This will provide a list of possible agents for the following
step. Select one or more agents, and a work item will be routed to them.
,QWKHVFUHHQ:RUNIORZ%XLOGHU&UHDWHFKRRVHWKH*HQHUDWHDQGDFWLYDWH
UXQWLPHYHUVLRQLFRQIROORZHGE\WKH7HVWLFRQ
,QWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQFKRRVHWKH5HIUHVK

RUJDQL]DWLRQDOHQYLURQPHQWEXWWRQ
&KRRVHWKH,QSXWGDWDEXWWRQ
,QWKH,QLWLDOL]H&RQWDLQHUGLDORJER[XVHWKHLQSXWKHOSDQGHQWHUWKHPDWHULDOLQ
WKH0DWHULDOILHOG
8VHIRUH[DPSOH7%''ZKHUHLV\RXUJURXSQXPEHU
SAP AG BC601 9-38

6ROXWLRQV
7RSLF$G+RF:RUNIORZ)XQFWLRQV
1-10 Make a copy of your material display workflow

Name your new workflow Z_Ad_Hoc_## .
'HILQLWLRQ7RROV!7DVNV7DVN*URXSV!&RS\
6HOHFW\RXUZRUNIORZWHPSODWH
0HQX7DVN&RS\
1DPH\RXUQHZZRUNIORZ=B$GB+RFB
6DYH\RXUZRUNIORZ
1-11 Delete the agent assignment for each dialog step in the copied workflow.
6$3($6<$&&(667RROV%XVLQHVV:RUNIORZ'HYHORSPHQW'HILQLWLRQ
7RROV:RUNIORZ%XLOGHU
8VHWKHPHQXRSWLRQ:RUNIORZ2WKHUZRUNIORZYHUVLRQ
WRRSHQ\RXU=B$GB+RFB:RUNIORZ
7KHQJRWRWKHFKDQJHPRGH
'RXEOHFOLFNHDFKGLDORJVWHS
,QWKH$JHQWVVHFWLRQGHOHWHWKHFRQWHQWVRIHDFKILHOGWRWKHULJKWRI
([SUHVVLRQ8VHU
1-12 Change the possible agents of the corresponding single-step tasks.

Deactivate the assignment general tasks ,
and enter four user IDs as possible agents.
'RXEOHFOLFNHDFKGLDORJVWHSLQWKH:RUNIORZ%XLOGHU
<RXFDQJRGLUHFWO\WRWKHDJHQWDVVLJQPHQWRIWKHWDVN
,QWKH7DVNSURSHUWLHVER[FKRRVHWKHLFRQ$JHQWDVVLJQPHQW
6HOHFWWKHWDVNWLWOH
8VLQJWKH$WWULEXWHVEXWWRQGHOHWHWKH*HQHUDO7DVNVIODJDQGXVHWKHPHQX
RSWLRQ$JHQWDVVLJQPHQW&UHDWHWRDVVLJQIRXUDJHQWV
SAP AG BC601 9-39

1-13 Now call the ad hoc function in the Workflow Builder that prepares the dialog steps
in the workflow for ad hoc processing.
What has changed in your workflow after doing this?
,QWKH:RUNIORZ%XLOGHUFKRRVHWKHPHQXRSWLRQ([WUDV$GKRFIXQFWLRQV
(QDEOHDGKRFDJHQWDVVLJQPHQW
&KDQJH(DFKVWHSWKDWKDGQRDJHQWQRZKDVDQHQWU\XQGHU$JHQWV7KHVH
DUHWKHYDULDEOHV $*(17B$JHQWV DQG $*(17B$JHQWV
7KHVHYDULDEOHVKDYHEHHQFUHDWHGE\WKHV\VWHPLQWKHZRUNIORZFRQWDLQHU
1-14 Activate your workflow
,QWKH:RUNIORZ%XLOGHUEDVLFVFUHHQFKRRVHWKH*HQHUDWHDQGDFWLYDWHUXQWLPH
YHUVLRQLFRQ
1-15 Insert a new step for the single-step task TS70007966

at the beginning of your workflow.
Define the workflow initiator as agent.
The binding for this task remains undefined.
,QWKH:RUNIORZ%XLOGHUEDVLFVFUHHQVHOHFWWKHHYHQW:RUNIORZVWDUWHG
&KRRVHWKH&UHDWHLFRQ
'RXEOHFOLFNWRFKRRVH$FWLYLW\DQGHQWHUWKHWDVN76LQWKHZRUNIORZ
VWHSGLVSOD\HG
,QWKH$JHQWVVHFWLRQVHOHFW:RUNIORZLQLWLDWRU
,QWKH:RUNIORZ%XLOGHUEDVLFVFUHHQFKRRVHWKH*HQHUDWHDQGDFWLYDWHUXQWLPH
YHUVLRQLFRQ
&KRRVHWKH7HVWLFRQ
7KHZRUNIORZLQLWLDWRUFDQQRZVHOHFWWKHGHVLUHGDJHQWVIRUWKHWDVNVZLWKDGKRF
DJHQWDVVLJQPHQWDWWKHVWDUW
1-17 Change the possible agents for your dialog tasks for material display. These tasks
should now be redefined as general tasks .
'RXEOHFOLFNHDFKGLDORJVWHSLQWKH:RUNIORZ%XLOGHU
<RXFDQJRGLUHFWO\WRWKHDJHQWDVVLJQPHQWRIWKHWDVN
,QWKH7DVNSURSHUWLHVER[FKRRVHWKHLFRQ$JHQWDVVLJQPHQW
6HOHFWWKHWDVNWLWOH
&KRRVHWKH$WWULEXWHVEXWWRQDQGVHWWKH*HQHUDOWDVNIODJ
1-18 Test your workflow again after you have refreshed the organizational environment.
Has the runtime procedure changed?
7KHZRUNIORZLQLWLDWRUFDQQRZHQWHURQHRUPRUHDJHQWV
SAP AG BC601 9-40

'HDGOLQHV
&RQWHQWV
l 'HDGOLQHPRQLWRULQJZLWK
l 6LPSOHGHDGOLQHV
l 0RGHOHGGHDGOLQHV
SAP AG 1999
SAP AG BC601 10-1

'HDGOLQHV8QLW2EMHFWLYHV
l 6HWXSDQGWHVWDVLPSOHGHDGOLQH
l $GGDGHDGOLQHWRDZRUNIORZVWHS
l ,QWHJUDWHDPRGHOHGGHDGOLQHLQWRDZRUNIORZ
GHILQLWLRQ
SAP AG 1999
SAP AG
SAP AG BC601 10-2

SAP AG 1999
SAP AG BC601 10-3

'HDGOLQHV%XVLQHVV6FHQDULR
l 7KHWRWDOPDWHULDOEXVLQHVVSURFHVVFDQQRW
H[FHHGGD\V
l 7KHGLVSOD\VWHSLVPRVWOLNHO\WREHODWH
l 2SWLRQVIRUODWHDFWLYLWLHVRQWKHFULWLFDOSDWKDUH
VLPSOHGHDGOLQHVRUPRGHOHGGHDGOLQHV
SAP AG 1999
SAP AG
SAP AG BC601 10-4

6LPSOH'HDGOLQHV
l 'HDGOLQHVDYDLODEOH l (DFKGHDGOLQHKDV
5HTXHVWHGVWDUW $QLQGLYLGXDOUHIHUHQFH
SRLQW
5HTXHVWHGHQG
$QRWLILFDWLRQDJHQWIRU
/DWHVWHQG
GHDGOLQHPRQLWRULQJ
/DWHVWVWDUW H[FHSWLRQ
5HTXHVWHGVWDUW
$QRWLILFDWLRQWH[W
H[FHSWLRQ
5HTXHVWHGVWDUW
SAP AG 1999
n Requested start
Earliest possible time for processing start; Introduced by the system:
The work item is not visible in the Business Workplace until this time.
n Requested end
Latest requested time for completion of processing of a workflow
n Latest start
Latest deadline for workflow processing start
n Latest end
Latest deadline for completion of processing of a workflow
n The deadlines are specified with reference to the start of the workflow or work item or an individual
expression.
n The deadline is defined in the workflow step behind the relevant tab page.
The recipient of the notification is also specified there.
n The definition of the text that is sent is part of the task definition.
It is behind the "Description" tab page.
n The missed deadline is evaluated by the job SWWDHEX.
SAP AG BC601 10-5

([DPSOHRID6LPSOH'HDGOLQH(VFDODWLRQ
:ULWHFKDQJHGRFXPHQW

0DWHULDO 0\BSDUW
l 6HQGUHPLQGHUPHVVDJH
2OGPDWHULDO 2ULJLQDOBSDUW (YHQW
1HZBSDUW
:RUNIORZVWHS
'LVSOD\PDWHULDO
2UJDQL]DWLRQDOSODQ 5HFLSLHQWDQG
'HVLJQGHSDUWPHQW GHDGOLQHGHILQHG
'HVLJQHUSRVLWLRQ
5HFLSLHQW
+ROGHU0DU\
0DWHULDO0DQDJHUSRVLWLRQ
+ROGHU)UDQN 'LVSOD\PDWHULDO
5HFLSLHQWZKHQ
GHDGOLQHPLVVHG 7H[WIRUPLVVHG
GHDGOLQHGHILQHG
7LPHRIIVHW
IRUODWHVW
HQG
SAP AG 1999
n Deadline monitoring can only be defined in the context of a workflow step.

n 'HILQLWLRQ
Integration of task in a workflow or selection of a workflow step.
The definition occurs in the workflow step on the tab page for the requested step.
The time, which can expire, is determined.
The reference point for the calculation is determined.
It is established that it is a simple deadline.
The recipient of the missed deadline work item is determined.
n 5XQWLPHEHKDYLRUIn the case of a simple deadline+
The work item remains in the Business Workplace after deadline reached.
The work item can be executed at any time, even after the deadline has been reached. The status
of the work item does not change.
A missed deadline work item is sent to the specified recipient. The work item text is defined in
the underlying task.
The recipient finds the work item in the Business Workplace by choosing Inbox -> Deadline
messages.
n 3UHUHTXLVLWHV
The job SWWDHEX has to be scheduled.
This job can be executed periodically, for example once every hour. It can also be scheduled so
that it always starts when a work item is pending for deadline monitoring.
You can read the help text for this job and schedule the job with transaction SWU3.
SAP AG BC601 10-6

0RGHOHG'HDGOLQHV
l 'HDGOLQHVDYDLODEOH l (DFKGHDGOLQHKDV
5HTXHVWHGVWDUW $QLQGLYLGXDOUHIHUHQFH
SRLQW
5HTXHVWHGHQG
$FXVWRPHUVSHFLILF
/DWHVWHQG
DFWLRQZKLFKLVH[HFXWHG
/DWHVWVWDUW ZKHQWKHGHDGOLQHLVUHDFKHG
SAP AG 1999
n The deadline is defined in the workflow step behind the relevant tab page.
n If a modeled deadline in chosen, the system automatically generates an extra branch in the workflow
definition.
n Modeled deadlines can be transferred into the workflow step manually or using a wizard.
n Modeling using a Workflow Wizard:
The monitored work item is set to obsolete when the deadline is reached.
The workflow goes to the branch that is behind the outcome Obsolete.
The customer-specific action was defined in this outcome.
The original work item can no longer be executed with it.
n Modeling manually on the tab page:
The workflow goes to the branch Deadline reached.
The customer-specific action was defined in this outcome.
The original work item is still executable.
Using the workflow step Process control, the status of the monitored work item can be
changed.
n The missed deadline is evaluated by the job SWWDHEX.
SAP AG BC601 10-7

0RGHOLQJ'HDGOLQH0RQLWRULQJ8VLQJD:L]DUG
User
decision
Result 1 Result 2 Obsolete Latest end reached

Set Deadline
reached indicator
$Q\DOWHUQDWLYHVWHS
LVLQFOXGHG
Flag set
Work item set

to "obsolete"
Work item set

to "obsolete"
SAP AG 1999
n Modeled deadlines
If a set deadline is missed, modeled subsequent actions are executed, rendering further
processing of the monitored work item superfluous.
When defining the monitored step, the exception processing "obsolete" must be selected and any
appropriate subsequent steps implemented. The data on deadline setting must be maintained. An
event description must be entered for the deadline to be monitored.
n The wizard Model deadline monitoring helps you to integrate the necessary steps.
This wizard can be found by choosing the "Wizards" menu option in the Workflow Builder.
n 5HOHDVH:
You insert a task in the definition by selecting an event and choosing Wizards -> Model deadline
monitoring in the Workflow Builder. The wizard queries the task and the data on deadline
monitoring.
n $VRI5HOHDVH:
You model deadline monitoring for an existing task by selecting an existing task in the Workflow
Builder and choosing Wizards -> Model deadline monitoring.
The wizard queries the data on deadline monitoring.
If you have not selected a task when you call the wizard, the wizard proceeds as in Release 4.5 and
earlier.
SAP AG BC601 10-8

([DPSOHRID0RGHOHG'HDGOLQH(VFDODWLRQ
l 7HUPLQDWHROGZRUNLWHPDQGVWDUWDQHZZRUNLWHP
0DWHULDO 0\BSDUW &KDQJHGRFXPHQWV
2OGPDWHULDO 2ULJLQDOBSDUW (YHQW

1HZBSDUW
:RUNIORZ
2UJDQL]DWLRQDOSODQ
'HVLJQGHSDUWPHQW
'HVLJQHUSRVLWLRQ 5HFLSLHQW
+ROGHU0DU\
0DWHULDO0DQDJHUSRVLWLRQ 6WHS
+ROGHU)UDQN 'LVSOD\PDWHULDO
7RRODWH
5HFLSLHQW $Q\
HVFDODWLRQVWHS
SAP AG 1999
n Modeled deadline monitoring without Wizard:

Integrate your task in a workflow.
Define deadline monitoring for the step on the required tab page.
Set the indicator for modeled deadline monitoring.
Switch to the "Outcomes" tab page and activate the event "Processing obsolete".
Integrate the processing branch that is to be included after obsolete.
If you want the work item to be terminated if the deadline is missed, you have to terminate it
yourself.
n Insert the workflow step "Process control" into your workflow definition.
SAP AG BC601 10-9

'HDGOLQHV8QLW6XPPDU\
l 'HDGOLQHIXQFWLRQDOLW\
LVLQWHJUDWHGLQ
6$3%XVLQHVV:RUNIORZ
l 7KHUHDUHWZRRSWLRQV
n VLPSOHGHDGOLQHV
n PRGHOHGGHDGOLQHV
SAP AG 1999
SAP AG BC601 10-10

([HUFLVHV
8QLW'HDGOLQHV
7RSLF0RGHOHG'HDGOLQHV

Use a wizard to create a modeled deadline
To demonstrate modeled deadlines, we will modify our workflow

definition created in previous exercises. After the step to display the
material changes, a new step to display the material has been inserted.
This step is to be monitored to ensure that the material change is
approved in good time. Otherwise, the work item is deleted from the
agents Business Workplace.
1-1 Call the workflow definition you created on the first day and start the Workflow
Builder.
1-2 The task "Display material" after the result "Changes displayed" is to be subject to
deadline monitoring. If the deadline has been reached, the work item is to be set to
obsolete and a new branch in the processing is included.
This "modeled deadline monitoring" is created using a wizard.
1-2-1 Add a deadline to control the latest end allowed for the completion of the
work item.
1-2-2 Give the agent 5 minutes once the work item has entered their Business
Workplace to complete processing.
1-3 If the deadline is missed, an alternative processing step is needed. For example, you
could use the user decision "My first test" from the exercise in unit 2. Activate the
workflow and exit the screen.
1-4 Start the workflow using the explicit start function. Make sure that you use the user
WF-BC-MGR.
1-5 A list of material changes is displayed. Process this work item by exiting the list
and then choosing the button for "Complete processing of step". Then switch to the
workflow inbox of your manager and employee. Do NOT, however, process the
"Display material" work item. Instead, switch back to the initiator s session and
choose "Workflow log" to monitor the workflow. Wait a couple of minutes, refresh
the workflow log and see what happens.
SAP AG BC601 10-11

([HUFLVHV
8QLW'HDGOLQHVDGGLWLRQDOH[HUFLVH
7RSLF0DNLQJ&XVWRPHU6SHFLILF&KDQJHVWRD:RUNIORZ
7HPSODWH6LPSOH'HDGOLQH0RQLWRULQJ
Copy a workflow template
Set up and test a simple deadline
Create and test an express work item
List options for recipient routing
Forward a message to a distribution list
The next user test was successfully completed.

Since the end users have a better understanding of the SAP Workflow
System, many additional requests are now made. The demand for a more
optimized process is particularly high for the procedure "Notification of
absence".
You agree to look into escalation procedures in order to achieve a
guaranteed maximum processing time.
Another important issue from the management s perspective is improved
routing to avoid information overload.
1-1 Copy the workflow template for "Notification of absence" (WS30000015) into a
separate workflow template: Z_##_process.
1-1-1 Note the new workflow task number:
___________________________________________________________
1-2 A deadline is to be set for the manager s approval. We will give the manager an
aggressive deadline of 5 minutes to check the notification of absence. The
employee is notified if the deadline is missed. Modify your workflow now to add
this deadline and the recipient for missed deadline.
1-2-1 Call your workflow in change mode in the Workflow Builder.
1-2-2 Choose the approval step in order to add a deadline.
1-2-3 Specify a deadline of 5 minutes and activate monitoring of requested end.
SAP AG BC601 10-12

1-2-4 Enter the recipient for missed deadline. In this exercise, we will use the
expression ,QLWLDWRUfrom the container as the recipient.
Note: Each workflow automatically contains the user ID that started

the workflow, in the "Initiator" field. In the case of the notification
of absence, this is the user ID of the employee who creates the form.
In this exercise, we will use the "Initiator" field to send the
notification of a missed deadline back to the employee who created
the form.
1-2-5 Enter the notification text for the task "Approve notification of absence".
The recipient receives this notification text if the deadline is missed.
1-2-6 Activate the workflow to check and save your changes.
1-3 Test the workflow with the new simple deadline. Each group is to start their new
workflow manually using the HPSOR\HH user ID %&. You can resubmit one
of the forms you created in the Business Workplace exercise for approval.
1-3-1 Start your new workflow explicitly.
1-3-2 Check the Business Workplace of user ID%&0*5to see if the

work item to be approved has entered the worklist. If it has, wait until the
deadline has passed.
1-3-3 Then check the HPSOR\HH

V Business Workplace to see if the notification
for missed deadline has appeared.
1-3-4 Execute this work item to check the notification text that was added and
remove the deadline notification from your worklist.
1-4 Managers often forget to check their workflow inboxes for notifications of absence
and, as a result, miss the deadline. You decide to define the approval step as an
express work item. Change your workflow accordingly.
1-4-2 Change the approval step.
1-4-3 Change the priority of the step to make it an express work item.
SAP AG BC601 10-13

1-5 Test your workflow with the express work item. Each group is to start their
workflow manually using the employee user ID. Use a different absence form from
the Business Workplace exercise
1-5-1 Start the workflow explicitly.
1-5-2 How is the PDQDJHU notified about this work item?
___________________________________________________________
___________________________________________________________
___________________________________________________________
SAP AG BC601 10-14

6ROXWLRQV
8QLW'HDGOLQHV
7RSLF0RGHOHG'HDGOLQHV
1-1 Change the workflow definition you created on the first day and go to the
Workflow Builder.
'RXEOHFOLFN:RUNIORZ%XLOGHU
,I\RXUZRUNIORZLVQRWGLVSOD\HGFKRRVHWKH2WKHUZRUNIORZYHUVLRQLFRQ
(QWHU:6DQG\RXUZRUNIORZWDVNQXPEHU
1-2 The task "Display material" after the event "Changes displayed" is to be subject to
deadline monitoring. Use the wizard to create modeled deadline monitoring.
3RVLWLRQ\RXUFXUVRURQWKHWDVN'LVSOD\PDWHULDOPDVWHUDQGFOLFNRQFHWR
VHOHFWWKHWDVN
&KRRVH:L]DUGV0RGHOGHDGOLQHPRQLWRULQJ
&KRRVHWKH&RQWLQXHEXWWRQWRVWDUWWKHZL]DUG
1-2-1 Add a deadline to control the latest end allowed for the completion of the
work item.
6HOHFWWKH/DWHVWHQGUDGLREXWWRQDVWKHGHDGOLQHW\SHWREHPRQLWRUHG
&KRRVHWKH&RQWLQXHEXWWRQ
1-2-2 Give the agent 5 minutes once the work item has entered their Business
Workplace to complete processing.
(QWHULQWKH7LPHLQWILHOGDQGVHOHFW0LQXWHVQH[WWRWKLVILHOG
6HOHFWWKH:RUNLWHPFUHDWLRQUDGLREXWWRQWRDFWLYDWHPRQLWRULQJIURP
WKHWLPHWKHZRUNLWHPLVFUHDWHG
&KRRVHWKH&RPSOHWHEXWWRQVRWKHZL]DUGFDQFRPSOHWHWKHSURFHVV
SAP AG BC601 10-15

1-3 If the deadline is missed, an alternative branch is needed.
You could, for example, use the user decision "My first test" from the exercise in
the Workflow Definition unit. Activate the workflow and exit the screen.
0DNHVXUHWKDW\RXDUHRQWKH:RUNIORZ%XLOGHU&KDQJH
]ZIBWHVW
VFUHHQ
6HOHFWWKHXVHUGHFLVLRQ0\ILUVWWHVWDQGFKRRVH
(GLW%ORFN&XW
6HOHFWWKHHYHQW2EVROHWHDQGFKRRVH
(GLW%ORFN3DVWH
,QWKH:RUNIORZ%XLOGHUFKRRVHWKH*HQHUDWHDQGDFWLYDWHUXQWLPHYHUVLRQ
EXWWRQ
1-4 Start the workflow using the explicit start function. Start the workflow as WF-BC-
MGR.
6$3($6<$&&(66!7RROV!%XVLQHVV:RUNIORZ!'HYHORSPHQW!5XQWLPH
7RROV!6WDUW:RUNIORZ7HVW(QYLURQPHQW
(QWHU:6;;;;;;;;ZKHUH;;;;;;;;LVWKHQXPEHURI\RXUZRUNIORZ
1-5 A list of material changes is displayed. Process this work item by exiting the list
and then choosing the button for "Complete processing of step". Then switch to the
workflow inbox of your manager and employee. Do NOT, however, process the
"Display material" work item. Instead, switch back to the workflow initiator s
session and choose "Workflow log" to monitor the workflow. Wait a couple of
minutes, refresh the workflow log and see what happens.
2QWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQFKRRVHWKH:RUNIORZORJ

EXWWRQWRPRQLWRUWKHSURFHVVLQJRIWKHZRUNIORZLQWKH9LHZ:RUNIORZ
&KURQLFOH
$IWHURUPLQXWHVFKRRVHWKH5HIUHVKEXWWRQDQGFKHFNLQWKHZRUNIORZORJ
WKDWWKHPLVVHGODWHVWHQGKDVDFWXDOO\EHHQUHDFKHG
,IVRWKHHQWU\'($'/,1(VKRXOGDSSHDULQWKH6WDWXVFROXPQDQG/DWHVW
HQGUHDFKHGLQWKH5HVXOWFROXPQ
SAP AG BC601 10-16

6ROXWLRQV
8QLW'HDGOLQHVDGGLWLRQDOH[HUFLVH
7RSLF0DNLQJ&XVWRPHU6SHFLILF&KDQJHVWRD:RUNIORZ
7HPSODWH6LPSOH'HDGOLQH0RQLWRULQJ
1-1 Copy the workflow template for "Notification of absence" (WS30000015) into your
own workflow template.
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW'HILQLWLRQ7RROV7DVN7DVN
*URXSV
'RXEOHFOLFN&RS\
2QWKH7DVN&RS\VFUHHQHQWHUWKHIROORZLQJLQIRUPDWLRQ
)LHOG1DPH ,QSXW'DWD
Task type WS (workflow template)
Task 30000015
&KRRVHWKH&RS\WDVNEXWWRQ
,QWKH&RS\7DVNGLDORJER[:RUNIORZWHPSODWHVKRXOGEHGLVSOD\HGLQWKH
7DUJHWWDVNW\SHILHOG$)BSURFHVVVKRXOGEHGLVSOD\HGLQWKH
$EEUHYLDWLRQILHOGDQG3URFHVVQRWLILFDWLRQRIDEVHQFHLQWKH1DPHILHOG
Note: Start the abbreviation and name with Z and your group number
so that you can identify your workflow.
2YHUZULWHWKH$EEUHYLDWLRQDQG1DPHDVIROORZV
)LHOG1DPH ,QSXW'DWD
Abbreviation Z##_process
Name Group## Process notification of absence
&KRRVHWKH&RS\WDVN(QWHUEXWWRQDWWKHERWWRPRIWKH&RS\7DVNGLDORJ
ER[
SAP AG BC601 10-17

1-1-1 Note the new workflow task number:
1XPEHUJHQHUDWHGE\WKHV\VWHP
1-2 A deadline is to be set for the manager s approval. We will give the manager an
aggressive deadline of 5 minutes to check the notification of absence. The
employee is notified if the latest end was missed. Modify your workflow now to
add this deadline and the recipient for missed deadline.
,QWKH6$3(DV\$FFHVVPHQXXQGHU'HILQLWLRQ7RROVGRXEOHFOLFN
:RUNIORZ%XLOGHU
,I\RXUZRUNIORZLVQRWGLVSOD\HGFKRRVHWKH2WKHUZRUNIORZYHUVLRQ
LFRQ(QWHU:6DQG\RXUZRUNIORZWDVNQXPEHUIURPWKHSUHYLRXVVWHS
&KRRVHWKH,QVHUWEXWWRQ
1-2-2 Choose the approval step in order to add a deadline.
'RXEOHFOLFNRQWKH$SSURYHQRWLILFDWLRQRIDEVHQFHVWHS
2QWKH:RUNIORZ%XLOGHU&KDQJH6WHS$FWLYLW\VFUHHQFKRRVHWKH
5HTXHVWHGHQGWDESDJH
1-2-3 Specify a deadline of 5 minutes and activate monitoring of requested end.
6HOHFW:RUNLWHPFUHDWLRQLQWKH5HIHUGDWHWLPHILHOG
,QWKHILHOGHQWHUDQGPDNHVXUHWKDWWKHGHIDXOWYDOXHIRUWKHXQLW
LV0LQXWHV
&KRRVHWKH6\QWD[FKHFNEXWWRQVFDOHVLFRQ
1-2-4 Enter the recipient for missed deadline. In this exercise, we will use the
expression ,QLWLDWRUfrom the container as the recipient.
Note: Each workflow automatically contains the user ID that started

the workflow, in the "Initiator" field. In the case of the notification
of absence, this is the user ID of the employee who creates the form.
In this exercise, we will use the "Initiator" field to send the
notification of a missed deadline back to the employee who created
the form.
2QWKH1RWLILFDWLRQWDESDJHVHOHFW:RUNIORZLQLWLDWRUH[SUHVVLRQ
IURPWKHSXOOGRZQPHQX
&KRRVHWKH6\QWD[FKHFNEXWWRQVFDOHVLFRQWRFKHFN\RXUVHWWLQJV
SAP AG BC601 10-18

1-2-5 Enter the notification text for the task "Approve notification of absence".
The recipient receives this notification text if the deadline is missed.
Note: The notification text for missed deadline is stored at the

individual task level and not in the workflow step.
7RGLVSOD\WKHWDVNFOLFNRQWKHEOXHWH[WOLQH
&OLFNRQWKH'HVFULSWLRQWDESDJHDQGVHOHFW5HTXHVWHGHQGWH[WLQWKH
7H[WW\SHILHOG
&KRRVHWKH&KDQJHWH[WEXWWRQ
2QWKH5HTXHVWHGHQGWH[W&KDQJHVFUHHQHQWHU\RXURZQWH[WWRLQIRUP
WKHFUHDWRURIWKHIRUPWKDWWKHPDQDJHUGLGQRWFRPSOHWHWKHFKHFNZLWKLQ
WKHUHTXHVWHGWLPHSHULRG([LWWKHVFUHHQ
Note: If the "Enter change request" dialog box is displayed, choose

the "Create request" button. Enter a short description and choose the
"Save Enter" button. On the "Enter Change Request" screen, choose
the "Continue Enter" button.
([LWWKH:RUNIORZ7HPSODWH&KDQJHVFUHHQDQGWKHQH[LVWWKH
:RUNIORZ%XLOGHU&KDQJH6WHS$FWLYLW\VFUHHQE\FKRRVLQJWKH
%DFNEXWWRQJUHHQDUURZ
&KRRVHWKH%DFNEXWWRQJUHHQDUURZWRUHWXUQWRWKH:RUNIORZ

%XLOGHU
&KRRVHWKH*HQHUDWHDQGDFWLYDWHUXQWLPHYHUVLRQEXWWRQPDWFKLFRQ
WRDFWLYDWHWKHZRUNIORZDQGVDYH\RXUFKDQJHV
5HWXUQWRWKH6$3(DV\$FFHVVPHQXE\FKRRVLQJWKH%DFNEXWWRQ
JUHHQDUURZ
1-3 Test the workflow with the new simple deadline. Each group is to start their new
workflow manually using the HPSOR\HH user ID %&. You can resubmit one
of the forms you created in the Business Workplace exercise for approval.
SAP AG BC601 10-19

1-3-1 Start your new workflow explicitly.
,QWKH6$3(DV\$FFHVVPHQXRSHQWKH5XQWLPH7RROVIROGHU
'RXEOHFOLFN6WDUW:RUNIORZ7HVW(QYLURQPHQW
(QWHU\RXUQHZZRUNIORZQXPEHULQWKH7DVNILHOG
Note: If the workflow was started automatically, it would receive

information about the absence form from the system as soon as the
form was created. Since we are starting this workflow explicitly, we
have to provide the workflow with the form number.
&KRRVHWKHPDWFKFRGHV\PEROIRUWKH1RWLIRIDEVHQFHILHOG
(QWHUWKHQXPEHURIRQHRIWKHIRUPV\RXFUHDWHGLQDQHDUOLHUH[HUFLVH
DQGFKRRVHWKH%DFNEXWWRQJUHHQWLFNWRFRQWLQXH
&KRRVHWKH([HFXWHEXWWRQ
1-3-2 Check the Business Workplace of user ID%&0*5to see if the

work item to be approved has entered the worklist. If it has, wait until the
deadline has passed.
7RFDOOWKHZRUNOLVWFKRRVHWKH%XVLQHVV:RUNSODFHEXWWRQRQWKH
6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQRUFKRRVH
2IILFH:RUNSODFHLQWKH6$3(DV\$FFHVV0HQX
1-3-3 Then check the HPSOR\HH

V Business Workplace to see if the notification
for missed deadline has appeared.
,QWKHHPSOR\HH
V%XVLQHVV:RUNSODFHDGHDGOLQHQRWLILFDWLRQLVGLVSOD\HG
LQERWKWKH:RUNIORZYLHZDVZHOODVWKH0LVVHG'HDGOLQHYLHZRIWKH
LQER[&KRRVHWKH0LVVHG'HDGOLQHEXWWRQ
1-3-4 Execute this work item to check the notification text that was added and
remove the deadline notification from your worklist.
'RXEOHFOLFNRQWKH([FROXPQ
<RXUGHDGOLQHQRWLILFDWLRQWH[WLVGLVSOD\HGLQWKH'HVFULSWLRQILHOG
7RUHPRYHWKHZRUNLWHPFKRRVHWKH6HWWR'RQHEXWWRQDWWKHWRSRI
WKHVFUHHQ
SAP AG BC601 10-20

1-4 Managers often forget to check their workflow inboxes for notifications of absence
and, as a result, miss the deadline. You decide to define the approval step as an
express work item. Change your workflow accordingly.
,QWKH6$3(DV\$FFHVVPHQXXQGHU'HILQLWLRQ7RROVGRXEOHFOLFN
:RUNIORZ%XLOGHU
,I\RXUZRUNIORZLVQRWGLVSOD\HGFKRRVHWKH2WKHUZRUNIORZYHUVLRQ
LFRQ(QWHU:6DQG\RXUZRUNIORZWDVNQXPEHUIURPWKHSUHYLRXVVWHS
&KRRVHWKH,QVHUWEXWWRQ
1-4-2 Change the approval step.
'RXEOHFOLFNRQWKH$SSURYHQRWLILFDWLRQRIDEVHQFHVWHS
1-4-3 Change the priority of the step to make it an express work item.
2QWKH:RUNIORZ%XLOGHU&KDQJH6WHS$FWLYLW\VFUHHQFKRRVHWKH
2WKHUWDESDJH7KLVWDESDJHLVWRWKHIDUULJKW\RXPD\KDYHWRXVH
WKHVFUROONH\WRVHOHFWLW
&KDQJHWKHSULRULW\IURP0HGLXPWR+LJKHVW([SUHVV
&KRRVHWKH%DFNEXWWRQJUHHQDUURZ
&KRRVHWKH*HQHUDWHDQGDFWLYDWHUXQWLPHYHUVLRQEXWWRQPDWFKLFRQ
WRDFWLYDWHWKHZRUNIORZDQGVDYH\RXUFKDQJHV
1-5 Test your workflow with the express work item. Each group is to start their
workflow manually using the employee user ID. Use a different absence form from
the Business Workplace exercise.
1-5-1 Start the workflow explicitly.
2QWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQFKRRVH:RUNIORZ7HVWRU
WKH7HVWEXWWRQ
2QWKH6WDUW:RUNIORZ7HVW(QYLURQPHQWVFUHHQ\RXUZRUNIORZQXPEHU
VKRXOGEHGLVSOD\HGLQWKH7DVNILHOG
&KRRVHWKHPDWFKFRGHV\PEROIRUWKH1RWLIRIDEVHQFHILHOG
(QWHUWKHQXPEHURIDIRUP\RXFUHDWHGLQDQHDUOLHU%XVLQHVV:RUNSODFH
H[HUFLVHDQGFKRRVHWKH%DFNEXWWRQJUHHQWLFNWRFRQWLQXH
SAP AG BC601 10-21

1-5-2 How is the PDQDJHU notified about this work item?
*REDFNWRWKHPDQDJHU
VVHVVLRQDQGFKRRVH(QWHU$GLDORJER[LV
LPPHGLDWHO\GLVSOD\HGLQIRUPLQJWKHPDQDJHUWKDWWKH\KDYHUHFHLYHGD
ZRUNLWHPZLWKSULRULW\7KHPDQDJHUFDQDFFHVVWKH%XVLQHVV
:RUNSODFHGLUHFWO\IURPWKLVGLDORJER[
SAP AG BC601 10-22

(YHQWV
&RQWHQWV
l &UHDWLQJZRUNIORZHYHQWOLQNDJH
DQGELQGLQJ
l +RZHYHQWVDUHFUHDWHGLQWKH
V\VWHP
l :L]DUGIRUFUHDWLQJHYHQWV
l 7HUPLQDWLQJHYHQWV
SAP AG 1999
SAP AG BC601 11-1

(YHQWV8QLW2EMHFWLYHV
l &UHDWHDQHYHQWGULYHQZRUNIORZ
l 7ULJJHUHYHQWVLQ5
SAP AG 1999
SAP AG BC601 11-2

SAP AG 1999
SAP AG BC601 11-3

(YHQWV%XVLQHVV6FHQDULR
l 7KHPDLQSDUWRI\RXUZRUNIORZLVILQLVKHG
l 7KHPRVWLPSRUWDQWPLVVLQJSLHFHLVWKHFRQQHFWLRQ
WRWKHWULJJHULQJ6$35DSSOLFDWLRQ
l ,Q6$35DWULJJHULVDQREMHFWW\SHHYHQW
l <RXQHHGWRNQRZKRZWKHVHSXEOLVKHGHYHQWVDUH
DFWLYDWHGLQDQDSSOLFDWLRQ
l <RXQHHGWRXQGHUVWDQGKRZWKHOLQNDJHRIWKH
HYHQWVWRWKHZRUNIORZIXQFWLRQV
SAP AG 1999
SAP AG BC601 11-4

([HUFLVH([DPSOH
7ULJJHULQJ(YHQWIRUD7DVN
7UDQVDFWLRQ3URFHVVPDWHULDOPDVWHU
%DVLFYLHZ
&UHDWLRQRIFKDQJHGRFXPHQWV
0DWHULDO 0\BSDUW
2OGPDWHULDO 2ULJLQDOBSDUW &RQILJXUDWLRQWUDQVDFWLRQ

6:(&
1HZBSDUW =%86
2OGB0DWHULDOB&KDQJHG
2UJ3ODQ
(QJLQHHULQJGHSDUWPHQW
(QJLQHHUSRVLWLRQ
+ROGHU0DU\ 3RVVLEOH :RUNIORZ
3URGXFWPDQDJHPHQWGHSW DJHQWV &KDQJHPDWHULDO
3URGXFWPDQDJHUSRVLWLRQ
+ROGHU-RQHV
Task
Display material
SAP AG 1999
n Object type events can be used to trigger tasks or workflows.

You need to have defined the relevant event for the object type in the BOR .
In the example, the event is old_material_changed.
n When a change document is written in the system, you have the option to trigger an event.
SAP logs the changes to master data information, and sometimes also the changes to transactional
document data in Change Documents.
Check whether change documents will be written for the scheduled data changes in your application.
If not, you will have to trigger the event in another way.
From Release 4.6 onwards, you can use the menu area Workflow - Events to view a list of existing
change document objects and when they were written.
Events -> Event Creation -> Change Documents -> Overview / Define Workflow Properties
n You can activate the triggering of an event due to a change to the material master by using
transaction SWEC, or a wizard.
n In the next step, you have to create the event as a triggering event in your workflow, and set the
event linkage to active.
SAP AG BC601 11-5

(YHQW&UHDWRUVDQG5HFHLYHUV
)OH[LEOHOLQNDJH
$SSOLFDWLRQ FDQEHGHILQHG $Q\QXPEHU
FUHDWHV LQGHSHQGHQWO\ RIUHFHLYHUV
HYHQWV IURP
WKHDSSOLFDWLRQ
7ULJJHU
ZRUNIORZ
(YHQW
$SSOLFDWLRQ 5HFHLYHU 7HUPLQDWH
HYHQWFUHDWRU IXQFWLRQPRGXOH WDVNV
5HFHLYHU
(YHQW GHILQHG
&RQWDLQHU E\WKH
DSSOLFDWLRQ
(YHQWPDQDJHU
SAP AG 1999
n An event in the BOR is uniquely identified by the

Name (for example, object created, object released, object deleted etc.)
Object type, for which it specifies a change in status (for example, invoice, material etc.)
n At runtime, the application must create the event when the specified change of status occurs. This
does not necessarily happen by default. Slide 10 of this unit shows the options for triggering events
using the application. Events contain information from the context of their creation. This information
is stored in the event container and is available for the event receiver.
n Event receiver linkage: The reactions to the occurrence of an event are defined outside the standard
application. The receiver of the event can be a workflow, or any appropriate function module
provided by SAP, the customer, or a third-party supplier.
n The event receiver linkage follows a "Publish and Subscribe" approach:
The event is created, the event manager is notified ("Publish").
The event-creating object does not need to know about potential interested parties (receivers) of
the event.
Interested receivers enter themselves in a linkage table (subscribe).
n Event manager: Checks the entries in the linkage table and performs the assignment
Important: There may be several receivers for an event.
SAP AG BC601 11-6

(YHQWV'HILQHGIRUDQ2EMHFW7\SHLQWKH%25
3DUNHGGRFXPHQWSRVWHG
5HFUXLWPHQWIUHH]H
%XGJHWOLPLWUHDFKHG 2EMHFWW\SH
HYHQW
2UGHUFDQFHOHG
3URMHFWPLOHVWRQHUHDFKHG
&XVWRPHUPDVWHUGDWDFKDQJHG
SAP AG 1999
n An event describes a possible change in status of an object in R/3.

n Before an event can be used in a workflow, it must be defined for the object type in the Business
Object Repository.
This definition does not mean it is created as a default in R/3.
n Events must be triggered explicitly. The R/3 application itself can be the trigger.
If a workflow reacts to an event that is not in the application, you can customize R/3 so that the
desired event is published in the system.
SAP AG BC601 11-7

:RUNIORZ7ULJJHULQJ(YHQWV/LQNDJH
l 3URFHGXUHIRUHQWHULQJHYHQWOLQNDJHIRUWULJJHULQJHYHQWVLQWKH
ZRUNIORZ
0DNHVXUHWKDWDYDULDEOHH[LVWVLQWKHZRUNIORZFRQWDLQHU
WKDWFDQWDNHXSWKHREMHFWUHIHUHQFHIURPWKHHYHQW
!6WDUWWKH:RUNIORZ%XLOGHU,QWKHH[LVWLQJYDULDEOHLQWKH
ZRUNIORZFRQWDLQHUVHOHFWWKHIODJVLPSRUWDQGREOLJDWRU\
6SHFLI\WKHHYHQWDVDWULJJHULQJHYHQWLQWKHZRUNIORZ
WHPSODWH
SAP AG 1999
n Events always occur in association with one particular object.

For example, at runtime the event "Material master changed" refers to the material P-100 or
TD_4958-AZ or LZN-6099.
The event "customer master created" can refer to the customers Jones, Hillberg, and Paretzky.
n If a workflow wants to react to an event, it must know the runtime-specific object.
It is transferred from the event manager in the variable _EVT_OBJECT.
In the workflow container, a variable must exist for recognizing the object.
This variable must relate to the desired object type. The flags Import and Obligatory must also be set.
n The triggering event is entered in the workflow in the tab page "Triggering events".
Menu path:
SAP EASY ACCESS -> Tools - Business Workflow -> Development -> Definition Tools ->
Tasks/Task Groups -> Change -> Task type: Workflow template, Workflow number ->Change
Tab page "Triggering events"
or
SAP EASY ACCESS -> Tools - Business Workflow -> Development -> Definition Tools ->
Workflow Builder ->
Enter workflow to be processed -> Goto -> Basic data
Input data: Object type and triggering event
SAP AG BC601 11-8

:RUNIORZ7ULJJHULQJ(YHQWV/LQNDJH
l 3URFHGXUH
2QWKH7ULJJHULQJHYHQWWDESDJHFKHFNWKH
ELQGLQJ
B:)B,QLWLDWRUB(97B&5($725
2EMHFWYDULDEOH!B(97B2%-(&7
$FWLYDWHWKHHYHQWOLQNDJH
&KHFNWKHELQGLQJLQWKH:RUNIORZ%XLOGHU
:RUNIORZFRQWDLQHU!7DVNFRQWDLQHU
SAP AG 1999
n The system automatically generates a binding between the event container and the workflow
container.
This binding must correspond to the entry on the slide.
To check, use the green button "Binding defined", or D... next to the object type entry.
n The event is now correctly bound to the workflow.
The linkage is, however, not yet active. This means when the event is created in the system, the
workflow doesnt start.
n The event linkage must be activated explicitly.
You have several options for activating the event linkage.
1. Tab page "Triggering event" - Double click the red button "Active/inactive, or A...
next to the entry for the object type
2. SAP EASY ACCESS -> Tools - Business Workflow -> Development -> Utilities ->
Events -> Simulate event
Enter object type and event, button "Execute"
3. Workflow Builder: Goto - Basic data - Tab page "Start".
n Caution:
The event linkage deactivates automatically after runtime errors, and must be reactivated after the
error is repaired
n A workflow can have more than one triggering event.
SAP AG BC601 11-9

+RZLVWKH(YHQW7ULJJHUHGLQWKH$SSOLFDWLRQ"
l 7KHDSSOLFDWLRQWULJJHUVWKHHYHQWE\GHIDXOW
l ,IWKHDSSOLFDWLRQGRHVQRWWULJJHUWKHGHVLUHGHYHQWE\
GHIDXOW
l /LQNWRZULWLQJRIFKDQJHGRFXPHQWVZL]DUG
l /LQNWRVWDWXVPDQDJHPHQW
l /LQNWRPHVVDJHFRQWURO
l +57DEOHV7:6$37;FXVWRPHU
l 5HOHDVHRQZDUGVFRQQHFWLRQWRWKHRSHQ),LQWHUIDFH
ZL]DUG
l 5HOHDVHRQZDUGVFRQQHFWLRQWR/,6H[FHSWLRQVZL]DUG
l ,IQRFRQQHFWLRQLVSRVVLEOHXVLQJFXVWRPL]LQJ
l 7ULJJHUXVLQJWKHIXQFWLRQPRGXOH6:(B(9(17B&5($7(
LQWKHDSSOLFDWLRQXVLQJ8VHU([LWV
SAP AG 1999
n You can see whether the application triggers an event by default by looking at the event trace.
Switch on the event trace and execute the desired function in R/3.
View the created events by choosing SAP EASY ACCESS - Tools - Business Workflow -
Development - Utilities - Events - Event Trace
n Exception: Starting the workflow from a system error message:
At runtime, a user can start a particular workflow after a particular error has occurred. Use the
Workflow Wizard to create the workflow, then start the workflow SAP EASY ACCESS - Tools
- Business Workflow - Development - Definition Tools - Wizards - Create "Call Workflow From
Message"
Follow the wizard:
- Table entry T100W: Application area, error number, and workflow to be started
- Create the workflow. It can be freely processed
- Enter a new icon in the technical help text, which can be called when the error message
appears in the system.
- Procedure when error occurs: Call the technical error display and click the "Start workflow"
icon.
n ([FHSWLRQ: Starting the workflow by a change of status in the DMS.
The workflow template is specified directly in the definition of the document type.
SAP Reference IMG - Cross-Application Components - Document Management System -
Control Data - Define Document Types - Define Document Status - Double-click Document
Status.
SAP AG BC601 11-10

7ULJJHULQJ(YHQWV+5/,62SHQ),
l +57DEOHV
,QWKHWDEOHV7:6$3DQG7;FXVWRPHU

\RXFDQGHWHUPLQHHYHQWVWKDWDUHWULJJHUHGZKHQDQLQIRW\SH
UHFRUGRIDQ+5REMHFWW\SHLV
&UHDWHG
&KDQJHG
'HOHWHG
l /,6H[FHSWLRQV
$ZL]DUGPRGHOVWKHUHODWLRQVKLSEHWZHHQDQ/,6H[FHSWLRQ
DQGWKHHYHQWRIDEXVLQHVVREMHFWW\SH
l 2SHQ),LQWHUIDFH
$ZL]DUGPRGHOVWKHUHODWLRQVKLSEHWZHHQDQRSHQ),HYHQWDQG
WKHHYHQWRIDEXVLQHVVREMHFWW\SH
SAP AG 1999
n An LIS exception can be, for example, "Orders with unscheduled scrap". Whilst using the wizard,
you can view the exceptions using the input help.
n To find the wizard, see
SAP EASY ACCESS - Tools - Business Workflow - Development - Definition Tools - Events -
Event Creation - Set up with Wizard - Logistics Information System.
n The open FI interface covers the events:
Creditor master data
Debitor master data
Post document
Reset cleared items
Credit management
Change document
n To find the wizard, see
SAP EASY ACCESS - Tools - Business Workflow - Development - Definition Tools - Events -
Event Creation - Set up with Wizard - Business Transaction Events.
SAP AG BC601 11-11

7ULJJHULQJ(YHQW&KDQJHWR0DWHULDO0DVWHU
3HUVRQUHVSRQVLEOH
IRUPDWHULDO
&KDQJH /RJJLQJ
in master data of a particular the change using a change
material document
To be implemented as (YHQW
customer-defined event (YHQWFUHDWLRQ
creation by writing a change document
3URGPDQDJHU
,QIRUPDWLRQ /LQNDJH
from the employee responsible of the event as the triggering
in the engineering office event for task
SAP AG 1999
n Changing a field in the master data of a particular material should, in the simplest of cases, mean that
an agent from materials management is "informed" of the change using a work item.
n The event changed is defined for the object type ZBUS1001 ( Material ).
n This event is established as a triggering event for the workflow Display Material Master .
n The logging of changes to the material master data by creating change documents for a particular
change document object (in this case the change document object MATERIAL), is already
implemented and therefore available in the application (in this case the application component MM).
n Creating an event when writing change documents is implemented as a customer-defined extension.
n Workflow and creation of change documents are independent tools.
If you want to trigger a workflow event, you need to know the objects for the creation of change
documents.
n From Release 4.6 onwards, the system provides an overview of the change document objects and
when a document from the application is written:
Events -> Event Creation -> Change Documents -> Overview/Workflow Properties
SAP AG BC601 11-12

7ULJJHULQJ(YHQW&KDQJHWR0DWHULDO0DVWHU
DVDUHVXOWRIOLQNDJHWR
WKHFKDQJHGRFXPHQWV 7KH0$5$:5.67WDEOH
ILHOGLVFKDQJHG
7 8 9 :; <!

"! = > ? A@ 3 8? BCD%E F 3 8,? > GH
8 ? = > ? JIK4LMON ? P8Q N ? P?
< 5 .6 /

#
$%'&)( *,+.-,/ 20 11%0
%3 4 5 . 6 / 4
F > %F 3 E$)F

;
WKHQWKH:5.67&KDQJHGHYHQWRI
WKH=%86REMHFWW\SHLVFUHDWHG
$UHIHUHQFHWRWKHFKDQJHGREMHFWRI
W\SH=%86FDQEHIRXQGLQWKH
HYHQWFRQWDLQHU
SAP AG 1999
n Creating the event trigger:

Call the appropriate wizard:
- SAP EASY ACCESS -> Tools -> Business Workflow -> Development -> Definition Tools -
> Events -> Event Creation -> Set up with Wizard -> Change Documents
or manually, without the wizard:
- SAP EASY ACCESS -> Tools -> Business Workflow -> Development -> Definition Tools -
> Events -> Event Creation -> Change Documents -> Linkage
n The change object is Material.
You also need to enter your object type and the event.
n You can set conditions to state which changes to which fields should trigger the workflow.
Select the desired entries in the linkage table for the change documents (transaction SWEC).
Then go to the field restrictions, and use "New Entries" to enter your desired database field and the
desired entries.
&DXWLRQ: If you name more than one field, the fields are linked with AND. The fields must then
occur in a logical unit.
n From Release 4.6 onwards, you can define complex conditions for the field restrictions using the
button "Condition editor".
SAP AG BC601 11-13

7ULJJHU(YHQW6WDWXV0DQDJHPHQW
SAP Business Object Type:

Production order
2EMHFWOLIHF\FOHGHVFULEHGE\
6WDWXVFKDQJHVIRUWKHSURGXFWLRQRUGHU
&5($7('
5(/($6(' 5(/,
7(&+1,&$//<&203/(7('
3XEOLVKHG
HYHQWV
RISURGXFWLRQRUGHU
SAP AG 1999
n Another option for triggering events is status management. Check the SAP application. If it offers
status management, for example, in the case of production order handling, follow the procedure
below to activate events:
n Find the status object family that is connected to the SAP application, in this case ORH.
n Check the status family for all statuses involved, for example, Released. Each status has an
internal SAP unique identifier. For example, the status "Released" has the identifier REL or I0002.
(Use transaction BS22)
n Map out the status life cycle of your object. Describe the different stages using the statuses delivered
by SAP.
n Next to each status, write the SAP name, number and the name of this status as it is used in your
business language. This chart becomes an important de-coding tool.
n Each status on this diagram can become an event in a workflow.
n The events are first described in the business object type.
SAP AG BC601 11-14

'HPR&KDQJH0DQDJHPHQW
l &UHDWHFKDQJHWUDQVDFWLRQ&&
7\SH&KDQJHUHTXHVW
R
&KDQJHW\SH&XVWRPHUFRPSODLQWZLWKZRUNIORZ
R
(QWHU
R
(QWHUWLWOH
R
6SHFLI\UHDVRQIRUFKDQJH
R
6WDWXVFKDQJHQXPEHU
R
6DYH
R
l &KDQJHFKDQJHQXPEHUWUDQVDFWLRQ&&
6HWVWDWXV
R
&KDQJHIURPFKHFNUHTXHVWWRUHTXHVWFKHFNHG
6DYH
R
SAP AG 1999
n Demo guide for creating a change request
SAP AG BC601 11-15

'HPR&KDQJH0DQDJHPHQW
l (YHQWWUDFHWUDQVDFWLRQ6:(/
7KHHYHQWV23(1('&5($7('DQG
R
$//B2%-(&76B&+(&.('
KDYHEHHQFUHDWHGIRUWKHEXVLQHVVREMHFWW\SH(&0
l 6WDWXVPDQDJHPHQWWUDQVDFWLRQ%69:
6\VWHPVHWWLQJV
R
6WDWXVUHVWULFWLRQVIRU
R
&'0(&0$//B2%-(&76B&+(&.('
,IWKHLQWHUQDOVWDWXV,DEEUHYLDWLRQ2*(3
R
RFFXUVLQWKHVWDWXVREMHFWW\SH&'0WKHQWKHHYHQW
(&0$//B2%-(&76B&+(&.('LVWULJJHUHG
SAP AG 1999
n The events OPENED and CREATED of the object type ECM are triggered directly by the
application from the ABAP code.
n The event ALL_OBJECTS_CHECKED is created using the Customizing settings in transaction
BSVW.
This setting is under "System settings", because it is delivered by SAP.
n The customer-specific settings are carried out in the transaction BSVW, under "Customer settings".
The first step in a typical entry may contain:
- Status object, for example, ORH
- Business object, for example, BUS2005
- Event, for example, released
In the second step, enter the status restrictions:
- Select "status restrictions"
- System status, for example I0002 (released)
n You can find the system status using transactions BS22, BS12 and BS02.
Selecting the appropriate status requires knowledge of the application.
SAP AG BC601 11-16

7ULJJHU(YHQW0HVVDJH&RQWURO
l &UHDWHDVHSDUDWHRXWSXWW\SHDQGGHFODUHZRUNIORZ
HYHQWDVWKHWUDQVPLVVLRQPHGLXP
l &UHDWHDFRQGLWLRQWDEOH
l &UHDWHDQDFFHVVVHTXHQFH
l $VVLJQWKHDFFHVVVHTXHQFHWRWKHGHILQHGRXWSXWW\SHIRU
DZRUNIORZHYHQW
l 'HILQHFRQGLWLRQUHFRUGVDQGGHFODUHWKHHYHQW
l $VVLJQWKHRXWSXWW\SHWRDSURFHGXUH
SAP AG 1999
n An event is triggered using message control by means of NAST.

n You need to create a new message type for a "Workflow event", and maintain it like every other
message type.
This requires knowledge of message control maintnenance. Use your message control experts for
this.
n Follow the steps described on the slide and in the message control.
Events -> Event Creation -> Message Control
n The actual linkage with the event occurs in the condition records.
Select the condition record with which the event should be triggered, and choose the menu option
Goto -> Communication, or the "Communication" button.
You then have the option to enter an object type and an event that should be created when the
condition occurs.
SAP AG BC601 11-17

%LQGLQJDQG(YHQW
SAP
SAP transaction,
transaction, for
for example,
example, "Release
"Release order"
order"

Order (YHQWFRQWDLQHU
released
&UHDWRU
2EMHFW
:RUNIORZ
&KDQJH 7DVNFRQWDLQHU :)FRQWDLQHU

2UGHU :,B2EMHFWB,' 3URGRUGHU
5ROHFRQWDLQHU :)LQLWLDWRU
7HFKQLFDOO\ (YHQWFRQWDLQHU
FRPSOHWHG REMHFW
SAP AG 1999

n The application activates the event Production Order was released.

n This event contains information in the event container:
The event object for the "production order".
The user who executes the application and becomes the event creator.
n The event linkage has to be activated in order for this workflow to be started.
At start time, the necessary information is transferred from the event container to the workflow
container.
n The data from the workflow container must be transferred to the task container.
n The application triggered by this task at runtime will eventually raise the event Production order
technically complete.
SAP AG BC601 11-18

:RUNIORZ6WDUW&RQGLWLRQV2YHUYLHZ
l 8VHWKLVIXQFWLRQLI\RXZDQWWRGHILQHVLPSOHLQGLYLGXDO
FRQGLWLRQVIRUWKHVWDUWRIDZRUNIORZ
l <RXFDQRQO\GHILQHVWDUWFRQGLWLRQVLIWKHZRUNIORZLV
VWDUWHGE\DQHYHQW
l 6HOHFWLRQFULWHULD
2EMHFWW\SH
R
(YHQW
R
:RUNIORZ
R
l 7KHFRQGLWLRQHGLWRURIWKH:RUNIORZ%XLOGHULVXVHGWR
GHWHUPLQHWKHVWDUWFRQGLWLRQV
SAP AG 1999
n The start of a workflow no longer only depends on whether a specific event is generated, but also on
the occurrence of additional conditions.
n ([DPSOHV:
A workflow should always be started if a notification of absence has been created, AND the creator
of the notification of absence belongs to a specific employee group.
A workflow should be started if a material master has been changed, and the material belongs to
industry "C".
n To display the start conditions for a workflow, choose the following menu path:
Tools - Business Workflow - Development - Definition Tools - Events - Event Linkages - Workflow
Start Conditions.
SAP AG BC601 11-19

6WDUWLQJD:RUNIORZ8QGHU6SHFLDO&RQGLWLRQV
&UHDWLQJDQHZVWDUWFRQGLWLRQ
)LQGLQJDQG
VHOHFWLQJWKH
REMHFWW\SHV
SAP AG 1999
SAP AG BC601 11-20

'HILQLQJ&RQGLWLRQLQWKH&RQGLWLRQ(GLWRU
'RXEOHFOLFNWRVHOHFWWKHILUVWH[SUHVVLRQ
'RXEOHFOLFNWRVHOHFWWKHRSHUDWRU
(QWHUWKHVHFRQGH[SUHVVLRQZLWKRXW
SAP AG 1999
SAP AG BC601 11-21

1DPHWKH6WDUW&RQGLWLRQ
&KDQJHPRGH
&OLFNWRFKDQJHWRILHOGHQWU\PRGH
(QWHUQDPH
&OLFN
UHWXUQ
WRVDYH
SAP AG 1999
SAP AG BC601 11-22

7HUPLQDWH7DVNV
l (QWHUHYHQWDVWKH
WHUPLQDWLQJHYHQWRIDWDVN
l 7HUPLQDWLQJHYHQWVGHVFULEHSURFHVVLQJUHVXOWVRIWKH
DSSOLFDWLRQVWDUWHGE\WKHWDVN
l %LQGLQJ7KHHYHQWSDUDPHWHUFDQUHWXUQLQIRUPDWLRQLQWR
WKHWDVNFRQWDLQHU
l $WDVNFDQKDYHPRUHWKDQRQHWHUPLQDWLQJHYHQW
SAP AG 1999
n A task based on an asynchronous method requires at least one terminating event.

Otherwise the corresponding work item cannot be terminated at runtime.
n For each terminating event you have to specify threeparameters for the task binding:
Object type: Use the same object type as for the method.
Event: Use the input help to get the correct spelling.
Element of the task container that contains the object reference, normally the variable
"_WI_Object_ID".
n If you do not enter the object reference, the system does not know at runtime which work item of the
task should be terminated.
n If the method that underlies the task is a synchronous method, the terminating event is only evaluated
in addition to the "normal" end of the method.
This means if a user executes the work item and their processing of the object does not create the
terminating event, the work item is terminated anyway. The method was correctly executed.
n If a work item should only be terminated by a particular event, the method must be asynchronous.
SAP AG BC601 11-23

(IIHFWRQ7\SH/LQNDJH
7KLVFKHFNIXQFWLRQ
PRGXOHHYDOXDWHVWKH
VWDUWFRQGLWLRQDW
UXQWLPH
$JUHHQOLJKWLQWKHVWDUW
FRQGLWLRQRU
WKHWULJJHULQJHYHQWLQWKH
ZRUNIORZ
VHWVWKHW\SHOLQNDJHWR

DFWLYH
SAP AG 1999
n Type linkages (= triggering events) are stored in the table SWETYPECOU.

To view the triggering events, choose
SAP EASY ACCESS -> Tools -> Business Workflow -> Development -> Utilities -> Events ->
Type Linkages
n Terminating events are stored in the same table, SWETYPECOU.
To view the terminating events, choose
Instance Linkages
n In Releases prior to 4.6C, the view
Type Linkages displays both the terminating events and the triggering events.
Whether a terminating event is involved can be seen in the user type, by choosing the "Global" flag.
For a triggering event, the user type is a workflow and the "Global" flag is set in the detail display.
For a terminating event, the user type is a work item and the "Global" flag is not set.
n &DXWLRQ
7KHJOREDOIODJFDQQRWEHPDLQWDLQHGPDQXDOO\
)URP5HOHDVH&RQZDUGVLWLVQRORQJHULQFOXGHGLQWKHFKDQJHPRGH
SAP AG BC601 11-24

(YHQWV8QLW6XPPDU\
l 2EMHFW7\SH(YHQWV
FDQEHXVHGWRWULJJHURU
WHUPLQDWHWDVNVRUZRUNIORZV
l &UHDWLRQRIDQHYHQW
FKDQJHGRFXPHQWV
R
VWDWXVPDQDJHPHQW
R
PHVVDJHFRQWURO
R
FHUWDLQ+5WDEOHV
R
,PSOHPHQWDWLRQLQSURJUDPFRGLQJ
R
XVLQJ86(5(;,76
l (YHQW:L]DUGFDQEHXVHGIRUHYHQW
FUHDWLRQ
SAP AG 1999
SAP AG BC601 11-25

([HUFLVHV
8QLW(YHQWV
7RSLF&KDQJH'RFXPHQWV

Use the flexible event creation.
Using flexible event creation , you can activate events in the SAP R/3
system without having to write ABAP code.
The following procedure will show you how to use the SAP Change
documents to activate an event for your object type Y##MARA . In
this case, the event '
Old_Material_Changed'will be used as a triggering
event for your workflow.
1-1 You want to support the business process for Material Masters with your workflow.
The first activity in your workflow is started whenever the material master is
changed. Before you actually build this workflow, familiarize yourself with the
change log of a material master.
1-1-1 Change the material master.

Change your material, for example T-BBD## .
On the Select view(s) screen, select Basic Data 1 , and continue.
On the Change material screen, enter your user ID in the Old material
number field. Save your entries and return to the SAP Easy Access menu.
1-1-2 Display the change log of the material master.
1-2 Now link an event of your object type with the workflow system, and arrange for an
event to be triggered whenever a material master is changed
1-2-1 In the first step, ensure the event is triggered by writing a change document.
This only includes the change documents that are created when a material is
changed. Use a wizard for this.
SAP AG BC601 11-26

1-2-2 Follow the instructions in the wizard.
Choose "MATERIAL" as the Change document. object , and enter your
object type Y##MARA as the Business object type . Choose your event
'
Old_Material_Changed' .
1-2-3 The event should be activated if the value is changed from anything to G##.
Do not specify more than one field, because changes to all listed fields
have to occur within one logical unit of work . At runtime, the user has
to change all listed fields before saving this event.
If every group uses their own group number for the New Value field,
all groups will be independent of one another.
You may be asked to enter a Change request. In the Enter change

request dialog box, choose Own requests . Double-click your change
request number in the display. Then choose the Continue Enter button.
1-3 In the second step, ensure that your workflow recognizes the event
'old_material_changed'as a triggering event, and that the event manager can
transfer the object reference into your workflow as an import variable.
In the example, the triggering event will "tell" the workflow which material master
has been changed. The object reference must be saved in a workflow container
element.
When inserting tasks into the workflow definition, task container elements that
were not contained in the workflow container were automatically created.
Therefore, the workflow already contains a container element that stands for the
object type Y##MARA. The element is, however, not yet in a position to receive
data from outside the workflow.
1-3-1 Call your workflow in the change mode. Flag the workflow container
element that refers to Y##MARA as Import and Mandatory .
SAP AG BC601 11-27

1-4 The next step is to link the event old_material_changed to your workflow. You
need to ensure that this event transfers the material object and the name of the user
modifying the material into the workflow container.
1-4-1 Enter a triggering event into the workflow. The object is Y##MARA and
the event Old_Material_Changed.
Check the binding from the event to the workflow.
1-4-2 Once you have defined a triggering event, you must activate it. Activate
the event linkage for this triggering event. Return to the Workflow Builder
to check. Activate the workflow.

request number in the display, then choose the Continue Enter button.
1-5 Another way to activate the linkage of a workflow is to directly modify the Event
Linkage Table. The table contains a record for each triggering event and each
workflow that it may start. Check this table for your new triggering event.
1-5-1 Find the entry for your event and display the details.
What is the type linkage activated flag for?:
______________________________________________
1-6 Now you can test your event driven workflow.

&$87,21
'RQRWIRUJHWWRUHPRYH\RXULQLWLDOYDOXHIURPWKHILUVWWDVNDVWKLVZRXOG
RYHUULGHWKHPDWHULDOPDVWHUWUDQVIHUUHGIURPWKHHYHQW
1-6-1 Change your material master (Transaction=MM02). This time enter your
group ID '
##'in the Old Material field.
1-6-2 Check your Business Workplace. Do you see your work item?
Are the change documents displayed?
SAP AG BC601 11-28

6ROXWLRQV
8QLW(YHQWV
7RSLF&KDQJH'RFXPHQWV
1-1 You want to support the business process for Material Masters with your workflow.
The first activity in your workflow is started whenever the material master is
changed. Before you actually build this workflow, familiarize yourself with the
change log of a material master.
1-1-1 Change the material master.
/RJLVWLFV0DWHULDOV0DQDJHPHQW0DWHULDO0DVWHU0DWHULDO
&KDQJH
'RXEOHFOLFN,PPHGLDWHO\
(QWHU\RXUPDWHULDO7%%'LQWKH0DWHULDOILHOGDQGFKRRVHWKH
(QWHUEXWWRQ
2QWKH6HOHFW9LHZVVFUHHQVHOHFW%DVLF'DWDDQGFOLFNWKH
&RQWLQXH(QWHUEXWWRQ
2QWKH&KDQJH0DWHULDOVFUHHQHQWHU\RXUXVHU,'LQWKH2OGPDWHULDO
QXPEHUILHOG7KHQVDYH\RXUHQWULHVDQGUHWXUQWRWKH6$3(DV\$FFHVV
PHQXE\VHOHFWLQJWKH%DFNEXWWRQJUHHQDUURZ
1-1-2 Display the change log of the material master.
,QWKH6$3(DV\$FFHVVPHQXFKRRVH/RJLVWLFV!3URGXFWLRQ!0DVWHU
'DWD!0DWHULDO0DVWHU!0DWHULDO!'LVSOD\&KDQJHV
'RXEOHFOLFNWKH$FWLYH&KDQJHVLFRQ(QWHU\RXUPDWHULDOLQWKH
0DWHULDOILHOG
'RXEOHFOLFNWKHPRVWUHFHQWHQWU\DQGFKHFN\RXUFKDQJH
SAP AG BC601 11-29

1-2 Now link the event Old_Material_Changed with your workflow, and arrange for
the event to be triggered whenever a material master is changed.
1-2-1 In the first step, ensure the event is triggered by writing a change document.
This only involves the change documents that are created when a material is
changed.
7RROV %XVLQHVV:RUNIORZ 'HYHORSPHQW'HILQLWLRQ7RROV
(YHQWV(YHQW&UHDWLRQ6HWXSZLWK:L]DUG
'RXEOHFOLFN&KDQJH'RFXPHQWVDQGFKRRVH&RQWLQXH
1-2-2 Follow the instructions in the wizard.

$QHYHQWLVGHILQHGDVWKHFRPSRQHQWRIDQREMHFWW\SH(QWHUEXVLQHVV
REMHFWW\SH<0$5$LQWKH2EMHFWW\SHILHOG
3UHVVWKH(QWHUNH\
$OOHYHQWVIRUWKLVREMHFWW\SHDUHGLVSOD\HG
'HVHOHFWWKH([WHQGREMHFWW\SHZLWKHYHQWILHOG
6HOHFWWKHHYHQW2OGB0DWHULDOB&KDQJHGWKHQFKRRVH&RQWLQXH
(QWHUWKH&KDQJHGRFXPHQWREMHFW0$7(5,$/LQWKH&KDQJHGRF
REMHFWILHOG
3UHVVWKH(QWHUNH\
6HOHFWWKH(YHQWXSRQFKDQJHUDGLREXWWRQLQWKH'DWHWLPHRIHYHQW
IUDPH
&KHFNDOOWKHHQWULHV\RXKDYHPDGHLQWKH(YHQWFUHDWLRQZL]DUGDQG
FKRRVHWKH&RPSOHWHEXWWRQ
1-2-3 Use the field MARA-BISMT as the field restriction. The event should be
activated if the value is changed from anything to G##.
,QWKH6$3(DV\$FFHVVPHQXFKRRVH7RROV%XVLQHVV:RUNIORZ
'HYHORSPHQW'HILQLWLRQ7RROV(YHQWV(YHQW&UHDWLRQ&KDQJH
'RFXPHQWV
'RXEOHFOLFN/LQNDJH
6HDUFKIRU\RXUQHZHQWU\XVLQJWKH&KDQJH9LHZ(YHQWVIRU&KDQJH
'RFXPHQW2YHUYLHZVFUHHQ
SAP AG BC601 11-30

)LHOG1DPHV
Chng. doc. obj. Business Object Event

Type
,QSXW'DWD Material Y##MARA Old_Material_Changed
6HOHFWWKLVQHZHQWU\DQGFOLFN)LHOGUHVWULFWLRQVRQWKHOHIWKDQGVLGHRI
WKHVFUHHQ
+HUH\RXFDQVSHFLI\ZKLFKFKDQJHVLQZKLFKILHOGZLOODFWLYDWHWKLVHYHQW
Do not specify more than one field, because changes to all listed fields
have to occur within one logical unit of work . At runtime, the user has
to change all listed fields before saving this event.
&KRRVH(GLW1HZHQWULHVRUWKH1HZHQWULHVEXWWRQ
)LHOG1DPHV
Table Field Name Old value New value
,QSXW MARA BISMT Blank Blank

'DWD
3UHVVWKH(QWHUNH\DQGFKDQJHWKH1HZYDOXHWR*ZKHUH*
UHIHUVWR\RXUXVHUJURXSQXPEHU
If every group uses their own group number for the New Value field,
all groups will be independent of one another.
&KRRVHWKH6DYHEXWWRQDQGOHDYHWKHVFUHHQ

request number in the display, then choose the Continue Enter button.
SAP AG BC601 11-31

1-3 In the second step, ensure that your workflow recognizes the event
old_material_changed as a triggering event, and that the event manager can
transfer the object reference into your workflow as an import variable. This object
must be saved in a workflow container element.
When inserting tasks into the workflow, task container elements that did not
appear in the workflow container were automatically created. Therefore, the
workflow already contains a container element that refers to the object type
Y##MARA. The element is, however, not yet in a position to receive data from
outside the workflow.
1-3-1 Call your workflow in the change mode. Flag the workflow container
element that refers to Y##MARA as Import and Mandatory .
'HYHORSPHQW!'HILQLWLRQ7RROV!:RUNIORZ%XLOGHU
,QWKHQDYLJDWLRQDUHDFOLFNWKH:RUNIORZFRQWDLQHUEDU
7KHYDULDEOHVRIWKHZRUNIORZFRQWDLQHUDUHGLVSOD\HG
'RXEOHFOLFNWKHFRQWDLQHUHOHPHQWWKDWUHIHUVWR\RXUREMHFWW\SH
<0$5$PD\EHGLVSOD\HGDV%86B*URXSBRU
0DWHULDOB*URXSB
,QWKH$WWULEXWHVVHFWLRQVHOHFWWKHUDGLREXWWRQVIRU,PSRUWDQG
0DQGDWRU\
,IQHFHVVDU\FRS\WKHQDPHRIWKHFRQWDLQHUHOHPHQWLQWRWKH
'HVFULSWLRQILHOG
$FWLYDWHDQGVDYH\RXUZRUNIORZGHILQLWLRQ
<RXQRZKDYHDYDULDEOHWKDWFDQUHFHLYHWKHREMHFWUHIHUHQFHIURPWKH
HYHQWPDQDJHU
1-4 The next step is to create the event old_material_changed in your workflow.You
need to ensure that this event transfers the material object and the name of the user
modifying the material into the workflow container.
1-4-1 Enter a triggering event into the workflow. The object is Y##MARA and the
event Old_Material_Changed.
*RWRWKH:RUNIORZ%XLOGHUEDVLFVFUHHQE\FKRRVLQJWKHPHQXRSWLRQ
*RWR%DVLFGDWD
&KRRVHWKH6WDUWWDESDJH
SAP AG BC601 11-32

)LHOG1DPH ,QSXW'DWD
Object type Y##MARA
Event Old_Material_Changed
3UHVVWKH(QWHUNH\
&OLFN%LQGLQJ'HILQLWLRQ
7KH7DVN&RQWDLQHUHOHPHQW
,QLWLDWRU
VKRXOGUHFHLYHLQIRUPDWLRQIURP
WKH(YHQW&RQWDLQHUHOHPHQW B(97B&5($725
7KH7DVN&RQWDLQHUHOHPHQW
0DWHULDOBUHIHUHQFH
VKRXOGUHFHLYH
LQIRUPDWLRQIURPWKH(YHQW&RQWDLQHUHOHPHQW B(97B2%-(&7
=0$5$
&RUUHFWWKHELQGLQJLIQHFHVVDU\
1-4-2 Once you have defined a triggering event, you must activate it. Activate the
event linkage for this triggering event. Return to the Workflow Builder to
check. Activate the workflow.
7DESDJH6WDUW
&OLFNWKHUHGUKRPEXVLQWKHOLQHFRQWDLQLQJWKHWULJJHULQJHYHQW
(QWU\ILHOGWRWKHIDUOHIW$FWLYHQRW$FWLYH
5HWXUQWRWKH:RUNIORZ%XLOGHUEDVLFVFUHHQDQGDFWLYDWHWKHZRUNIORZ
SAP AG BC601 11-33

1-5 Another way to activate the linkage of a workflow is to directly modify the Event
Linkage Table. The table contains a record for each triggering event and each
workflow that it may start. Check this table for your new triggering event.
1-5-1 Find the entry for your event and display the details.
What is the type linkage activated flag for?:
______________________________________________
7RROV!%XVLQHVV:RUNIORZ!'HYHORSPHQW!'HILQLWLRQ7RROV!
(YHQWV!(YHQW/LQNDJHV
'RXEOHFOLFN7\SH/LQNDJHV
8VHWKH3RVLWLRQEXWWRQWRVHOHFW\RXUREMHFWW\SH)LQDOO\FKRRVH
*RWR'HWDLOV
7KH7\SHOLQNDJHDFWLYHIODJLQGLFDWHVWKDWWKHHYHQWOLQNDJHLV
DFWLYDWHG7KLVFKHFNER[PXVWEHVHOHFWHGLQWKHSURGXFWLYHV\VWHP
1-6 Now you can test your event driven workflow.
1-6-1 Change your material master (Transaction=MM02). This time enter your
group ID '
G##'in the Old Material field.
1-6-2 Check your Business Workplace. Do you see your work item?
SAP AG BC601 11-34

:RUNIORZ:L]DUGV
&RQWHQWV
l :RUNIORZ:L]DUGV
l 8VLQJZL]DUGVWRVLPSOLI\WKHZRUNIORZ
HGLWRU
SAP AG 1999
SAP AG BC601 12-1

:RUNIORZ:L]DUGV8QLW2EMHFWLYHV
l )LQGRXWZKHWKHUDZL]DUGPDWFKHV\RXUEXVLQHVV
VFHQDULR
l 8VHWKH:RUNIORZ:L]DUGWRFUHDWHDFRPSOHWH
ZRUNIORZGHILQLWLRQ
l 8VHWKH:RUNIORZ%XLOGHUZL]DUGV
SAP AG 1999
SAP AG BC601 12-2

SAP AG 1999
SAP AG BC601 12-3

:RUNIORZ:L]DUGV%XVLQHVV6FHQDULR
l $EXVLQHVVSURFHVVLVUHDG\WREHLPSOHPHQWHG
l :L]DUGVFDQVXSSRUW\RXZKHQVSHFLI\LQJD
ZRUNIORZGHILQLWLRQ
l )LQGRXWLIDQGKRZZL]DUGVFDQKHOS
l )LQGRXWZKLFKZL]DUGVDUHSURYLGHG
SAP AG 1999
SAP AG BC601 12-4

:KDW0DNHV:L]DUGV(DVLHU%HWWHUWKDQ1RUPDO7UDQVDFWLRQV
l :L]DUGVEULQJWRJHWKHUGRFXPHQWDWLRQDQGIXQFWLRQVE\
n $VNLQJRQO\DIHZTXHVWLRQVRQHDFKVFUHHQ
n 3URYLGLQJDOOLQIRUPDWLRQUHTXLUHGWRDQVZHUWKHTXHVWLRQV
l :L]DUGVHQVXUHDOOGDWDLVPDLQWDLQHGFRQVLVWHQWO\
l :L]DUGVGRQRWRYHUORDGWKHXVHUZLWKLQIRUPDWLRQ
SAP AG 1999
n Normal transactions: Creating a workflow without using wizards.

n Why do we need wizards? What is the objective? Who can use wizards?
Wizards are designed to make complex transactions and processes easier.
Wizards cannot do everything. Instead, they are specific to one task and provide all you need to
complete that task successfully. They also leave out irrelevant information and have very simple
screens.
Wizards are provided for both professionals andbeginners.
n Important: If you have to manage a lot of separate objects, you are likely to forget one. Wizards
ensure overall consistency.
SAP AG BC601 12-5

'R:H1HHG:RUNIORZ:L]DUGV"
,I\RXUEXVLQHVVSURFHVVLVUHDG\WREHLPSOHPHQWHG
V
RXU
<RXFDQXVHWKH:RUNIORZ%XLOGHUDQGLPSOHPHQW
WKHSURFHVVIURPVFUDWFK +
<RXFDQILQGFRS\DQGDGMXVWDZRUNIORZ RX UV
WHPSODWH +
<RXFDQILQGD:RUNIORZ:L]DUGWKDWGRHVWKLV
X WHV
0LQ
ZRUNIRU\RX
SAP AG 1999
n The implementation of workflow definitions takes some time. You have to define container
elements, insert steps, create bindings, assign agents, and, most importantly, define the flow logic.
n The flow logic for approval procedures (notification of absence, and so on.), circulars, and other
typical processes is always quite similar.
n If an experienced workflow developer has already implemented a workflow definition, such as the
approval of a notification of absence, they can use their experience or even the existing process
definition (as a template).
n But what if you are not an experienced workflow developer? Do you always have to start from the
beginning again, making all the mistakes that have been made by so many others? No! If you can use
the knowledge of a very experienced developer, you can save time and money.
n Therefore, we have integrated the knowledge and experience of our developers into the workflow
system and generated typical workflow definitions for you.
n Obviously, we cannot cover every occasion, but you can always change the generated workflow
definition.
SAP AG BC601 12-6

'LIIHUHQFHV%HWZHHQ6$37HPSODWHVDQG:L]DUGV
6$3:RUNIORZ7HPSODWHV
:RUNZLWKDVSHFLILF
REMHFWW\SH
+ DYHWREHFRSLHGDQG
DGMXVWHGFRQWDLQHUHOHPHQWV
ELQGLQJDQGVRRQ
:RUNIORZ:L]DUGV
*HQHUDWHZRUNIORZGHILQLWLRQV
IRUDQ\REMHFWW\SH
3URFHVVORJLFFDQEHDGMXVWHG
VLPSO\E\DQVZHULQJTXHVWLRQV
3URYLGHVLPSOHGLDORJDQGJXLGH
\RXWKURXJKSURFHVVHV
SAP AG 1999
n Workflow Wizards generate workflow definitions, but they can be changed with the Workflow
Builder like any workflow definition.
n Important:The Workflow Wizards themselves are workflow definitions. If you execute a wizard, a
workflow is executed. This allows you to leave a Workflow Wizard without losing data (except the
current screen) and to restart the Workflow Wizard. Whenever you call the Workflow Wizard
Explorer, it checks if there are any incomplete Workflow Wizards and allows you to finish them.
n Background: We started to develop the concept of Workflow Wizards in 3.0C. We began by thinking
about the book Design Patterns - Elements of Reusable Object-Oriented Software' by the Gang of
Four' (Gamma, Helm, Johnson and Vlissides) and tried to adopt the main concept for process
definitions.
The main aim of these authors is to publish the knowledge of experienced software developers in
order to help other programmers. They call this knowledge "Design Patterns". We call our
knowledge "Workflow Wizards" and do not only propose a solution that can be implemented.
We also provide a component that generates workflow definitions according to your
requirements.
SAP AG BC601 12-7

:RUNIORZ:L]DUGV$UH)RXQGLQWKH:RUNIORZ:L]DUG
([SORUHU
/RRNLQWKH:RUNIORZ:L]DUG
([SORUHULI\RXZDQWWR
LPSOHPHQW
$SSURYDOSURFHGXUHV
&XVWRPL]LQJ:L]DUGV
&LUFXODUVIRUIRUZDUGLQJREMHFWV
6LPSOHVHTXHQWLDORU
SDUDOOHOZRUNIORZGHILQLWLRQV
5HDGWKHGRFXPHQWDWLRQFDUHIXOO\DQG
GHFLGHLIRQHRIWKHZL]DUGVPHHWV\RXU
UHTXLUHPHQWV
SAP AG 1999
n There is now an improved user interface for accessing the Workflow Wizards. Each wizard has a
short description, which is displayed in the lower part of the screen when the user clicks on the
wizard text. The HTML documentation is accessed using a pushbutton in the tree.
n The documentation is no longer divided up into four documentation sections. This enables users to
access the whole documentation more quickly.
SAP AG BC601 12-8

8VLQJ:RUNIORZ:L]DUGV
l )LQGWKHULJKW:RUNIORZ:L]DUG
l 5HDGWKHGRFXPHQWDWLRQ
l 6WDUWWKHZL]DUGE\FKRRVLQJ&UHDWHZRUNIORZ
GHILQLWLRQ
l 5HOHDVH'HFLGHZKHWKHUWR
n 'LVSOD\ZRUNIORZGHILQLWLRQGXULQJJHQHUDWLRQ
GRQRWFKRRVHWKLVRSWLRQ
n $FWLYDWHZRUNIORZGHILQLWLRQFKRRVHWKLVRSWLRQ
n &ODVVLI\WDVNDVJHQHUDOWDVNFKRRVHWKLVRSWLRQ
l $QVZHUDOOTXHVWLRQV
SAP AG 1999
n You have found the Workflow Wizard closest to your requirements - what do you do now?
n Start the Workflow Wizard by choosing Create workflow definition'and answer the prompts that
follow.
SAP AG BC601 12-9

:RUNIORZ:L]DUGV([DPSOH
&DQZHXVHDZL]DUGWRLPSOHPHQWWKHEXVLQHVV
VFHQDULRRIDSSURYLQJDQRWLILFDWLRQRIDEVHQFH"
l 6WDUWWKH:RUNIORZ:L]DUG([SORUHU
l )LQGWKHGLIIHUHQWDSSURYDOSURFHGXUHV
n &DUHIXOO\UHDGWKHSUREOHPGHVFULSWLRQRIHDFKZL]DUG
w <RXRQO\QHHGWRGRWKLVRQFH
n )LQGWKHZL]DUGFDOOHG+ LHUDUFKLFDO
n 6WDUWWKLVZL]DUG
SAP AG 1999
n Approval object type

Which object type is to be approved in this procedure? We want to approve Formabsenc'
.
n Number of approval levels (= number of agents involved)
How many agents have to approve the object (in this case '
Formabsenc'
)? We only need one agent.
n Exclude initiator of decision
In most approval procedures, you want to prevent objects from being released by the creator.
n Approval task
Which task is to be used to approve the notification of absence? We can choose any task that refers
to Formabsenc.Approve' . The system checks if agents are assigned to the task and if the task has
results such as approved'or rejected'- if not, the system does not accept the task.
n Optional: Select agent
If not all possible agents are to receive the work item, an agent can be specified.
n Select approval result
Since the wizard works with any object type, it does not know which result is returned by the object
method (for example, ' A'for '
approved'or '0'for 'approved' ).
SAP AG BC601 12-10

:RUNIORZ:L]DUGV5HVXOW3DUW,
,QLWLDOL]H$SSURYDO&RXQWHU
:RUNIORZFRQWDLQHU
ZLWK

$SSURYDO&RXQWHU
([FOXGHLQLWLDWRUIURPGHFLVLRQ
([FOXGHG$JHQWV
$SSURYDO([FOXGHDSSURYHUIURP
IXUWKHUGHFLVLRQVDGGWR
H[FOXGHGDJHQWV
1R <HV
6XEWUDFWIURP$SSURYDO&RXQWHU
QRZLWLV
$GGDSSURYLQJDJHQWWR
([FOXGHG$JHQWV
3DUW,,
SAP AG 1999
n First, the process initializes the ApprovalCounter with 1'(there is only one approval step).
n Then, the _WF_Initiator is added to the container element ExcludedAgents to exclude the creator of
the object from the approval decision.
n The next action is to find the valid agent(s) for the approval. The ExcludedAgents table is used to
exclude the agents that are not to be involved in the approval decision (again).
n If the notification of absence is approved, '
1'is subtracted from ApprovalCounter (current value: '
0')
and the approving agent is entered in the ExcludedAgents table so that they are no longer involved in
this approval process.
n In the event of rejection, the process is finished anyway. No further action is required for the
ApprovalCounter. If the ApprovalCounter is not 0' , the notification of absence is rejected.
SAP AG BC601 12-11

:RUNIORZ:L]DUGV5HVXOW3DUW,,
3DUW,
:RUNIORZFRQWDLQHU (YDOXDWHDSSURYDOVWDWXV
$SSURYDO&RXQWHU $SSURYDO&RXQWHU "1RWLILFDWLRQRI
DEVHQFHDSSURYHG"
([FOXGHG$JHQWV
$SSURYDO5HVXOW
Yes No
$VNFUHDWRULIWKH\ZDQWWRFKDQJH
6HW$SSURYDO5HVXOWWR$
RUGHOHWHWKHQRWLILFDWLRQRIDEVHQFH
$SSURYHG
Flag set
Delete Change
6HQGHPDLOWRFUHDWRURI
6HW$SSURYDO5HVXOWWR'
'HOHWHGRU&&KDQJH
Mail sent Flag Flag set
set
SAP AG 1999
n After the real'approval process has been finished, the results are evaluated.
n First, we check if all agents (in this case only one) have approved the request. The value of the
container element ApprovalCounter must be 0'so that the approval is recognized. All other values
are interpreted as rejection.
n If the notification of absence was approved, the value A'is assigned to the container element
ApprovalResult to show that the result was positive. An e-mail is then sent to the _WF_Initiator.
n If the notification of absence was rejected (ApprovalCounter <> 0' ), we ask the _WF_Initiator,
using a User Decision, if they want to change or delete the request. In each case, we set the
ApprovalResult to D'or C'in order to have the option of adding flow logic.
n Ensure that the following notes exist in your system:
0097933 '
WF Wizards: Wizards are not executable
0097188 '
WF Wizards: DYNAMICCIRCULAR creates incor. WF def.
0093507 '
WF Wizards: CIRCULAR generates incor. WF definit.'
0097180 '
WF Wizards: Modelled date monitoring
0082308 '
WF Wizards: CIRCULAR terminates'
n Report any problems with wizards. Wizards should be self-explanatory.
SAP AG BC601 12-12

,PSRUWDQW:L]DUGVWR6LPSOLI\WKH:RUNIORZ%XLOGHU
,QFOXGH([HFXWHIRUP
,QFOXGH&DOOWHVWSURFHGXUH&$77
0RGHOGHDGOLQHPRQLWRULQJ
,QFOXGH&UHDWHREMHFWUHIHUHQFH
,QFOXGH([HFXWHUHSRUWMRE
,QFOXGH&KRRVHDJHQW
SAP AG 1999
n Execute report
Integration of a step in the workflow definition that calls any report in the R/3 System. You can
specify the variant that is to be used. (The report can be executed by a user, or the system can
execute the report and place the result as an ALI list in any Business Workplace folder.)
n Model deadline monitoring
Integration of a step that is monitored by the system and executed when the deadline is reached.
n Call test procedure (CATT)
Integration of a step that calls any test procedure. You can start the test procedure and transfer data
(test procedure with import parameters) and call the data after the test procedure is completed (test
procedure with export parameters).
n Execute form
Integration of a step that is used to call a SAPforms form.
n Choose agent
Integration of a step in order to dynamically choose agents from a number of possible agents at
runtime.
SAP AG BC601 12-13

:L]DUGV([HFXWLRQRI5HSRUWV
:KDWLQSXWLVUHTXLUHG"
Report
Optional: Variant
Operation mode: Dialog processing (with or without selection
screen) or background processing (create ALI = ABAP list
and store in Business Workplace folder)
:KDWGRHVWKHZL]DUGGR"
Creates task with reference to report Execute_2
Classifies task as background task
or general task
Integrates task into the workflow definition and creates binding
SAP AG 1999
n Reports can be called in SAP Business Workflow without creating a separate object type. The
selection criteria obtain their values from the workflow container using the binding.
n A task is created using the wizard, the container definition of which corresponds to the input data of
the report. Therefore, the selection values from the workflow container can be transferred to the
wizard.
n A report can only have input parameters.
n ,PSRUWDQW QRWH
If additional parameters are inserted into the selection screen of the report or existing parameters are
deleted, the task including the report must be changed manually. You can, of course, always use the
wizard to create a new task.
SAP AG BC601 12-14

:L]DUGV([HFXWLRQRI7HVW3URFHGXUHV
:KDWFDQWKHWHVWSURFHGXUH&$77GR"

Automate WUDQVDFWLRQVin R/3 and R/2 Systems
Transfer parameters from and to transactions
:KDWLQSXWLVUHTXLUHG"
CATT procedure (test procedure, created using SCAT)
Naming of parameters (optional)
:KDWGRHVWKHZL]DUGGR"
Creates task using object method &DWW([HFXWH

Integrates task into the workflow definition and creates
binding from workflow container to task container
SAP AG 1999
n Unfortunately, SAP cannot anticipate and implement all object types required during a workflow
project. Either you implement the required object types yourself or you use one of the following
options for calling functions in the R/3 System without implementing an object type:
Integration of CATT procedures
Integration of reports
n The CATT task reflects the parameters of the test procedure exactly in its task container. A CATT
procedure can have input and output parameters.
n ,PSRUWDQWQRWH: If the CATT procedure included in a task is extended by the addition of parameters
(import or export) or if parameters are deleted, the task must be adapted manually or a new task
generated with the wizard.
n You generate CATT procedures with transaction SCAT by executing the following steps:
You record the required transaction and enter the basic data for the CATT procedure.
You designate fields on the various screens as input or output parameters.
n A CATT procedure can automate any transaction in the R/3 System (parameters can be transferred
and called again). Transactions can also be controlled in an R/2 System using CATT with SAP
Business Workflow.
SAP AG BC601 12-15

:RUNIORZZLWK&$77
7KHREMHFWW\SH&$77FDQVWDUWDQ\WHVW
SURFHGXUHLQWKH6$36\VWHP
<RXFDQLQWHJUDWHWKHWHVWSURFHGXUHLQDQ\
H[LVWLQJZRUNIORZLQDPDWWHURIPLQXWHV
<RXQRORQJHUQHHGWRGHILQH\RXURZQ
REMHFWW\SHVWRFDOOWUDQVDFWLRQV
<RXFDQFKDQJHWKHJHQHUDWHGSDUWRIWKH
ZRUNIORZGHILQLWLRQDVUHTXLUHG
SAP AG 1999
SAP AG BC601 12-16

&$77:RUNIORZ6FHQDULR
l 6WHS &UHDWHD&$77SURFHGXUHIRUWUDQVDFWLRQ68
6HWWKHLPSRUWSDUDPHWHU
7HVWWKH&$77SURFHGXUHFKHFNWKH&$77ORJILOHV
l 6WHS &UHDWHZRUNIORZWHPSODWHLQWKH:RUNIORZ%XLOGHU
l 6WHS,QFOXGHWKHFUHDWHG&$77SURFHGXUHXVLQJZL]DUG
9HULI\DJHQWDVVLJQPHQW
'HILQHZRUNIORZLPSRUWSDUDPHWHU
l 6WHS &UHDWHDXVHUGHFLVLRQDWWKHVWDUWRIWKHZRUNIORZ
l 6WHS7HVWWKHZRUNIORZ3URYLGHLQSXWGDWD
l 6WHS &KHFNWKH&$77ORJILOH
SAP AG 1999
n At first glance, a CATT procedure appears to be like a background step.

However, it is actually a dialog step. The user who executes the user decision is also the agent of the
CATT step.
n Three prerequisites have to exist in R/3 in order for a CATT procedure to run correctly:
CATT procedures have to be permitted in general
The user who executes the CATT has to have general CATT authorization
The user has to have specific authorization for the specific CATT
SAP AG BC601 12-17

6WHS&UHDWH&$773URFHGXUH
l &KDQJHRZQXVHUGDWDV\VWHPXVHUSURILOH
l &$77([WHQGHG
0HQX7RROV$%$3:RUNEHQFK7HVW7HVW:RUNEHQFK

7UDQVDFWLRQ6&$7

l (QWHUDQDPHIRUH[DPSOH=68
l &KRRVHWKH7&'EXWWRQ5HFRUGWUDQVDFWLRQ
l (QWHUWUDQVDFWLRQ68DQGFKRRVH5HFRUG
l &KDQJHWKHHQWULHVIRU%XLOGLQJ)ORRU5RRPQR
l 6DYHDQGFKRRVHWKH(QGUHFRUGLQJEXWWRQ
l 6DYHWKH&$77SURFHGXUHDQGH[LWWKHDSSOLFDWLRQ
SAP AG 1999
SAP AG BC601 12-18

6WHS&$77,PSRUW3DUDPHWHUV
l &KRRVHWKHLQLWLDOVFUHHQLQWUDQVDFWLRQ6&$7

&OLFNRQWKH&KDQJHEXWWRQ
)LQGIXQFWLRQ7&'DQGVFUHHQ6$3/688

l ,PSRUWSDUDPHWHUV
3RVLWLRQWKHFXUVRURQWKH5RRP)ORRU%XLOGLQJILHOGV

&KRRVHWKH,QVHUWLPSRUWSDUDPHWHUEXWWRQ

7KHVHILHOGVDUHWKHQGLVSOD\HGLQJUH\
6DYH\RXU&$77SURFHGXUH

l 6WDUW\RXUWHVWE\FKRRVLQJWKH([HFXWHEXWWRQ

3URYLGHWKHSDUDPHWHUYDOXHVDQGFKRRVH&$77VHWWLQJV
6WDUWWKH&$77FOLFNWKH([HFXWHEXWWRQDJDLQ

&KRRVH(QWHU!RQHYHU\VFUHHQWRQDYLJDWHWKURXJKWKHWUDQVDFWLRQ

l &KHFNWKH&$77ORJILOHDQG\RXUQHZGDWD
SAP AG 1999
SAP AG BC601 12-19

6WHS&$77:RUNIORZ:L]DUG
l &DOOWKH:RUNIORZ%XLOGHU
:RUNIORZQDPH=68B:)

&KRRVHWKH:RUNIORZVWDUWHGHYHQW

&KRRVH:L]DUGV!,QFOXGH&DOOWHVWSURFHGXUH&$77

([HFXWHWKHIROORZLQJVWHSV

w 6WDUWVWHS &RQWLQXH!
w 7HVWSURFHGXUH (QWHU\RXU&$77IRUH[DPSOH=68
w 3DUDPHWHUV 7KH&$77LPSRUWSDUDPHWHUVDUH
SURSRVHGDQGFUHDWHGDVZRUNIORZ
FRQWDLQHU
w %DVLFGDWD
$EEUHYLDWLRQ =68

1DPH &$77SURFHGXUHJURXS
w &RPSOHWLRQVWHS 'RQH!
SAP AG 1999
SAP AG BC601 12-20

6WHS)XUWKHU:RUNIORZ$FWLYLWLHV
l &DOOWKH&$77ZRUNIORZVWHS
l &KHFNWKHELQGLQJ
l $VWKHDJHQWFKRRVH
([SUHVVLRQDQGWKHZRUNIORZLQLWLDWRU B:)B,1,7,$725
l 'HILQHWKHXQGHUO\LQJWDVNDVDJHQHUDOWDVNDQGUHIUHVK
WKHLQGH[
l 6DYH\RXUZRUNIORZDQGUHWXUQWRWKH:RUNIORZ%XLOGHU
l 6HWWKHQHZZRUNIORZFRQWDLQHUHOHPHQWVWR,PSRUWDQG
0DQGDWRU\
l &KHFNDQGDFWLYDWHWKHZRUNIORZ
SAP AG 1999
SAP AG BC601 12-21

6WHS,QVHUW8VHU'HFLVLRQ
l ,QVHUWXVHUGHFLVLRQDWWKHVWDUWRIWKHZRUNIORZ
'R\RXZDQWWRVWDUWWKH&$77SURFHGXUH"

'HFLVLRQ<HV1R
As the agent, choose Expression and the workflow initiator

(The system will use this user later to start the CATT)
l 0RYHWKH&$77ZRUNIORZVWHSWRWKH<HVEUDQFKRIWKHXVHU
GHFLVLRQ

6HOHFWWKH&$77VWHS

5LJKWPRXVHEXWWRQ&XW

6HOHFWWKH<HVEUDQFK
5LJKWPRXVHEXWWRQ3DVWH

l &KHFNDQGDFWLYDWHWKHZRUNIORZ
SAP AG 1999
SAP AG BC601 12-22

:RUNIORZ:L]DUGV6XPPDU\
l :L]DUGVDUHWKHUHWRKHOS\RX
l :RUNIORZ:L]DUGVDUHIRXQGLQWKH
:RUNIORZ:L]DUG([SORUHU
l /RRNLQWKH:RUNIORZ%XLOGHUIRU
ZL]DUGVWKDWFDQKHOS\RXIRUVKRUW
VHFWLRQVLQWKHZRUNIORZGHILQLWLRQ
SAP AG 1999
SAP AG BC601 12-23

([HUFLVHV
8QLW:L]DUGV
7RSLF:RUNIORZ:L]DUGV

Find the Workflow Wizard that meets your requirements
Use the Workflow Wizard to create a complete workflow definition
The first steps have been completed. The business process has been
designed and is ready for implementation. Wizards can support you when
specifying a workflow definition. You must learn how and when wizards
can help you. You need to know what type of wizards are available to
simplify the procedure for workflow definition.
$SSURYDOSURFHGXUH
1-1 You have already learned how an approval procedure is created for a notification of
absence. The Workflow Builder played a key role in this procedure. The
implementation time can now be reduced by using a Workflow Wizard.
First, you have to find the Workflow Wizard that matches your business scenario in
the :RUNIORZ:L]DUG([SORUHU.
The Workflow Wizards have to be activated before you can use them.
The instructor has already activated these wizards in the training system.
You do NOT, therefore, have to activate them now.
7KHH[DPSOHLQWKHSUHVHQWDWLRQVOLGHVXVHVWKHVDPHZL]DUG
As you already know, Workflow Wizards are also workflows. Workflows
can be interrupted and continued later. The Workflow Wizard Explorer
contains all started and unfinished Workflow Wizards. These wizards can
be continued at any time from the Explorer. You can also delete an active
wizard. During this exercise, you should press the "Return" key if a
dialog box indicating an unfinished Workflow Wizard appears.
SAP AG BC601 12-24

A hierarchical approval procedure has to be created for this exercise. The
essential feature of this variant is that one user must agree initially before
the next user can make a decision. Each agent has the option of rejecting
the request and, therefore, completing the entire procedure.
Since the workflow can be completed by any agent, it is important that
the workflow passes through lower positions in the hierarchy first and
higher positions last. It would not make sense for a managing directors
decision to be declared null and void by a department head, for example.
This logical sequence cannot be checked by the Workflow Wizard.
Therefore, it has to be defined correctly by the user.
1-1-1 To find the appropriate Workflow Wizard, expand all folders under
$SSURYDOSURFHGXUH in the tree structure and display the documentation for
each wizard.
1-1-2 Start the Workflow Wizard that meets your requirements by choosing the
"&UHDWHZRUNIORZGHILQLWLRQ" button
1-1-3 The wizard begins and various questions are displayed. Answer using the
following parameters:
Number of approval levels = 1
Use the object FORMABSENC
On the first screen, +LHUDUFKLFDODSSURYDOSURFHGXUH, you have to

deselect the option 2QO\REMHFWW\SHVWKDWVXSSRUWLQWHUIDFH,)$33529(.
If this option is selected, only object types that support the specified
interface are displayed. 2EMHFWW\SH)250$%6(1&GRHVQRWVXSSRUW
LQWHUIDFH$33529( If no option is selected, the contents of the entire
Business Object Repository are displayed.
On the second screen, 7DVNIRUDSSURYDOIRUOHYHO, you have to deselect

the option 2QO\WDVNVWKDWUHIHUWRWKHPHWKRG$33529$/ because the
approval method for object type )250$%6(1&( is called $33529(.
1-1-4 When the Workflow Wizard has completed processing, you are still in the
Wizard Explorer.
Choose (QYLURQPHQW-> 7DVNV to go to the Workflow Builder for the
generated workflow.
1-1-5 Check the workflow.
1-1-6 While in the Workflow Builder, open the workflow container and define the
element )250$%6(1&as a mandatory import parameter. Activate your
workflow.
1-1-7 As the user BC601-##, fill out a new notification of absence and then start
the generated workflow manually. Specify the number of this notification of
absence as an input parameter. Afterwards, check your manager s worklist.
SAP AG BC601 12-25
&LUFXODU2EMHFW)RUZDUGLQJ
2-1 You have now completed your first wizard. Wizards can, however, do more.
Circulars are often used within an enterprise in the form of folders that are passed to
teams or departments.
Never design processes like this from scratch! Wizards for generating
workflow definitions for circulars are also provided by SAP.
Open the Workflow Wizard Explorer and look in the &LUFXODU folder.
This section contains the following wizard types:
Circular
This wizard creates a workflow definition that routes an object
through a number of organizational units or positions. In the
workflow wizard definition, you define this number and specify the
recipients.
Ad hoc: Dynamic circular
This wizard creates a workflow definition as above, except the
number of recipients is assigned at runtime.
Both wizards have the same disadvantage: They forward objects
sequentially.
The following two wizards have the same features as the above wizards
but they route the object in parallel to all the recipients who have been
assigned.
Ad hoc: Dynamic parallel circular
Parallel circular
2-1-1 To find the appropriate Workflow Wizard, open the &LUFXODU folder in the tree
structure and read the documentation.
For this exercise, you should use the Workflow Wizard &LUFXODU. This
wizard is ideal for beginners as it contains few options and all the
information you need about circulars.
2-1-2 Start the Workflow Wizard by positioning the cursor on the wizard in the tree
structure and choosing the "&UHDWHZRUNIORZGHILQLWLRQ" button.
SAP AG BC601 12-26

2-1-3 The wizard starts and various questions are displayed. For this exercise, use
object type 62)0 (RIILFHGRFXPHQW). This object type provides a 'LVSOD\
method (DISPLAY) (Important: The method has to be executed synchronously
and in dialog mode).
1RWHWKDWWKLVH[HUFLVHZRUNVZLWKGHDGOLQHPRQLWRULQJ
On the third screen, 'HDGOLQHPRQLWRULQJIRUFLUFXODU, you have to
activate deadline monitoring for the display steps.
&DXWLRQ Modeled deadlines usually contain a task that sends an e-mail.
This is only a suggestion - modify your deadline handling to suit your
needs.
2-1-4 Choose (QYLURQPHQW -> 7DVNV to go to the Workflow Builder after

the Workflow Wizard has completed processing.
Check the workflow.
2-1-5 Subsequent activities:

At the start of your workflow, insert the new step for the task TS30000747. The
responsible agent is the workflow initiator.
Check all dialog steps and their tasks for agent assignment.
Define "Import" and "Mandatory" for the container element SOFM.
Add agent assignment for the workflow definition so you can start this
manually.
Activate your workflow again and test it. You have to refresh the organization
before you can test your workflow.
SAP AG BC601 12-27

6ROXWLRQV
8QLW:L]DUGV
7RSLF:RUNIORZ:L]DUGV
$SSURYDOSURFHGXUH
1-1 You have already learned how an approval procedure is created for a notification of
absence. The Workflow Builder played a key role in this procedure. The
implementation time can now be reduced by using a Workflow Wizard.
First, you have to find the Workflow Wizard that matches your business scenario in
the :RUNIORZ:L]DUG([SORUHU.
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW 'HILQLWLRQ7RROV:L]DUGV
'RXEOHFOLFN:RUNIORZ:L]DUG([SORUHU
The Workflow Wizards have to be activated before you can use them.
The instructor has already activated these wizards in the training system.
You do NOT, therefore, have to activate them now.
7KHH[DPSOHLQWKHSUHVHQWDWLRQVOLGHVXVHVWKHVDPHZL]DUG
As you already know, Workflow Wizards are also workflows. Workflows
can be interrupted and continued later. The Workflow Wizard Explorer
contains all started and unfinished Workflow Wizards. These wizards can
be continued at any time from the Explorer. You can also delete an active
wizard. During this exercise, you should press the "Return" key if a
dialog box indicating an unfinished Workflow Wizard appears.
A hierarchical approval procedure has to be created for this exercise. The

essential feature of this variant is that one user must agree initially before
the next user can make a decision. Each agent has the option of rejecting
the request and, therefore, completing the entire procedure.
Since the workflow can be completed by any agent, it is important that
the hierarchy is respected (lower positions first, higher positions last)
since it would not make sense for a managing directors decision to be
declared null and void by a department head. This logical sequence
cannot be checked by the Workflow Wizard. Therefore, it has to be
defined correctly by the user.
SAP AG BC601 12-28

1-1-1 To find the appropriate Workflow Wizard, expand all folders under
$SSURYDOSURFHGXUH in the tree structure and view the documentation for
each wizard.
'LVSOD\WKHGRFXPHQWDWLRQIRUHDFKZL]DUGE\FOLFNLQJRQWKHZL]DUG
QDPH,I\RXFKRRVHWKHTXHVWLRQPDUNEXWWRQDGMDFHQWWRWKHZL]DUG
QDPHWKHFRPSOHWHGRFXPHQWDWLRQLVGLVSOD\HG
$IWHUKDYLQJFDUHIXOO\UHDGWKHGRFXPHQWDWLRQ\RXGHFLGHWKDWWKH
:RUNIORZ:L]DUG+LHUDUFKLFDODSSURYDOZRUNIORZPHHWVWKH
UHTXLUHPHQWVIRU\RXUEXVLQHVVVFHQDULR
1-1-2 Start the Workflow Wizard that meets your requirements by choosing the
"&UHDWHZRUNIORZGHILQLWLRQ" button.
6WDUWWKH:RUNIORZ:L]DUG+LHUDUFKLFDODSSURYDOZRUNIORZE\FOLFNLQJ
RQWKHZL]DUGQDPHDQGFKRRVLQJWKH&UHDWHZRUNIORZGHILQLWLRQ
EXWWRQ
1-1-3 The wizard begins and various questions are displayed. Answer using the
following parameters:
- Use the approval object type FORMABSENC
- Number of approval levels = 1
- Select your manager as the agent for approval
7KH+LHUDUFKLFDODSSURYDOSURFHGXUHVFUHHQWKDWDSSHDUVQH[W
UHIHUVWRWKHREMHFWW\SH
5HPHPEHUWRHQWHUWKHREMHFW)250$%6(1&'HVHOHFWWKH2QO\
REMHFWW\SHVWKDWVXSSRUWLQWHUIDFH,)$33529(FKHFNER[
7KHQXPEHURIDSSURYDOOHYHOVVKRXOGEHVHWWR

2QO\RQHSHUVRQ
KDVWRDSSURYHWKHQRWLILFDWLRQRIDEVHQFH
7KH([FOXGHLQLWLDWRUIURPGHFLVLRQFKHFNER[VKRXOGEHVHOHFWHG
7KLVSUHYHQWVXVHUVIURPKDYLQJWRDSSURYHWKHLURZQQRWLILFDWLRQRI
DEVHQFH
On the first screen, +LHUDUFKLFDODSSURYDOSURFHGXUH, you have to

deselect the option 2QO\REMHFWW\SHVWKDWVXSSRUWLQWHUIDFH,)$33529(.
If this option is selected, only object types that support the specified
interface are displayed. 2EMHFWW\SH)250$%6(1&GRHVQRWVXSSRUW
LQWHUIDFH$33529(If no option is selected, the contents of the entire
Business Object Repository are displayed.
SAP AG BC601 12-29

7KH7DVNIRUDSSURYDOIRUOHYHOVFUHHQWKDWDSSHDUVQH[WUHIHUVWR
WKHVWHSWKDW\RXDUHLQVHUWLQJLQWKHZRUNIORZ
(QWHUWKHWDVNQXPEHU76IRU$SSURYHQRWLILFDWLRQRI
DEVHQFH
'HVHOHFWWKH2QO\WDVNVWKDWUHIHUWRWKHPHWKRG$33529$/
FKHFNER[
On the second screen, 7DVNIRUDSSURYDOIRUOHYHO, you have to deselect

the option 2QO\WDVNVWKDWUHIHUWRWKHPHWKRG$33529$/ because the
approval method for object type )250$%6(1&( is called $33529(.
You cannot choose this method if this option is selected.
7KH$JHQWIRUDSSURYDOIRUOHYHOVFUHHQWKDWDSSHDUVQH[WUHIHUVWR
WKHUHVSRQVLEOHDJHQWIRUH[HFXWLQJWKHVWHSWKDW\RXDUHLQVHUWLQJLQWR
WKHZRUNIORZ
$OOSRVVLEOHDJHQWVIRUWKHWDVNUHFHLYHWKHZRUNLWHPIRUDSSURYDO,I
\RXFKRRVH&RQWLQXHDOOSRVVLEOHDJHQWVUHFHLYHWKHZRUNLWHP'R
QRWGRWKLVLQVWHDGVHOHFWWKHXVHU,'RI\RXUPDQDJHU
7KH$SSURYDOUHVXOWIRUOHYHOVFUHHQLVGLVSOD\HG7KLVVFUHHQ
UHIHUVWREUDQFKLQJLQWKHZRUNIORZLIWKHQRWLILFDWLRQRIDEVHQFHLV
DSSURYHG
&KRRVH$SSURYHG
2QWKH&UHDWHZRUNIORZWHPSODWHVFUHHQWKDWDSSHDUVQH[WHQWHUWKH
EDVLFGDWDIRU\RXUZRUNIORZGHILQLWLRQ
(QWHUDQDEEUHYLDWLRQDQGDQDPHIRU\RXUZRUNIORZ
1-1-4 Choose (QYLURQPHQW -> 7DVNV to go to the Workflow Builder after the
Workflow Wizard has completed processing.
7KHJHQHUDWHGZRUNIORZGHILQLWLRQLVGLVSOD\HG
1-1-5 Check the workflow.
,QSDUWLFXODUFKHFNWKHDJHQWDVVLJQPHQWERWKRQWKHZRUNIORZOHYHODQG
WKHWDVNOHYHO
SAP AG BC601 12-30

1-1-6 While in the Workflow Builder, open the workflow container and define the
element )250$%6(1&as a mandatory import parameter. Activate your
workflow.
'RXEOHFOLFNRQWKHHOHPHQWIRU)250$%6(1&,QWKH$WWULEXWHV
VHFWLRQVHOHFWWKH0DQGDWRU\DQG,PSRUWSDUDPHWHUV
([LWWKH:RUNIORZ%XLOGHU&KDQJHVFUHHQDQGDFWLYDWH\RXUZRUNIORZ
5HWXUQWRWKH:RUNIORZ:L]DUG([SORUHUVFUHHQE\FKRRVLQJWKH
%DFNEXWWRQ
1-1-7 As the user BC601-##, fill out a new notification of absence and then start
this workflow manually. Specify the number of this notification of absence
as an input parameter. Afterwards, check your manager s worklist.
SAP AG BC601 12-31

&LUFXODU2EMHFW)RUZDUGLQJ
2-1 You have now completed your first wizard. Wizards can, however, do more.
Circulars are often used within an enterprise in the form of folders that are passed to
teams or departments.
$QREMHFWLVWREHIRUZDUGHGIURPRQHDJHQWWRDQRWKHUDQGDWWKHVDPHWLPHLW
KDVWREHHQVXUHGWKDWDOODJHQWVKDYHVHHQWKHREMHFW,WVKRXOGEHSRVVLEOHIRUDQ
5XVHUWRVHQGDSDUWLFXODUREMHFW0LFURVRIW:RUGGRFXPHQWEXVLQHVV
GRFXPHQWDQGVRRQVHTXHQWLDOO\WRVHYHUDOGHILQHGRUJDQL]DWLRQDOXQLWVLQWKH
56\VWHPVRWKDWWKH\FDQFKHFNWKHREMHFWDQGPDNHFRPPHQWV,IWKHREMHFW
UHPDLQVLQDZRUNOLVWIRUWRRORQJZLWKRXWEHLQJYLHZHGWKHLQLWLDWRURIWKH
FLUFXODULVLQIRUPHG
Never design processes like this from scratch! Wizards for generating
workflow definitions for circulars are also provided by SAP.
Open the Workflow Wizard Explorer and look in the &LUFXODU folder.
This section contains the following wizard types:
Circular
This wizard creates a workflow definition that routes an object
through a number of organizational units or positions. In the
workflow wizard definition, you define this number and specify the
recipients.
Ad hoc: Dynamic circular
This wizard creates a workflow definition as above, except the
number of recipients is assigned at runtime.
Both wizards have the same disadvantage: They forward objects
sequentially.
The following two wizards have the same features as the above wizards
but they route the object in parallel to all the recipients who have been
assigned.
Ad hoc: Dynamic parallel circular
Parallel circular
SAP AG BC601 12-32

2-1.1 To find the appropriate Workflow Wizard, open the &LUFXODU folder in
the tree structure and read the documentation.
8QGHU&LUFXODULQWKHWUHHVWUXFWXUHYLHZWKHGRFXPHQWDWLRQIRU
HDFKZL]DUGE\FOLFNLQJRQWKHZL]DUGQDPH,I\RXFKRRVHWKH
TXHVWLRQPDUNEXWWRQDGMDFHQWWRWKHZL]DUGQDPHWKHFRPSOHWH
GRFXPHQWDWLRQLVGLVSOD\HG
$IWHUKDYLQJFDUHIXOO\UHDGWKHGRFXPHQWDWLRQ\RXGHFLGHWKDWWKH
:RUNIORZ:L]DUG&LUFXODUPHHWVWKHUHTXLUHPHQWVIRUWKHEXVLQHVV
VFHQDULR
For this exercise, you should use the Workflow Wizard &LUFXODU. This
wizard is ideal for beginners as it contains few options and all the
information you need about circulars.
2-1-2 Start the Workflow Wizard by positioning the cursor on the wizard in
the tree structure and choosing the "&UHDWHZRUNIORZGHILQLWLRQ" button.
6WDUWWKH:RUNIORZ:L]DUG&LUFXODUE\FOLFNLQJRQWKHZL]DUGQDPH
DQGFKRRVLQJWKH&UHDWHZRUNIORZGHILQLWLRQEXWWRQ
2-1-3 The wizard starts and various questions are displayed. For this exercise,
use object type 62)0 (RIILFHGRFXPHQW). This object type provides a
'LVSOD\method (DISPLAY) (Important: The method has to be executed
synchronously and in dialog mode).
2QWKH2EMHFWW\SHIRUFLUFXODUVFUHHQHQWHUWKHREMHFWW\SH62)0
2IILFHGRFXPHQW
2QWKH7DVNIRUFLUFXODUVFUHHQHQWHUWKHWDVNIRUWKHFLUFXODU8VH
DWDVNWKDWUHIHUVWRWKH',63/$<PHWKRGRI62)08VH76
\RXKDYHWRHGLWWKLVWDVNVHSDUDWHO\DQGFODVVLI\LWDVDJHQHUDOWDVNVR
HYHU\6$3XVHULVDSRVVLEOHDJHQW
1RWHWKDWWKLVH[HUFLVHZRUNVZLWKGHDGOLQHPRQLWRULQJ
On the third screen, 'HDGOLQHPRQLWRULQJIRUFLUFXODU, you have to
activate deadline monitoring for the display steps.
&DXWLRQ Modeled deadlines usually contain a task that sends an e-mail.
This is only a suggestion - modify your deadline handling to suit your
needs.
SAP AG BC601 12-33

2QWKH'HDGOLQHPRQLWRULQJIRUFLUFXODUVFUHHQHQWHUWKHWLPH
SHULRGIRUGHDGOLQHPRQLWRULQJWKDWPHHWV\RXUUHTXLUHPHQWV
2QWKH:RUNIORZ:L]DUG([SORUHU&LUFXODUVFUHHQ\RXFDQDVVLJQ
WKHDJHQWVZKRDUHWRUHFHLYHWKHFLUFXODU6HOHFWWKHDJHQWUHTXLUHG
IURPWKHOLVWXQGHU$OODJHQWVDQGFKRRVHWKH$GGVHOHFWHGDJHQW
EXWWRQ
2QWKH&UHDWHZRUNIORZWHPSODWHVFUHHQWKDWDSSHDUVQH[W\RXFDQ
HQWHUWKHEDVLFGDWDIRU\RXUZRUNIORZGHILQLWLRQ
(QWHUDQDEEUHYLDWLRQDQGDQDPHIRU\RXUZRUNIORZ

development class = and choose the "Own requests" button.
Select your change request.
2QWKH&RPSOHWHZRUNIORZGHILQLWLRQVFUHHQFKRRVHWKH
&RPSOHWHEXWWRQ
2-1-4 Choose (QYLURQPHQW -> 7DVNV to go to the Workflow Builder after the
Workflow Wizard has completed processing.
Check the workflow.
2-1-5 Subsequent activities:

At the start of your workflow, insert the new step for the task
TS30000747. The responsible agent is the workflow initiator.
Check all dialog steps and their tasks for agent assignment.
Activate your workflow again and test it. You have to refresh the
organization before you can test your workflow.
SAP AG BC601 12-34

:RUNIORZDQGWKH,QWHUQHW
&RQWHQWV
l (OHFWURQLF)RUPV6$3)RUPV
l (DV\:HE7UDQVDFWLRQV
l :HEIORZ;0/EDVHG
l (PDLOQRWLILFDWLRQ
SAP AG 1999
SAP AG
SAP AG BC601 13-1

:RUNIORZDQGWKH,QWHUQHW8QLW2EMHFWLYHV
l 'HVFULEHKRZWKH,QWHUQHWSODWIRUPLQWHUDFWVZLWK
6$35
l /LVWWKHSRVVLELOLWLHVIRULQWHJUDWLRQZLWKZRUNIORZ
SAP AG 1999
SAP AG BC601 13-2


SAP AG 1999
SAP AG BC601 13-3

:RUNIORZDQGWKH,QWHUQHW%XVLQHVV6FHQDULR
l <RXUHQWHUSULVHXVHV6$3%XVLQHVV:RUNIORZ
$VZHOODVWKH5SRZHUXVHUV\RXZDQWWR
DOORZDOOXVHUVLQWKHHQWHUSULVHWRSDUWLFLSDWHLQ
EXVLQHVVSURFHVVHVIRUH[DPSOHLQVHOIVHUYLFH
VFHQDULRV
l <RXZDQWWRFUHDWHD:HELQIUDVWUXFWXUHWR
HQDEOHXVHUDFFHVVWRWKHEXVLQHVVIXQFWLRQVRU
l <RXDUHDPHPEHURIWKHSURMHFWWHDPWKDWKDV
EHHQJLYHQWKHWDVNRIOLQNLQJ6$3%XVLQHVV
:RUNIORZZLWK:HEWHFKQRORJ\
SAP AG 1999
SAP AG BC601 13-4

(OHFWURQLF)RUPV
FDQEHVHQWDXWRPDWLFDOO\WRDJHQWV
XVLQJDZRUNIORZ
Customer Data

DUHHDV\WRGHVLJQ
FDQEHHDVLO\GLVWULEXWHG
DQGXSGDWHGXVLQJD

VHUYHU

DUHHDV\WRVDYHDQG
DUHLQWHJUDWHGLQ5
DUFKLYH
! "
$# !% "
&' ()
KDYHPLQLPXP SURYLGHDQLQWHUDFWLYH
XVHUJXLGHDQGHQWU\
WUDQVSRUWWLPHV
FKHFN
(OHFWURQLFIRUPVDUHIDVWLQH[SHQVLYHDQGODUJHO\LPPXQHWRHUURUV
SAP AG 1999
n You can use electronic forms to:

Allow new users access to workflow
Exchange data with SAP Business Workflow
Create simple and individual interfaces
Use the existing mail infrastructure in your enterprise
n Forms are not:
a 1:1 mapping of complex SAP System transactions. They are intentionally simplified interfaces
suitable replacements for the SAP GUI or for simulating complex SAP System transactions
suitable for saving or managing business data
n The following forms are possible:
HTML form
Visual Basic form
Outlook form
Lotus Notes form.
n Visual Basic, Lotus Notes, and Outlook forms can be connected with SAP Business Workflow by
using SAPForms.
n For further information on SAPForms, see the documentation:
Basis - Business Management - SAP Business Workflow - Reference Documentation - Form
integration using SAPForms.
SAP AG BC601 13-5

$GYDQWDJHVRI6$3%XVLQHVV:RUNIORZDQGWKH
,QWHUQHW
l For the end user

*
Paper-free application with mulitmedia support
*
Simple screen layout
*
No SAPGUI on the PC
l For the implementation team

*
Generation of your own screens for workflow activities
*
Generation of SAP transactions
*
Generation of HTML templates
*
Generated HTML pages can be formatted
l For the customer

*
The business scenario is supported by Workflow process logic
*
BAPI or CATT procedures can be easily integrated
SAP AG 1999
SAP AG BC601 13-6

5&OLHQW6HUYHU$UFKLWHFWXUHZLWK,76
3UHVHQWDWLRQ
6$3*8, :HEEURZVHU
:HEVHUYHU
,QWHUQHW
WUDQVDFWLRQ
VHUYHU
$SSOLFDWLRQ
'DWDEDVH
SAP AG 1999
n The ,QWHUQHW7UDQVDFWLRQ6HUYHU,76extends the three-stage Client/Server structure of the SAP
System into the Internet.
n For the SAP System, the ITS and the Web server form an intermediate level between the application
level and the presentation level.
n For the Internet user, the ITS provides interactive HTML pages (generated at runtime).
n Simultaneous use of an SAP System with a SAPGUI and an Internet Transaction Server is easily
possible.
SAP AG BC601 13-7

:(%,QER[
SAP AG 1999
n The slide shows a representation of a WEB inbox.

If you are familiar with the worklist of the Business Workplace, you will find the Web Inbox easy to
use.
n The service displayed above is automatically created when installing the Internet Transaction Server,
and can be called using the name BWSP.
n From Release 4.6C onwards, each R/3 System can be processed incorporating the SAPGUI for
HTML.
This service has the name WEBGUI.
SAP AG BC601 13-8

*HQHUDWHG(DV\:(%7UDQVDFWLRQ
7KLVJHQHUDWHG(DV\
+C
-,/.1032
4D
45
76A
698E
:,@
<;>=D
3?>
?@?A;
,
,B4D
4
:(%7UDQVDFWLRQ
LVXVHGIRU
HQWHULQJDQHZ
FXVWRPHU
+C
-,/
B.1
F069
>8K
G8H2@I@J 0B
=
B5J 6AI:?<=B5
=
7KHWUDQVDFWLRQ
VWDUWVDZRUNIORZ
+C,/.F
16O
A;L<
@=@
<I@J M)=B
5J 6AID=<
@N/
)=B4
D4@JPLAI3
<8:
E,<I
D5 LQVWDQFH
H[HFXWHVD
ZRUNLWHP
SAP AG 1999
n You can use WEB forms to start workflows or to execute work items.
n When you start a workflow with a WEB form, no event is published. The form data is transferred
directly to the workflow container and the internal event Workflow started occurs.
n WEB forms can start workflow templates (WS).
Standard tasks (TS) can be used for processing forms.
SAP AG BC601 13-9

:RUNIORZ%LQGLQJ
Customer SAP
Sales Sales Sales
in the BAPI
support manager rep.
Internet CATT
Workflow container
Logical information flow
Import data at start
Data from workflow container before starting the work item
Data saved in workflow container after executing the work item
SAP AG 1999
n The logical information flow in SAP Business Workflow is controlled by the workflow container.
n At runtime, the data enters the workflow container, and is transferred to the individual steps of the
workflow.
SAP AG BC601 13-10

%LQGLQJ'HILQLWLRQDQG5XQWLPH
Transaction for starting

:RUNIORZ
a workflow
Workflow
container
,PSRUW
3URFHVV
Execute task )RUPWDVN

Task
container
:RUNIORZ ,PSRUW GLVSOD\

:RUNIORZ
Workflow Workflow
FKDQJH
container ([SRUW container
HQWHU
SAP AG 1999
n %LQGLQJDWWKHVWDUWRIDZRUNIORZ
When you start a workflow with a WEB form, no event is published.
The data is transferred directly from the form into the workflow container, and the workflow
starts with the first processing step.
Import elements are displayed on the form as "ready for input", and are then exported into the
workflow container.
Workflow templates and tasks can be started in this way
Recommendation: Only start workflow templates
n %LQGLQJZKHQDWDVNLVH[HFXWHG
The WEB form is a copy of the workflow container
Import elements are transported from the SAP System into the task container, and are displayed
on the form
Export elements are displayed as "changeable", and are then transferred from the form into the
workflow container
The underlying task must refer to the method FORM.HTMLprocess
SAP AG BC601 13-11

7DVN%DVHGRQ2EMHFW7\SH)250
7DVN76 TC6ON ,G;7,46ANP25J 6AI

U ;LAV2@I9J 5
4<WVPVXV
2EMHFWW\SH)250 )RUPLV d <

Q c L ,@I5
0HWKRG+70/3URFHVV FDOOHG
=B4D4@J LAI38G,<I5
$WWULEXWHV Y%Z[,<ID,<;=<N\5$=49]/^[6A;
=D0/5J _9J 5a`GLA;6A29b
R@,SD5
4
c e 6A;]gf 57,8hR@,/S5 iBRjJ 5N ,g6<k@5lD,

.m6A;]mJ 5$,38nJPIg5l,GJPI9o6S
c p 6jIL:5
,/SD5
4 i
q r ,B4<03;JXb5J 6AI
q +-635J kJ 0B=D5J 6AI
q r ,=3?ANsJPI,g8K6AI@J 56O;JPIL
SAP AG 1999
n Use the method HTMLProcess of the object type FORM for WEB forms.
n As with every task, you must maintain an agent assignment.
n As with every task, you must maintain notification texts.
n The flag Executable in the Internet is not applicable in Release 4.6C,
since all tasks can now be executed in the Internet.
SAP AG BC601 13-12

6FUHHQVDQG%LQGLQJ
Transaction Complete form

YABWS98700001H
Screen 50 Screen 150 Screen 200
Workflow Workflow container:

WS98700001 One element for each field
Task
Task container:
Transaction
One element for each screen field
YABTS98700009H
Approve
form Screen 100 Screen 200
Task Single-Step Task Container:

BAPI One element for each parameter
Create record
SAP AG 1999
n If you use an EASY WEB transaction to start a workflow, you should

Skip screen 50
Use screen 150 for data entry
Use the SAP screen 200 to display the started workflow instance ID
n If you use an EASY WEB transaction for processing a workflow, use
- Screen 100 for data entry.
n A correct URL for a service that calls a WEB form may look as follows:
http://<its-server>/scripts/wgare/<generated WEB transaction>/!?web_flag=x&~okcode=cont
n The parameter okcode=cont ensures that screen 50 is skipped.
SAP AG BC601 13-13

:HE7UDQVDFWLRQ
t)u>vxwBy z
System help
{ || { |~{ } { }}
,B`3,<;
Name of customer:
t)u>vxwBy z
System Help
{ || { |~{ } { }}
150
,QWHUQHW :HE
,76
Customer Meyer created
%URZVHU VHUYHU
200
VFUHHQ 5
WHPSODWH
+70/SDJH 6HUYLFH
+70/
%XVLQHVV
ILOHV WHPSODWHV
SAP AG 1999
n A Web transaction consists of three components:

Web-compatible SAP transaction
Service file
HTML business templates
n Web-compatible SAP transaction
Data display in simple screens
Support for synchronization by the ITS
n HTML business templates
Representation of the data displayed on the screens of an SAP transaction
Each screen has one template that is converted at runtime to one HTML page.
SAP AG BC601 13-14

3URFHGXUH0RGHO:RUNIORZ ,QWHUQHW
Where? What?
1. R/3: Define container for task

2. R/3: Generate www transaction
3. R/3: Insert form-based step in workflow
4. SAP@Web/se80: Define site definition

5. SAP@Web/se80: Create service for www transaction
6. SAP@Web/se80: Create HTML templates for screens
7. SAP@Web/se80: Transfer services & templates to IST
8. Test Re-Design (activities 1, 2, 5, 6, 7)

9. HTML editor: Fine setting for HTML pages
10. Web browser: Start workflow with specific URL
SAP AG 1999
n Step 3 can be skipped if you want to execute a workflow without using a form.
n If the workflow contains more than one form, you must repeat the process for every step.
n Exception:
The site definition must only be created once.
n From Release 4.6C onwards, sap@web Studio activities can be carried out within transaction SE80
of the R/3 System.
SAP AG BC601 13-15

1DPLQJ&RQYHQWLRQV
2 characters
1DPHVSDFHWHPSODWH $%
:RUNIORZWHPSODWH :6
Service
name =
6HUYLFH <$%:6+ Trans-
action
0RGXOHSRROZLWKVFUHHQ
6$30<$%:6+ name

+70/WHPSODWHV 6$30<$%:6+B+70/
6$30<$%:6+B+70/
6$30<$%:6+B+70/
6$30<$%:6+B+70/
SAP AG 1999
n To reserve namespaces for WEB transactions and the associated module pools, you need to define a
namespace template.
You can enter any 2 characters.
n You are recommended to use a general development class for the namespace template and the
generated WEB transactions.
SAP AG BC601 13-16

6$3#:HE6WXGLR
l Project-oriented approach
l Enables creation, management, maintenance, and
publishing of
3URMHFWV

6HUYLFHVWUDQVDFWLRQV

+70/ WHPSODWHVVFUHHQV
>B
6$3#:HE l Contains wizards for automatically creating the
6WXGLR
named files
l Can be installed on NT-based PCs
l You can download the ,76
and the 6$3#:HE6WXGLRfrom the Internet
homepage of SAPlabs in Palo Alto
l From Release 4.6C onwards, you can use
the Workbench for SAP@WEB Studio tasks
SAP AG 1999
n You use the 6$3#:HE6WXGLR to maintain all the components of a WEB transaction outside the
R/3 SAP System. This includes the following components:
Service files
HTMLBusiness templates
MIME objects for pictures, sound, videos, ...
Files with language-dependent place holders
n The SAP@Web Studio is a project-oriented tool. This means that developers create a local directory
for their project, where they store the different components of the WEB transaction. A project can
have more than one WEB transaction.
n There are wizards to help create new objects (services, templates).
n Objects are transferred to the ITS by publishing them.
n All objects maintained with the SAP@Web studio can be transferred to the R/3 SAP System
Workbench Organizer, and the R/3 transport system. They are then fully embedded in the R/3
development environment.
n The SAP@Web studio is installed using the IST, and runs on NT4.0 and above.
SAP AG BC601 13-17

6WUXFWXUHRIDQ+7735HTXHVW
p 69=D?
,<;
_>J 0B,K<JPN ,
-4,<;CT-,DO2D,B45
=9NPN e Z[=B5
, ,<I? TjaEfPI@b9259
T-,A2D,B45G
e ,<og4D,@;$_,<; e L<=57,
d Z=B5,
CR p bD=DL9, CR p bD=L<,m TOa U 25b@259

p 6<=?
R
- p 5
,8b9N =B5
,
N =@ILA2D=3 L<,?<,@bD,<I<?<,<I5>
SAP AG 1999
1. A user requests information from a WEB server (by clicking on a link or input URL)
2. The WEB server sends the request to the Wgate (Wgate is a part of the URL
(for example, http://myserver/scripts/wgate.dll/pzm1/! )
3. WGate converts the request to a form suitable for R/3, and sends it to the Agate. The AGate starts a
new transaction, or forwards the request to an already existing session. (In this case, step 4 is
skipped)
4. If a new session is started, the AGate loads the Service File to get the connection parameters (R/3
system, user, client,) and logs on to a new SAP System.
5. The data in the request is transferred to the input fields in the input screen. (Similar to a batch input
session)
6. The screen is processed in the R/3 SAP System, and a new screen is transferred to the Agate (the
screen is identified by the program name and the screen number).
7. Agate loads the relevant HTML template and replaces the place holders with the data from the R/3
SAP System.
8. The resulting HTML page is transferred to the Wgate.
9. WGate forwards the HTML page to the WEB server. It sends the page to the client (browser), from
which the request has come.
SAP AG BC601 13-18

([DPSOHRIDQ(DV\:(%7UDQVDFWLRQ
l &KDQJHZRUNIORZWHPSODWH
&DOO\RXU&$77ZRUNIORZ

&KDQJHLWWRDJHQHUDOWDVN

&KRRVHWKHPHQXRSWLRQ*RWR:HEWUDQVDFWLRQDQGH[HFXWH

WKHZRUNIORZ
l 6WDUWWKHQHZWUDQVDFWLRQIRUH[DPSOHQ<$%:6+
&RQWLQXHRQVFUHHQ

5HIUHVKWKH2UJ%XIIHU

(QWHUQHZGDWDIRUWKHURRP

7UDQVIHUDQGYHULI\WKHVWDUWHGZRUNIORZ

l &KRRVH<(6LQWKHXVHUGHFLVLRQ
l :DLWIRUD&$77VWDWXVPHVVDJH
l &KHFNWKHUHVXOWRIWKH&$77
SAP AG 1999
SAP AG BC601 13-19

:HEIORZ%XVLQHVV3URFHVVHVRQWKH,QWHUQHW
Option 1: Person triggers process using Web browser
Order
Company
Company Computer
Computer
"1999"
"1999" Status query manufacturer
6WDUW
SXUFKDVH
Company
Company RUGHU Computer
Computer
"200x"
"200x" manufacturer
manufacturer
(QG
QRWLILFDWLRQ
Option 2: Process - process communication using XML

SAP AG 1999
n 2SWLRQ:
Customer gives an order directly to a supplier in an external system.
The business processes are started as "subroutines".
n 2SWLRQ:
In a workflow-controlled business process, an XML-based task is called, which in turn starts a
workflow in an external system (receiver).
The data for the called workflow is transferred at the same time.
n The following combinations of calling and receving system are possible:
SAP non-SAP
non-SAP SAP
SAP SAP
n The SAP Business Connector is not needed for this scenario.
The workflow WEB activity generates the XML code independently.
n Customers who would like to become pilot customers should send an e-mail to the following
address: bpt@sap.com.
SAP AG BC601 13-20

6WDUWLQJ3URFHVV8VLQJ:HEIORZZLWK(QG
1RWLILFDWLRQ
Legend for XML operation:

Start Request
Direct response:
- Message received
- Process xy started
CreateProcessInstance
;0/ Start
End
ProcessInstanceStateChanged
(State = completed)
End
SAP AG 1999
n "6HQG": Web activity step (new step type in the Workflow Builder) with parameters:
URL of the external process
Reference workflow, whose container is used to generate XML messages
Format (Wf-XML or "without envelope")
Flag "Wait for end confirmation"
(Similar to the terminating event for an asynchronous method)
n "5HFHLYHU": Handling incoming XML documents
n Format for query and response is described in XML
n Queries and responses can be sent using the HTTP protocol
SAP AG BC601 13-21

6WDQGDUGL]LQJ;0/
l :RUNIORZ0DQDJHPHQW&RDOLWLRQ:I0&6WDQGDUG

l :I0&
2UJDQL]DWLRQIRUWKH6WDQGDUGL]DWLRQRI:RUNIORZ0DQDJHPHQW

6\VWHPV
$SSUR[PHPEHUV:)06PDQXIDFWXUHUVXVHUV

FRQVXOWDQWVDQDO\VWV
SAP AG 1999
n The interface was redefined by the Workflow Management Coalition (WfMC).

SAP is one of the first firms to implement it.
n If you would like support for a pilot project, please contact the following address:
bpt@sap.com
n The members of the WFMC include, among others:
Computron Software Inc., DEC (COMPAQ), FileNet Corporation, Fujitsu Software Corporation,
Hitachi Ltd., IBM UK Ltd. , IDS Scheer AG, Microsoft Corporation, SAP AG, Sun Microsystems,
Toshiba Corporation
SAP AG BC601 13-22

6WUXFWXUHRID:I;0/5HTXHVW
"[POYHUVLRQ "!
:I0HVVDJH9HUVLRQ !
:I7UDQVSRUW!
:I0HVVDJH+HDGHU!
5HTXHVW!
5HVSRQVH5HTXLUHG!<HV5HVSRQVH5HTXLUHG!
5HTXHVW! 5HFHLYHU85/ 5HFHLYHU:)WHPSODWH
.H\!KWWSZZZ[\]FRP:IHQJLQH"LG .H\!
2SHUDWLRQ!&UHDWH3URFHVV,QVWDQFH2SHUDWLRQ!
:I0HVVDJH+HDGHU!
:I0HVVDJH%RG\!

:I0HVVDJH%RG\!
:I0HVVDJH!
SAP AG 1999
SAP AG BC601 13-23

6WUXFWXUHRID:I;0/5HTXHVW
:I0HVVDJH%RG\!
&UHDWH3URFHVV,QVWDQFH5HTXHVW!
5HVSRQVH
.H\!KWWSZZZ[\]FRP:IHQJLQH"LG .H\!
WRWKLV
DGGUHVV 2EVHUYHU.H\!KWWSZZZDEFFRPZI[2EVHUYHU.H\!
&RQWH[W'DWD!
0DWHULDO7R2UGHU!
&RPSXWHU! ;0/'RFXPHQW
7\SH!QRWHERRN7\SH!
6HULHV!,QVSLURQ6HULHV!
2SWLRQ!'9'2SWLRQ!
&RPSXWHU!
0DWHULDO7R2UGHU!
&RQWH[W'DWD!
6WDUW,PPHGLDWHO\!<HV6WDUW,PPHGLDWHO\!
&UHDWH3URFHVV,QVWDQFH5HTXHVW!
:I0HVVDJH%RG\!
SAP AG 1999
SAP AG BC601 13-24

:RUN,WHP1RWLILFDWLRQE\5HSRUW
l $LP
(YHU\WLPHDZRUNLWHPLVVWRUHGLQWKH6$36\VWHP
%XVLQHVV:RUNSODFHWKHUHOHYDQWXVHUVKRXOGUHFHLYHD
PDLO
l 3URFHGXUH
7KH6$31HWQRWHFRQWDLQVDQ$%$3SURJUDPDQGD

SURFHVVGHVFULSWLRQ
(YHU\6$3XVHUPXVWPDLQWDLQWKHLURZQHPDLODGGUHVVLQWKH

:RUNSODFHXQGHU6HWWLQJV2IILFHVHWWLQJV$XWRPDWLF
IRUZDUGLQJ
7KHXVHUIRUZKRPWKHUHSRUWLVVFKHGXOHGPXVWKDYH

PDLQWDLQHGDQ,QWHUQHWDGGUHVVLQWKHXVHUGDWDXQGHUIXUWKHU
FRPPXQLFDWLRQ7KLVEHFRPHVWKHVHQGHURIWKHPDLO
$6HQG0DLOSURFHVVPXVWEHDFWLYH

$Q,QWHUQHW*DWHZD\PXVWEHDFWLYHLQWKH6$36\VWHP

SAP AG 1999
n The e-mail text is formed from the description text for the underlying task of the work item.
n The program also offers the option to attach the URL address for the R/3 system WEB Inbox to your
email.
n Using transaction SCOT, you can determine whether the necessary processes are running in the
system.
You also can trigger sending specifically from this transaction.
n The send process is called RSCONN01.
n For sending missed deadline work items, read Note 200996.
SAP AG BC601 13-25

:RUNIORZDQGWKH,QWHUQHW8QLW6XPPDU\
l 7KHUHDUHYDULRXVIRUPVRI
LQWHJUDWLRQZLWKWKH,QWHUQHW
6$3)RUPV

(DV\:HE7UDQVDFWLRQV

;0/IORZ

l &RPPXQLFDWLRQZLWK5V\VWHPV
LVE\5)&0DLODQG,76
SAP AG 1999
SAP AG BC601 13-26

$SSHQGL[
l 7KLVVHFWLRQFRQWDLQVVXSSOHPHQWDU\PDWHULDO
WREHXVHGDVUHIHUHQFH
l 7KLVPDWHULDOLVQRWSDUWRIWKHVWDQGDUG
FRXUVH
l 7KHUHIRUHWKHLQVWUXFWRUPLJKWQRWFRYHUWKLV
GXULQJWKHFRXUVHSUHVHQWDWLRQ
SAP AG
SAP AG BC601 14-1

5ROHV$GGUHVVLQJ8VLQJ6$32UJ2EMHFWV
l ,QWKH%25ILQGDVXLWDEOHREMHFWW\SHIRUWKH6$3
2UJ2EMHFWZLWKNH\DWWULEXWH
'HVFULSWLRQ
DQG
PHWKRG
([LVWHQFH&KHFN
l &KHFNWDEOH7IRU6$32UJ2EMHFWV7KLVWDEOH
GLVSOD\VZKLFKRUJDQL]DWLRQDOREMHFWVWKH6$3
RUJDQL]DWLRQDOREMHFWW\SHFDQEHOLQNHGWR
l /LQNWKH6$3RUJDQL]DWLRQDOREMHFWWR\RXU
RUJDQL]DWLRQDOVWUXFWXUH
l ,IQRW\HWDYDLODEOH,QWKHREMHFWW\SHWKDWLVEHLQJ
SURFHVVHGFUHDWHDQDWWULEXWHWKDWUHIHUVWRWKH
6$3RUJDQL]DWLRQDOREMHFWW\SH
l &UHDWHDUROHRIW\SHRUJDQL]DWLRQDOGDWD
SAP AG 1999
n In table T7791 you will find the SAP organizational object type T024L, which stands for a design
office. This can be linked to organizational units.
n Creating a link to customer-specific organizational structure:
SAP EASY ACCESS - Tools - Business Workflow - Development - Definition Tools -
Organizational Management - SAP Organizational Objects - Create Assignments
Enter the object type T024L and your desired organizational unit, and choose the "Change"
button.
Select your organizational unit and choose Assignment - Create.
The system displays a popup and asks for the value for the laboratory that is to be linked to the
organizational unit specified.
Enter the required value.
The members of the organizational unit named are then responsible for all material masters that
refer to the value entered in the laboratory field.
n In the object type that you want to process in the workflow, ensure that an attribute refers to the SAP
organizational type. In the material master, the attribute laboratory refers to T024L.
n Define a role with role type organizational data, and enter T024L as an SAP organizational object
type.
n Enter this role in the workflow step and secure the binding.
SAP AG BC601 14-2

'HILQLWLRQRI6$32UJDQL]DWLRQDO2EMHFW7\SHV
7/ Object type

%86
!"#$%!&" 5&6$

7#+"8 9#
Attribute %25
/DERUDWRU\
:;4!=<

> #
30
7
2'HVLJQ8QLW
')(+*,'.- /+0132 ')-/40132 627/.%

3RVLWLRQB860HLHU
7/
23URGXFW0DQDJHPHQW8QLW 3'25*
627/30

3RVLWLRQB86+LQ]
SAP AG 1999
n Runtime:
a) Because the role input parameter was BUS1001.Laboratory, the role resolution scans the whole
organizational plan for units that are linked to this object of type T024L.
b) If they are also possible agents of the task, the holders of positions in these units are the recipients.
SAP AG BC601 14-3

7XWRULDO
7XWRULDO&UHDWLQJD1RWLILFDWLRQRI$EVHQFH:RUNIORZ
In this exercise you will create a workflow for a "Notification of

absence". The exercise begins by creating the first step task. This
sends the employee a form to fill out and send to the manager for
approval. The exercise then continues with creating the workflow
definition for the Notification of Absence (NOA).
Next is the approval step, which sends the completed form to the
correct agent for approval. Additional steps are also determined as a
consequence of the manager decision (approval or rejection) in the
workflow definition. Depending on the managers decision, the
workflow is either continued and completed, or the notification is
returned to the initiator for further action, (to revise or cancel request).
This exercise is intended to provide practical experience of the

workflow tools required to build, modify and test workflow
definitions.
You will learn which steps you need to carry out to define the
standard task Create notification of absence. Because this is your
first standard task, the individual steps are described in detail. Any
subsequent definitions of standard tasks are not described in such
detail. A standard task is always a single-step task with reference to an
object method.
The subsequent steps in the exercise extend the workflow definition,

utilizing additional functions and step tasks that will be incorporated
into the notification of absence to make the workflow definition
complete.
SAP AG BC601 14-4

1-1 3URFHGXUH&UHDWLQJD:RUNIORZ
1-1-1 Start from the SAP Easy Access menu and open folders:
7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
This displays the screen "Task: Maintain".
Select the task type Workflow template and enter task ZWF_NOA_##.
The screen Workflow Template: Add is displayed.
1-1-2 Enter the Basic data for the Workflow template.

Describe the workflow template to be created in the fields Abbr. and
Name.
Abbr.: <=:)B12$B>
1DPH<Workflow: Notification of absence (ZWF_NOA_##)>
( ## represents your assigned group number)
Save your entries.
7DVNVDQGZRUNIORZVPXVWEHDVVLJQHGWRHDFKSRVVLEOHDJHQW7RFDUU\
RXWWKLVDVVLJQPHQWPDNHWKHIROORZLQJHQWULHV
1-1-3 6HOHFW$GGLWLRQDOGDWD$JHQWDVVLJQPHQW0DLQWDLQ
The screen Workflow template: Maintain Agent Assignment is displayed.
Position the cursor on the name of your workflow template.
Choose the Attributes button. This displays the dialog box Task: ....
Select General task and choose Transfer (green check). Refresh the
index (red and white ball).
Return to the previous screen and save your entries.
,QWKHILUVWVWHSRIWKHH[HUFLVH\RXFUHDWHGWKHZRUNIORZWHPSODWHWKDWLV
WKHSUHUHTXLVLWHIRUEXLOGLQJDQGH[WHQGLQJWKH1RWLILFDWLRQRI$EVHQFH
ZRUNIORZGHILQLWLRQ&DUU\RXWWKHIROORZLQJVWHSVWREXLOGWKH
1RWLILFDWLRQRI$EVHQFHZRUNIORZ
SAP AG BC601 14-5

2-1 'HILQLQJWKH6WDQGDUGWDVN&UHDWH1RWLILFDWLRQRI$EVHQFH
2-1-1 In the SAP Easy Access menu, choose Task/Task Groups, -> "Create" to
start this exercise.
Re-open the folders:
7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
Select the task type Standard task, and enter task T1_Create_##.
This displays the screen "Standard Task: Add".
2-1-2 Entries for Basic data

Describe the standard task to be created in the fields Abbr. and
Name.
$EEU7B&UHDWHB!
1DPH&UHDWHQRWLIRIDEVHQFH7B&UHDWHB
( ## represents your assigned group number)
2-1-3 Entries for Object type and Method

Position the cursor in the input field for Object type, and use F4 to see
the possible entries.
This displays the dialog box "Input Help Personal Value List".
Select "Information system".
The dialog box Repository Infosystem: Business Object Types is
displayed.
In the Object type input field, enter FORM*.
Choose Enter (green check).
Choose the object type )250$%6(1&.
You have now specified the object type. The next step is to choose one
of the methods that FORMABSENC provides.
Position the cursor in the Method input field, and use F4 to call the
possible entries.
Select the method CREATE.
Press the enter key (or green check) to confirm the entries you have
made.
SAP AG BC601 14-6

2-1-4 Entering a work item text
As soon as the work item for the task Create notification of absence is
received in your inbox, the work item text appears as an information text in
the Business Workplace Inbox.
Enter any text in the Work item text field, for example
<Create notification of absence>
Confirm your entries.
2-1-5 Defining an agent:

Confirm request to save your data (select Yes)
The screen Workflow template: Maintain Agent Assignment is
displayed.
Position the cursor on the name of your standard task.
Select the function Attributes.
This displays the dialog box Task ......
Select General task and choose Transfer. Refresh the index by
clicking on the red/white ball.
Return to the previous screen and save your entries.
'HILQLQJ\RXUWDVNDVD*HQHUDOWDVNPHDQVWKDWHYHU\HPSOR\HHKDV
DXWKRUL]DWLRQWRFUHDWHDQRWLILFDWLRQRIDEVHQFH)XUWKHUHQWULHVIRU
SRVVLEOHDJHQWVDQGRWKHUDGGLWLRQDOGDWDDUHQRWUHTXLUHGDWWKLVSRLQW
<RXKDYHQRZIXOO\GHILQHG\RXUILUVWVWDQGDUGWDVN6DYH\RXUZRUNDQG
WKHQUHWXUQWRWKH6$3(DV\$FFHVVPHQX
SAP AG BC601 14-7

3-1 Integrating "Create Notification of Absence" into the Workflow Definition
The workflow definition is created using the Workflow Builder. You have already
created your workflow template. You will now start to create the associated
3-1-1 Start from the SAP Easy Access menu. Select "Change" under folder
Task/Task Groups and then select the workflow template you have
already created.
Use the following steps to select the workflow template:
'RXEOHFOLFN&KDQJHXQGHUIROGHU7DVN7DVN*URXSV
Position the cursor in the input field Task type, and use F4 to call the
possible entries.
Select the object type Workflow template (WS) from the object types
displayed.
Position your cursor in the input field Task and use F4 to call the
possible entries.
This displays the dialog box Choose Workflow template.
,QWKHILHOG6HDUFKWHUPHQWHUHLWKHUWKHHQWLUHDEEUHYLDWLRQRI\RXU
ZRUNIORZWHPSODWHRU\RXUJURXSQXPEHUWRUHVWULFWWKHVHOHFWLRQRIWDVNV
IRUH[DPSOH DQGFRQILUP\RXUHQWU\
If there are several workflow templates which match the search term
entered, a list is displayed from which you can select your workflow
template. If only one task is found, its unique identification number is
entered automatically in the Task input field in the screen Task:
Maintain.
The screen "Task: Maintain" is displayed. The input fields should now
contain the task type and identification number of your workflow
template.
6HOHFW7DVN&KDQJHRUFKRRVHWKH&KDQJHEXWWRQ
The screen Workflow Template: Change is displayed.
You have already entered the basic data of the workflow template in the
second unit ( Step 2: Creating the workflow template) You can now go
directly to the Workflow Builder without making any further entries.
Start the Workflow Builder.
&KRRVH*RWR:RUNIORZ%XLOGHU&XUUHQWYHUVLRQRUFKRRVHWKH
:RUNIORZ%XLOGHUEXWWRQ
SAP AG BC601 14-8

3-1-2 Creating an activity as a step in the Workflow Definition
7KH:RUNIORZ%XLOGHUKDVDQRGHDUHDIRUREMHFWVWKDWFDQEHLQVHUWHG
LQWR\RXUZRUNIORZGHILQLWLRQ<RXFDQDGGQHZVWHSVIURPWKLVDUHDWR
\RXUZRUNIORZGHILQLWLRQE\XVLQJ'UDJ 'URS
In the node area area, click on the icon for Activity.

Note: The cursor changes.
Position the cursor on the Undefined step that follows Workflow
started, and click. This inserts a step of the selected type (Activity) into
the workflow definition.
The screen Workflow Builder: Create.. is displayed for defining an
activity in standard mode.
3-1-3 Entering Basic data for Control

In the Task field, enter the ID ( TS <8-digit number> ) of the standard
task that you defined in the last exercise ( Step 3: Defining the standard
task Notification of absence.)
,I\RXQRORQJHUNQRZWKH,'XVHWKH)KHOSWRVHDUFKXVLQJWKHWDVN
DEEUHYLDWLRQ7KHGLDORJER[6HDUFKDQG)LQG7DVNVLVGLVSOD\HG
6HOHFWWKH7DVNWDE
(QWHU\RXUFKRVHQDEEUHYLDWLRQRUJURXSQXPEHUDVWKHVHDUFKFULWHULD
IRU\RXUVWDQGDUGWDVN&UHDWHQRWLILFDWLRQRIDEVHQFH,I\RXRQO\HQWHU
WKHILUVWIHZFKDUDFWHUVRI\RXUDEEUHYLDWLRQ\RXJHWDOLVWRIWDVNVIURP
ZKLFK\RXFDQFKRRVHWKHWDVNUHTXLUHG6HOHFW\RXUWDVNLQWKHOLVWDQG
FOLFNWKH7UDQVIHUEXWWRQ
(YHU\DFWLYLW\DVDVWHSLQDZRUNIORZGHILQLWLRQUHIHUVWRDWDVN
Confirm your entries with Enter (green check).

Review the proposed binding of workflow and task containers, and
choose Enter to proceed.
If the screen 'HILQH&RQWDLQHU(OHPHQWVDQG%LQGLQJ is
QRW displayed, click the red and white ball next to the binding. Review
the proposed binding of workflow and task containers and choose
Enter to proceed.
In the Control tab of the activity, change the Step name.
(Proposal: )LOO2XW1RWLILFDWLRQRI$EVHQFH).
Choose the tab page 2XWFRPHV, and enter a name (proposal:
1RWLILFDWLRQRIDEVHQFHILOOHGRXW) in the table Possible outcomes of
step, in the input field after Step executed.
SAP AG BC601 14-9

,QWKH:RUNIORZ%XLOGHU
6WHSQDPH7KHFXUUHQWVWHSLQ\RXUZRUNIORZGHILQLWLRQDSSHDUVXQGHU
WKHQDPHHQWHUHGKHUH
2XWFRPH(DFKVWHSLVIROORZHGE\DWOHDVWRQHRXWFRPHWKHQDPHLVWKDW
XVHGIRUWKHRXWFRPHLQWKHZRUNIORZGHILQLWLRQ
3-1-4 Check the binding

From the Control tab, select the function Binding (exists) .
This displays the screen Binding for Step. .
1. A container element which can contain a reference to the object
"notification of absence" is created automatically in the workflow
container. The element has the name AbsenceForm and refers to an
object of type )250$%6(1&.
2. A binding is defined automatically. You can generally define the
binding between the task container and the workflow container in
two directions:
Task container <== Workflow container (top part of screen)
Task container ==> Workflow container (bottom part of screen)
7KH&5($7(PHWKRGUHIHUUHGWRLQ\RXU&UHDWHQRWLILFDWLRQRI
DEVHQFHWDVNFUHDWHVDIRUPWKDWZLOOEHVXEPLWWHGWRWKHVXSHUYLVRUIRU
DSSURYDOODWHULQWKHZRUNIORZ7KHUHIHUHQFHWRWKHQRWLILFDWLRQRI
DEVHQFHFUHDWHGPXVWEHNQRZQLQWKHZRUNIORZFRQWDLQHU7RDFKLHYH
WKLVDELQGLQJPXVWEHGHILQHGIURPWKHWDVNFRQWDLQHUWRWKHZRUNIORZ
FRQWDLQHU
7KLVKDSSHQVE\WKHDVVLJQPHQW1RWLILFDWLRQRIDEVHQFH !
$EVHQFH)RUP WKDWLVDXWRPDWLFDOO\FUHDWHG7KHRWKHUELQGLQJ
GLUHFWLRQLVQRWUHOHYDQWIRUWKLVVWHS
No further entries are required at this point.

Exit the screen.
Workflow Builder Create is displayed. (Note, the title of the screen
may also read :RUNIORZ%XLOGHU&KDQJH6WHS)
3-1-5 Entries for Responsibility

From the Control tab, use F4 to see possible entries for the field in the
Agents frame.
Select Expression .
Position the cursor in the Expression field, and click.
Select the expression Initiator of workflow .
SAP AG BC601 14-10

3-1-6 Close Step definition
Select the function Syntax Check to check your entries and return to
the Workflow Builder.
.
7RYLHZ\RXUZRUNIORZIXOO\LQWKHGLVSOD\DUHD\RXPD\KDYHWRDGMXVW
WKHYLHZLQWKHQDYLJDWLRQDUHD
:KHQ\RXUHQWLUHZRUNIORZLVVKRZQLQWKHGLVSOD\DUHD\RXFDQSRVLWLRQ
WKHPRXVHRQDQHYHQWRUDVWHS7KHUHOHYDQWQDPHLVGLVSOD\HGLQWKH
ORZHUVFUHHQERUGHU
Activate your workflow definition.
4-1 )LUVW7HVWRIWKH1RWLILFDWLRQRI$EVHQFH:RUNIORZ
You can now perform the first test on the workflow template you have created.
Starting workflows and filling out forms.
Remain in the screen Workflow Builder: Change.
To start the workflow, choose:RUNIORZ7HVWor choose the Test
buttonThis displays the screen Start Workflow (Test Environment).
Click on the Refresh organizational environment button.
Your workflow template ID is displayed in the Task field.
Start your workflow template.
This displays the screen Create Notification of Absence and the form
for the notification of absence.
Fill out and save the form.
The screen Start Workflow (Test Environment) is displayed again.
Return to the SAP Easy Access menu
5-1 'HILQLQJWKH6WDQGDUGWDVN&KHFN1RWLILFDWLRQRI$EVHQFH
In the SAP Easy Access menu, choose Task/Task Groups, -> "Create" to
start this exercise.
Re-open the folders
7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
Select the task type Standard task, and enter task T2_Create_##.
SAP AG BC601 14-11

5-1-1 Entries for Basic data
In the fields Abbr. and Name, describe the standard task to be
created.
$EEU<7BFKHFNB> ( Note: ## is your group number)
1DPH<&KHFNQRWLILFDWLRQRIDEVHQFH7BFKHFNB!
5-1-2 Entries for Object method

Position the cursor in the input field for Object type, and use F4 to see
the possible entries. This displays the dialog box "Input Help Personal
Value List".
Choose the object type FORMABSENC.
You have now defined the object type. In the next step, choose one of
the methods which FORMABSENC provides. Position the cursor in the
Method input field, and use F4 to call the possible entries.
Choose the method APPROVE.
Use Enter to exit the info message " The result parameter will be
changed according to the object method".
Save your entries.
5-1-3 Enter a work item text

Enter the work item text in the Work item text field.
<RXKDYHWKHRSWLRQWRLQFOXGHSDUDPHWHUVLQWKHZRUNLWHPWH[W$W
UXQWLPHWKHVHSDUDPHWHUVZLOOEHILOOHGZLWKYDOXHV
<RXZDQWWRLQFOXGHWKHQDPHRIWKHDXWKRURIWKHQRWLILFDWLRQRIDEVHQFH
LQWKHZRUNLWHPWH[W$VVRRQDVWKHZRUNLWHPDSSHDUVLQWKH
VXSHUYLVRUVLQWHJUDWHGLQER[WKHQDPHRIWKHDXWKRUZLOODSSHDULQWKH
ZRUNLWHPLQIRUPDWLRQWH[W
First enter the following text for the work item:

"&KHFNQRWLILFDWLRQRIDEVHQFHIURP
Make sure there is space after from, and the cursor is positioned after
this space.
Then select the Insert variables icon to assign the text variable.
This displays the dialog box Please Choose an Expression.
In the dialog box under, Container, choose the expression:
1RWLIRIDEVHQFH,VVXHUREMHFWUHI8VHUQDPH
SAP AG BC601 14-12

&KRRVHWKH6ZLWFKGLVSOD\7HFKQLFDOQDPHGHVFULSWLRQWRVZLWFK
EHWZHHQDWHFKQLFDODQGVHPDQWLFYLHZRIWKHSRVVLEOHH[SUHVVLRQV,QWKH
WHFKQLFDOYLHZ\RXFDQVHHWKDWWKHQDPHUHIHUVWRWKHDWWULEXWHQDPHIRU
WKHREMHFW&UHDWRUZKLFKLQWXUQLVDQDWWULEXWHIRUWKHREMHFW
$EVHQFH)RUP
Choose Continue to
to return to the Standard Task: Change screen.
The parameter &_WI_OBJECT_ID.CREATOR.ID& has been added to
the work item text automatically.
The & symbol marks the position in the text where the parameter will be
inserted.
5-1-4 Defining an agent

First save all your previous entries.
The screen Standard task: Maintain Agent Assignment is displayed.
&KRRVH$JHQWDVVLJQPHQW&UHDWH
This displays the dialog box Choose agent type.
Select -RE, and confirm your entry with Continue.
This displays the dialog box Choose Job.
Enter a search term containing part or all of your abbreviation for your
job of department head. (You created the department head in a previous
exercise, it started with zjob*.)
If a list: Job (1) ..Entries found is displayed,
you can select the Head of department job from the list.
6HOHFW(GLW5HIUHVKLQGH[
<RXKDYHDVVLJQHGWKHVWDQGDUGWDVNWRDGHSDUWPHQWKHDGMRE<RXXVH
WKLVMRELQWKHRUJDQL]DWLRQDOSODQWRGHVFULEHDSRVLWLRQ7KHKROGHURI
WKHSRVLWLRQLVDOVRGLVSOD\HG&RPSDUH\RXUDVVLJQPHQWVZLWKWKRVH
GHILQHGLQ\RXURUJDQL]DWLRQDOSODQ
Go back to the Standard Task: Change screen.

The task Check notification of absence has now been defined
completely. Save your entries and return to the SAP Easy Access menu.
You have now completed this activity. Your next task is to integrate the
standard task into the workflow definition.
SAP AG BC601 14-13

5-1-6 Display your organizational plan again
In the SAP Easy Access menu, choose:
2UJDQL]DWLRQDO0DQDJHPHQW2UJDQL]DWLRQDO3ODQ'LVSOD\
Search for your organizational unit by
clicking on Organizational unit in the upper left part of the screen.
Double-click your organizational unit in the lower left part of the screen.
In the upper right part of the screen, choose the Goto icon, and choose
Task assignment.
Expand all the nodes of your organizational unit (in the upper right part
of the screen)
5HVXOW When you defined your task for Check notification of
absence, you selected the job of department head when you assigned an
agent. This information has been automatically integrated into your
organizational plan.
6-1 ,QWHJUDWLQJ&KHFN1RWLILFDWLRQRI$EVHQFHLQWKH:RUNIORZ'HILQLWLRQ
You have already created a workflow template in the preceding exercise Creating
a Workflow template. You then integrated a standard task in the workflow
definition for the step "Create Notification of Absence". You will now continue by
integrating the standard task "Check notification of absence" into the workflow
definition.
6-1-1 Start from the SAP Easy Access menu.

7DVNV7DVN*URXSV&KDQJH
Choose the workflow template that you have just created.
'RXEOHFOLFN&KDQJHXQGHUIROGHU7DVN7DVN*URXSV
Position the cursor in the input field Task type, and use F4 to call the
possible entries.
Select the object type Workflow template (WS) from the object types
displayed.
Position your cursor in the input field Task, and use F4 to call the
possible entries.
This displays the dialog box Choose Workflow template.
Search for and select your previously defined workflow template.
SAP AG BC601 14-14

The screen "Task: Maintain" is displayed. The input fields should now
contain the task type and identification number of your workflow
template.
6HOHFW7DVN&KDQJHRUFKRRVHWKH&KDQJHEXWWRQ
Choose Goto Workflow Builder Current version or the Workflow

Builder button. This displays the Workflow Builder. Adjust the
navigation area so that the entire workflow can be seen in the display
area.
6-1-2 Creating an element in the workflow container

6HOHFW*RWR:RUNIORZFRQWDLQHU
The screen Workflow ....: Edit Container is displayed.
6HOHFW(GLW&UHDWH
Define the element in the following fields:
(OHPHQW: Authorizer
1DPH Authorizer
'HVFULSWLRQ Approver of notification of absence
Container elements can be defined using ABAP Dictionary field

proposals. Use this option now.
Enter :)6<67 in the Reference table field.
7DEOH:)6<67LVWKHWDEOHVWUXFWXUHWDEOHXVHGE\WKHZRUNIORZ

PDQDJHUDQGZKLFKGHILQHVWKHDWWULEXWHVXVHGLQWKHZRUNIORZ
FRQWDLQHU
In the Reference field , enter $*(17
Choose the Continue Enter button.
The element Authorizer has been created.
Go back to the Workflow Builder Change screen.
SAP AG BC601 14-15

6-1-3 Creating an activity as a step in the workflow definition
In the "node area", click on the icon for activity. The cursor changes.
Position the cursor on the Undefined step which follows the outcome
1RWLILFDWLRQILOOHGRXW,and click. This inserts a step of the chosen type
(Activity) into the workflow definition. The screen for defining an
activity in standard mode is displayed.
6-1-4 Enter Basic data for Control

In the Task field, enter the ID ( TS <8-digit number> ) of the standard
task &KHFNQRWLILFDWLRQRIDEVHQFH, that you defined in the last exercise
.
If you no longer know the ID, use the F4 help to search using an
abbreviation of the task. In the Search and Find: Tasks dialog box,
choose the Task tab, and enter the abbreviation of the single-step task.
Choose the Find button. A list of matching tasks is displayed. Select
your task. Confirm you entries by pressing Enter.
When your TS number is displayed in the task field, confirm your
entries using Enter.
The screen "Define Container Elements and Binding" is now displayed.
Review the proposed binding and choose Enter.
The method APPROVE of the object type FORMABSENC, referred to
in the standard task definition, has a specific result parameter defined
using a Data Dictionary field. The confirmation of your task entry
transferred the following information into the definition of the outcome
of your activity :
The step name was transferred from the definition of your standard task.
The following possible subsequent outcomes are displayed in the
"Outcome" tab:
- 5HMHFWHG
$SSURYHG
1HZ
The meaning and consequences of these entries are described below.
Change the entry for the step name using the Control tab:
6WHSQDPH&KHFNQRWLILFDWLRQRIDEVHQFH
SAP AG BC601 14-16

6-1-5 Defining Binding
Click Binding Definition . This displays the screen Binding for
Step. .
If necessary, the binding can be defined in two directions: From the
workflow container to the task container, and from the task container
to the workflow container.
Notification of absence <== &AbsenceForm&
Notification of absence <== &AbsenceForm&
7KHILUVWHQWU\GHILQHVDELQGLQJIURPWKHZRUNIORZFRQWDLQHUWRWKHWDVN
FRQWDLQHU7KLVHQVXUHVWKDWWKHWDVN&KHFNQRWLILFDWLRQRIDEVHQFH
NQRZVZKLFKREMHFWLVLQYROYHG
7KHVHFRQGHQWU\GHILQHVDELQGLQJIURPWKHWDVNFRQWDLQHUWRWKHZRUNIORZ
FRQWDLQHU7KLVHQVXUHVWKDWDQ\GDWDFUHDWHGDVDUHVXOWRIWKHVWHSWDVNLV
WUDQVIHUUHGWRWKHZRUNIORZFRQWDLQHUIRUWKHVXEVHTXHQWVWHSLQWKH
ZRUNIORZGHILQLWLRQ
$IXUWKHUELQGLQJGHILQLWLRQPXVWEHH[HFXWHGLQZKLFKWKHDFWXDODJHQWRI
WKHZRUNLWHPIRUH[DPSOHWKHVXSHULRULVVWRUHGLQDQHOHPHQWRIWKH
ZRUNIORZFRQWDLQHU
&KRRVHWKH6KRZOLQHVEXWWRQ
All elements of the task container are now displayed on the left. You
can use these elements for other definitions. The name of the agent
for the work item is available in the element $FWXDODJHQWHOHPHQW
QDPH:,B$FWXDOB$JHQW of the task container after the work item
has been executed. Note: Choose the Technical view on/off button
to see the technical name for the element WI_Actual_Agent.
To define the binding from the task container to the workflow
container, position the cursor in the bottom part of the binding editor
display, in the empty input field opposite $FWXDO$JHQW. Use F4 to
call the possible entries.
The dialog box: Please Choose an Expression for Element Actual
Agent is displayed.
Select $XWKRUL]HU from the list by double-clicking.
In addition to the bindings that already exist, the following binding
has now been defined:
Actual Agent==> &Authorizer&
Exit the screen.
The assignment Notif. of absence. ==> &AbsenceForm& is not
actually necessary for this step.
SAP AG BC601 14-17

6-1-6 Defining the outcome
The method APPROVE, referred to in the task definition, has one result
parameter that can assume three different values. Depending on these
values, the activity Check notification of absence can have three different
subsequent outcomes:
5HMHFWHG
$SSURYHG
1HZ
Exit the step definition and return to the Workflow Builder. In
accordance with the three subsequent outcomes for the step Check
notification of absence, three branches were automatically inserted into
the workflow definition.
Now call processing of the activity Check notification of absence
again by double-clicking on the step symbol.
In the "Outcomes" tab, all three subsequent outcomes are selected.
Delete the name for the outcome 1HZ, and return to the Workflow
Builder.
The dialog box $VVLJQPHQW2XWFRPHV!6XEVHTXHQW6WHSVis
displayed
Make the proposed assignments.
This displays the dialog box Save Step which informs you that the
subsequent outcome includes (undefined) steps which have already been
created. These steps will now be deleted.
Choose "Yes".
Two branches have been inserted in your workflow definition for the
two selected outcomes Rejected and Approved. There is no branch
for the outcome New.
SAP AG BC601 14-18

5HVSRQVLELOLW\PXVWEHGHILQHGIRUHDFKVWHS7KDWPHDQVWKDWZKHQ
WKHVWHSLVH[HFXWHGLQWKHZRUNIORZSURFHVVWKLVVWHSLVRIIHUHGIRU
SURFHVVLQJWRDOOHPSOR\HHVGHILQHGDVSRVVLEOHDJHQWVRIWKHVLQJOH
VWHSWDVN&KHFNQRWLILFDWLRQRIDEVHQFH7KLVPHDQVDOOHPSOR\HHV
ZKRVHSRVLWLRQLVGHVFULEHGE\WKHMRE+HDGRIGHSDUWPHQW
5HPLQGHU
You maintained the organizational plan with jobs, positions and staffing
assignments in the exercises for the Introduction unit.
You defined the single-step task "Check notification of absence" with the
assignment of the possible agents when defining the standard task "Check
notification of absence".
<RXPXVWHQVXUHWKDWWKHXVHUZKRLVDVVLJQHGWRWKHSRVLWLRQRIPDQDJHU
LQWKHRUJDQL]DWLRQDOVWUXFWXUHFUHDWHGLQWKHSUHYLRXVXQLWVLVWKHVDPH
DVVLJQHGKROGHUIRUWKHDSSURYDOVWHS7BFKHFNB
Double-click the Check notification of absence step.

In the Control tab, select5ROH in the Agents section Select F4 for
possible entries in the blank field next to 5ROH.
In the Choose Standard role dialog box, enter 0$ From the list of
possible entries, select Manager (US) Superior (as user for) .
Confirm your entry by choosing Enter .
Choose the Binding (does not exist) button for the Role. Enter
Initiator of workflow in the first field, ORG_OBJECT (use F4 to
display a list of possible entries, and select).
Return to the Workflow Builder.
6-1-8 Close the step definition

Check your workflow definition.
You have the option of creating several versions of workflow definitions
for a workflow template. However, do not use this option now.
5HVXOW Your workflow definition can now be subjected to a second test.
SAP AG BC601 14-19

7-1 6HFRQGWHVWRIWKH$SSURYDOVWHSIRU1RWLILFDWLRQRIDEVHQFH
You can now perform the second test on the workflow template you have created.
Before doing this, login as both BC601-## $1' BC601-MGR##. From the SAP
Easy Access menu, choose Start Workflow (Test Environment)then click the
Refresh organizational environment button
7-1-1 6WDUWLQJWKH:RUNIORZWHPSODWHDQG)LOOLQJ2XWWKH)RUP
From the SAP Easy Access menu, choose 7RROV%XVLQHVV:RUNIORZ
'HYHORSPHQW5XQWLPH7RROV. Double-click "Start Workflow (Test
Environment)". Click the Refresh organizational environment button.
As in the previous exercises, start your workflow template by choosing the
Execute button.
Alternatively, you can branch directly from the Workflow Builder to
starting a workflow by choosing :RUNIORZ7HVWor the7HVW button. The
task number is already determined.
)URPWKHDSSOLFDQWVSHUVSHFWLYH8VHU,'%&
When the workflow is started, the work item for creating the notification
of absence is displayed immediately. This is because subsequent work
items can be started immediately. You were introduced to this in the first
test. The screen Create Notification of Absence is displayed. Fill out
and save the form.
)URPWKH+HDGRI'HSDUWPHQW
VSHUVSHFWLYH8VHU,'%&
0*5
You have defined the step Check notification of absence in your
workflow definition so that all possible agents for the single-step task
are considered as agents for this step. Since you occupy the position of
both applicant and head of department, you are automatically
immediately presented with the work item Approve notification of
absence. This is again due to the fact that follow-up work items are
started immediately.
As the superior, you have several options. You can
- $SSURYHWKHDSSOLFDWLRQ,
5HMHFWWKHDSSOLFDWLRQ
- &DQFHOSURFHVVLQJRIWKHDSSOLFDWLRQ.
Choose the Cancel option.
$WWKLVSRLQWLQWKHILUVWWHVWRI\RXUZRUNIORZWHPSODWH\RXZHUH
LQWURGXFHGWRZRUNLWHPDQDO\VLV<RXDUHQRZJRLQJWRZRUNZLWKWKH
ZRUNIORZRXWER[
7KHZRUNLWHPVWKDW\RXVWDUWHGLQWKHGLDORJZLWKGDWHWLPHDQGFXUUHQW
VWDWXVDUHGLVSOD\HGLQWKHZRUNIORZRXWER[
SAP AG BC601 14-20

7-1-2 5HWXUQWRWKH6$3(DV\$FFHVV0HQXDV%&
DSSOLFDQWDQGFKRRVH
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW5XQWLPH7RROV
%XVLQHVV:RUNSODFH
2SHQWKH2XWER[IROGHUDQGFOLFN6WDUWHGZRUNIORZV
The window with the list of 6WDUWHGZRUNIORZV is displayed.
In this list, there is also an entry for your workflow.
Position the cursor on your workflow template.
'RXEOHFOLFNRQWKHHQWU\
This displays the Work item attributes screen.
Choose the Log button.
This displays the screen Workflow Log .
The work item for the single step Approve notification of absence
now has the status in process , as does the whole workflow. The step
"Fill out notification" was completed correctly.
You can also view a list with technical details by clicking the List with
technical details icon.
To display the meanings of the symbols in the first column, position the
cursor on the icons.
Exit the workflow log and workflow outbox.
7-1-3 Integrated Inbox - Checking the Notification of Absence

Log on to the R/3 System as the manager. You now resume the role of
the superior who canceled processing earlier when the Notification was
to be checked.
Call the Business Workplace inbox using Runtime Tools . Double-
click "Business Workplace", and open the Inbox folder.
Open folder or click on Workflow to call the work list (the workflow-
specific part of the Inbox).
Select the Notification of absence work item by double-clicking the
symbol (small checkmark) under the heading "Ex" (Execute).
You can decide whether you want to approve or reject the application.
Start the workflow twice and test each variant.
To check that the workflow was completed correctly, go to the
workflow log of your workflow. The steps required to do this are
described in an earlier exercise for the first test. Return to the SAP Easy
Access menu
SAP AG BC601 14-21

8QLW&RPSOHWH1RWLILFDWLRQRI$EVHQFH:RUNIORZ
7RSLF$SSOLFDWLRQ5HMHFWHG8VHU'HFLVLRQ
In the preceding units, you have already created a workflow template

and integrated two standard tasks into the workflow definition
(Integrating Create Notification of Absence, and Check
Notification of Absence into the workflow definition). You now
continue by integrating the user decision as an additional step in the
If the department head rejects the request for leave, the employee
should have the chance to revise and resubmit the request. In this
situation, a user decision can be integrated as a step in the workflow
definition.
8-1 8VHUGHFLVLRQ
Start the SAP Easy Access Menu, and choose
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW'HILQLWLRQ7RROV7DVNV7DVN
*URXSV&KDQJH
8-1-1 Choose the workflow template that has already been created, then go to the
Workflow Builder.
8-1-2 Creating a user decision as a step in the workflow definition
Click in the node area on the icon for User decision. The cursor
changes.
Position the cursor on the Undefined step after the outcome 5HMHFWHG,
and click. This inserts a step of the desired type 8VHUGHFLVLRQ into the
The screen for defining a user decision in the standard mode is
displayed.
SAP AG BC601 14-22

8-1-3 Enter Basic data for User Decision
In the Decision tab page, enter a text in the input field Title. It will
appear at runtime as the heading of the dialog box with the decision
options.
Title: <RXUDSSOLFDWLRQZDVUHMHFWHGE\ 5HYLVH"
The & symbol is a placeholder for parameters that are assigned a
value at runtime.
Position the cursor in the input field Parameter 1, and use F4 to call
the possible entries. This displays the dialog box Expression for first
parameter of user decision.
Choose the container element $XWKRUL]HU that you have created.
Enter the Decision texts as follows:
'HFLVLRQWH[WV 2XWFRPHQDPH
Revise application? Application revised
Withdraw application? Application withdrawn
7KH'HFLVLRQWH[WV\RXFDQHQWHUKHUHZLOODSSHDUDVSRVVLEOHGHFLVLRQVLQ
WKHZRUNLWHPWKDWWKHDSSOLFDQWFDQSURFHVVDIWHUKLVKHUUHTXHVWIRU
OHDYHKDVEHHQUHMHFWHG
7KH2XWFRPHQDPHVDUHWKHWHUPVWKDWGHVFULEH\RXURXWFRPHVLQWKH
ZRUNIORZGHILQLWLRQ
8-1-4 Change step name.

In the Control tab, enter a text for the step name.
6WHSQDPHDecision: Change - Withdraw
8-15 Entries for Responsibility

In the Decision tab, in the category Agents,
select Expression from the pull down menu.
Position your cursor in the input field Expression, and use F4 to call
Select the expression Workflow Initiator.
Return to the Workflow Builder.

Test your workflow.
Activate your workflow.
You can now subject your workflow definition to another test.
SAP AG BC601 14-23

9-1 7KLUG7HVW7HVW8VHUGHFLVLRQVWHS1RWLILFDWLRQRIDEVHQFH
The individual steps required to carry out this test are described in an overview. If
this information is not sufficient, check the instructions for the previous test.
6WDUWLQJWKHZRUNIORZILOOLQJRXWWKHIRUPFKHFNLQJWKHDSSOLFDWLRQ
XVHUGHFLVLRQ
5HPHPEHUWKDW\RXPXVWEHORJJHGRQWRWKH56\VWHPDVERWKWKH
$SSOLFDQWDQGWKH0DQDJHUWRH[HFXWH\RXUWHVWDQGWRVZLWFK
EHWZHHQVHVVLRQVIRUWKHDSSURSULDWHVWHSVGXULQJWKHH[HFXWLRQRIWKH
ZRUNIORZ
)URPWKH$SSOLFDQWV3HUVSHFWLYH
To start the workflow, choose
7RROV%XVLQHVV:RUNIORZ'HYHORSPHQW5XQWLPH7RROV6WDUW
:RUNIORZ7HVW(QYLURQPHQW
Select your workflow template. (Refresh organizational environment)
Start your workflow template. The form is displayed for processing. Fill
out and save the form.
When you have saved the form, switching logon sessions to the
applicants manager allows you to directly approve or reject the
application (because subsequent work items are started immediately).
)URPWKH6XSHULRUV3HUVSHFWLYH
Reject the application.
Exit the screen.
You integrated the user decision as a subsequent step in the workflow
definition in case the application is not approved. The applicant was
entered as the agent for this step. You therefore immediately have the
option to execute the user decision as an applicant (because subsequent
work items are started immediately).
)URPWKH$SSOLFDQWV3HUVSHFWLYH
You have three options:
- 5HYLVHDSSOLFDWLRQ
:LWKGUDZDSSOLFDWLRQ
&DQFHO
It is irrelevant whether you choose change or withdraw, because
you have not defined any follow-up steps.
If you choose &DQFHO, this work item stays in your inbox. Start your
workflow several times and test the different options.
The processing can be checked each time in the workflow log, through
work item analysis or the workflow outbox.
SAP AG BC601 14-24

7RSLF5HYLVH1RWLILFDWLRQRI$EVHQFH
This unit describes the steps that you need to carry out to define the
standard task "Revise notification of absence". You have already
learned that a standard task is always a single-step task that refers to
an object method.
In the previously defined steps in the Notification of absence

workflow definition, you determined that your workflow initiates the
creation of the NOA form, and sends the form for the manager's
approval. In this exercise, you will extend your workflow definition to
allow the initiator the option to revise their request after the manager
has initially rejected it.
10-1 'HILQLQJWKH6WDQGDUGWDVN5HYLVH1RWLILFDWLRQRI$EVHQFH
10-1-1 In the SAP Easy Access menu, choose Task/Task Groups -> "Create".
Re-open the folders
7DVNV7DVN*URXSV
'RXEOHFOLFN&UHDWH
Select the task type Standard task in the Task type field.
Entries for Basic data:
Describe the standard task to be created in the fields Abbr. and
Name.
$EEU <T3_Revise_## >
1DPH <Revise notif. of absence (T3_Revise_##)>
Entries for Object method:
Enter FORMABSENC in the Object type field.
Enter UPDATE in the Method field.
Choose F4 for possible entries.
SAP AG BC601 14-25

Entering a Work item text:
In the Work item text field, enter the following text for the work item:
5HYLVHQRWLILFDWLRQRIDEVHQFH
Defining an agent:
First save all entries made so far.
&KRRVH$GGLWLRQDOGDWD!$JHQWDVVLJQPHQW!0DLQWDLQ
Select the function Attributes.
This displays the dialog box Task:...
Select General task and then Transfer.
Do not forget to update the index.
To do this, click on the red and white ball.
Choose Back and then save.
The standard task for revising the notification of absence has been fully
defined.
11-1 ,QWHJUDWLQJ5HYLVH1RWLILFDWLRQRI$EVHQFHLQWKH:RUNIORZ'HILQLWLRQ
You have already created a workflow template and integrated several steps into the
workflow definition. You will now continue by integrating the standard task
"Revise notification of absence" into the workflow definition.
11-1-1 Start from the SAP Easy Access menu. Choose "Change" under folder
Tasks/Task Groups, and then choose the workflow template you have
already created.
'RXEOHFOLFN&KDQJHXQGHUWKHIROGHU7DVNV7DVN*URXSV
Use F4 to show the possible entries if necessary, and enter the type
(WF) and the ID of the workflow template you created, into the relevant
input fields.
&KRRVH6HOHFW7DVN&KDQJHRUFKRRVHWKH&KDQJHEXWWRQ
&KRRVH*RWR:RUNIORZ%XLOGHU&XUUHQWYHUVLRQRUFKRRVHWKH
:RUNIORZ%XLOGHUEXWWRQ
This displays the Workflow Builder. Adjust the navigation area so that
the entire workflow can be seen in the display area.
SAP AG BC601 14-26

11-1-2 Creating an activity as a step in a workflow
Click in the node area on the icon for $FWLYLW\.The cursor changes.
Position the cursor on the Undefined step after the outcome Revised ,
and click. This inserts a step of the chosen type (Activity) into the
This displays the screen for defining an activity in standard mode.
(QWHULQJ%DVLFGDWDIRU&RQWURO
In the Task field, enter the ID ( TS<8-digit number> ) of the standard
task that you defined in the last exercise for
defining the Standard task "Revise Notification of Absence".
If you no longer know the ID, use the F4 help to search using the task
abbreviation.
Confirm your entries
by clicking on Enter . The screen "Define Container Elements and
Binding" is now displayed.
Confirm the binding by pressing the Enter key
Allocate the following, user-definable texts for step and outcome names:
6WHSQDPH Check notification of absence
2XWFRPH: Notification revised
11-1-4 Check the binding

In the Control tab, select the function Binding (exists) .
This displays the screen Binding for Step. .
Exit the screen.

Position your cursor in the input field Expression , and use F4 to call
Select Initiator of workflow .
Check the step and return to the Workflow Builder.
Test your workflow.
Activate your workflow.
You have the option to create several versions of workflow definitions
for a workflow template. However, do not use this option now.
SAP AG BC601 14-27

11-1-7 Fourth test: Revise Notification of Absence
You can now subject your workflow definition to another test. If you have
any questions regarding the procedure, refer to the preceding units, which
describe how to test the workflow definition.
Suggestion for testing:
1. Applicant: Start workflow (Refresh organizational environment)
2. Applicant: Create notification of absence
3. Superior: Reject notification of absence
4. Applicant: User decision: Revise
5. Applicant: Revise application (New step)
According to your workflow definition, you can only reach this step if
you decide to revise the application in the preceding step.
6. End of workflow
SAP AG BC601 14-28

7RSLF,QWHJUDWLQJWKH817,//RRSIRU5HDSSURYDO
In this exercise, you will extend the processing logic of the Notification
of absence workflow by incorporating an until loop. The until loop
introduces procedures that were not needed in the definition of previous
steps in the workflow definition.
If the initiator decides to revise and resubmit the application to his/her

superior, the form must be passed to the Check application step again.
There are various ways to achieve this. The advantage of the method
described below is that it introduces you to several new aspects of SAP
Business Workflow functions.
12-1 ,QWHJUDWLQJWKH817,//RRSIRU5HDSSURYDO
First, you need to create another element in the workflow container. It is used to
define the condition in the UNTIL loop. To assign values to the container element,
you need to carry out container operations with the workflow container.
12-1-1 Start at the SAP Easy Access menu and open folders Tasks/Task Groups .
Double-click "Change". Then choose the workflow template that is already
created.
Selecting a workflow template / Calling the Workflow Builder
As in previous units of this exercise, access your workflow template and
activate the Workflow Builder to start the required activities for this
exercise. If you require additional information to perform these tasks,
refer to earlier units for more detailed instructions.
From within the Workflow Builder, set the navigation area so the entire
workflow can be seen in the display area.
SAP AG BC601 14-29

12-1-2 Adding an Element in the Workflow Container
&KRRVH*RWR:RUNIORZFRQWDLQHU
The screen Workflow ....: Edit Container is displayed.
&KRRVH(GLW&UHDWH
Define the element in the following fields:
- (OHPHQW: Flag
- 1DPH Flag
- 'HVFULSWLRQ Revise: Yes/No
Container elements can be defined using ABAP Dictionary field

proposals. Use this option now.
Enter 6<67 in the Reference table field.
For Reference field , enter ,1387

Create the element.
12-1-3 Integrating the UNTIL Loop as a Step

Click in the node area on the icon for /RRS8QWLO. The cursor changes.
Position the cursor on the last step&RPSOHWH:RUNIORZand click.
This inserts a step of the chosen type loop (until) into the workflow
definition.
SAP AG BC601 14-30

12-1-4 Basic Data
Enter the following basic data:
6WHSQDPH: Loop (until)
&OLFNRQWKHWH[WLQWKH&RQGLWLRQZLQGRZ
This displays the screen Change Condition.
Select "Flag" from the Expression list by double clicking. This will
insert Flag in the Expression1 area of the screen. Select the (=)
operator from the Operators area.
Enter the operator ";" as the constant.
7KHZRUNIORZFRQWDLQHUHOHPHQW)ODJZKLFKUHIHUVWRDQ$%$3
'LFWLRQDU\ILHOGKDVWKHW\SH&+$5DQGOHQJWK7KHHOHPHQW)ODJKDV
QRW\HWEHHQDVVLJQHGDYDOXH,QWKHQH[WVHFWLRQ\RXZLOOWKHUHIRUH
LQVHUWFRQWDLQHURSHUDWLRQVLQWRWKHZRUNIORZGHILQLWLRQ7KHFRPSDULVRQ
EHWZHHQWKHFRQWDLQHUHOHPHQW)ODJDQGWKHFRQVWDQWH[SUHVVLRQ;
UHWXUQVHLWKHUWKHUHVXOWWUXHRUIDOVH7ZRVXEVHTXHQWRXWFRPHVDUH
WKHUHIRUHSRVVLEOH
End the condition editor with the button

Transfer condition, and return to the screen for defining the loop.
In the area entitled 2XWFRPHV, make the following entries:

7UXH: Flag has value X
)DOVH: Flag does not have value X
Check your entries and return to the Workflow Builder.
You have now inserted an isolated UNTIL loop into the workflow
definition. This does not yet make sense from a process logic point of
view; the step Check notification of absence must be within the loop
To understand the required steps, you must familiarize yourself with
block operations.
SAP AG BC601 14-31

12-1-5 Block Operations
Set the navigation area so that the entire workflow definition is visible in
the display area.
Display the block structure of your workflow definition.
&KRRVH*UDSKLF%ORFNV6KRZ
7KHZRUNIORZGHILQLWLRQLVEORFNRULHQWHG(DFKEORFNUHSUHVHQWVDQ
HOHPHQWDU\VWUXFWXUDOHOHPHQWWKDWIRUPVDVHOIFRQWDLQHGDQGFRQVLVWHQW
DUUDQJHPHQWRIVWHSVDQGRSHUDWLRQV
,IIRUH[DPSOH\RXFUHDWHDQHZVWHSWKDWKDVRQHVXEVHTXHQWRXWFRPH
WKLVSDLUVWHSRXWFRPHUHSUHVHQWVDEORFN,WLVLPSRUWDQWWRUHPHPEHU
WKDWRSHUDWLRQVWKDWDUHSHUIRUPHGRQRQHVWHSGHOHWHFXWHWFDOZD\V
DIIHFWWKHHQWLUHEORFNDVVRFLDWHGZLWKWKDWVWHS
,QWKHH[DPSOHDERYHLQZKLFKWKHEORFNFRQVLVWVRIWKHSDLUVWHS
RXWFRPHGHOHWLQJDVWHSZLOODOZD\VGHOHWHWKHFRUUHVSRQGLQJRXWFRPHDV
ZHOO<RXVKRXOGWHVWDOOWKHRSHUDWLRQVOLVWHGXQGHU(GLW%ORFN
First, save and activate your workflow.

Test the various block operations.
Any changes you make can be canceled by

Edit Undo.
$QRWKHUSRVVLELOLW\LVWROHDYHWKHZRUNIORZHGLWRUZLWKRXWVDYLQJ\RXU
ZRUNDQGWRWKHQFDOOLWDJDLQ
7KHVWHS&KHFNQRWLILFDWLRQZKLFKIROORZVWKHRXWFRPH$SSOLFDWLRQ
ILOOHGRXWLVWKHILUVWVWHSLQDQHZEORFN7RLPSOHPHQWWKH
UHVXEPLVVLRQWKHZRUNIORZPXVWIRUZDUGWKHDSSOLFDWLRQWRWKLVVWHSDIWHU
LWKDVEHHQUHYLVHGE\WKHSHUVRQFRQFHUQHG:HKDYHXVHGDQ817,/
ORRSIRUWKLVSXUSRVH
7KHVWHS&KHFNQRWLILFDWLRQRIDEVHQFHPXVWOLHZLWKLQWKLVORRS)RU
WKLVUHDVRQILUVWFXWRXWWKHHQWLUHEORFNWKDWVWDUWVZLWKWKLVVWHS7KHQ
LQWHJUDWHWKH817,/ORRSLQWRWKHUHPDLQLQJZRUNIORZGHILQLWLRQDQG
SDVWHWKHFXWEORFNLQWRWKH817,/ORRS
Select the step&KHFNDSSOLFDWLRQ.

Cut the block indicated by this step.
&KRRVH(GLW%ORFN&XW
In order to paste the cut block back in, select the undefined stepjust
before the UNTILloopstep and VHOHFW(GLW%ORFN3DVWH
&KHFNDQGDFWLYDWHWKHZRUNIORZ
The integration of the UNTIL loop has now been completed. For control
purposes, a few operations are still required with the container element
Flag which has not yet been assigned a value. We will therefore insert
several container operations into the workflow definition.
SAP AG BC601 14-32

12-1-6 Integrating the Container Operation as a step
The container operation allows you to manipulate individual elements of the
workflow container. The following operations are supported:
Addition, subtraction, multiplication, division,
assignment.
You need to insert a container operation at three different points in your
7KUHHFRQWDLQHURSHUDWLRQVDUHUHTXLUHGWRGHWHUPLQHZKLFKORJLFDOSDWKWR
WDNHLQWKH:RUNIORZ7KHIROORZLQJGRFXPHQWVZKLFKFRQWDLQHURSHUDWLRQV
DUHUHTXLUHGEXWRQO\RQHH[DPSOHLVVXSSOLHGWRGHPRQVWUDWHKRZWR
LPSOHPHQWFRQWDLQHUVLQWRWKHZRUNIORZGHILQLWLRQ
$WWKLVSRLQW\RXDVVLJQWKHYDOXH=WRWKHZRUNIORZFRQWDLQHUHOHPHQW
7KHFRPSDULVRQLQWKH817,/ORRSWKHQUHWXUQVWKHUHVXOWIDOVH,QWKLV
FDVHWKHZRUNIORZFRQWLQXHVEHFDXVHWKHRXWFRPHIODJGRHVQRWKDYH
YDOXH;DQGWKHDSSOLFDWLRQLVUHVXEPLWWHGLQWKHVXSHULRUVLQER[
Container operation after the outcome Application revised

Click in the node area on the icon for Container operation . The cursor
changes.
Position the cursor on the 8QGHILQHGVWHS that follows the outcome
$SSOLFDWLRQUHYLVHG and click. This inserts a step of the chosen type
(Container operation) into the workflow definition.
Make the following entries for basic data:
6WHSQDPH Set flag to Z
(YHQWQDPH Flag = Z
Make the following entries for operation:
(YHQWHOHPHQW (select using F4 )
([SUHVVLRQ Z
Make sure that the input fields for the operator and second expression
are empty.
Second operation after the outcome Withdrawn , and third operation
after the outcome Approved .
$WWKLVSRLQW\RXDVVLJQWKHYDOXH=WRWKHZRUNIORZFRQWDLQHUHOHPHQW
IODJ7KHFRPSDULVRQLQWKH817,/ORRSWKHQUHWXUQVWKHUHVXOWWUXH
7KHORRSLVH[LWHG
SAP AG BC601 14-33

Click in the node area on the icon for &RQWDLQHURSHUDWLRQ. The cursor
changes.
Position the cursor on the Undefined step which follows the outcome
:LWKGUDZQ, and click. This inserts a step of the chosen type (Container
operation) into the workflow definition.
Make the following entries for basic data:
6WHSQDPH Set flag to X
(YHQWQDPH Flag = X
Make the following entries for the operation:
(YHQWHOHPHQW Flag (select using F4 )
([SUHVVLRQ X
Make sure that the input fields for the operator and second expression
are empty.
Repeat this procedure for the outcome Approved .
7KHRSHUDWLRQHQWULHVDUHH[HFXWHGDWUXQWLPH:KHQ\RXVWDUWWKH
ZRUNIORZDQGWKH6HWIODJWR=VWHSLVH[HFXWHGWKLVPHDQVWKDWWKH
HOHPHQW)ODJLQWKHZRUNIORZFRQWDLQHULVJLYHQWKHYDOXH=7KHYDOXHRI
)ODJLVUHWDLQHGXQOHVVLWLVFKDQJHGH[SOLFLWO\
Go back to the workflow definition.

Check your workflow definition.
You have now made all the entries required to integrate the UNTIL
loop. You can carry out another test to check the UNTIL loop.
13-1 )RXUWK7HVW 3URFHVV1RWLILFDWLRQRIDEVHQFHZLWK8QWLOORRS

Go to the SAP Easy Access menu.
As the employee, initiate the notification of absence workflow template. Fill
out and save the form. This starts your workflow template.
Switch to the manager logon session and check the inbox for the form submitted
by the employee. The manager receives the form, and has the option to approve
or reject the employee'
s request for leave.
As the manager, first reject the application and then exit the notification of
absence processing.
When the manager refreshes his/her integrated inbox, the work item is no longer
in the inbox. The superior has performed his/her task. It is now up to the
applicant to decide how the process is to continue.
SAP AG BC601 14-34

$SSOLFDQWV3HUVSHFWLYH
Call the inbox using 5XQWLPHWRROV%XVLQHVV:RUNSODFH
Open folder Workflow .
Due to the rejection by your superior, you find a work item in your Workflow
inbox.
Execute the work item.
You are now in the user decision step of your workflow. You can either
withdraw or revise the application. You should decide to revise it.
Select Revise application in the User decision dialog box.
You can now see the advantages of follow-up work items starting immediately.
You can revise the application directly without switching to the integrated inbox
again.
Change the application (you can also resubmit it with the same entries).
Save and exit the notification of absence.
Refresh the Workflow inbox. The work item is no longer contained in the list.
Your manager is now required to take action again.
0DQDJHUVSHUVSHFWLYH
The employees application is resubmitted to the superior. He/she can carry out
the steps described above to approve or reject the application.
This workflow definition does not provide for a situation where employee
and superior do not reach an agreement. However, it would not be
difficult to integrate additional steps in the workflow definition (for
example, automatic notification of another person if the application is
exchanged repeatedly between the employee and head of department).
14-1 5HSRUWLQJDQG$QDO\VLV
You should start the workflow several times and test the alternatives. They can then
be analyzed using work item analysis or the workflow outbox. The step log
provides information on all stages of the processing. This includes the following
information:
Which steps were executed
Who the agent was
When processing was carried out?
The result of the processing
,WLVRIWHQQHFHVVDU\WRDXWRPDWLFDOO\VHQGQRWLILFDWLRQVDERXWVLWXDWLRQV
WKDWDULVHQWRSDUWLFXODUUHFLSLHQWV7RGRWKLV\RXFDQGHILQHDVLQJOH
VWHSWDVNWKDWVHQGVDQRWLILFDWLRQZKHQH[HFXWHG<RXWKHUHIRUHH[WHQG
WKHZRUNIORZGHILQLWLRQVRWKDWWKHSHUVRQUHTXHVWLQJYDFDWLRQLV
LQIRUPHGDXWRPDWLFDOO\RQFHWKHUHTXHVWKDVEHHQDSSURYHG
SAP AG BC601 14-35

15-1 'HILQLQJWKH6WDQGDUGWDVN6HQG1RWLILFDWLRQ
7KHVWHS6HQGPDLOQRZKDVLWVRZQZRUNIORZDFWLYLW\
&DOOWKH:RUNIORZ%XLOGHULQWKHFKDQJHPRGHIRU\RXUZRUNIORZ
=:)B12$B
15-1-1 Send mail

Click in the node area on the icon for 6HQGPDLO. The cursor changes.
Position the cursor on the 8QGHILQHGVWHS that follows the outcome
$SSOLFDWLRQUHYLVHG, and click. This inserts a step of the chosen type
(6HQGPDLO) into the workflow definition.
Make the following entries in the tab page Mail :
5HFHLYHUW\SH: Organizational object
([SUHVVLRQ: &_WF_INITIATOR&
6HQG([SUHVV: X
15-1-2 6XEMHFW:
Enter the text Vacation: , then click the Insert expression button
(beneath Subject text ).
Choose the attribute Notification of absence absent from 1st day by
double-clicking.
15-1-3 Mail text:

Enter a description that you want to send as confirmation.
Enter more than one attribute in your text.
Click the insert expression button at the bottom of the screen.
1RWH
7KHUHPXVWEHDWOHDVWRQHVSDFHEHIRUHDQGDIWHUHDFKDWWULEXWH
SAP AG BC601 14-36

15-1-4$IWHUZDUGVFOLFNRQWKHWDESDJH&RQWURO
)RUHDFK6HQGPDLOVWHSWKHZRUNIORZV\VWHP
DXWRPDWLFDOO\FUHDWHVDVLQJOHVWHSWDVN
&UHDWHWDVN
Enter the abbreviation of your mail task: T_MAIL_##,
then enter the /RQJQDPH for your mail task: Mail ##
Click Continue Enter and save your mail task.
The number of your task now appears in the Control tab page.
1RZHQWHUDVWHSGHVFULSWLRQIRUH[DPSOHVacation request.
This name is displayed in the Workflow Builder next to the activity.
)LQDOO\FKHFNWKHELQGLQJ
15-1-5$FWLYDWHDQGWHVW\RXUZRUNIORZ
In this test run, the superior approves the vacation request.
15-1-65HDGYDFDWLRQPDLO
This workflow sends the initiator a mail. This mail is not a work item. You
can read the mail in your Business Workplace.
In the Business Workplace, click on the unread documents in the inbox.
Double-click the subject line to display the mail in detail
7KH6$36\VWHPGRHVQRWDXWRPDWLFDOO\GHOHWHWKLVPDLO
DIWHU\RXKDYHUHDGLW
'HOHWHWKHPDLO\RXUVHOI
15-1-7 View once more the single-step task generated for you by the SAP System.
End of tutorial.
SAP AG BC601 14-37

$SSHQGL[*ORVVDU\
:RUG 'HILQLWLRQ
Activity Reference to a task as a step within a workflow definition. The
referenced task can be a single-step task (customer task/standard task) or
a multistep task (workflow task/workflow template).
Depending on the possible results and exceptions of the activity, the
appropriate branches are created for modeling the subsequent steps in
the workflow definition and are filled initially with an undefined step.
Activity profile Besides the task profile, the activity profile also comprises the reports
and transactions which are assigned to a particular job, position,
organizational unit, or user.
A task can be assigned to an employee personally or indirectly via
the position the employee occupies
the work center which belongs to the position
the job which describes this position
the organizational unit to which the employees position belongs
A user is assigned to the customer tasks and standard tasks which belong
to his/her activity profile as a possible agent.
A user can execute the workflow tasks and workflow templates which
are part of his/her activity profile.
Archiving object A work queue comprises a list of objects which are to be processed once
together within a specified period.
The work queue provides a framework for the individual items which
need to be processed and manages the list of objects which require
processing, including their status and the tasks which need to be carried
out on them. The status of the work item (type A) which represents this
work queue indicates the processing status of the work queue in general.
Asynchronous method Asynchronous methods are called and then run in their own logical
context. The calling program of the method continues its processing.
Asynchronous object methods do not return a result, nor any parameters
or exceptions but report their processing result using various (published)
events.
All methods based on SAP transactions are generally asynchronous
methods.
A single-step task which refers to an asynchronous object method must
be completed by one or more published events.
Attribute Property of an object.
The possible attributes of an object are defined as part of the object type
definition in the Business Object Repository.
Attributes can be used to formulate conditions in the workflow
definition. The object attributes are read or determined at runtime and
used to control the workflow.
An object attribute can return
the value of a field in the ABAP/4 Dictionary (database field
attribute)
an object reference to a (dependent) object
a value which is not determined until database contents are
calculated and/or evaluated at runtime (virtual attribute)
SAP AG BC601 14-38

Block Elementary structural element of a workflow definition.
A block always contains a consistent arrangement of steps and operators.
A block has exactly one input and output.
The consistency of the workflow definition is ensured because a block is
always generated when a new step is created or an undefined step
changed. When individual steps are deleted, cut, or inserted, the entire
block in which the step is located is affected.
Class This classification is used to distinguish the various functions of the
Workflow and SAPoffice components in the integrated inbox.
The user is only offered the functions possible for the class selected.
At present, the classes WF (workflow) and SO (SAPoffice) are
distinguished.
Condition Two-way fork (IF) as a step within the workflow definition.
The condition allows branching to occur based on control information
from the runtime-dependent context of the workflow and the application
objects processed.
Constant Fixed value or object reference as constituent of binding definition or
initial value assignment.
Container Basic common data structure of the various definition and execution
components of SAP Business Workflow.
Containers have a table-like structure and are used to hold values
(constants) and object references for control purposes for the workflow
process and execution of work items.
Container definition General information about the structure of the data which is to be stored
in a container. The elements which are held in a container are specified.
Each of these container elements is specified by entering its attributes.
The following are defined as the attributes of a container element:
its name
the descriptive short text
the data type of the value assigned to this element in the container
instance
The data type is described by specifying a data type reference (either
Dictionary field or object type).
A container definition is not an independent action but always
incorporated in one of the definition tools (object type definition, role
definition, task definition, workflow definition) in SAP Business
Workflow.
Container operation Operations on the workflow container as a step within the workflow
definition.
Container operations can be used to influence individual elements of the
workflow container.
Operations which can be carried out on the workflow container are:
elementary arithmetic operations
value assignments of an expression to a container element
Control flow in the The steps within the workflow definition can be arranged in sequence or
workflow definition in parallel (fork). Repeated processing of steps is also supported (loop).
The operators (OR), (AND), and XOR (exclusive or) are used for
branches in the workflow.
SAP AG BC601 14-39

Control record Data record containing information which identifies a process.
The control record contains the following information:
process number
process type
current status
person responsible
Customer task A single-step task created by customers to meet their specific
requirements.
Customer tasks have the following attributes:
object type T in organizational management
client-dependent, restricted period of validity, plan version-specific
Deadline The following deadlines can be set in the workflow definition:
requested start - earliest possible time for starting processing;
implemented by the system
requested end - requested deadline for completion of processing of
a workflow
latest start - latest deadline for starting processing a workflow
latest end - latest deadline for completion of processing of a
workflow
The deadlines are specified with reference to the start of the workflow.
The deadlines can only be specified if the respective workflow
task/workflow template was started by a user (and not by an event).
If the deadlines are exceeded, the deadline agent is generally informed.
Default role Agent information specified when a single-step task is defined in
addition to the assignment to its possible agents.
Default role for agent
The role specified is resolved at runtime to determine the selected agents
from the possible agents of the single-step task.
Default role for the deadline agent
Default role for the notification agent
Default roles are optional entries. If default roles are specified, it may be
necessary to define an appropriate binding from the task container to the
role parameter container. When an activity is defined within a workflow
definition, the default roles may be overwritten by other entries made on
responsibility.
By specifying default roles for determining the selected agents and the
deadline and notification agents, a single-step task is enhanced in terms
of modularity and reusability.
Delegation type Object type whose definition is used at runtime instead of another object
type although this other object type is specified in all definition
components (task and workflow definition, linkage tables,...).
The delegation type must always be a sub-type of the object type it is to
replace. The delegation type can have different or additional methods,
attributes, and events.
It is therefore possible to extend application objects in the standard
version easily as part of customer-specific configuration of the R/3
System.
SAP AG BC601 14-40

Dialog work item Runtime representation of a single-step task which requires user
interaction. It is generally these normal type W work items which are
displayed in a work list.
A single-step task represented by a dialog work item can be
apart of a workflow definition
In the workflow definition, reference is made to single-step tasks in the
steps activity and user decision.
started as a single step via an event or in dialog
Single-step tasks can be started as elementary activities directly in dialog
or via a triggering event. These customer tasks/standard tasks are also
represented by a dialog work item in the integrated inbox.
Entity type Entity types are formal representations of object classes of the business
world in the SAP System. Entity types have a reference to ABAP/4
Dictionary tables.
Each object type can be assigned to an entity type, which further
classifies the object type in the company environment.
Event Events are defined as a collection of attributes of objects in the workflow
object type catalog and they describe the change in the state of an object.
A publicized event is announced throughout the system by a special
function module that can be called up by any application or system
program (the event creator).
Information (the event parameters) is transported from the user who
created the event to the receiver in the event container. This ensures that
the events are linked to run time-dependent data, which is then available
to the receiver and can be used for event-driven control and
communication mechanisms.
Which function module should be called up as an event receiver is
determined in linkage tables flexibly and independently of the
application that initiated the event.
Event creator Creation of a published event as a step within the workflow definition.
The event is described uniquely by specifying the
event name
object type
The event must be defined in the object repository for this object type.
object key
The object key is specified as a container element of the workflow
container and contains the object reference to the object whose status
change is published by the event.
Event in the workflow State or result after processing a step. Each step in the workflow
definition definition is followed by at least one event.
These events describe the result or the state reached after a step and
therefore determine the branch of the workflow definition which is to be
executed. The events are displayed in both the graphical representation
and the alphanumeric representation. Events are used for the internal
control of the workflow.
Published events should be distinguished from these events.
SAP AG BC601 14-41

Event manager All the programs and tools provided by the workflow system for event
handling.
This term includes:
the definition components (for creating creator-receiver linkages) the
runtime components (for triggering an event instance, evaluating the
event instance with regard to existing linkages, managing the assignment
of creators to receivers, and for the actual data transfer)
Exception Object method exceptions are used for error handling and indicate
whether a method was successful.
All exceptions which can occur are defined for each method as part of
the object type definition. They are therefore known in the workflow
definition and can be taken into account in order to implement
appropriate response mechanisms.
Exceptions which are not referred to explicitly in the implementation of
a workflow definition generally lead to a termination of the running
workflow.
Exclude agent Users who are excluded from processing a work item.
Excluded agents are determined dynamically at runtime so that
information from the workflow execution environment (agents of
previous steps) or from the context of the processed application objects
can be taken into account.
Fork Parallel processing paths with their own independent steps within the
General task Flag for a task which can be executed or started by any user.
Inheritance Relationship between object types allowing common attributes and
methods to be passed automatically from super types to sub-types.
Inheritance is based on a hierarchical arrangement of object types with
an is a relationship.
Certain methods which can be used on all or many objects can be
defined centrally as an interface type and then used for several object
types. In this case, the method name and method parameter interface are
inherited.
Instance linkage Assignment of a specific receiver instance to a particular combination of
event, object type, and object key.
The instance linkage is entered in the instance linkage table by potential
event receivers via APIs. The instance linkage table is one of the two
linkage tables contained in the system.
If necessary, this instance linkage table is evaluated at runtime by the
event manager following the evaluation of the type linkage table. It is
only evaluated if an event could be assigned to an event receiver
according to the type linkage table and this linkage is not defined in the
type linkage table as a global linkage.
If an event is then created in the system with the values entered in the
instance linkage table for object type and key, the receiver ID specified
in the instance linkage table is written to the event parameter container,
the receiver function module specified in the type linkage table activated
by the event manager, and the receiver type and event parameter
container passed to this receiver function module.
If events are used in SAP Business Workflow (as triggering and
terminating events, in wait steps), the entries required in the linkage
tables are made by the workflow system.
SAP AG BC601 14-42

Integrated inbox Extended inbox as a front-end application which displays, manages, and
visually formats a users work list, in addition to the documents in the
SAPoffice inbox list.
The work list is the Workflow component in the integrated inbox and
contains the list of all work items (list of all jobs which need to be
processed) assigned to the user.
The work items can be displayed in the work list according to predefined
sort and filter criteria.
The selected agents determined from the organizational model and role
resolution can access the work items from their work lists and reserve
them for processing.
Various access authorizations are provided for displaying the work list
and accessing the work items.
Job Jobs are areas of activity in a company which are described by tasks.
Examples include secretary , clerk , or financial accountant .
Jobs can be created across organizational units.
Key field The key fields of an object type are defined as part of the object type
definition.
The definition of the key fields of an object type determines the structure
of the identifying key, which allows an object of this type to be accessed
uniquely.
The key fields may contain key fields inherited from the super type,
which can be extended by object-type-specific key fields. The key fields
of an object type are generally also the key fields of the table containing
the essential information on the object type.
Linkage table Table containing the assignment of events to the event receivers
interested in the event.
A distinction needs to be made between type linkage and instance
linkage which are contained in separate tables.
If events are used in SAP Business Workflow (as triggering or
terminating events, in wait steps), the entries required in the linkage
Loop Repeated processing of steps within the workflow definition until the
termination condition defined in the respective loop statement has been
reached.
UNTIL and WHILE are available as loop types.
Multiple condition Branching of the workflow definition into two or more branches as a
step within the workflow definition.
To evaluate the multiple condition, the value of the basis of comparison
is checked against the conditions at runtime and branching then carried
out accordingly.
You also have the option of branching to the others branch if none of
the conditions correspond to the value of the basis of comparison.
Multi-step task Runtime representation of a task or a step in the workflow definition.
Work items are subdivided according to type.
Work items which are visible in the integrated inbox are generally type
W work items ( dialog work item ). At runtime, they represent a single-
step task with user dialog or a user decision.
SAP AG BC601 14-43

Notification item Used to inform the notification agent that processing has been
completed.
The notification item is a mail document which appears in the SAPoffice
inbox list in the integrated inbox of the respective agent. The notification
item text is entered as a long text for the task which is represented by the
completed work item/workflow. This text can be assigned values from
the runtime-dependent environment of the work item/workflow
(attributes of the application objects involved).
When this type of document is executed, the key information on the
monitored or completed work item or the monitored workflow is
displayed. As with other mails, each agent can execute this mail
document. Each agent must process the mail in order to delete it.
Object Any type of related information which can be accessed uniquely under
an identifying key. Most of this information is generally stored in an
ABAP/4 Dictionary table.
The definition of what an object is not general but depends on the
specific context in which you use this term.
In particular, the definition referred to above does not indicate the
complexity or scope of an object. Two or more objects may, in another
context, be sub-object types of a composite object.
Objects are created at runtime and are the specific instances of a
previously defined object type which have been assigned values.
Object type Generic description of an object created at runtime.
While you use the term object when working with instances, which refer
to specific objects, terms, and numbers, a description (definition)
generalizing the elements of an object is used at the type level.
Objects are therefore the specific instances of an object type which have
been assigned values.
Object types are described and implemented in the object type definition
by specifying their elements:
basic data
key fields
attributes
methods with parameters, result and exceptions
events with parameters
implementation in program
The object repository contains a complete list of all object types. An
appropriate object type must be defined before an object is first used.
SAP AG BC601 14-44

Organizational Organizational management objects play a role in the integration of SAP
Management object Business Workflow and PD Organizational Management. The objects
are identified by an 8-digit number and a one- or two-character identifier
for their object type.
The following object types are used for the organizational plan and for
specifying agents or responsibilities:
organizational unit (O)
job (C), position (S)
user (US), employee (P)
work center (A)
role (AC)
Tasks are identified in the following way:
standard tasks (TS), customer tasks (T)
workflow templates (WS), workflow tasks (WF)
Organizational management objects also have an abbreviation which is
not necessarily unique and a descriptive name.
Organizational unit An organizational unit is one of the objects contained in an
organizational plan. Organizational units represent various entities of a
company created for business purposes. These may be departments,
groups, project groups, etc.
Organizational units can be created separately or linked together by a
hierarchical reporting structure.
Each organizational unit comprises positions. One (or more) of these
positions can be designated as the chief position of the organizational
unit.
Possible agent Single-step task (customer task/standard task)
Employees in the company who are organizationally responsible and
authorized to execute the work item which represents the respective task
at runtime.
Multistep task (workflow task/workflow template)
Employees in the company who are authorized to start the respective
task in dialog.
The assignment between a task and its possible agents is created when
the respective task is defined. It may also be determined indirectly by an
employees organizational assignment.
Program (implementation) ABAP/4 program containing the actual implementation of methods and
attributes of the object type.
Such a program is required for each object type, in addition to the
attributes, methods, and events with which the interface of the object
type is described and all significant information on the object type
documented. This program is usually created automatically as part of the
object type definition.
The call to the underlying ABAP/4 function and the provision of
parameters in the form of subroutines needs to be programmed for each
method defined for this object type. The individual read access also
needs to be programmed for each attribute.
This collection of subroutines is then accessed by the functions modules
of the runtime environment to call methods and read attribute values.
SAP AG BC601 14-45

Receiver function module Function module for receiving an event.
The potential event receiver must make available the receiver function
module. The interface of this function module is standard and
predefined.
The receiver function module requires the name of the event, the event
parameter container, and the name of the receiver type as input
parameters. Return parameters are not passed by the receiver function
module.
The receiver function module must be defined as RFC-enabled.
To use events in the SAP Business Workflow environment (triggering
events), a receiver function module
(SWW_WI_CREATE_VIA_EVENT) is available.
Receiver instance Instance of the object which is manipulated by the event receiver.
The ID of a receiver instance (receiver ID) is entered in the instance
linkage table at runtime by the potential event receiver. When the
instance linkage is established by the event manager, it writes the
receiver ID to the event parameter container and passes it to the receiver
function module declared in the type linkage table for further evaluation.
In the workflow environment (wait steps, terminating events), the
number of a work item is generally used as a receiver instance at
runtime. This entry is made by the work item manager.
Receiver type Additional input parameter for the receiver function module which
determines the type of object which is manipulated by the event receiver
(in the broadest sense).
The receiver type, like the receiver function module, is entered in the
type linkage table by the event receiver.
A value does not have to be entered in the type linkage table for the
receiver type; the receiver type is an optional import parameter of the
receiver function module.
In the workflow environment (triggering events), the unique ID of a task
is generally used as the receiver type.
Recipient Users who may actually process a work item and hence see it in their
Integrated Inbox.
When using a single-step task in a workflow definition, a user is only
included among the recipients of a work item, if he is a possible agent of
the single-step task and a responsible agent of the activity, but not an
excluded agent.
SAP AG BC601 14-46

Responsibility for activity The following are specified:
and user decision
the selected agent(s) - (not for steps which are executed in the
background, not for wait steps)
If an agent is not entered, the default role defined for the customer
task/standard task is evaluated at runtime.
If there is no default role for the customer task/standard task, processing
is carried out by the possible agents determined from the assignment of
the customer task/standard task to the objects of the organizational
model.
the notification agent
the deadline agent
If an agent is not entered, the default roles defined for the customer
task/standard task are evaluated at runtime. If there are no default roles
for the customer task/standard task, a notification is not sent to any
agents.
All entries are optional. They can be specified
as a role
as a PD organizational management object
as a container element
Responsible agent Agent assigned locally to an activity or a user decision in the workflow
definition.
Result A specific parameter of a synchronous method for returning the essential
result of this method.
The possible values of this result can be defined in a fixed value domain
or a check table so that they are known in the workflow definition and
can be taken into account.
Role A person (or group of persons) qualifying to process a customer
task/standard task or serve as an addressee for particular messages is
determined on a business and functional-oriented basis.
These selected agents or addressees are determined by role resolution.
This is not carried out until the runtime of the workflow, depending on
and using information from the process which is then running.
This ensures that when persons are determined, the resulting information
is always up-to-date. Substitutions and replacements can therefore also
be managed. The definition of roles for a customer task/standard task
also allows similar activities to be managed for specific countries,
customers, or products.
Role definition The role definition specifies which information (role parameters) needs
to be known so that role resolution can be carried out at the runtime of
the workflow. A container is therefore defined as part of the role
definition. It contains the role parameters as elements.
The name of the function module which is called by the workflow
manager or work item manager for role resolution must also be specified
in the role definition.
SAP AG BC601 14-47

Role resolution Determination of the agents combined in a role.
An appropriate function module containing the rules for role resolution
must be made available in order to resolve a role. The interface of this
function module is predefined.
Runtime-independent information (role parameters) and information
from the master data, stock data, or from customizing tables is used for
role resolution. The result of role resolution is a list of selected agents
who are responsible for the actual processing of the customer
task/standard task.
Root organizational unit A root organizational unit is the highest organizational unit in an
organizational structure, for example the board of directors .
A new organizational unit is created from the root organizational unit,
which therefore needs to be created first and must be unique.
Starting from the root organizational unit, the organizational plan is set
up by adding other organizational units. This is carried out in change
mode in an existing organizational plan.
SAP Business Workflow SAP Business Workflow 3.0 comprises technologies and tools for
automatic control and execution of cross-application processes. This
primarily involves coordinating
the persons involved,
the work steps required,
The data which needs to be processed (business objects).
Its main aims are to reduce throughput times and the costs involved in
managing business processes and to increase transparency and quality.
Single-step task Activity which is described by an object method.
Single-step task is used to refer to standard tasks and customer tasks.
In contrast to single-step tasks, multistep tasks are described by a
Standard task A single-step task which is supplied by SAP as part of a workflow
scenario and may also be used by customers.
Customers can create their own standard tasks.
Standard tasks have the following attributes:
object type TS in organizational management
client-independent, with unrestricted period of validity, not plan
version-specific
supplied by SAP
SAP AG BC601 14-48

Step Elementary module which makes up a workflow definition.
A step can be:
activity (= task reference)
condition, multiple condition
event creator, wait step
container operation
control command
user decision
loop
undefined step
The arrangement and sequence of the individual steps can be sequential
or parallel.
Steps within a workflow definition can only be changed or inserted
according to certain rules, taking into account the block orientation.
Step description The step is labeled and described in the workflow definition under this
name.
A step is identified uniquely by a node number, which is assigned to it
automatically.
Step log All steps in a workflow for which processing has been started are
recorded in the step log.
From the step log of a workflow, you can double-click on the
appropriate entry to branch and display the work item (and change it if
you have the appropriate authorization).
Errors which may have occurred during a workflow are displayed in the
step log and can be analyzed using the error messages shown.
Substitute profile The authorizations of a substitute are determined by the substitute
profile. This substitute profile is assigned to the substitute when the
substitution is defined.
A substitute profile comprises certain task classes. Customer
tasks/standard tasks are assigned to task classes when they are defined.
Substitute profiles are defined and task classes assigned to a substitute
profile in customizing.
The following substitute profiles which have been assigned task classes
are generally provided:
professional
disciplinary
Subworkflow Runtime representation of a multistep task used as a step in a workflow
definition.
Table element Element of the workflow container which has been defined as multiline
and can contain a list of values. A table element can be specified for an
activity step.
The activity is executed in parallel processing branches whenever values
are contained in the table.
SAP AG BC601 14-49

Task Goal-directed description of an activity.
The following need to be distinguished:
single-step task (customer task/standard task) - Activity in which an
object method is carried out on a specific object.
multistep task (workflow task/workflow template) - Activity in the
description of which a workflow definition is referenced.
In an activity, which can be a step in a workflow definition, reference is
always made to a task.
Task container Container of a single-step task.
The workflow container generally contains workflow-specific system
variables from the context of the single-step task or the respective work
item (object reference to the object to be processed, current agent of the
work item, ...), and the parameters (if available) of the method which is
to be executed.
Other elements which may be useful, for example, for variable
replacement in connection with notifications can also be added to the
task container.
Task profile List of tasks which are assigned to a particular job, position,
organizational unit, or user.
An employees task profile comprises the tasks assigned to him/her
personally and those assigned to him/her indirectly via
the position the employee occupies the work center which belongs to the
position the job which describes this position the organizational unit to
which the employees position belongs
A user is assigned to the single-step tasks which belong to his/her task
profile as a possible agent. A user can start the multistep tasks which are
part of his/her task profile.
Template Multistep task supplied by SAP which may be used but not changed by
customers.
Workflow templates are supplied by SAP and serve as usable templates
for workflow task definitions which are written by customers. Workflow
templates cannot be modified. Before changing and adapting a workflow
template to your own requirements, you should create a copy of the
template in a workflow task.
Workflow templates have the following attributes:
object type WS in organizational management
client-independent, unrestricted period of validity, not plan version-
specific
Terminating event Published event whose occurrence ends a single-step task.
Terminating events can only be specified for single-step tasks which
refer to an asynchronous object method.
The event must be defined in the object repository as an attribute of the
object type and must be specified as a terminating event of the single-
step task which is to be completed. A single-step task can have several
terminating events.
SAP AG BC601 14-50

Triggering event Published event whose occurrence starts a task (event receiver).
The event must be defined in the object repository as an attribute of the
object type and must be specified as a triggering event of the task which
is to be started. A task can have several triggering events.
Information from the event creation context can be passed to the
receiving task in the binding from the event parameter container to the
task or workflow container.
Type linkage Assignment of receiver function module and receiver type to a specific
combination of event and object type.
The type linkage is entered in the type linkage table. This table must be
filled if an event is always to be responded to in some way, even if the
linkage is instance-based. The type linkage table is evaluated at runtime
by the event manager.
The entry in the type linkage table needs to be made by the user or the
event receiver using a provided API.
If this linkage is defined as a global linkage, the receiver function
module specified in the type linkage table is always activated by the
event manager when an event is created in the system with a
corresponding value for the object type. The receiver type and the
event parameter container are passed to the receiver function module.
If the linkage is not defined as a global linkage, the instance linkage
table is also evaluated by the event manager.
If events are used in SAP Business Workflow (as triggering and
terminating events, for wait steps), the entries required in the linkage
Undefined step Serves as a placeholder for a step which will be specified later.
On the one hand, undefined steps can be inserted by the system, such as
when creating a new workflow definition or when inserting block
structures which are to be extended or specified later.
Undefined steps can also be inserted whenever individual steps are
required in a generated block which however still need to be specified
according to particular rules.
Undefined steps are always followed by an undefined event. Together
they form a unit and therefore ensure the consistency of a workflow
definition.
User decision Local decision by a user as a step within the workflow definition.
A question is defined with a decision text, which requires an explicit
decision by the current agent at runtime and whose response determines
which subsequent step is selected.
Up to four values from the workflow container can be referenced as
parameters in the decision text.
View Selection of work items on the basis of an evaluation path within the
organizational plan.
This evaluation path enables navigation from the user logged on to other
employees in the company and to the customer tasks/standard tasks
assigned to them. The successful use of these evaluation paths is based
on the relationships between the individual objects in organizational
management which are maintained in the organizational plan of a
company.
A user can therefore see work items in his/her integrated inbox which
are not assigned to him/her as a possible agent.
SAP AG BC601 14-51

Wait step Waiting for a published event as a step within the workflow definition.
Further execution (in this branch) of the workflow is not continued until
the relevant event occurs. The data from the event parameter container is
passed to the workflow container in accordance with the binding
definition.
The event is described uniquely by the
event name
object type
The event must be defined for this object type in the object repository
object key
The object key is specified as a container element of the workflow
container since it is not known at definition time.
The entries in the linkage tables are made by the workflow system.
Work item Runtime representation of a task or a step in the workflow definition.
Work items are subdivided according to type.
Work items which are visible in the integrated inbox are generally type
W work items (dialog work item). At runtime, they represent a single-
step task with user dialog or a user decision.
Work item manager Active unit which provides methods for the work items.
The work item manager has the following functions:
The work item manager can initiate calling of background
processes. This is necessary because activities in the workflow
definition can refer to object methods which run in the background.
The work item manager is responsible for deadline monitoring and
initiating appropriate measures (escalation).
The work item manager makes available the event interface. It acts
as the receiver of events for tasks which are terminated by an event
and for wait steps.
The integrated inbox is linked to the work item manager by released
interfaces. The Workflow component of the integrated inbox could, in
principle, be replaced by a customer-specific front-end application.
Work item text Text which appears in the integrated inbox to describe the work item.
The work item text is entered when a customer task/standard task is
defined.
The work item text can reference up to four elements from the task
container. At runtime, a text containing the current values of the
container elements is displayed.
SAP AG BC601 14-52

Work item type Work items are subdivided according to the work item type they belong
to.
Internal processing is controlled via the work item type. The work item
type determines the valid statuses and transitions.
Depending on the work item type, some of these work items are
displayed in a users work list. Other work items, however, are only used
and processed within the system.
The following work item types are displayed in the integrated inbox:
Work item type W (work item with dialog) - Runtime representation
of standard tasks or customer tasks which require user interaction
Work item type D (deadline item) - Work item for notification of
exceeded deadline
Work item type A (work queue) - Runtime representation of a work
queue
Other work item types which can only be displayed using the selection
report for finding work items are:
Work item type F (workflow item) - Runtime representation of a
workflow task/workflow template
Work item type B (background item) - Runtime representation of a
customer task/standard task which runs in the background.
Work item type E (event item) - Runtime representation of a wait
step
Work list List of all work items which are assigned to a specific user at a particular
time. This user is one of the selected agents of each work item.
Work queue A work queue comprises a list of objects which are to be processed once
together within a specified period.
The work queue provides a framework for the individual items which
need to be processed and manages the list of objects which require
processing, including their status and the tasks which need to be carried
out on them. The status of the work item (type A) which represents this
work queue indicates the processing status of the work queue in general.
Workflow Online execution (instance) of a predefined workflow task or a
predefined workflow template (multistep task).
A workflow consists of a sequence of steps, which are processed by
people or automatically by the system.
The chronological and logical sequence of steps linked to the evaluation
of conditions is handled by the workflow manager and can be controlled
flexibly by event-related response mechanisms.
SAP AG BC601 14-53

Workflow administrator Person responsible for the workflow definition from a technical point of
view (system administrator).
The workflow administrator should be able to correct errors in
workflows. This administrator receives a notification in the form of a
repair work item in the integrated inbox. When this repair work item is
processed, the step log of the incorrect workflow is displayed. It is
possible to analyze and correct the error from there.
The workflow in which the error occurred can then be resumed;
processing continues from the last step before the error.
The workflow administrator can be preset globally in the administration
data of the workflow editor and/or specified individually for each
workflow definition in its basic data.
The information on the workflow administrator is located in the
workflow container under the element _WF_Administrator which is
generally available.
Workflow container Container of a workflow task/workflow template.
The workflow container contains workflow-specific system variables
and other elements which are defined explicitly.
As part of the definition of the workflow task, the import and export
parameters of the workflow are defined as elements of the workflow
container.
When the workflow is defined in the workflow editor, elements can also
be added to the workflow container. These elements are then local
variables within a workflow definition and can be used, for example, to
set up a counting loop. However, these container elements can no longer
be defined as import or export parameters.
Workflow definition Description and technical implementation of a workflow process.
The workflow is defined using the workflow editor.
A workflow definition is made up of individual steps. The arrangement
and sequence of the individual steps can be sequential or parallel.
The representation of a workflow definition in the graphical editor is
based on the methods and symbols of the R/3 Analyzer reference
models.
Workflow editor The workflow editor allows the workflow definition to be implemented.
The workflow editor provides two views of the workflow definition. It is
possible to edit a workflow definition from both views with the same
functionality:
Tree representation The steps, events, and operators are shown in
a tree-like hierarchy. A maximum of three consecutive node levels
can be displayed.
Graphical representation (graphical editor) - The steps, events, and
operators are shown graphically in a network. In the graphical
representation, the step symbol is a green rectangle with rounded
corners. Events are indicated by red hexagons. Operators are
represented by blue circles.
Workflow manager Programs and functions provided by SAP Business Workflow at runtime
for controlling and managing a workflow.
SAP AG BC601 14-54

Workflow task A multistep task defined by customers to meet their specific
requirements.
Workflow tasks have the following attributes:
object type WF in organizational management
client-dependent, restricted period of validity, plan version-specific
SAP AG BC601 14-55

7UDQVDFWLRQ&RGHVDQG0HQX3DWKV
7UDQVDFWLRQ 0HQX3DWKIURPDUHD
&RGH PHQX
6$3%XVLQHVV:RUNIORZ
'HYHORSPHQW
$:89 Wizard for event creation 'HILQLWLRQWRROV(YHQW Event Creation
FUHDWLRQ6HWXSZLWK
ZL]DUG
0&$ Workflow Information 5HSRUWLQJ:RUNIORZ Workflow
System ,QIRUPDWLRQ6\VWHP:,6 Information System
(WIS)
22$: Evaluation paths
3)$& Maintain standard roles Role Definition
3)$&B&+* Change roles 'HILQLWLRQWRROV
6WDQGDUGUROHV&KDQJH
3)$&B'(/ Delete roles 'HILQLWLRQWRROV
6WDQGDUGUROHV'HOHWH
3)$&B',6 Display roles 'HILQLWLRQWRROV
6WDQGDUGUROHV'LVSOD\
3)$&B,16 Create roles 'HILQLWLRQWRROV
6WDQGDUGUROHV&UHDWH
3)20 Maintain assignment to SAP 'HILQLWLRQWRROV6$3 Making Links in
organizational objects RUJREMHFWV&UHDWH PD Organizational
DVVLJQPHQWV Management
3)26 Display assignment to SAP 'HILQLWLRQWRROV6$3
organizational objects RUJREMHFWV'LVSOD\
DVVLJQPHQWV
3)62 Organizational environment
of a user
3)7 Maintain customer task
3)7& General task maintenance Creation and
Processing of Tasks
3)7&B&+* Change tasks 'HILQLWLRQWRROV
7DVN7DVNJURXSV
&KDQJH
3)7&B&23 Copy tasks 'HILQLWLRQWRROV
7DVN7DVNJURXSV&RS\
3)7&B'(/ Delete tasks 'HILQLWLRQWRROV
7DVN7DVNJURXSV
'HOHWH
3)7&B',6 Display tasks 'HILQLWLRQWRROV
SAP AG BC601 14-56

7DVN7DVNJURXSV
'LVSOD\
3)7&B,16 Create tasks 'HILQLWLRQWRROV
7DVN7DVNJURXSV
&UHDWH
3)75 Standard task for transaction Simplified
Definition of
Standard Tasks
3)76 Standard task
3):) Maintain workflow task
(customer)
3):6 Maintain workflow template
332& Create organizational plan 'HILQLWLRQWRROV Enterprise-Specific
2UJDQL]DWLRQDOSODQ Organizational Plan
&UHDWH
3320 Maintain organizational 'HILQLWLRQWRROV
plan 2UJDQL]DWLRQDOSODQ
&KDQJH
3326 Display organizational plan 'HILQLWLRQWRROV
2UJDQL]DWLRQDOSODQ
'LVSOD\
6:'$ Ongoing Settings $GPLQLVWUDWLRQ6HWWLQJV (Ongoing) Settings
6:'& Workflow editor Customizing, part of Workflow Editor
administration data ongoing settings Administration
Data Maintenance
6:'0 Business Workflow 'HILQLWLRQWRROV Functions of
Explorer %XVLQHVV:RUNIORZ Business Workflow
([SORUHU Explorer
6:( Display and maintain event 8WLOLWLHV(YHQWV Type Linkage
type linkage 7\SHOLQNDJHV Table Maintenance
6:( Display instance linkages 8WLOLWLHV(YHQWV Instance Linkage
,QVWDQFHOLQNDJHV Evaluation
6:( Switch event log on/off 8WLOLWLHV(YHQWV Event log
(YHQWORJ2Q2II
6:(& Link change documents to 'HILQLWLRQWRROV(YHQW Creation of Events
events FUHDWLRQ&KDQJH When Change
GRFXPHQWV/LQNDJH Documents are
Written
6:(' Assignment of change 'HILQLWLRQWRROV(YHQW Relevant Settings
document objects to object FUHDWLRQ&KDQJH for Change
types GRFXPHQWV'HILQH Documents
ZRUNIORZSURSHUWLHV
6:(/ Display event log 8WLOLWLHV(YHQWV Event log
SAP AG BC601 14-57

(YHQWORJ'LVSOD\
6:) Workflow Wizard Explorer 'HILQLWLRQWRROV Workflow Wizard
:L]DUGV:RUNIORZ Explorer
:L]DUG([SORUHU
6:) Workflow Wizard 'HILQLWLRQWRROV Workflow Wizard
Repository :L]DUGV:RUNIORZ Repository
:L]DUG5HSRVLWRU\
6:, Selection report for 8WLOLWLHV:RUNLWHP Selection Report
workflows VHOHFWLRQ for Finding Work
Items
6:, Work item analysis 5HSRUWLQJ:RUNLWHP Work Item
DQDO\VLV Analysis
6:, Workflow outbox 5XQWLPHWRROV Workflow Oubox
:RUNIORZRXWER[
6:, Task analysis 5HSRUWLQJ7DVN Task Analysis
DQDO\VLV
6:, Workload analysis 5HSRUWLQJ:RUNORDG Workload Analysis
DQDO\VLV
6:, Object links 5XQWLPHWRROV2EMHFW Object Links
OLQNV
6:, Workflow resubmission From Integrated Inbox or Workflow
folder Workflow Outbox Resubmission
Folder
6:, Error overview Part of administration of Error Selection
workflow runtime system
(transaction SWUF)
6:/ Settings for dynamic Customizing, part of Defining Dynamic
columns ongoing settings Columns for
Integrated Inbox
6:/& Check tasks for agents 8WLOLWLHV&RQVLVWHQF\ Display
FKHFN2UJDQL]DWLRQDO Organizatioional
DVVLJQPHQW Assignment
6:/' Workbench for Workflow Area Menu SAP
4.0 Business Workflow
(Development)
6:/3 Copy plan version
6:/9 Maintain work item views Customizing, part of Views
ongoing settings
6:/: Workbench for Workflow Area Menu SAP
3.0 Business Workflow
(Organization)
6: Business Object Builder 'HILQLWLRQWRROV Business Object
%XVLQHVV2EMHFW%XLOGHU Builder
SAP AG BC601 14-58

6: Customizing object types )URP%XVLQHVV2EMHFW Adapting Object
%XLOGHUFKRRVH6HWWLQJV Types on a
'HOHJDWH6\VWHP Customer-Specific
ZLGH Basis
6:8 Event simulation 8WLOLWLHV(YHQWV Simulation: Event
6LPXODWHHYHQW Creation
6:8 RFC monitor 8WLOLWLHV:RUNIORZ RFC Monitor
5)&PRQLWRU
6:8 Customizing consistency 8WLOLWLHV&XVWRPL]LQJ Auto-Customizing
check and Consistency
Check for
Customizing
6:8 Consistency check for 8WLOLWLHV&RQVLVWHQF\ Consistency Check
standard tasks FKHFN7DVN for Tasks
6WDQGDUGWDVN
6:8 Consistency check for 8WLOLWLHV&RQVLVWHQF\
customer tasks FKHFN7DVN
&XVWRPHUWDVN
workflow tasks FKHFN7DVN
:RUNIORZWDVN
workflow templates FKHFN7DVN
:RUNIORZWHPSODWH
6:8 Switch technical trace 8WLOLWLHV7HFKQLFDO Technical Trace
on/off WUDFH2QRII
6:8 Display technical trace 8WLOLWLHV7HFKQLFDO
WUDFH'LVSOD\
6:8' Diagnostic tools 8WLOLWLHV'LDJQRVLV Error Diagnosis -
List of Problems
and Solutions
6:8( Trigger event 8WLOLWLHV(YHQWV Creation of an
*HQHUDWHHYHQW Event for Test
Purposes
6:8) Runtime system $GPLQLVWUDWLRQ Administration of
administration 5XQWLPHV\VWHP Workflow Runtime
System
6:8* Workflow start transactions 'HILQLWLRQWRROV Definition of a Start
:RUNIORZVWDUW Transaction for a
WUDQVDFWLRQV Workflow
6:8, Start workflows From the R/3 initial Starting a Task in
screen, choose Dialog
2IILFH6WDUW:RUNIORZ
6:86 Start tasks 5XQWLPHWRROV6WDUW Starting a Task in
SAP AG BC601 14-59
ZRUNIORZ Dialog
6:8< Wizard for message linkage 'HILQLWLRQWRROV Starting a Task
to workflow :L]DUGV&UHDWH&DOO from Message Long
ZRUNIORZIURPPHVVDJH Text
6:; Create notification of
absence
6:; Change notification of
absence
6:; Display notification of
absence
6:; Approve notification of
absence
6:;) Form applications: (QYLURQPHQW'HPR Demo Example:
Access point H[DPSOHV)LOORXWIRUP Processing a
Notification of
Absence
SAP AG BC601 14-60

:KLFKZRUNIORZWHPSODWHVDUHDYDLODEOH"
Detailed information is available on the Online Documentation CD as well as in the Online Help. The Templates
listed here are internationally available templates. There are other templates available for specific countries only.
6XSSOLHGZLWK5HOHDVHDQGEHORZ
&$&URVV$SSOLFDWLRQ&RPSRQHQWV
Processing Document Info Records (CA-DMS)
Message Control (CA-GTF-BS)
EDI Status Record Processing (CA-EDI)
ALE Error handling on incoming Idocs
),)LQDQFH
Workflow Scenarios in Finance (FI)
Parked Documents
Payment Release
Financial Calendar
Workflow Scenarios in Asset Management (FI-AA)
Bulk Changes to Master Data
Mass Retirement
Processing Incomplete Assets
Triggering a Workflow From a Validation (FI-SL)
/2/RJLVWLFV
Changes with Reference to an Engineering Change Request or Engineering Change Order (LO-ECH)
Logistics Information System: Trigger Workflow from an Exception in the Early Warning System (LO-
LIS)
000DWHULDOV0DQDJHPHQW
Releasing a Purchase Requisition (MM-PUR-REQ)
404XDOLW\0DQDJHPHQW
Quality Notification (QM-QN)
Quality Inspection (QM-IM)
303ODQW0DLQWHQDQFH
Maintenance Order Management (PM-WOC-MN)
Purchase Order Change (PM-WOC-MO)
Service Management (PM-SMA)
363URMHFW6\VWHP
SAP AG BC601 14-61
Workflow in the Project System (PS-EXE-WFL)
3$3HUVRQQHO$GPLQLVWUDWLRQ
Recruitment (PA-APP)
Personnel Administration (PA-PAD)
Process Absence Approval (PA-TIM-REC)
Automatic Generation of Documents for HR Applications Using SAP Business Workflow
%&%DVLV
Demo Example: Processing a Notification of Absence (BC-BEW-WFM)
Example: Processing a Notification of Absence using SAPforms (BC-BEW-WFM Form)
1HZZLWK5HOHDVH
0RGLILFDWLRQVRIH[LVWLQJWHPSODWHVDUHQRWPHQWLRQHGKHUH
),)LQDQFLDO7UDYHO([SHQVHV
Trip request approval (FI-TV)
Trip Reimbursement approval (FI-TV)
000DWHULDOV0DQDJHPHQW
Releasing a whole Purchase Requisition
Releasing a Purchase Order
Releasing a Quotation
Releasing a Contract
Releasing a Scheduling Agreement
Settlement of Agreements in Purchasing
Release of locked Vendor Data
Process Absence Approval (using SAPforms)
Raise of Salary (using SAPforms)
5HWDLO
Currency Conversion (LO-MD)
1HZZLWK5HOHDVH
3'3HUVRQQHO'HYHORSPHQW7UDLQLQJDQG(YHQWV
Business Event Lifecycle (PE)
+5+XPDQ5HVRXUFH(666FHQDULRV
SAP AG BC601 14-62

Notification change of address (HR-CA)
ESS Activities after Hire (HR-CA)
ESS Activities after Leaving (HR-CA)
+5+XPDQ5HVRXUFH0DQDJHUV:RUNEHQFK
Notification/Approval for New Positions (HR-CA)
Approval of Organizational Change (HR-CA)
6'6DOHV
Dealing with Credits (SD-SLS-OA)
Change of Group Contracts (SD-SLS-OA)
7UHDVXU\
Approval of Investments
5HWDLO
Release of Locked Deliverer Data (LO-MD-BP)
5HDOHVWDWH
Management of Rental Units
%DVLV
Customer Record approval via WEB
1HZZLWK5HOHDVH
Salary & Bonus Approval (PA-CN)
3'3HUVRQQHO'HYHORSPHQW7UDLQLQJDQG(YHQWV
Qualification Planning (PE)
SAP AG BC601 14-63

BC601 en 46C FV

Загружено:

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

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

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

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

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

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

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

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

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

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

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

BC601 en 46C FV

Загружено:

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

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

6$3%XVLQHVV:RUNIORZ

SAP AG BC601 1-1

SAP AG BC601 1-2

SAP AG BC601 1-3

Unit 1 &RXUVH2YHUYLHZ Unit 8 &RQWDLQHUV

SAP AG BC601 1-4

SAP AG BC601 1-5

SAP AG BC601 1-6

SAP AG BC601 2-1

n This unit is a short review of BC600 SAP Business Workflow - Introduction

SAP AG BC601 2-2

SAP AG BC601 2-3

SAP AG BC601 2-4

SAP AG BC601 2-5

SAP AG BC601 2-6

0HWKRGV   !#"%$  $WWULEXWHV %XVLQHVV

SAP AG BC601 2-7

SAP AG BC601 2-8

f g* ''h* )'

& (')%* + ,-* .)$

SAP AG BC601 2-9

n For each step you should ask yourself:

SAP AG BC601 2-10

SAP AG BC601 2-11

&RQQHFWH[LVWLQJRUJDQL]DWLRQDO 2UJDQL]DWLRQDOVWUXFWXUH 7KHUHLVRQO\RQH

SAP AG BC601 2-12

n The maintenance of SAP organizational management is available as a Basis component.

SAP AG BC601 2-13

SAP AG BC601 2-14

SAP AG BC601 2-15

SAP AG BC601 2-16

0DWHULDO  (QWU\LQ

2OGPDWHULDOQR 2ULJLQDOBSDUW WULJJHUV

/DE 30 (YHQW

n General scenario for this process:

SAP AG BC601 2-17

SAP AG BC601 2-18

At the conclusion of these exercises, you will be able to:

In previous software projects you have done some programming. Now

SAP AG BC601 2-19

task standard task single-step task

SAP Workflow multi-step task workflow template

object method object type

1-2-1 An__________________________ is the encapsulation of functionality and

1-2-2 The_________________________ refers to a generic description of an

1-2-4 ___________________________ refers to an object method or a manual

1-2-5 ___________________________ is a pre-defined workflow definition

1-2-6 Interaction between the runtime execution of workflows and users

SAP AG BC601 2-20

1-2-8 A multi-step task defined by the user or supplied by SAP is called a

1-2-9 The ___________________________ is a tool that is used to define, access

1-2-10 The technical implementation of a business process is referred to as a

1-2-11 From an organizational perspective, ___________________________ are

1-2-12 Any number of workflows can be derived from a workflow definition as

SAP AG BC601 2-21

At the conclusion of these exercises, you will be able to:

Personnel positions within the organization are assigned as responsible agents to

SAP AG BC601 2-22

SAP AG BC601 2-23

1-1 The correct answers are as follows:

1-2-1 AnREMHFW is the encapsulation of functionality and behavior for performing

1-2-2 The2EMHFWW\SH refers to a generic description of an object created at

1-2-4 0HWKRGV refers to an object method or a manual activity.

6$3%XVLQHVV:RUNIORZ

0HWKRGV !#"%$ $WWULEXWHV %XVLQHVV

f g* ''h* )'

& (')%* +,-* .)$

0DWHULDO (QWU\LQ

2OGPDWHULDOQR 2ULJLQDOBSDUW WULJJHUV

/DE 30 (YHQW

2-2-2 The next step is creating the position =SRVBHPSOB

MNCO#9;PJ 7$B @ 9;CQ9;CQJR9;C5@ B 9;K@SCTU92OF809KV0@ B 2JQ:8W@ BIXWB J 6 9; 7 ZY

B#7 B < 7B :9O G7 ?VT;P9;FC<0_`9 G

#B 7 BFB @ JUa92O G7 ?2VT=9;FC2<b_=9 G 10:25:00

Displays existing document templates.