Release strategy config

Hello All,
Does all the release strategy config for Scheduling Agreements automatically gets updated in POs also?
e.g. we have a scenario whereas the once released SAs should not come into release procedure at all. (I know this speaks somewhat uncommon, but this is how the requirement is). For this I have made the following config:
MM>Purchasing>SA>Release procedure for scheduling agreements>Define Release procedure for scheduling agreements>Release Indicator> 1. B         6                           blocked
                                                    2. C         6          100%       changeable
                                                    3. R         2                           released
It is serving the purpose for SAs, but the same is also spilled over to PO config, which we donot want
Is there any ay which we can check it getting effected for POs?
Thanks.

H
Hi please create some characteristics  which you may be using exclusively for PO alone. These characteristics should not be used in S.A. I guess if you are using SA as your major transaction for material movement then most probably you will be using PO for cost center and some other emergency purchase in that case It should not be a problem for you.  This strategy if Im not wrong spills over to RFQ/CONTRACT/SA/PO, we need to take call based upon  the utilisation factor.
Regards

Similar Messages

  • Release strategy for Return PO

    Hi,
    Can we create Release strategy for Return PO's. ?
    Regards
    Sunil

    Hi,
    The process for return PO is:
    Process:
    - Create a return PO
    - Create a outbound delivery
    - Goods issue
    Release Strategy can be created for All Document Types as Document Types being one of the determining factors for Release strategies. So under Classification data Characteristics which we maintain determine the release strategies for a Particular Purchasing documents. Actually it depends on your Business case that for what all documents you want to have a release strategy config.
    regards,
    Prashant Rathore.

  • Release strategy Purchase order missing

    Hi experts,
    I set release strategy for purchase order and it was working OK, but now release procedure is not active when I create a purchase order, all setting are correct and verificaction too.
    Sap version is ECC 6.0, I do not know if there is something to correct this error, because I created some POs and release tab was displayed correctly but now it does not work.
    Do you know something to solve this issue?
    Thanks
    Regards,
    Lili.

    Please make sure the release strategy is not changed by some one and than check it out
    or go to release strategy config and check the release strategy of last config
    here everything should be green or yellow
    now go to CL30 and enter your class and class type 032 and hit enter
    then enter the value of you charactristics which you have used in the Po and hit the Find in inti class from top menu
    see what all release stra get pulled.
    if oyu pulled more than one that means you have duplication inyour release strategy

  • PR Release Strategy for DOCUMENT TYPE

    Hi Gurus,
    I have created a Document Type in PR & I want to set a Release Startegy for ONLY that Document Type.
    Can anybody explain me step by setp procedure for this ?, I have gone thru one link :
    http://www.sap123.com/showthread.php?t=59
    but I could not set the relase startegy. May be I am missing something ??
    Thanks & Regards,
    Vikas

    If you want to define the release strategy only for doc type
    then
    create the class using CL02
    create the chra for Doc type using CT04  - the table is CEBAN and the field is BSART
    then assign the doc type value in char (after you create the char then go back and assign the value)
    now assign your char to your class
    now go to SPRO and goto PR release strategy config -  procedure with classification
    go to Set Up Procedure with Classification
    create your release group by assigning the calss you have created (make sure this config should have only one class)
    create release code
    release indicator is already exist in sap so you don;t need to create
    create your release strategy and assign the value in classification tab of release strategy
    this will work
    but make sure that - if you are creating only for doc type means all the reqs created for this doc type will be blocked by the system. so if you have reqs like if this doc type and the amount >5000 then only block then you have to have amount is also you char in your class
    hope this will give you a cleat idea

  • How config release strategy by materia type.

    Hello... Help me...
    I want to PO Release by material type(MTART), but in CEKKO, there is no MTART.
    So I use user-exit EXIT_SAPLEBND_002-ZXM06U22.
    But I didn't config PO release by material type.
    I set characteristic-additional data  Table name : CEKKO, Field name : LBLIF.
    What is wrong this user-exit program? (If material type = ZROH' --> PO Release)
      DATA IS_BEKPO TYPE BEKPO.
      move-corresponding i_cekko to e_cekko.
      LOOP AT IT_BEKPO INTO IS_BEKPO.
        IF IS_BEKPO-MTART = 'ZROH'.  
           MOVE IS_BEKPO-MTART TO  E_CEKKO-LBLIF.
        ENDIF.
      ENDLOOP.
    Edited by: maro Kim on Oct 29, 2010 11:52 AM

    Hi,
    For PO's, only header level release is possible. There is no item level release possible.
    Material type is item level data. That's why using material type, you can't configer release strategy for the PO's.
    Regards
    KRK

  • Config process for release strategy of PR & PO

    Please give configuration cycle for PR & PO Release strategy.

    Here you go...http://www.saptechies.com/configuring-the-po-release-strategy/

  • 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

  • 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

  • Scheduling Agreement Release Strategy Issue

    Hi,
    We have a typical problem in Scheduling Agreement Release Strategy.
    Once the SA is released for the first time it should restart the release strategy again if there is a change in Quantity or Value or Purchasing group. The release strategy is getting restart for some of the release strategies and not for others. I compared the characteristics, class for both the release strategies and I am not seeing any difference.
    Can anyone please help me in this regard.
    Thanks in advance.
    Regards
    Ram

    release strategy can be rerigger in case where qty or price change and the changes is over the percentage you defined for Release indicator
    goto release indicator config and in SPRO for release strategy and check the Value change %
    maintian 0.1 here
    so any change above 0.1 will retrigger
    and maintian value 4 in chgable field.

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

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • New release strategy should not trgger for PO released with old Rel Strategy

    Hi All,
    Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy  XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
    But requirement is if there is  any change or value decreasing in fully released Pos with old strategy  it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
    Please help me on this.
    regards,
    Rohit

    HI Rohit
    A reset of the release strategy only takes place if
           -  the changeability of the release indicator is set to '4' in
              case of a purchase requisition and '4' or '6' in case of
              another purchasing document (purchase order, request for
              quotation, contract, scheduling agreement),
           -  the document is still subject to the previous release
              strategy,
           -  the new TOTAL NET ORDER VALUE is higher than the old one.
    The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
    The commom steps are:
    1- make sure all of the old POs should have been released.
    2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
    3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
    Kind regards,
    Lorraine

  • Message no. CZ160 - Select a valid release strategy - IS Retail

    while assigning PR release strategy to site thru' "Determination of Release Strategy" under tcode WB02, i am getting following error message.
    Select a valid release strategy
    Message no. CZ160
    Diagnosis
    The release strategy 01 is not defined.
    Procedure
    List the permissible values using F4, and choose a valid release strategy.
    FYI, i configured PR release strategy "01" with required config. requirements and checcked the same thru' simulation and it is working fine.

    Hi,
    Please follow the steps;
    1. Create characteristics via tcode CT04
    2. Create Class for class type 032. Via tcode CL02
    3. Then go to SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure. create release group, rel obj, class 032.
    Next, set up release codes followed by release indicator.
    Then the release strategies.
    4. go to tcode CL20N to assign the release group and release strategy to the class and class type.
    5. SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure -> Check Release Strategies

  • P.O Release Strategy Problem

    Hi,
    I have a case in our production system, where we have a release strategy for P.O, which has got 3 release codes.. Say strategy is A and Release group is B.
    When I create the P.O, The release strategy B A is being called, but inexplicably, I see 4 release levels,  I go to SPRO and check the Release Strategy B A  but in that strategy too, only 3 levels are maintained.
    I went to release simulation, here I see 4 levels !! Where if the approval is given at the 3rd level, the 4th level is automatically shown as approved, and the P.O gets released.
    I am curious to know, from where did this 4th level of approval come from, even though it is not defined in the config of the release strategy.
    The release code description for the 4th level (the additional level) is Financial release, I was wondering whether this additional level has got something to do with some setting done in FIAR/AP-Business Transactions...
    Can someone throw some light on this.
    Many Thanks
    Shailesh

    Hi Nick,
    I also thought the same, but to my utter surprise, I see only 3 levels in the release pre requisites, while when I click on simulation, I see 4 !!!
    However in the P.O as well as in simulation, once the 3rd level approves, the 4th one which is the Finance release happens automatically .
    I am trying to understand how did the 4th level come in from, Is it some other finance config setting?
    Thanks
    Shailesh

  • Mm pr-po release strategy : error

    Dear MM experts,
    We already having MM-rel strategy for PR & PO with classification procedure and working fine,
    Now business requirement is to change the MM-Rel PR& PO strategy,
    New mm-rel strategy for PR customised in class 032  (not to use existing release groups & release strategies) 
    After doing config settings in customising client, the request moved to another client for testing.
    Testing client, request moved successful, and while checking the settings in testing client,
    in Release Strategies - details mode
    Informatination is available at Release pre-requisites, Release Statuses without any error,
    but when we try for Classification, we are getting the following error
    "Error in classification (class PRREL class type 032)"
    Can u please suggest what needs to be done so that we can go ahead further.
    Kindly note while doing config setting client, we did not encounter the above error, it has accepted all the settings (copy existing rel group & having differnt rel strategies, etc)
    pl help
    Thanks in advance
    Srihari

    Hi Friends,
    My requirement is to add new release strategy for pr & po.
    Characteristics & Class are remain unchanged.
    Pl advise to how to proceed, i mean
    i have to set/create new release procedure, ie.,
    New release groups
    New release codes (bcos new codes are added & release levels remained same)
    New release strategies
    How i can retain the Old PRs & POs released with earlier release strategy/release codes?
    PRs & POs not released can be with new release strategy,  but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
    Also, I need ur advise, how the new release strategy works for workflow
    pl help
    thanks & regards
    Srihari

Maybe you are looking for

  • Problems with String.getBytes() method

    Consider this code     for(int k=0 ; k<256 ; k++)        char[] cc = {(char)k};        String xxx = new String(cc);        byte b1 = (byte)xxx.charAt(0);        byte[] bb = xxx.getBytes();        byte b2 = bb[0];        boolean diff = (b1!=b2);      

  • Bought a tv show on iTunes, file could not be found

    I bought a season of a tv show on iTunes on a laptop. I transferred some episodes onto my iPod and watched some on my iPod on iTunes using the internet, I reset my iPod and still can't find the tv show on iTunes on my iPod in the purchased section an

  • B9180 Printing w/ paper longer than 19"

    Is there a way to print on paper up to 44 inches long?  I thought I read somewhere that this printer could accept paper up to 13 x 44 using the specialty media tray.  I have a panorama that is 42 x 12 just waiting to come to life.

  • Issues with Image rendering from Database

    Maestros, I have an issue here that I working but can hardly find a plausible solution and would like some help from the community. I'll do my best to explain the my issue in detail that way those of you who are savvy in this domain can jump on it ri

  • Changing Variable & Method Names

    I wish to call a colour from the java.awt package, & want to be able to enter the colour on the fly. how do I call 'theColourIWant' & append it to the end so I get Color.theColourIWant. Another example would be to create multiple instances of a class