You are on page 1of 129

GlobalSoft Solutions, Inc.

505, Thornall Street, Suite 300


Edison, NJ 08837

m  
   
   

àusiness Workflow
m 

 




 

 
àusiness Workflow
m 

 




 

 
Workflow Definition
‡ 
 
cross-application tool
 


 
 
tasks/processes  

 

‡ T
 
! !
"#$" $%  !

&!   


' ("  )* 

 !  
!
Need for Workflow
‡ 
   
 &  +

 
  & !
!  
 


 , 
  -
   
 !  .

‡ T 
  
/
  

 
 '  

 0 !,
0 

.
 + 

1
!

‡     ensures that the right work is sent to


right person at the right time in the right sequence with the
right information
Why SAP Workflow?
‡ T 
2
 business
processes
‡ N
!  
 


‡ O 
across applications
‡ !



 
‡ &
!  
active support
Workflow àoundaries
‡ T    existing transactions 3 function
modulesT 
 
 !

0


 
  ! 
 !   
 ! 
 
! 

‡ 
 !  
& 
 !
  

 


‡ T   "#$ 


 



   r r 
r 


àusiness Workflow
m 

 




 

 
Workflow
‡ 
  1  
 
 !

 
  
Workflow àuilder
‡ M!


!


 
 
 ! !



 T  !
&!



Workflow Definition
‡ T
! 

 
‡ !


 
! 
!
&
! 
  !&  
   ! 
&  
  
T 
 
  !
 1  

‡ T!


 
   
!
  
40   1


 

 ! 


1  

   !
Workflow Instance
‡    

 

!  


 40 


  1


 
  
Task
‡ TT    
 
&
!
 

 40 &



   
 

‡ D 
 
  
   


‡ 4
  0

 0/
 
