Can an existing Release Strategy be deactivated?

Hi MM Gurus,
We have configured Release strategy which is working fine. Now, a new requirement has come up.
We donu2019t want to use the old Release strategy codes and want to create new one.
Is there any way which we can deactivate the old release groups/strategy/codes? What is the standard practice? Can we also delete the same?
Thanks in advance
M

Hi,
Addition of new release code will not affect previously created POs .
but for newly created POs it will add one more level.I think it is desirable results.
regards,
sujit

Similar Messages

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Release code addition in an existing release strategy

Dear All,
Kindly let me know what are the implications when we have to add a release code in already working release strategy?
Thanks,
Sam

Hi,
Addition of new release code will not affect previously created POs .
but for newly created POs it will add one more level.I think it is desirable results.
regards,
sujit

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Po release strategy - if value decreased

Dears,
If the Po value is decreased, I need the release strategy to be re triggered. As I know in standard its not possible. But can you help Is there any BADI or user exits can be used to accomplish this task.
Regards
Kamesh

Hi,
Use release indicator '4' or '6" during designing of release strategy.
And
If you want PO release strategy should trigger for reduced value ,then you can for User exit EXIT_SAPLEBND_002 or check to modify standard function module ME_REL_STRATEGIE_EKKO which help to reset existing release strategy for reduced/increased and/or values.
For more check the SAP note:493900
Regards,
Biju K

Release strategy modification

Hi all,
I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document & 2. Purchasing Group .
Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
Please help! How can I achieve this...
Thanks,
Rajan U

Hi,
As needed, you created one more charterictics CEBAN - CFWRT and included it in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
1. <= 5000 INR
2. > 5000 INR
Craete release group as PO and create two release codes C1 & C2.
Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
Regards,
Biju K

Release strategy based on costcentre for PR

Hi Experts
I want to add Cost Centre as my release criteria in the existing release strategy . Presently I have Purchase grp and amount as my release criteria . Pls advise me how to proceed on this . Kindly also let me know how the user can be mapped to cost centres for approval as the user wants to have different approvers for different cost centres. We have searched for the authorisation obj for cost centre but could not get mor information .Pls help .
Thanks
Edited by: Devashish Lenka on Sep 6, 2010 2:10 PM

Hi,
Option-1:
You can create release characteristics with field KOSTL and add this characteristic with release class with other release characteristics. And you can design your release strategy based on requirement & then limit the cost center via authorization object K_REPO_CCA
Option-2:
Create Purchasing Group (OME4) as Department & assign the department to Cost center(KS02/KS01). Now create purchasing group as release characteristics with field EKGRP add this characteristic with release class with other release characteristics. And now you can design your release strategy based on requirement.
Regards,
Biju K

Release Strategy De-Commissiono

Hi Guru's
Please can you give me the best advice on how to de-commission an existing Release Strategy.
We have a Release Strategy in place which is not suppose to be effective in the new process orders being created.
Since the previous consultant removed all the cost centres out of the strategy, however when Purchase Orders are being created the original strategy assigned to the PO is over written by the release strategy that does not have any cost centers assigned to it.
How could shoudl I approach this with p[[reventing this strategy from appearing in the PO's agauin?
Points will certainly be awarded.
Kind regards
Kasavan Aboo

Basically you have to compe with the unique combination of your requirements, without looking your classificaiton data we can not suggest what to do becuse we don;t know the requirements and classification.
Please provide the details than we can help you out.

No Release Strategy determined - Message no. Z_MESSAGES032

Hi All,
I am trying to creat PO without reference to PR and facing error:
No Release Strategy determined
Message no. Z_MESSAGES032
This is for newly created PO type and new cost center.
We don't have any PR, we are creating PO directly
please advice

Hi Vishal,
As you mentioned you have created new PO type so I think release strategy is not created for this document type. You can go to the IMG ==> MM ==> Purchasing ==> Purchase Order ==> Rlease Procedure for Purchase order ==> Define Release Procedure for Purchase Order.
Select Release Strategies option and create new Strategy. Selecte the newly created strategy and go to details and click on Classification and then Add your document type and other information. If you have any existing release strategy you can select that and add another document type in the classification.
I hope this will help.
regards,
Ajay Mishra

Reset Purchaser Order release strategy

Hi All
Does any one knows how to configure the Resetting of Release Strategy when the PO value/amount is reduced? We are in 4.6C, is it standard or are there any settings or transaction code?
Please help.
Thank you
Jesielle

Hi,
Use release indicator '4' or '6" during designing of release strategy.
And
If you want PO release strategy should trigger for reduced value ,then you can for User exit OR modify standard function module which help to reset existing release strategy for reduced/increased and/or values.
For more check the SAP note:493900
Regards,
Biju K

Release Strategy - Object "ZX NX" already classified with same characterist

Hi Gurus
While modifiying the exist release strategy the following error occurs.
Object "ZX NX" already classified with same characteristic values
Message no. C1818
Diagnosis
Object ZX NX was already classified with the same characteristic values. In class maintenance, you define whether a warning message or error message is displayed in these circumstances. This message draws your attention to the possibility of data redundancy.
Procedure
Change the assigned characteristic values, so that you do not have redundancy in your system.
Perhaps the object you are classifying is not necessary, because it can be replaced by the object found by the system.
Please advice on this.
Thanks in advance
ARAS

Hi
Thanks for your input. I will test this and come back.
Experts, any further inputs...
Regards
Aras

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

Precautions to be taken before going for new PR Release strategy

Dear all,
We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
Need your advice on
1)If we go for new release strategy as off with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
3)Any other which I missed out, please suggest me
Thanks
RS

Hi,
It is better to release all existing PRs using your current procedure without classificaton and clean up.
If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
REgards
Ram
Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

Release strategy for Release POs

Hi Every one,
We have a requirement.
A contract is created and approved as per the regular strategy.
The releases (POs) are created against it and sent directly to the vendor.
As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
But the business wants the PO releases too to follow the release strategy.
Can you please look in to this and let me what changes we need to make this happen.
Regards
Pavan

As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
So that the Release Process is applicable to PO's created w.r.to Contract also..
For ex: if you use the field purchase Doc category as a Character in the Release , it differentiates whether it is PO or Contract..
So that you can define different Release Strategy for PO & Contract
Or if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
then the release strategy applies to PO also..

Release strategy not getting triggered.

Hello,
As per the client request, new Purchase group had to be added to the existing release strategy.
I had added the purchase group in the edit characteristics and in the release strategies: classification.
But now the the release strategy is not getting triggerred.
In CL20n I see that the, status is marked 3 i.e incomplete. The reason to this is not known as customizing done is correct.
In OMGSCK i see that no errors are found with the release strategy.
Please suggest.
Regards,
Neetha

hi,
Sometimes the strategies are taken after restarting the sap system...there has been one same situation before also..at that time the same strategy started working after restarting the sap system...
pls check it may be the same issue with you also..
Regards
Priyanka.P

Can an existing Release Strategy be deactivated?

Similar Messages

Maybe you are looking for