Enhancement of existing workflow for our Purchase Requisition Release (approval - ME53n)??

[Richard Marut]

Sri,
 
I've run into to this same situation once. What I did was I added a step
with a new method prior to the release requisition that did the same lookup
as the role resolution for the release step. I passed an indicator back to
the container that specified if an automatic release should occur when an
agent was missing. If it needed to, I branched to a step that processed the
release method. Of course there was more to it than just checking if an
agent didn't exist in the org structure involving items such as cost center,
dollar amount, etc., which were all built into the lookup.
 
Richard...
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Sri
Neela
Sent: Friday, May 21, 2004 12:25 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Enhancement of existing workflow for our Purchase Requisition
Release (approval - ME53n)??
 
Hi,
Enhancement of existing workflow for our Purchase Requisition Release
(approval - ME53n)??
We have a Release Strategy configured with classification based on the
characteristics, Requisition Doc Type and Dollar value. There are 7 (R0
to R6) Release Codes for different dollar amounts and all Release Codes
are configured with Release Prerequisites. For example, R2 requires that
R0 and R1 be released before the person with R2 authorization can
release it and so on. Each step creates a workflow item and routes it to
the appropriate user based on the Org Structure.
Here is the problem we have....
When there are people in the Org structure for each level for each
Release Code, it all works fine. However, there are times when the Org
Structure does not have a person assigned to a particular position. For
example:
Person A has the authorization to be able to use Release Code R2 but
there is no one in the Org Structure for Release Codes R0 and R1. In
this case the workflow goes to Person A. So far it's good...that is what
we want. However, the problem is that Person A has to execute the
workflow item 3 time (one each for R0, R1 and R2) before the Requisition
is released (due to the Release Code prerequisites in the configuration
as described earlier). The users do not like that.
Is there a way so that the system will only require Person A to use
Release Code R2 in the above example (and not force them to have to
approve the same workflow 3 times using R0, R1 and finally R2)?
1- For this particular issue, the Requisitions are being generated from
a Network for a WBS element in PS and are identified in our system by a
Document Type (ZAPR). Transaction code CN22 allows change of Network and
if the Control key specified is for external purchasing, the system will
generate a Requisition automatically.
2- We are on 4.6C release.
3- Business Object for Requisition is BUS2009. We have copied it as
ZMBUS2009. The Workflow template we are using is WF90500007, which is
also copied and modified.
4- We have custom program (Z_GET_NEXT_RELEASE) we are using to determine
what Release Code is required for this Requisition and Using for Role
Resolution: Z_GET_SUPV_WITH_PREQ_REL_AUTH
 
Thanks in advance for your time.
 
Rgds,
Sri Neela