Agent for workflow task TS20000159 (release step created)

[Bradshaw-Long, Kathleen]

Rita,
 
 
The problem turned out to be that one of our developers had added
release code 01 to the role container in the task ---and so the release
was "hard coded" in a way to keep returning to the initial approver.
Once we removed release code 01 from the role container, the default
role 20000026 was able to find the proper approver according to the
release strategy and org. structure settings.
Thank you for validating the use of the default role. =20
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
ritatimmons
Sent: Wednesday, January 21, 2004 5:17 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Agent for workflow task TS20000159 (release step created)
 
 
Kathleen:  I am working with this now and was using the default role
20000026.  I am no expert - but my take on this is that the workflow
selects the agents for the release in the config under the WORKFLOW
button in OMGQ (Purch req release config).  Here you assign the release
group to the release code to the org structure.  I am using overall
release strategy, so plant is blank in my config.  Here is an example:
 
Grp     Code                            Org
Y1      L1      Supervisor              C       50001226  *job
supervisor, could be position, agent,
etc.
Y1      L2      Plant Mgr               C       50001228
Y1      L3      VP                      C       50001229
Y1      L4      President               S       50001137
 
Maybe this helps?
 
Regards,
Rita
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Bradshaw-Long, Kathleen
Sent: Wednesday, January 21, 2004 2:50 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Agent for workflow task TS20000159 (release step created)
 
 
Dear Workflow users,
 
This is a follow up to a previous question of routing a purchase
requisition to a second approver.  A few of you were kind enough to
respond and give me some ideas to check the release strategies and make
sure they are workflow relevant.
 
        I have done so and everything looks fine.  However, workflow
(which we are starting manually) is still only going to the first
approver...Even when there are 02 approvals in the release strategy.
 
        When we trigger the workflow manually (entering the requisition
no. and release code 01), we are putting in the position number of the
1st approver in the org. structure as the agent for the step overall
release of purchase requisition.  It is working fine.
        Then, when we trigger the workflow manually for the second
approval step (entering the requisition no. and release code 02), we are
putting in the position number of the 2nd approver in the org. structure
as the agent ---but the requisition is still going to the initial
approver's inbox.
 
        Has anyone used the default role 20000026 (person responsible
for release of requisition)as the agent for this step?
        I guess what I'm ultimately trying to understand is how SAP
automatically determines the appropriate agent for the workflow step
from the release strategy and org. management settings when we automate
the workflow.
 
 
        Kathleen Bradshaw-Long
        BP/IS
 
> North America Operations
> 836 North Street
> Tewksbury, MA 01876
> Tel: 978-858-8909
>
        Kathleen.Bradshaw-Long at getronics.com
> <www.getronics.com>
>
>