PR release Strategy Restrictions

HI Experts,
PR is created & There are 5 levels of approvers. My requirement are as follows
1.If one level approver is released & he should unrelease the same level
2. Creater should not be allowed to change the PR if realese process is going on i.e. some levels alredy approved
3.If three levels are released 2nd level approver should not taken back the release
Regards,
PR

Hi,
For example:
User1u2026u20261st level approver( Release code: C1)
User2u2026u20262nd level approver( Release code: C2)
User3u2026u20263rd level approver( Release code: C3)
User4u2026u20264th level approver( Release code: C4)
User5u2026u20265th level approver( Release code: C5)
Now User 6 create PO(ME21N) and then PO go for approval process before sending to vendor.
Select Changeability indicator as 2 (Cannot be changed) in the release Indicator, so that changes are not allowed.
Regards,
Biju K

Similar Messages

In release strategy unrelease should happen from higher level

Dear Users,
In our release strategy we want to make changes like whenever user want to unrelease it should happen from higher hierarchy to bottom level as vice versa of release process. If there is any solution for this process please provide your suggestions.
Thanks,
Manoj

Hi,
For restriction from higher hierarchy to bottom level, refer similar blog
Release Strategy: Restrict lower users to revoke PO after the complete release by superior
Regards,
Biju K

Release Strategy in Purchase Order

Hi,
Can any explain the usage of Release Strategy in Purchase Order.
ganesh

Hi Ganesh,
Release strategy works the same way in purchasing documents (i.e. PR and PO). It is a form of control that company use to control the purchases made.
In your scenario, a PO release strategy is used to control the PO release status for Good Receipt process. Once the PR is released by the relevant releaser, you will see that the PR is now unblocked for issuance of PO.
Once the PO is issued with reference to the PR, it is now blocked again by a release strategy for user to perform Goods Issue. The releaser will evaluate the PO issued and determine if it is necessary to be released for GR / Service Acceptance process. At this stage, the releaser can still reject the PO although issued, and hence GR / Service Acceptance is not able to be performed. Different value will trigger different set of release strategy with different level of approvals, depending on how the PO release strategy is configured by the MM functional consultant. Usually, the PO release strategy has a flatter approving level as compared to PR release strategy, reason being that once the PR has been fully released by all releaser and the PO issued, usually the purchase is deemed necessary and PO releaser would usually consider to release the PO for GR or Service Acceptance process, unless there is discrepancy or sudden change in decision of Management.
Hence, all in all, the PO release strategy act as another form of control to the company to restrict the release of PO for GR or Service Acceptance.
Hope this will give u a better understanding on the function of a PO release strategy.
Rgds.

Release Strategy in purchase order document type

Hi Gurus..
I'm tring to tweak the single RS in the system.
I've set the charcteristic using table CEKKO field BSART, restriction 032, I've set two document types as the Characteristic Value (ZLOG - ZADM). Then I´ve set the class with this characteristic, Created Release Groups & linked to class , Created Release Codes, Release Indicator, and Set up strategies
.. but It doesn´t pick any release strategy.
The funny thing is if I delete the document types values entered in CL20N it works for all doc typs, but if I set the docs types that it should take to pick the RS it doesn't work at all...
Please advice..

I´m not such a abapper but I guess there is not values taken to ekko, does it ring a bell?
                                        BUKRS
                                        BSTYP
                                        BSART
                                        BSAKZ
                                        LIFNR
                                        SPRAS
                                        EKORG
                                        EKGRP
                                        WAERS
                                        BEDAT                                             00000000
                                        LLIEF
                                        KUNNR
                                        RESWK
                                        LBLIF
                                        INCO1
                                        KTWRT                                             0.00
                                        LIFRE
                                        WERKS
                                        MATKL
                                        LTSNR
                                        USRC1
                                        USRC2
                                        USRN1                                             0000000000
                                        USRN2                                             0000000000
                                        GNETW                                             0.00
                                        SUBMI
                                        MEMORY
                                        KONNR
                                        REVNO
                                        PDUMMY
                                        KDATB                                             00000000
                                        KDATE                                             00000000
                                        EBELN

