Need workaround - Release strategy

Hi,
I have done three release strategy(R.S.) for PO.
First R.S. is from 0 t0 9,999
Second R.S. is from 10,000 to 99,999
Third R.S. is from 100,000 to 500.000.
When the PO value is 250,000 the third R.S. comes to picture and it is released by people concern.
When the same PO value is decreased from 250,000 to 90,000 the PO is de-released and it goes back to second R.S.
wherein the enduser is not comfortable as the PO is already released with third R.S..
Enduser do not want to release again using second R.S.
Please suggest to stop from derelease after it is released by third R.S.....

Hi Vishnu,
See Note 662993 on conditions based on which release strategies are reset.
When quantities or values are decreased, the system resets the release
only if a different release strategy is determined for the lower
quantity or the lower value.
If no different release strategy is determined due to the quantity or
the value decreasing, the system retains the releases that already
exist.
This is the desired standard system behavior.
As it also says: "This function can be changed only by a customer-specific modification."
So there is no standard way of achieving this.
Hope this helps.
Purnima.

Similar Messages

Release Strategy for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

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

Need to activate release strategy for PR from PS(a/c assignment N)

Dear experts,
I need to establish release strategy in PR raised from Project System. PR account assignment in 'N'= network. PR will be differentiated PR value wise . Please help in this regards,
Thank you.
Kind regards,
Zusen

Hi
You already have account assignment category (KNTTP) in communication structure CEBAN. You can use it to define your release strategy. If you wan to use field which is not there in CEBAN then you need to append CEBAN with the help of apaper.
Use this link as an example for release procedure and create your own with KNTTP.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Need to send work item to mutiple users at top level in PR release strategy

Dear All,
We are using workflow WS20000077 for PR release strategy.
Now the requirement is, at higer level, say at Board of director level, the work item should go to mutiple users and any one can approve/reject the work item. In other words, upto the board of director level , the workflowwill send work item to respective users as defined in release strategy, only at the Board of director level it should send work item to multiple users.
So how to send work item to mutiple users at a particular level in release strategy.
Thanks & Regards,
Fawaz

Hi Fawaz,
Your requirement can be achieved if you use Organisation Plan for agent assignment.
In the plan, you create position for each stage and assign the position ID in the worklfow section of the PR release strategy against the release code in MM.
The work item will goto all the users assigned to that position. this way is very flexible too for future agent change. only change the user assignment to the position.

Release Strategy for STO

Hello Experts,
We have a requirement to configure release procedure for STO scenario. Release procedure needs to be captured in STO PO's.
We have 6 plants - A,B,C,D,E,F, and each plant is having different approving authority individually.
When STO PO is created, it has to be approved by Issuing plant authority & receiving plant authority as well. The major concern here is for eg., approval authority for plant A can be a issuing authority at one instance & receiving authority at another instance.
How to configure release strategy for this.
We believe ,creating those many release strategies for all the combinations of plants will be a hectic task & still it'll multiply with the introduction of more number of plants.
Hence looking for a more simpler & feasible workaround/solution.
Regards
Mahesh.C.R

Hi,
you can use Supplying plant ( RESWK) and issuing plant (werks) both as characteristic and with these combination you can configue release strategy.
Or you can use User field format character for release strategy (USRC1)as per your requirement.
YB

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

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

Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

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 problem

I am working on configuration of PO release strategy.
I have two plants in one PO. I included both as values in characteristics and then selected in OMGS (classification) but release strategy is not working when I created purchase order with both plants but works with single plant.
Does anybody know why ?

Hi,
Release strategy for PO with line item charcterstics like Plant, item category, material group etc., gets updated into the structure CEKKO as blank if two different values found in a document. For this type you need to create a assign a value as blank for the Plant.
Ex: Release strategy S1 for plant 1000 with Charctertic value 1000
Release strategy S2 for plant 1100 with charcterstic value 1100
Release strategy S3 for both plants 1000, 1100 with charcterstic value " BLANK"
Regards,
Ramakrishna

Release strategy problem in Purchase order

Hi Guys,
I was trying to configure Release strategy for the purchase order and this button   is not triggering in my purchase order.
I dont know where I was doing wrong and where might be the problem as I tried several times.
Can someone give me some good idea about it how to configure in a proper way.
If you need any further information please let me know.
Thanks
Krishna

Hi
I hope you followed the following steps:
1. Create Characteristic using CT04
2. Create a class and link to the characteristic using CL02( class type: 32)
3. Configuration of release procedure
    SPRO IMG->MM-> Purchasing -> PO -> Release Procedure -> Set up procedure
    A) Create release group and link to class
    B) Create release code
    C) Set up the release indicator
    D) Set up Release Strategies-> strategy and codes
    E) Set up Release Strategies -> pre requisites
    F) Set up Release Strategies -> status
    G) Set up Release Strategies -> values for strategy
Regards,
Subhashini

PO Release Strategy - Only for Non MRP generated materials

Hello,
I have a requirement in which any material which was generated via MRP (via PR) should not go through a release strategy at the PO level, but a non MRP generated PR should...
Is this possible at all? I know its possible at the PR level, but not sure at the PO... Would this be a case where we would need to added a field to the CEKKO structure thats for MRP generated PRs ?
Thanks

Hi,
By business any PO created, should follow release procedure as PO a committed document which will further send to vendor.
If you are sure about your requirement, PO created from MRP PR should not follow release strategy, then no need to go for any User Exit.
Just create separate document type for PR (ZMNB) , create separate document type MRP PO( ZMNB) and link MRP PO document type ( ZMNB) with MRP PR document type( ZMNB) in flowing path:
SPRO>MM>Purchasing>Purchase Order>Define Document Types
Now select your ZMNB B Purchase Order Document type and click link purchase requisition document type in Dialog Structure, enter ZMNB Purchase Requisition Document type with a new entry & save.
As you created release characteristics of document type (CEKKO with BSART), then do not keep Value u201CMRP PO document type (ZMNB) u201Cin the release characteristics of document type and design your release strategies.
Now create your PO with MRP PO document type (ZMNB) and see no release strategy triggered.
Regards,
Biju K

New Release Strategy in case of PO amendment

Dear All,
We have the release strategy at PO level on 3 parameters,
Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
When ever users edit the PO, again system sets the release strategy as per above logic.
Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
Can any one send me a user manual and steps for this.
Thanks in advance,.
Vikas

Hi,
You can set a control within Config. there is a parameter called as release indicator.
Follow this IMG path:
SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
1     Cannot be changed
2     Changeable, no new determination of strategy
3     Changeable, new release in case of new strategy
4     Changeable, new release in case of new strat. or val. change
5     Changeable, new release if new strategy/outputted
6     Changeable, new rel. if new strat. or value change/outputted
     Changeable, new release in case of new strategy
Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
Hope this explanation was clear.
Prashant Rathore.

Need workaround - Release strategy

Similar Messages

Maybe you are looking for