PO approval Release strategy

Hello gurus ,
1.How can I view the approval workflow for my Purchase Orders created ? ( Who is the approver for a PO?)
2.How can I set approver for a PO
2. What is a release strategy for PO/PR ? and How can I view the same
Victor

Hi,
check this link i posted earlier also.
http://www.sap123.com/showthread.php?t=59
Regards,
Batchu

Similar Messages

Purchase order release strategy Workflow not working

Hi All,
I am working on PO Approval release strategy and it is not working fine . The release strategy set up is configured by my functional consultant . I just copied the standard workflow template WS20000075 and making changes to my custom workflow template . When ever po is created an event "RELEASESTEPCREATED" get triggered and the first approver receives an workitem and when he approves it goes to Second Approver and it is working fine . But when rejected then a notification email goes to initiator . Now when an initiator login into ME22N and made any changes ( even material text change ) in it then again "RELEASESTEPCREATED" event getting triggered . But I need to trigger my workflow only when there is change in PO Net value .
Kindly help me how to achieve this functionality .
Thanks and regards
Dilip

Hi Vikram,
There is already an existing entry for BUS2012 with event CHANGED against the change doc EINKBELEG .
Acutlly when login as initiator and try to change PO through ME22N here are my observations :
case 1: When Buyer click on " Cancel Reject " button and do any changes ( even text change ) then RELEASESTEPCREATED and CHANGED events are triggering . But since the event linkaged is set to RELEASESTEPCREATED workflow get restarted again.
Even the CHANGE event does'nt have 'RELEASECODE' as parameter to restart workflow .
Case 2: When Buyer doesn't click on " Cancel Rejection" buttion and do any changes then only CHANGE event get triggered
which do nothing since there is no event linkage .
Is to click on " Cancel Reject" button mandatory ? . But even though we make " Cancel Reject" as Button mandatory then RELEASESTEPCREATED Button triggering for any change but we need to trigger it for only net Value change .
Thanks and regards,.
Dilip Kumar

Purchase Order Release Strategy Approval

HI All,
I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
Level one will have 1 approver
Level two must have two approvers.
The scene is:
Level one will approve all purchase orders betwee 400 to 5000 euros. 1 approver only
Level two will approve all purchase orders above 5000 euros. 2 approvers.
The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
Pur. group G70, Release Group GC and release strategy DF.
I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
CL20N is completed for both levels and works correctly for level one approval but not for level two
Can any please help
Leslie

Hi,
May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
1. PO Order Type (ZPO_BSART),
2. Company Code (ZPO_ BUKRS),
3. Purchasing Organization (ZPO_EKORG),
4.Plant (ZPO_WERKS)
5. Purchasing Group (ZPO_ EKGRP) and
6. Total net PO Value (ZPO_GNETW)
Create one release class ZPO_CLASS & then add all above release characteristics
And then design your release strategies as required.
AND under release characteristic for PO Value (ZPO_GNETW) keep following values
A. <= 400 EUR
B. 400.01- 5000 EUR
C. >5000 EUR
As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
Regards,
Bijju K

Purchase Req Release strategy - Requestor /Approver

We want to skip the Approver to release his own purchase requisition without workflow set up.Is it possible in ECC6.0 ?. Any help will be highly appreciated
Thanks
Nick

Hi Nick
While configurating add P group as one of charactaristic.Then maintain values of all P. Group in this charactaristic
While defining Release strategy Do not tick against Approvers P group which means release strategy will be skiped for him
( Release strategy--classification here u difine value for P Group skip P group here)
Cheers!!!
Vishal...

MM:Release Strategy for Release Order again Approved Contract

Hi,
Release strategy for Release Order is required or not against approved contrat??
As fas as I know once the contract is approved, release order is not required to approve again.
This is the standard setting from SAP or We need to do some setting for this??
In my support project I have studied the release procedure and found that, same release strategy and release Group has been used for Purchase Order and Contract.
Please let me know if anyone have faced this rquirement or I have to go for Z development for this requirement.
Thanks you.

