Requisition workflow

[Vineet.Mehta@mbusi.daimlerchrysler.com]

We have exact scenario. What we do in such cases is have it approved by
WF-BATCH multiple times till it gets to the highest level.
What we also do in org structure for these scenarios, we do not populate
the org structure.
 
If you have access to my presentation from ASUG BITI Forum, Fall 2003 you
will see some information which you might be able to utilize.
 
I hope that helps.
 
 
 
 
 
fezkhan at usa.net
Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU
06/18/2004 12:02 PM
Please respond to SAP-WUG
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Requistion workflow
 
 
We have PR release Strategy with classification based on Doc Type and
dollar value. Then We have purchase Requisition workflow setup as well
which kicks off a workflow item and routes it to the appropriate user
for approval.
 
Now We have modified the release strategy to have pre-requisites for
each release code (there ar 5 codes total). The problem is that when an
approver has authorization for more than 1 release codes, s/he is
forced to release the requisition multiple times. This means that a
workflow item keeps poping up in his inbox until the he approves the
highest release code that he is authorized for (due to the
pre-requisites in the release strategy).
 
Example: If JOHN has authorization for release code T1 through T3. When
the workflow item comes to his inbox, he releases it. It releases T1.
Then a new workflow item comes to his inbox for him to release T2. After
 that another work flow item pops up in his inbox to do T3. Then it goes
 on to the next person or requisition gets unblocked.
 
My question is if there is a way to avoid having work flow item popping
up multiple times in the inbox and executing the highest release code
that this user has the authorization for?
 
My work flow experinece is limited. I would really appreciate it very
much.
 
Faiz
 
 
Faiz