Revoke Release Strategy (Reverse Steps)

Hello Experts
Please help with following revoking issue:
In Release Strategy, every release code is authorized for its own release, however revoking of release can be done by any release code available in hierarchy on above level.
Example:
Release Group: PR
Release Code: S1 (Initiator), S2 (Head1), S3 (Head2)
Release Strategy: 01
When Release Strategy 01 triggers S1, S2 & S3 release codes comes for approval in the correct order which has been configured that S1 will initially release a document, S2 will be able to release the document when it has been already released by S1, S3 will release when the document has been released by S1 & S2 respectively.
Following is the problem:
Document released by release code S3 higher authority can be REVOKED by release code S1 or S2. We want is there a way we can restrict that S2 can only revoke release when S3 has revoked the release similarly S1 can revoke the release when it has been already revoked by S3 & S2 respectively.
Regards-Amit Bali

Hi Amet,
The concept of the Release procedure is the Approving the external document electronicaly....(insted of manual)
as per your case...
you have set up 3 stages for approval...S1,S2 & S3...
If every thing in the document is fine, it will follow the sequece of approval as per your configuration S1 ---> S2 ---> S3...
If any one feels it is not meeting the requirement they can reject... so that it will go to PO creater for correcting the things in the PO....
and again it will follow the flow of approval .... S1 ---> S2 ---> S3...
Hope this is clear to you..
Thanks & regards
Anand

Similar Messages

Release strategy reversal for the purchase requisition.

Hi all,
I have a scenario were we have three release levels to release the PR through ME54N tcode.
After all the levels are released,If at the first level the PR release is cancelled all other levels are automatically cancelled.
Now my concern is until the 3rd release cancellation is done, 2nd and 1st level should not be allowed to cancel the release of PR. and until 3rd & 2nd release cancelltion is done, 1st level should not be allowed to cancell the release of PR.
Please Let me know if any BADI or any enhancement is available to acheive this back release strategy for PR.
Regards,
Kumar
Edited by: kumar g on Jul 16, 2009 6:21 AM

-

Increasing release strategy levels/steps

Dear gurus,
We recently added a release code (FC) on our release strategies for our purchase requisitions. The condition is that all Pru2019s have to be released and/or checked by the Financial Controller prior to being released by the process leaders.
Challenge
It has since been discovered that the last release code on each strategy can no longer release once the approval has been affected by the first release codes in a given strategy. How and where can this be sorted?
regards,
Chansa.
Edited by: DAVIES BWALYA CHANSA on Mar 16, 2011 9:58 AM

i assume you have now 2 heirarchy levels to approve the PR
to ensure that release is effected only after l1 and l2 are approved and also that L1 approval happen before L2 you may have to ( 1) check mark the box in release pre requisites , ( 2) in release status make the status released only for the level where both L1 and L2 are checkmarked. other lines to have blocked status. both are avialable under release strategies in OLME

Purchase Order Release strategy revoke when Delivery Comp indicator Ticked

Dear Experts,
There is PO for 100.Release strategy is activated for PO.PO is released.
Inbound Delivery for 100 was done .after which for 70 Goods reciept was done.
Then User wanted to Short close as no more quantiy is going to come.
So user went to ME22n and Done Delivey completed indicator was ticked which can be done Without Re-Release.
But When i am seeing the Log of PO (Both Header and Item Changes) The Release strategy is again Getting Revoked,
And going to Release again.
What should i do for not revoking Release strategy.And Also Price is getting Changed.
with regards,
GMP

hi,
Release strategy is revoked via release indicator settings done via settings up the release strategy...
If you don't want any revoke even if any field is changed then used the changebility as '1'...
Also as per std sap settings, once you make changes to com. indicator in PO, system will revoke the release again...
so, decide and make settings as you need...
Regards
Priyanka.P

Workflow - Purchase order Release strategy

Hi All,
Good Morning
I had created workflow for Purchase order release strategy with steps(To Determine Agents, Release of Purchase order, Release of PO effected) and in Me21N I created PO and PO came to my SAP inbox(SBWP) and I released that PO and saved it.
but My problem is after releasing PO when I checked my Inbox again still that PO is sitting there, it is supposed to disappear from there
Can anyone please assist me to resolve this issue .
Thanks in advance.

Hi,
In standard SAP workflow, SAP is sending a mail item (notification) to SAP mail inbox. There is no action is required from there. So mail will remain their as mark as read. If you want to remove it than one needs to delete it from respective mail box.
Best Regards,
Bhagat

PR/PO release strategy should be revoked

Hi Experts,
How to revoke the release of a PR /PO if value is decreased. In standard only value increase will revoke the release strategy. I am having overall release of a PR.
Regards

This cannot be achieved through standard release strategy configuration.
Basically the requirement is any change on PO price should result in blocking of the PO. You can create a custom field in the PO header that will function as a Price Change Indicator. Add this indicator to the release class and trigger the release strategy when the Price Change indicator is set to "Yes". Populating this custom field with value "Yes / No" should be carried out using a user-exit by invoking it in the PO change transaction.

Additional PR release step in current release strategy

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the first release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise how to implement the additional release step. Thanks.