Hi Lalita,
Thank you for your quick suggestion.
yes definitely the release stratergy and release group should be set up separately but here both are same
that is the reason this is picking of the same release procedure again evenif the contract is approved.
we have following release characterstic for the release procedure.
1) Purchasing Group
2)Total Net Order Value
3)Order Type
4)Purchase Organisation
5)Material Group.
I think for the above characterstic we must a separater value for PO and Contract but Currently all are merge
in this only
But Can you tell me "Release Order should be subjected to release procedure" this is correct or not .
If yes then what is the base for this, I mean is it working on the concept that " If do relevent
release characterstic value is found then no release procedure and this is treated as autorelease in sap"
Thanks you.

How to approve or release a Custom workflow release strategy using a prog.

Hi There,
I am working with a custom transaction with release strategy using custom workflow. I am done with the module pool and workflow templates. And also I can able to start workflow using the FM SAP_WAPI_CREATE_EVENT.
My actual Issue is I have set of buttons in the module pool screen with names Approve (1 to 5) and Reject (1 to 5). When I press the "Approve 1" release strategy of the first person need to approved. Is there any Function Module or Classes for approving the workflow release strategy using buttons in screen.
Thanks in advance,
Viruman

Hi
Make use of the function module SAP_WAPI_DECISION_COMPLETE. To this function moduel pass the workitem ID and pass decision parameter value as 0001 for approve and 0002 for rejection action. You can check in this forum with this function module you will find lot of threads.
If its not a decision step then you can make use of SAP_WAPI_EXECUTE_WORKITEM or SAP_WAPI_WORKITEM_COMPLETE.
Regards
Pavan
Edited by: Pavan Bhamidipati on May 26, 2011 11:43 AM

Issue with Purchase Requisition Release Strategy (Approval)

Hi There,
I am facing an isssue with the PR Release Strategy. Please read the description below.
When a PR is created the PR Release Strategy is getting determined correctly. But the problem is that for example, if the Strategy has found a two level approval, the system is allowing level 1 user to approve both the levels, which should not be the case. User 1 should be allowed to approve only Level 1.
Though the system is currently allowing the same user to approve both the levels. If User 1 approves only Level 1 and saves the PR then the PR approval notification goes to User 2. So there is nothing wrong with the workflow or notification.
It is just that system is allowing the User to approve both the levels.
Any help is appreciated and rewarded.
Thanks,
Chan

Hi,
I believed releases strategy correctly designed with release prerequisites.
Now need to check following in basis side by having a purchase order release matrix.
Lets say you have following release codes
C1 & C2
AND
Having following users
U1 & U2
Now give authorization to user U1 to release with release code C1 and user U2 to release with release code C2 ONLY.
Regards,
Biju K

Release strategy not trigerred if PR changed after Approval

Dear Gurus,
I have a requirement kindly help.   We have a PR generated from PS module, This PR is released by the approver. After the Approval, PS user change the PR qty and value has been increased. Now my client wants that this PR should be again sent for approval and release strategy should be trigerred. After the approval my release indicator is 2 RFQ/Purchase Order. I have set the Changeability indicator to 4 and define the tolerance to 0.1 %.
But PR release not trigerred even after this. Kidnly help.
Thanks.
Johi

Hi Johi,
Check note 493900 point 3:
3. Question :
Why is the release strategy not reset?
Answer :
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
I hope this helps.
Regards,
Ashwini.

Re: Cancelling of approval in standard SAP release strategy.

Hello All,
At present the release strategy used by our client has the standard SAP strategy. The release strategy works fine for the approval part. The issue lies with withdrawal of approval.
At present when a lower level approver withdraws his approval, higher level approvals are withdrawn automatically. Our client requires that when a higher level approver has approved the doc, the lower level approver ( who has already approved the doc) should not be able to withdraw it.
i have looked around on SAP but i don't believe that standard SAP allows for a strategy for withdrawal of release. I believe this is a common requirement for many businesses. Could you please show me how to go about this. Should it be done through customizing. We do have a workflow in place.
If your business had the same requirement, how did you configure.
Thanks for reading this.
Regards,
Soumyadeep Paul

