Defining agent for subsequent tasks

Van der Burg, Jeroen JA SITI-ITPSEE jeroen.vanderburg at shell.com
Mon Oct 14 11:18:29 EDT 2002


Marques,
 
Normally you would use the actual agent parameter of a dialogue step for =
this (_WI_Actual_Agent), but you may run into problems here when the =
workitem is forwarded or substituted (as then the manager of the person =
who processed the item has to deal with it, not the manager of the =
manager of the person who requested the trip).=20
 
It may be a better idea to define the manager here as a separate =
container element which gets refreshed in your approval loop in a =
separate workflow step running the FM for role 168, or use a number of =
virtual attributes in your delegated object to do precisely that =
(approver_1, approver_2, approver_3).=20
 
The first option allows you to have one nice loop to run your approvals, =
the second one gives more clarity in your workflow log (your approver =
container element is not overwritten with every loop pass). I'll be a =
bit careful with going up to high in the org structure, as org units do =
not always have managers (meaning you skip an extra level and quickly =
can end up at a level where the manager does not know this employee's =
name).
 
 
Regards,
 
 
Jeroen
 
-----Original Message-----
From: Marques Rodrigo (RBBR/ASE61) *
[mailto:Rodrigo.Marques at br.bosch.com]
Sent: 14 October 2002 16:51
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Defining agent for subsequent tasks
 
 
Hello Everybody,
 
We are currently working on a workflow for Trip Approval and we are =
facing
troubles when defining agents.
The approval may have many steps, depending on the total value of the =
trip.
We want it to work like this...
 
If there are several steps: The first one must be approved by the
initiator=B4s manager (no problem with that!), the second approval must =
be
done by the manager of the preceding manager...and so on...
We are using role 168 (Manager US) to define the manager. In the next =
step,
the agent (manager) found in the previous step should be passed to role =
168
again and so on...
 
The question is...
Where do we get the agent found in the previous role definition? Is =
there a
field in the workflow container that should have this value?
 
Thanks in advance for your attention
 
Kind Regards
Rodrigo Marques=20
Robert Bosch Brazil
 


More information about the SAP-WUG mailing list