About workflow problem in 4.6C for PR

Question

Hello Expert:
i met a quesiton about the workflow for PR in 4.6C.
the detail is as following.
The requestor created a PR for waiting for approve, there are 3 approvor to handle the PR.
maybe the second approvor modified the quantity or amount of the PR before release, but system seems can't trigger the new workflow to go back to first approver in 4.6C. So once the second approvor released the modified PR, then the PR will go to next approver.  Now my requirement is to hope the workflow can get back to start point for waiting for approval. or could i close the PR completely.
even i am cancelled the PR, the purchasing group can generate new PO with the cancelled PR as well.
Did you face the same problem in 4.6C workflow?
hope to get your help
Thanks in advance
Kevin

Answer 1

Hello Kevin,
you can find this setting in the customizing tree:
I assume that you're using purchase requisition item based released based on classification
MM>Purch.>Req>Rel.Proc.>with class. -->Set up procedure with classification
Push "Release indicator"
Select the release indicator that blocks your PO (e.g. X blocked)
Using the SAP Standard only you have the following two choices that makes the most sense:
- Changebility = 1  i.e. cannot be changed
- Changebility = 4 and Value change = 0,00   i.e. changeable and new release on value change
The first option locks the requisition for any changes at all, forcing your purchasing group to re-create the PR once it should be changed.
The second option allows any change, but when the value is touched in any way (+/- 0%) all previously given release codes will be reset making the release all-over again.
I tip that the second option is the one you're looking for.
If both option are not workable for your requirement, you have to create an additional event (as one of the previous contributors Aditya already mentioned), which could be restricted to the fields that you want your requisition to reset with.
Then you have to throw in an event coupling where you use as a receiver event function module a custom-made function module that runs through the release codes of the requisition to reset all releases. This is done using the function module BAPI_REQUISITION_RESET_RELEASE. If you're choosing this way, I propose that you go a bit forward and open a new thread. But I remember that I was proposing this solution a couple of months ago. So maybe searching the forum could be a good idea then.
With the very best wishes,
   Florin
Edited by: Florin Wach on Mar 4, 2009 6:03 PM:   The proposed paths also apply to all versions >= 4.6B