Release Strategy Get cancelled - Reg

Hai,
We are in SAP R/3 -ECC 6.O
Release stratgey has been set for the Purchase order  and its works well for so many years.
The issue is , Some of the P.O alone , when the Header Terms & condition changed , Like adding one text line, or Some space or some dot, comma, The Release Strategy gets Re - Triggered ( Plz mind that , i have not changed any P.O Qty  / Value/ Organisation entities/ Material Group/ Material/Tax code)
Kindly update , The reason - Why Release strategy gets re triggred for the , already Released P.O.
Regards,
PS

Release strategy gets retriggered only in case you have changed the amount or qty thereby increasing the amount of the PO
but as you say that you have not changed any thing which will impact the amount of the PO but the RS still gets re-triggered then we are left with only one option that some user exit has been active for this or some BADI please take help of abaper to find out the exit for this

Similar Messages

  • Cancellation of release strategy

    Hello to all,
    i have release strategy defined for purchase requisition and i want that when a post is deleted from the purchase requisition, the release strategy is canceled and must be released again.
    How to setup this.
    Regards.
    Zied.

    Hi ,
    In the release indicator mention 4 for chageability and mention some % for the value change.
    You have to check your scenario for the release indicator.
    Also for change in value only Release strategy will be reapplied and not in any other case.
    Regards
    Ankur

  • Release Strategy to work on PO Gross value (inclusive of taxes)

    Dear MM Gurus,
    We have configured the PO Release strategy as under:
    1) < 500000
    2) > 500000
    After checking the PO, we now find that the release strategy gets
    triggered on the basic price only. Any additions to the amounts in the
    condition tab also adds it to the Basic price and the release strategy
    is properly working.
    But when the user defines Tax code under Invoice tab, the Tax amount
    gets added to the PO value. But in this case, the Release strategy
    functionality does not work.
    Requirement is that the Release strategy should work on the total PO
    value (including Tax amounts). Any addition to the PO value by either
    Condition amounts and/or Tax amounts should activate the Release
    Strategy functionality.
    Currently, it works only for the Net order value. Please let us know
    how to configure for the PO Gross order value.
    Thanks in advance
    M

    How can you include tax amount in the release strategy process. Approvers are doingthe approval/rejection through release strategy only for goods that are being purchased and it is value and tax amount is not relevant here at all.
    Explain to your customer that this requirement cannot be implemented. If he still insists thatn tell him that only if they convert the tax amount into a price component, then it is possible. But then doing this means it is not tax, so basically the requirement is crazy.

  • Release Strategy - Purchase requistion go back to unreleased

    Hi Friends,
    I am facing  two  problem in release strategy in our client system.
    Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
    Current System Settings;-
    Release Procedure:- Procedure with classification ( Also setting available for  setup procedure without classification maintained )
    Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
    Value maintained in CL24N for plant , Creation indicator.
    Release Indicator:- 1 Stage:- X. Blocked
                                    2 Nd Stage:- 4.RFQ/PO no changes
    Scenario :- When  PR is created and released , If any one changes the Purchase Group in any line item  which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
    I checked all the system setting and it seems to be correct except when i  use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
    Checks re requisns. with item-wise release 3
    -> Checks re release group and release class 2
    -> No release group exists 1
    Problem. 2:- Purchase Requisition not triggering when  PR is created from other source linked to SAP.
    Please suggest the solution for the above problem.

    Hello Kunal,
    A few thoughts and questions on your problem:
    You generally can't have both release procedure without classification and release procedure with classification working at the same time.
    To get the system with classification working, you have to have several things in place and consistent: You need a release group.  It should have a class.  That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release).  You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
    You have to choose item-based or overall release for each requisition document type.  You mark this on the document type.  You must also choose the same option for the release groups that the document type will be assigned to.  Example: document type NB is item-based.  Document type ZB is overall.  Document type will be a characteristic.  CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ.  Release group NN will be marked as item-based.  Release group ZB will be marked as overall-based.  Usually, I think, you will  just use one or the other, and it will be less complicated, but the release group must match the document type.
    The indicators themselves have some configuration, including a field for changeability.  Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
    As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
    If you are using workflow, there might be custom events related to the business objects involved that  can change things, as well.
    Are you using workflow?
    Are you using overall or item-based release?
    Good luck,
    - Jeff

  • Purchase Requisition Release Strategy - multiple account assignments

    Hello,
    We would like to be able to create a purchase requisition where each line item can have 1of 3 account assignments (KNTTP).  These 3 account assignments all have the same Release Strategy.  Our expectation was that the purchase requisition would have a release strategy but it doesn't.  If we use 1 account assignment withmultiple line items we get a Release Strategy but if we mix them we get nothing.
    Does anyone know how to make the Release Strategy show up for multiple account assignments that share the same Release Strategy?
    Regards,
    Corinne Taylor

    Dear Corinne Taylor,
    You may assign a BLANK value in the characteristic:
    You can add also as " " and named it as BLANK so you can have your release strategy get trigger
    for all MRP account assignment or multiple account assignment.
    Example setup
    Account assignment A
    Account assignment K
    Release group X1 strategy 01 classfication has blank in values.
    Classification:
    Value Description
    A         Account assignment A
    K        Account assignment K
               BLANK
    Test this and it will work.
    Best Regards,
    Ian Wong

  • PR Old Release Strategy - triggering NEW Release strategy any change OLD PR

    Dear Gurus,
    We have implement item level PR release strategy,
    characteristic used:  1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
    BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
    Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
    Please advice
    REgards
    RS

    HI,
    If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
    ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
    Is this is standard behaviour? pleae advice
    Regards
    RS

  • Release strategy error in RFQ

    Dear MM gurus
    I have maintained all the steps for release strategy for RFQ, while clicking on release flag in ME42 it is giving following error. please guide
    Purchasing document 6000000015 not subject to
    release strategy
    Thanks in advance
    kailash N. thakkar
    9869171090

    Hai,
          Release strategy gets effected when all the characteristics mentioned for the release strategy are complied otherwise the strategy will not affect the RFQ.You might have given any value not relevant to the characteristic.For eg you might have given alower value than the value mentioned for the characteristic RFQ value.
    Regards,
    Gangadhar

  • 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.

  • 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

  • Reg:SAP_REORG_UPDATERECORDS job getting cancelled

    Hi Experts,
    I have a standard background job,SAP_REORG_UPDATERECORDS getting cancelled regularly in one of our production boxes.
    It runs only for a few seconds and then gets cancelled.
    The job log is.....
    "Job started
    Step 001 started (program RSM13002, variant SAP&001, user ID <XXXXXX>)
    Reorganization of update date not allowed in batch
    Job cancelled"
    I have searched for notes,but could not able to get the right solution
    kindly,help me resolve the issue
    Thnaks in advance
    Rgds-
    Venu

    Hello Venu,
    This job is no more needed as per recommenation from SAP
    Please go through the following notes:16083 and 67014 it shows that job is no more needed.This is the note of SAP about this job:
    "The standard job SAP_REORG_UPDATERECORDS that was contained in some delivered versions must no longer be executed (see Note 67014). In its new version, the underlying ABAP Program RSM13002 is programmed so that it terminates when running in a job (that is, in the background). Therefore, the job SAP_REORG_UPDATERECORDS always terminates in this case. In any case, the job SAP_REORG_UPDATERECORDS should be deleted from the pool of standard jobs, if it is still there: sm36 -> 'Standard jobs' -> 'Delete standard jobs'. In addition, released jobs that may exist and contain report RSM13002 should be deleted. You can find and delete these jobs using sm37."
    Rohit

  • Cancel PO - Release strategy remains active... WHY?

    Sometimes, when I cancel a Purchase Order with the bin, the release strategy remains active and the approver finds the PO among the ones he has to approve, even if it has been cancelled. In many other cases, instead, when I cancel a PO the release strategy correctly disappears.
    Could someone let me know why the release strategy remains active?
    Thank you so much.
    Fabio

    Thank you for your reply but I don't agree at all with you.
    In many cases, the most cases, when I delate a PO the release strategy disappears. Sometimes it remains active and I don't understand why.
    The approver shouldn't see these delated PO's among the ones he has to approve.
    Thanks again.
    Fabio

  • 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

  • Release strategy is not getting Trigerred for Multiple Plants in PO.

    Dear gurus,
    I have a Release strategy which is working Fine when I create a PO with Same Plant in line items.
    But My release strategy is not getting trigerred when I have Different Plants in Line items.
    I have Maintained all the Plants in the characteristic Values of Plant.
    Why does the RS work for Single Plant & doesn't work for Multiple Plants in the same PO.
    Is there any SAP Note applicable to this? Pl Suggest.
    Thanks guys
    SN

    i got your point but i will again say the same thing that for item level field system is not  able to block the po if there are multiple line item in RS and that too with different values against same char as system picks only 1 value and it sends that value in RS to cross check wheteher this po needs to be blocked or not .
    now in your case system is getting multiple values against 1 field that is plant so now system is not able to send 1 in backend and hence it sends blank value in back end so system dosent blocks the po
    even if you use material group or any other item level field system is going to behave that way only that is it will not be blocking the po

  • PO Release strategy workflow not getting transferred

    Hi All,
    I have done all the configurations related to PO release strategy workflow but when transferred to Quality certain configuartion done in PFTC workflow builder are not getting transferred.
    I also got message like 'release of purchase order transferred to buffer'.
    Please guide.
    Thanks in advance
    Pavan H S

    Hi,
    In QA
    1) Go to SWU3 check Workflow Configuration Done or not
    2) Execute the workflow in SWUS and check it
    3) If it working, test the workflow it via T.code SWUE, If not working then workflow is deactivated
    4) You have to move the Workbench Transport Request first,  then you have to Move customizing Transport Request.
    Regards,
    Surjith

  • Purchasing document release strategy to be cancelled at all changes

    I want the release strategy of  PO/ Contract/ Sch. Aggr. to be cancelled at every change i make to the document and not only the value. I do not want to include any fields at the class, i just want any change (like addition of new material, change of account assignment etc) to cancell the release document.
    Regards

    The way to achieve this requirement is to create a custom field in the PO header that signifies that the PO has been changed.
    It should be populated with a value say - X when a change is done and presence of this X should trigger release strategy. So you will need only this field in the characterisitcs and through user exit populate this field with X when PO was created and once released, make it blank. Then when changed repopulate with X
    In this way you can ensure that any change to PO will trigger the release strategy

Maybe you are looking for