Hi Arghadip,
Thanks for your reply. My intention to create different doc type is for separate set of release strategy.
In current release strategy, for example, if doc type = NB, creation indicator = manual and the total value of PR is $1K, then the PR requires release code A1 for approval and the approval is align with the company finance policy. The manager (with release authority A1) of the PR creator then selected by the user exit and assigned with workflow task.
For the request for additional release step, if doc type = ZS, creation indicator = manual and the total value of PR is $1K, then the PR requires release codes AA and A1 (new release strategy). The user exit will assign a dedicated position/user (not necessary the manager of the PR creator) for release code AA, and then assign the manager of the PR creator for release code A1. Therefore, even the total value of PR is also $1K, but since the PR item contains material group 80501, then the PR require an additional approval on top of the $1K financial approval.
Your comment is welcome. Thanks again.

Customizing steps of workflow for Release strategy

Hi Experts,
Iam looking for step by step customizing details of workflow for Release Strategy for Purchase Requisition.
I need necessary classification and Customizing settings for a release procedure in the purchase requisition to the workflow.
I am looking for the steps, in which the purchase requisition can be edited straight from the workflow inbox.
Regards
Nani

Hi Nani,
First you have to confirm what kind of release it is in Purchase req you have Item level release and over all release.
Item level release - WS00000038
Over all Release - WS20000077
Now please confirm with your MM consultant that he has done the release Strategy and tesed it Ok.
Escecially things like assigning plant, Assigning Agents,Release codes and so on when everything is done by him in SPRO.
Now your work starts If it is just release use the standard workflow.
If they need additional notification mails and things like that copy the standard workflow and do the customization in the copied version and deactivate the standard workflow.
You can also do dead line monitering (Factory Calander) and many more things.
also please go through these 2 links you will get better idea.
http://www.****************/Tutorials/Workflow/POReleaseStrategy/Details.htm
http://www.****************/Tutorials/Workflow/PRRelease/PRRelease1.htm
If you have any othere queries please feel to ask.
Regards,
Dheepak
Edited by: dheepak on Dec 1, 2008 7:48 PM

Po Release Strategy Change

Hi Gurus
I am changing the release strategy for po.
Same characterstics and value also same.
only change is release codes. so that, what i can do. if i add new release codes in same old strategies ?
Otherwise i can create new release strategies ?
if i create new what i have to take steps ?
if i use same old release strategy and in that i can chage release codes what about previous documents ?
client side cl24n here we can block old stratiges what about the documents created on old ?
If any body answer right rewarded full.
Thanks in advance
Regards
Laxman

Hi
we have also did some changes to relase codes after once in use & we had encountered some problems in the PO.
For E.g. If you have the previous repease codes as L1 & L2 , & if you are removeing the L2 form the release codes then All the PO's whcih are approved by L1 & awaiting tobe approed by L2 will be in hanging status. You need to go into each PO 7 click on revoke acceptance & Click on check then The new relase codes will appear.
If you can clearly explain what you are planning to do on the relase codes , then we can advise you in the right manner.
Thanks & Regards
Kishore

Error relate to PO Release Strategy

Hi expert,
I have a problem relate to PO release strategy. I try some of suggestions but nothing work. I hope you guy can help me to fix it.
I have finished configuring PO Release Strategy and Release Group is ZT with 2 release code (01, 02).
After that i created some of other release groups and delete the first release group ZT (include release strategy). But whenever when i go to ME29N, ZT always appear in release group with it's release strategy even i already deleted it.
Thanks for your help

Hi,
What procedure did you follow while deleting the release group ? The process for release group deletion should be as mentioned below.
1. First delete the classification data for the release strategies you want to delete
2. Delete release strategies ( from detail view in SPRO )
3. Then delete release codes ( including description in different languages - translation )
5. Lastly delete release groups ( including description in different languages - translation )
If you dont follow the above process inconsistency might be there.
After deletion if you want to create new release groups follow the steps in reverse reverse order.
1. Create Release group ( including description in different languages - translation ) Check table - T16FG
2. Create Release Codes ( including description in different languages - translation ) - Check table - T16FC/T16FD
3. Create Release Strategies ( ( including description in different languages - translation ) - Check table - T16FS/T16FT
- Assign codes to Release Strategies
4. Maintain classification values - Tocode CL20N
Please let me know ifyou need any further help.
Regards
Sayan
Edited by: Sayan Pal on Dec 8, 2011 3:28 AM

PO Release strategy

Hi,
I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
Any suggestions are highly appreciated to fix this issue.
Regards
Sudhakar

Hello,
After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
regards
anand

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

Error while creating new release groups in PO release strategy

Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
Illan

Dear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
**Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
*Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

PO release strategy problem

Hello Friends
Who can help me?
I created one PO, then check in ME23, and found release strategy for this PO is 'VS', but when I check PO release strategy in customizing, it's not defined for PO release strategy. So, how strategy 'VS' is assigned to PO during order creation?
This order can't be released in ME28

Check below link ;
release strategy
Create a purchase order strategy with four release steps.
http://www.sap123.com/showthread.php?t=59%20-Release%20strategy
Release procedure

Revoke Release Strategy (Reverse Steps)

Similar Messages

Maybe you are looking for