New release strategy / Old PReqs

Hi,
New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
Many thanks in advance for your clues.
Regards,
Grzegorz

Hi,
Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

Release strategy-- very very urgent

hi,
i have created the release strategy & its working properly in devolopment client. The entire thing is transported to quality client. But the characteristics values are not coming in the classification tab of release strategy. I have saved even the view in transport request but still the values are not coming. Can anyone suggest something. Its very urgent
thanks

Hi,
The transport of release procedure customizing data can only be done in
a restricted manner. Please take a look at attached Note 86900 and
follow the procedure described in this note, in order to correctly
transport your release strategies.
The classification data must be sent over using ALE. It does not
get transported directly. Notes 45951, 86900 and note 365604 should
help. Please follow the instructions in note 45951.
You can obtain information about how to set-up ALE in the Online
Documentation CD (R/3 Library -> CA - Cross Aplication Components ->
Business Framework Architecture -> ALE Integration Technology ->
ALE Quick start).
However, if you can't set-up ALE, you can re-create the classification
data agin in your target system.
For that you have to:
1. assign new values to the characteristic master data (trx. CT02)
2. assign the new data to the classification system (trx. CL30)
3. verify the consistency with trx. CL24. Please see note #186809.
For more information, please see note #365604.
There is another possibility that you could take into consideration for
the classification is to import them via batch input:
RCCTBI01 for creating characteristics
RCCLBi01 for creating classes
RCCLBI03 for classification
Regards,
Sunitha.

Preq release strategy

My Preq release indicator has it's changeability indicator set to 4. So if the value increases (qty or price) after release this works fine and PR is resent for approval
However if I change the material after it's been released (ME52N) but the value does not change the release strategy's not triggerred again. Is there no means of making the release strategy field dependant, or should I set the material field to display only in the field selection after release. My concern is a Preq could be created for say u20AC100, the PO changed and material A replaced by material B for the same value (or less) and the release strategy not triggered.
Thanks in advance.

I think the only way is to set the field selection of the release ID to display fields.
This will restrict the users from changing the field value once the Release ID say "4" is set.

EXIT_SAPLEBND_002 -- user exit for release strategy

Hi,
This is regarding help on user exit for release strategy, ref: note no. 365604, however after going through all the config part given in the given note we activate the fm in cmod.... but after activating the release tab goes off from me29n.
That is after you activate in cmod and then if u create po and go to me29n the relese tab is not there.
if u deactivate and create po and then relese the release tab in me29 would appear.
All we are trying is that the po in me29n should be open to release again if we change the delivery date. However what coding and how is still a second step , first is as soon as the exit is active the tab goes off.
New to user exit . plz help.

Hi Again,
I guess I have solved the issue temporarily, however Am not sure if this is the best which cld be doen to the issue.
I didnt make any new characteristics in ct04, for the delivery dats since i didn't want to restrict the delivery date. All I did i yje coding below in the exit :
DATA wa_eket TYPE LINE OF mmpur_beket.
DATA wa_eket1 TYPE LINE OF mmpur_beket.
data: c type i.
   data: p type i.
break1.
break2.
e_cekko   = i_cekko.
loop at it_beket into wa_eket . " for comparing previous and the current del date
e_cekko-usrc1 = wa_eket-eindt.
SELECT SINGLE * FROM eket INTO wa_eket1 WHERE ebeln = wa_eket-ebeln
AND ebelp = wa_eket-ebelp.
if wa_eket1-eindt <> wa_eket-eindt.
import c from memory id 'CID'.
c = c + 1.
clear p.
p = c mod 2.
if p is not initial.             " adding 0.01 to the characteristic value for p.o amt.
e_cekko-GNETW = e_cekko-GNETW + '0.01'.
else.
e_cekko-GNETW = e_cekko-GNETW - '0.01'.
export c to memory id 'CID'.
endif.
endif.
endloop.
The logic I tried using is since the relese gets reset incase of p.o amnt and hence indirectly po amnt so i changed the value of p.o value by 0.01 incase of change in delivery date. cekok-gnetw doesnt reflect anywhere in the p.o as amnt, I guess its for defing range for relese stragey's amont in ct04 characteristics.
However anything better incase u know plz let me know, or do u think this can cause any problems later....new to exits.
Rgds,
Anu.