-  
‡ 
&


 (!
0 !  


(
 M 
-  ,.
‡ 
&
 ! 

 
 !  
!



Work Item
‡ 

 
 

! 
 4
0   
  &

 
Agent
‡       ,&


 .40 1


  !
 
! 

‡    

 
&


  !0  


‡ T    &



 
  
‡ U 
 
2
  
2!   !
0  
!

 " 
  
‡ U 
! 
!



 '0 !!  
‡ U 
0 !!


›ontainer
‡  

! !

!

‡ 
 !   &
 !


 

‡  
 & 
  !

/
 5  ,   .
   
 O(  
 0

‡ T 
    ! 0 
 
 
 ! 

‡ T  
/
  

 T  

 '&  

 M! 

 "  

àinding
‡ 
!

   !

!

 !
 

‡ 
 &   
 
 


‡ 
!
!


 /
 


 
   ! 



 ! 
 
0 !  
 
àusiness Object àuilder
‡ T
 !

 (
 

‡   ! !




  (


‡    !0




 
(
Object Type
‡ 
 ( 
 ! ! 
 

 

 
  

‡ T 




 

 
0


 !   
1
!! 
  &
  
Object Type
‡ D 

 !,( .
  !!


 



 O(
!

‡ O( ! 
! !
 ! 



   /
 
!
 6
!
 
 
 M! 
   !0

 '&  

  
  

‡ TO( !
!
 !,O( . 
!
  
Workflow project Approach
! 

  

Does an SAP
workflow already
Yes exist in the standard No
system

U  1. 

 
2.

3. T 
àusiness Workflow Overview
m 

 




 

 
WORKFLOW AR› ITE›TURE
Workflow Architecture
" T 

O 
2
 

 

 #( O 


4!



  


  '&  M!


  O(
O(
WORKFLOW ›USTOMIZING
What Auto-
Auto-›ustomizing Does
‡ The automatic workflow customizing sets up the system using
defaults so that you ready to use the system as quickly as possible.

‡ The most important activities are as follows:


 Maintain Active Plan Version
‡ Plan version (with its contents) is seen by the workflow system
as the only valid plan version.
‡ All SAP Workflows supplied automatically become part of the
plan version that has been selected as the active plan version
‡ Only one of the plan versions created in the system can be
active.
 ›onfigure RF› Destination
‡ The runtime system always executes its tRF› calls via the
logical destination WORKFLOW_LO›AL_XXX (XXX stands for
client number)
‡ The workflow runtime system is client dependent i.e. a single
workflow instance normally executes within one client
 Maintain Workflow System Administrator
 Schedule àackground Job for Missed Deadlines
 Maintain Prefix Numbers
Automatic Workflow ›ustomizing:
SWU3
›ustomizing the system is the very first step that you will take when
you plan to use workflow

U 
  
 

 
2

 
2


 
&

 
2



&
ORGANIZATIONAL
STRU›TURE
›reating an Organizational Plan
Crti

r 
izti
l l
(il
i
t

)

  
   
 ! 
! 
"!
"! # 
# 
t m t  iti
l
Crt rt r 
izti
l
it
r 
izti
l
it

t 4  t  Crt


ð 
ð iti
 j ð 
ð

 


 ! 
! 
t  i
t  i

l r l r


   

   
    

m. r rm 

    
. B i
r l I r r t


l ,C m

     
r rtr . i

  r 
tl   l  tri
i

ti
t l  r  tril fr
t
r. l  il  lit f i l  ti 
r r mt. I ill  rti
 ririt
liti
fr t

   


  
  
ü §   777
 

‡ The above diagram illustrates that the first step in Simple Maintenance is to
create a root organizational unit. Once one organizational unit has been created,
the organizational units below it have to be created.
‡ Organizational units and jobs may be created in any order but must exist before
the associated positions are created.
‡ Jobs may exist in the job index or may be created once the model contains an
organizational unit.
‡ Positions are created once the relevant jobs have been created in the job index.
‡ Tasks are assigned using jobs and positions.
‡ olders are assigned to positions, not to jobs.
Assignment Workflow Tasks:
i

t
rfl  - Ör 
izti
l Öj t
Organizational Objects
Ör 
izti
l
it II rt
t
Ör 
izti
l
it rt
t

 r j

 r j 
m, 
 iti
  f I
rt
t 8
8 

 4
 fr
 fr  rtr
 rtr 
, 
iti

iti
  rtr
 rtr
8
8 9
9

iti
 II  i
itrtr
iti
  i
itrtr mm 8
8 


 fr
 fr II 
l
l
4, 
iti
 II  i
itrtr
iti
  i
itrtr

8
8 


‡ The relevant users receive a work item at runtime.


ü §   777

 Task 1: User 1 (via manager job)


 Task 2: User 1, user 2 (via manager job/job for secretary)
 Task 3: User 1, user 2, user 3, user (via organizational
unit)
 Task : User 1, user 3, user (via position for head of FI
department/job for FI employee)
 Task 5: User 2 (via secretary job)
 Task 6: User 3, user (via job for FI employee)
›reate Job: PPOM
Positions
Positions

Task: Approve
vacation request X Positions are specific to your
organization.
X Multiple positions may
perform similar job tasks.
X Each position typically
represents one employee, but
Job: ›hief may be partially filled by more
than one.

Position: Position:
›hief - Europe ›hief - West Region

Position:
›hief - East Region

ü  m
›reate Position: PO13
Bi  fi
iti
fr rfl
àasic R Definition for Workflow

 


rt
rt  r
 r r 
izti
l
r 
izti
l l

l
i l i
t
i l i
t f
ti 
µil
f
ti 
µil i
t

!
i
t

!
i

i

 Ör 
izti
l
Ör 
izti
l 
 
t.

 
t.   
l tr fr

l tr fr t
t i
i j t
j t

tir

tir rlti
i.
rlti
i.

 
2 
 






8 

ü §   !777

 T 
 T-!/4T

›lient Independent
 !! /TS
T/WS
T   /TG

N  ! 
!

&
 &


›lient Dependent
   /T
T /WF
Five Questions for each part of a àusiness
Process and how to map them in Steps/Tasks
In What Order?: Workflow Definition

Workflow definition controls the calling


sequence of each step. Steps like workflow,
can also be triggered by events.
In What Order?: Workflow àuilder
(SWDD)« ow
Workflow it looks
Definition: Workflow àuilder

Workflow
Workflow
definition
definition Workflow àuilder:
Triggering
event Ë N&

  !!

Ë 
/:#"#$ #

Ë  !
&
Step

Symbol for
workflow start
and end

ü  m """
With What Object? What?:
T-code: PFT›, ›alling Methods within a Task
O(M! 

&O(  O(
T !M!N

D

‡ #  
‡D
 #
 D


D

!
 T 
 
 !M!
With What Object?:
àusiness Object and its Method

 O(
' U %;
What?: Method
›onfigurations
What?: Method Parameters
W O: Agents
" 
  

'0 !!  


  

      

  
 

 
!


   

 
When? T-code: PFT›
Events can be used to trigger:
‡
 


‡   
‡
    
     
When?
SWDDË Double ›lick on Step«

 !

 M 
 !

  !U D

 
&    !! !

  !

   
0 !

O   !  !  !



STEP TYPES
Step Types in Workflow
U D

 

- T  
 !1  
  !
& -!
!

 

- 
 &




- ' 
  

Step Types in Workflow
:,U 
.

" 
 /
-   

&

  ! 
 !

 
Step Types in Workflow

 !M
/

- T0 !

 
   
 -


- 0 ,  


!. !
 

 ,
 .   
Step Types in Workflow
‡  !M
/
T (



- <%
 
0

T

 


'  

T 
0



Step Types in Workflow
‡  !
/
TM
T0

   !
! 

 T




T  T 
, !
ONT"O:.
T (


  


T0
Step Types in Workflow

 !



" 
 /
-   !
  
 
  
 ! !   !

 

  
 !


Step Types in Workflow
  

- T
  ! 0 
 

 

 

- 

     

   
Step Types in Workflow
  /

T 
 T
 
 
 ! &


! !
 
 
4 
  
 
Step Types in Workflow
M 
 !

 /

 ! & 


 
   &
  

 !
M 
 !


Step Types in Workflow
'& /

- T
 & 


- D& & 
Step Types in Workflow

/

- T  
  

& 

!

- T

 !
0!
&  
Step Types in Workflow
4/
- U !  


- T  !


    ! 
 !!4
 !
 


- T 
!!

 !

 
Step Types in Workflow
 

 /

- 4  






 & 
  
 

-     !!

  !
- M 


 !
Step Types in Workflow

! 

-
&  
   &
 
  


- T   ! 



 
Step Types in Workflow

&


- T ! 
   !


 =M:O
  
Step Types in Workflow
‡  /
-  
&
   
 

‡ U !
!/

-T   ! ! ! 


!& 

- T
! 

›ONTAINER & àINDING
What is a ›ontainer
‡  
  !
!
  
 > 
  

‡  
  !

 
!
   ! 
 !
 

 
Type of ›ontainers
‡  
 ! 
 Only container elements classified as import can be
filled when the workflow is started.
‡   
 
 Import container elements are filled from the workflow
container and export container elements are transferred
back.
‡ ! 
!
 Import container elements are filled from task container
and export container elements are transferred back.
‡  &  
& 
 All event containers are export container elements only.
‡   
 
 The import container elements are filled from the
workflow container (or task container). The
_RULE_RESULT elements is the only export parameter
and this is optional.
àinding
‡ D  !  


!


‡  
 
!
0 !




 4
        
-- 
!

0 ! 


  ! --

!

0 ! 


 
›ontainers
C
ti
r 
Bi
i
and àindings

R    
R  
 
 r  r  r  r  r


ri ri


t m

"
l

4 

. 
.
 t
 

#
l

m$ mm

. 
. ri
ti

 t 
t
m"

m
ü §   #777
WORKITEM
Work Item
‡ O(    
 

  


‡ 
  !
&
!!
 



!


  T
 

!   !&


T

!
 
    !


 &
!

‡ D !
 
   

 !
!
 ? 
O

   !   ! ! !

 
Work item Types
‡  Work item that represents a Work Queue
‡  Work item for àackground step
‡  Work item that represents a container linkage
‡ D Deadline work item; Notification upon Missed
Deadline
‡ ' Workitem that waits for an Event (Wait step)
‡ 4 Workflow (Also subworkflow)
‡ N Notification Item (Obsolete)
‡  Work item that Represents a Remote Work item
(Proxy WI)
‡ " Work item that Represents a Remote Work item
(http)
‡  Dialog work item; Represents a Single-step Task
‡ =Work item that Represents a àlock
Work item Status
‡ TN : Waiting (Also: Work items in Resubmission)
‡ "'DY
‡ ':'T'D: Reserved
‡ T"T'D: In Process
‡ '""O"
‡ OMMT'D: Executed (Only If Expl. End ›onfirmation Is
Expected)
‡ OM:'T'D
‡ N'::'D: Logically Deleted
‡ +'6'D: In Preparation
‡ '=U +T: Exception caught
‡ '=+ND:": Exception àeing andled
Deadline Monitoring
ë li
 fr &rfl t

Deadlines for Workflow Steps


X ë li
  i
ii l ti rfr


 
t
X il  li

% Ö % &'  ( 
) t trt m  " 4   
# m$ mm m m" m4
) t 
m m m m# m $ m
 " 4    #
*tt trt
 "$ "m
*tt 

X il  li
 r   l  li


ü §   $777
Deadlines for Workflow Steps
‡ "1  ! 
 Earliest possible point in time for the commencement of processing

 The requested start is not a monitored deadline in the strict sense. It


is when a work item first appears in an agent's inbox.

‡ "1  ! !
 Requested end deadline for processing a step

‡ :  
 Latest start deadline for processing a step

‡ :  !
 Deadline by which the processing of a step must be completed.

N/
!!
 
!
  !(D+'=

( T( "D+'=
àusiness Objects
›reation of Object type
‡ NO(
‡  - 0

O(
‡ !& -/ 


 
   ,! 
  
 !&  .

(

 !

 
 
 
Sub--type
Sub
‡ T -@
 -@D& -@
D


 T -@
 O(
!
‡  
!( (
  0 !
‡   
‡ ' 
1   (    
! 

  !  
‡ &

Object Type Definition
‡ T 
 !/SWO1
‡ 
!
  / T "    

  3T 
 D /M!3
 

A  !
Object Type Definition (contd..)
‡ 64
!

 D
 


 , .!
 &!

 O 
!   !

 
!
!&  &
!
1 
! 


  
(
 

  ! &


›ontd«
›reation of Key fields
‡ 

     6
!  !
 BC  

‡   


!
! 
  D >

‡ '   /56

‡ T

! 
!
!  
 
&   /5:'N
Object Type Definition (contd«)
‡ 
 
  O( A database attribute is
defined with reference to a
   
 column (not a key column)
‡ D 4
! of the related application
‡ 5
  table.
‡ O( A virtual attribute is
 M 
:
/ calculated with AàAP
code.
‡  
-

   !  
  !


A  !
›reation of Attribute
Object Type Definition  !

‡ M!
 D
 #  !
    #   
 4 
 M! 
 
 T 
 !
 "
 O
A  !
Types of methods


&0   
   ! 
&
        !

‡    ! /
l '0   !!

 
l '0
 
!
‡     ! /
l M!0 
 
      !  1  
!
l '0   
2!
l '0
  

    
Parameter calls from methods
‡ 
‡ '0
‡ " , 
0.
‡ '0
 /
 T
 

 
  
Object Type Definition  !
‡ '& 
  
!    

 O(

‡ '&    ! ! 


 ( 
 

O(

‡ T

  
&  !
O(
Release Status
‡ M!! /
Not accessible at runtime.
‡  !/
Only in test or internal use, possibly unstable.
‡ " !/
Released for use by the customer.
‡ O /
The functionality has been replaced. The old
functionality is still supported for two releases.
Macros used during SAP
Object Programming

‡   !E  %m@O"  !E(@


‡  
D
 /
FONTN'"E 
@
‡  



2
 /
F"'T'FONTN'"
E 
@

A  !
Macros used during SAP
Object Programming  !

‡ 

4
!& /
F'TF':'M'NTE 
@
E @E& @
‡ "!
4
!& /
F 'TF':'M'NTE 
@
E @E& @
‡ 

M 
:

!& /
F'TFT:'E 
@
E @E& @
‡ "!
M 
:

!5 /
F 'TFT:'E 
@
E @E& @
DELEGATION
Delegation
ë l ti

 r  fi
iti
BÖB
B % m$$m
$$$m $$$
 B%m$$m. B%m$$m. ' it
t
r ' it ëil ë il

B % m$$m

' it
ë il
 $$m  $$  $$"
I
rit
 +B%m$$m. +B%m$$m. +B%m$$m.
' it ëil l +B % m$$m

' it
ë il
 l

B % m$$m
B % m$$m

' it
ë il
$$$m $$$  $$4
ë l ti
B%m$$m. B%m$$m. B%m$$m.
' it ëil l +B % m$$m

' it
ë il
 l
ü §    %7 7 7
Delegation
‡    (    
!  
 D 
  
& 
 !   

  !
!

‡ D 
    0

   !  !
 ( 

   

‡    
 (0
 
  &  
 
!

‡ 
 &
!
0

       !!
( 
 0

EVENT
Events
‡ '&  
 ( 
!
  
 ( 
  
  

‡ U !T


‡ N 

  !  ! 
BT

'&  C
!
‡ '

 
  

!
Y   
! 
‡ '&    !
!
  T
&




&  !!
O( 
Event ›reators & Receivers
Event ›reation and Triggering
‡ D
O(

 O(

!
‡ T
'& /
 

&
  
 0
 !         
   
 '0

&
 
 ! 
‡ 'F"'T'F'5'NT
Event Triggering: Status ›hange
Event Triggering: Message control
‡     !! ,& . 
 

 !


‡  !

 

‡   1  

‡ 
  1  !
!  
& 

‡ D
 !

 !  !!& 

‡ 
  ! 
Event Triggering: ›hange
Documents
Event Triggering: AàAP ›ode
‡ 4
&  


& 
‡  (


(
‡ 
'F'5'NTF"'T'
‡ 4M !

‡ T
& 
0




àusiness Workplace
Worklist as Interface for End
&rlit  I
trf  fr '
%r

User li ti


&rfl

C
 
r
tr C
 it t
tr  
t r

r
il
ë lr

l rr
tti Cr it rr
tti r ti

 r

rr
  j t r it liit C
 r ti

iit l

'  t i 

tr i
t B i
 &rl 
ü §   &777

‡ T
 

  

 &
  T  

&!    !

 


 O  ,G
.
  0 ! !!    
!
‡ T
 

 ,
&

  !.

!
 T
 
 
 

 

!--!
àusiness Workplace in SAP R/3
àusiness Workplace in R/3

Automatic
grouping
Worklist

Work item text

Tips/Tricks
Special
Overview work items Work item
tree preview
Your logo and text

Task description Related


objects
ü  m '''
‡ T
    
 /
 O&&

 

 
&

àusiness Workflow
m 

 




 

 
Demo: Notification of
Absence
àusiness Workflow
m 

 




 

 
MONITORING & ANALYSIS
Monitoring & Analysis
‡ "

 M


  

 ! 

‡ D
  
T
Reporting
‡ "
  
‡  
D 

‡  
M
!D!

‡  T 
‡ "
   &

Reporting on Workflow Progress
‡ T 
 !/m
 T
  
 
  


 

!
 T

  !



Reporting on Workflow Progress
‡  O(
 T 
 !/*
‡ T
  
  
!
 
(
 
‡ '0/
   O!
Reporting on Workflow Progress
‡  O(
 T 
 !m)
‡ T
  
  !
  
(
  
 (
‡ '0/ !  O!
Work Items by Processing Duration
‡ T 
 !/ FDU"
 T

& 

  ! 


! 
  

! 

!  
 T

  ! 2

Work Items with Monitored Deadlines
‡ T 
 !/ FD'D
 T
!
 
 

!!


 

 
 4
!!!
     


 
 T

  ! 2

Work Items per Task
‡ T 
 !/ F4"'H
 T
   
 !



!
!
 T

  ! 2

Reporting on Agent àehavior
‡ T 
 !/<
 

   
1
  
 


 T

   
!&
 


!
 T

  
  !1    

     
 T

  ! 2!
Workflow Diagnostic Tool
‡ T 
 !/UD
 
!
  

  2!


 
 4

 &
/
‡ 5
 
2

  
2

‡ /T !   
 T! 0  
‡ /


  

       

 !  
‡ T ' &
  
  

     

   
 T

 
 !
   ,  
  
 ( ! !
 ( .
Workflow Diagnosis

 m/T  
!


 
 2!


  /
T

 




 $/
 
!


 
Working with the Workflow Log
‡  
  
  

,4.   
 
‡ T  

 
!! 
0 
 
 

  !!&

‡   !!    !      
&&
   !
 T
&

‡   !!!&  !!


Standard View
‡ 
, ! I
‡    , !I.
‡ O( ,  !I.
Workflow ›hronicle

The tab page Workflow ›hronicle shows a


hierarchical display of all the steps in the workflow. If
workflow has a subworkflow structure, the subworkflow are
also displayed.
Workflow Agents

The Tab page Workflow Agents shows the agents involved in the
workflow.
Following options are displayed for each agent:
‡ What action was carried out in what step
‡ When this action was carried out
‡ The objects involved
Workflow Objects

The tab page Workflow Objects lists the objects related to


the workflow. This view shows what objects were created and
processed.
Technical View

‡ T
&
  
 !  ! 
    
    ! !!
Workflow Status
"!    '0 !

T
  T

 T


  !   
 

0


0 
  !  !  

 
 
 
 !
 

 
 
 

0 !
 !


  
! :
D! '

T0 
  '0 
  '0 
 




   
 
! 
 1
! 
!
 

 
Workflow Log
 

 
 
&
 
 !0 !!
    

D
  



D
 


 
 
  
List of Transaction ›ode
‡ SWO1/
 O(
!
‡ SWDD/
!
‡ SWUD/D
 

‡ SàWP/
 
‡ SWU3/ 
 
2

‡ PFT›/M

T 
‡ SWO3/ 
 O("
 
‡ SWE2/'& :
 
‡ SWI1: "

‡ SWI2_FREQ/ T 
‡ SWI2_DEAD/ 

!D!