Hi,
I think you have configured you release matrix in such way that even higher level approver is dependent on the approval of the lower level approver.
In release prerequisite, don't set lower level approver's approval as a prerequisite for approval of higher level approver and then check. But this should be first discussed with the Business users and then only can be implemented.

Release Strategy ME53N - Approver rejection

Dear all,
I would like to generate a change history report based on approvers choice on Release Strategy in ME53N. The thing is I can't find any table where rejections are stored when a approver doen't release a PR.
I know that in CDPOS I can find wich ones were released, but what about when it is rejected?
I would appreciate any help.
Thanks in advance,
Alm.

Thanks again, Eddy.
Not yet what I'm looking for, here is an example:
Consider a PR XXXX with the Release Strategy flow - CG-F3-FM.
In ME53N we can see:
CG - Green Check Icon (approver released)
F3 - Green Check Icon (approver released)
FM - Yellow Icon (Waiting Approval) However I know this approver has rejected the PR in the past, but the System only shows that this approval is pending - the system does not inform the existing rejection.
Where to find that behind this yellow icon there is already one rejection?
Thanks in advance.

Regarding Release strategy - Approver on vacation

Hi ..
This is regarding Release Strategy ..
We don't have work flow configured now. can you please suggest for below
1. If a Person responsible for a role [release code] is on vacation, how we pass this authorization to alternative person
2. i believe without work flow there will be no way that we can notify approver
Thanks

You can assign the Role/Profile containing the authorisation on a time limited basis to the person who covers for the person on holiday.
It's not particularly efficient to have to continue doing this though so I'd suggest doing it on a permanent basis.
Regards,
Nick

PO Workflow for release strategy approval process (BUS2012)

Hi Experts,
I have configured a workflow that should get triggered by the event "RELEASESTEPCREATED" in the Business Object BUS2012.
The workflow is triggering perfectly and is working exactly as per the requirement, but the problem I am facing is the event "RELEASESTEPCREATED" is getting triggered twice.
I went to SWEL and saw that the above event is getting triggered twice by the system. I am not calling the event in any user exit. I have de-activated the event linkage in the standard workflow. Only my custom workflow link is active.
Due to this all my workitems, mails are getting duplicated as the workflow is being called twice.
I just need to know, why the event is getting triggered twice in the system.
If you need more details in the issue, I will provide that.
Your help is highly appreciated. Points will be awarded to the helpful answers.
Thanks
Anirban

Hello,
First off a small comment on terminology because a lot of people say this:
Events are not triggered, they are raised or published by the application (regardless of workflow). An event is the trigger for a workflow.
Now we have that cleared up, have a look at the workflows that are triggered by your events and check the container to determine the release codes for each workflow. It seems to me like you are probably processing two different release codes at the same time. This could be perfectly normal (e.g. you may want to perform two approvals at the same time) and is controlled by the MM config for the release strategy. If this is not what you want then this should be adjusted by your friendly MM people.
Cheers,
Mike

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Hello everyone,
I've run into an interesting problem:
We have defined several PO release strategies. Most of these work in the traditional manner, requiring manual approval by a given user. One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
What would cause this discrepancy? The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
Thank you ahead of time for your help.
-Jarrod

Configuration issue/user error.

Issue: Purchase order release strategy with storage loaction.

Hi Friends,
I have created release strategy for purchase order considering following characteristics.
1. Plant
2. Purchase organization
3. Purchase group
4. Document type
Hence the release strategy is working fine.
Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
Can any one tell me how to maintain this LGORT filed in structure CEKKO.
Thanks in advance
Shashidhar

HI Shashi ,
Thanks for your quick response,
I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
Also we written the code :move: i_cekko = e_cekko, in user User-Exit M06E0004 function exit
FUNCTION EXIT_SAPLEBND_002.
However, the release strategy is not triggering when PO is saved,
also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
in it.
Kindly reply.
Thanks ,
Shashidhar

PO approval Release strategy

Similar Messages

Maybe you are looking for