Purchase Requisition release strategy problem

Hi,
We have maintain the Item wise PR Release Strategy in three levels (1-Site In-charge, 2-Project Manager, & 3- Director). PR release is in sequence from 1 to 3 but in any case changes required after full release in PR we need to restrict the user for sequence unrelease from upper to lower one then change. Now lower one unrelease the fully release PR and change it. So please suggest me for sequence unrelease from upper to lower one then after changes being possible.
Thanks.

I believe you should have addressed this question to some of ERP forums as the current one is for ME application.

Shoul order type be part of release strategy or WF logic?

Hi,
In our release strategy for purchase order we have set up anything that is > £500 needs approving. This kicks of the standard PO wf, but the workflow should also only start if the order type = NB or 8000.
Can anyone tell me if the order type should be part of the release strategy or the workflow logic?
Thanks
Forhad

Hi,
See its purely based on the requirement, if you maintain at the release strategy level then the release strategy itself will not be available for those kind of PO's.
so its better to restrict this at Wf level thru start conditions.

Release strategy in credit management

Dear All,
My client, wants to configure credit management in such way as
For some say Rs 20000/- debit, some X shd release the blocked delivery document
and for say rs Rs 50000/- debit, some X and Y shd release the blocked delivery document
I hope I am able to put my query in right perspective.
Kindly advice
Shailesh

Shailesh,
This one is very much possible.
You have to take help from your basis person for releasing these docs through vkm3, vkm4, vkm5.
With the help of BASIS you can restrict release strategy as per herarcy...
You will have to use some logic in Authorisation profile/Role with the help of BASIS..
AWARD PONIS IF U FINDS THIS AS USEFUL....
Regds
MM

PR release strategy with classification

As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.

Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

Removal of plant from P/R release strategy of another plant

Dear Friends,
In our office there are two plants P068 & P281 both belongs to two separate co codes. In its P/r release strategy in characteristics plants are mentioned so for each plant their should be separate p/r as they are located differently. But unfortunately plant P281 is added in the release strategy of plant P068 though there is a separate release strategy configured for plant P281. So while making P/r of plant P281 release strategy of plant P068 is getting called & the user is not able to release the same because of the restricted authorizations. We have tried to remove the plant P281for which we created the request on DEV server & transported to PRD server but this is not removed. It is still reflecting in P068 P/r release strategy. Kindly advise how we can remove this ? Is their any other alternative way?
Rgds
Prashant B

You need to remove the plant from classification of release strategy. If system is modifiable, go into release strategy and classification and uncheck the plant, which is not required and save.
OR
If backend is unmodifiable, use this t-code CL20n/CL24n, put in the release code strategy combination and in the classification remove the plant of it and then save and your problem will be solved.
Follow the above steps for adding the plant to new release strategy as well.
Edited by: Afshad Irani on Apr 28, 2010 4:45 PM

Release Strategy for inter Storage Loc Material transfer within same Plant

Hi Guru's
I hope all are doing good. I gota small concern to share with you. Is it possible to apply Release Strategy between two Storage Locations within same Plant for Material Movement?
Many Thanks
SONAL

Release Strategy cannot be assigned in material document.
However you can restrict this at authorisation level for T code MIGO_TR.
Regards
Bhavesh Mistry

Release Strategy Question

Hi,
Can anyone explain me with example, why is it that we can have only one class and not more, when configuring groups in the release strategy.
Why is it mandatory to have only one class for overall and one class for line item release, can someone explain with examples.
The system allows creation of multiple groups, but all have to use the same Class when it comes to overall release/ Line item release.
I am not able to understand the reason behind this restriction as of now, can someone share some insights.
Thanks
Shailesh

Hi,
Better & always keep one release class ....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.Under each separate class keep your requires characteristics.Then do necessary confuguration for release statergy.
For more check the links:
/people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
Re: Class and release group and code in release strategy??
Regards,
Biju K

PR release Strategy Restrictions

Similar Messages

Maybe you are looking for