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

Similar Messages

  • Release strategy determination for PO item level characteristic value

    Hi Experts
    I have user material group as release characterstic for PO.
    I have created two line items with two different material groups.
    How the release strategy determination occurs when the two different material groups are linked to two different strategies?
    regards
    ramSiva

    Hi,
    in this case system is NOT able to find the release startegy.
    Please take care of the following explanation (see note 365604)
    o  For OVERALL RELEASE (purchase order and purchase requisition) the
       item fields such as Plant and Material Group will be aggregated
       to header level.
       For example you use Plant/material group
    as one of your characteristics. If all
    items do not belong to the same plant/material group
    then
    *******the relase strategy will not be found***********
    unless you have maintained a blank value as one
    of your allowed values for the characteristic Plant/material group
    . If all items
    belong to the same plant7material group
    then that plant is aggregated to the
    header; if one or more is different then a blank is aggregated to
    the header.
    If you use an overall release strategy all
    characteristics which you have defined in the customizing (CEKKO-MATKL
    must have the same value. If one item has material class x and the
    other y the system does not know with which material class it should
    look for a release strategy. Now the system sets the material class
    to 'blank' and tries to find a release strategy. If you do not have
    defined a blank entry in the customizing (Transaction: OMGS
    : OLME >release procedure for PO > rel. strategy ) the
    system won't find a release strategy.
    you need
    to add a blank value to your allowed characteristic values in your
    release strategy.  To do this you can define a blank value in your
    characteristic (CT04).  On the values screen leave the char.value
    blank and add a description and save.  Now in OMGS you can select
    this value as an allowed value for the characteristic.
    (Example:
    To avoid this you can do the following:
    - go into transaction CT04
    - enter the characteristic 'CEKKO-MATKL'
    - click on the tab 'values'
    - set a flag in 'additional values'
    - in the column 'Char. value' do not enter anything
    - in the column 'Description' enter a text like 'no material class'
    - save this setting
    Now
    - go into transaction OMGS -> button 'release strategy'
    -> button 'classification'
    - double click on CEKKO-MATKL' and set a flag in 'no material class' )
    Please also have a look into the attached note 365604 point  2d).
    BR
    Nadia Orlandi

  • PO Release Strategy Determination

    Hi,
    Is there a user exit/badi where we can skip calling the FM ME_REL_STRATEGIE_EKKO (I believe this FM is responsible for re determining the release strategy of a PO) if this change is not related to any item price change ? What we want to have is for the PO to use the same release strategy if the header text is the only one changed.
    Thanks.

    Hi,
    I dont think there is any EXIT/BADI to avoid FM 'ME_REL_STRATEGIE_EKKO'.
    You can actually create an enhancement point at the start of this FM and check for the conditions when you want this FM to skip and EXIT from this FM.
    But this is not the wise way of doing.
    If you can elaborate your requirement in detail, may be some one can help you with other alternatives..
    Regards,
    Gautham Paspala

  • 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

  • PR Release Strategy for Account assignment cat "U"

    Is it possible to set up release strategy for Acct assignment Cat "U" - if yes, How would it be configured?  additionally we are also setting up Rel str for acct assign cat K and A - specific question is relative to "U" in addition to K and A.
    Other parameters being used are
    pur Org
    Doc type
    cost center
    Total value
    Thanks for the help in advance
    Raj

    Dear Raj,
    When you creating PR with acct assignment U, the acct. assignment tab will not appear, thus
    you not able to enter cost center. You may try this workaround via customizing.
    a) You may define a <BLANK> value for the cost center in customizing and assign it to your release strategy.
    Characteristic:
    Cost Center:
    Value    Desc:
    1000     1000
    2000      2000
                    <BLANK>
    b) You may use user exit  EXIT_SAPLEBND_001 and pass the dummy cost center to get the release strategy
    determine.
    Regards,
    ian Wong Loke Foong

  • Cost Center based Release Strategy for PR's

    System :4.6c
    At this time, we have PR release strategy with classification configured for over all release.
    Created a new characteristic for cost center , assigned the values for the cost center characteristic, with zeros at the beiginnig.
    Now when I create a PR with multiple line items and with multiple cost centers, the system is not deriving the release strategy defined. But if I create multiple line items with the same cost center, the system is able to find the right release strategy.
    Does it have to be the same cost center in all the line items to trigger the right release strategy?
    Thanks.

    Hi,
    Looking at your question it seems you are using overall release strategy. If the characteristic value is not same for all line items then during overall release strategy determination, the system uses "BLANK" value for this characteristic.
    In order for a release strategy to be found, when you have different
    cost center in different PR items you need to add a blank value to your allowed characteristic value for the cost center in your release strategy. Also use Account Assignment Category (KNTTP) as one of your characteristics and define K as an entry, so that release is triggered only when it determines cost center blank with account assignment K.
    But if for diff cost centers there is diff strategy then you better opt for Item level Release.
    Please give this a Try.
    Regards
    Chandra Shekhar

  • How to block PR creation with no release strategy

    Hi,
    We have this PR release strategy implemented. Currrently, user are able to create the PR even there's no release strategy determined. Thus, PO can be created as the processing state is "02 Active". 
    Would like to block user from creating the PR if there's no release strategy determined. How should we do in order to achieve this?
    Many thanks in advance.
    Sue

    Hi Sue
    Assuming that you are using release with classification.
    Create a new characteristic for PR document type (CT04)
    Attach this characteristic to your Class (CL02)
    Create new release strategy and in Characteristic data you will have to assign all your PR document type. This will ensure that all the PRs need to be released.
    Regards
    Rajesh
    -Do reward if this is useful.

  • Release strategy PO/PR - no SPRO

    Hi everyone!
    I'm trying to check whether release strategy for PO and PR are set up correctly.
    How can I check this on IMG withouth having access to transaction SPRO?
    Thanks!
    Cira

    Hi Cira
    Probably the easiest way is to create a PO and debug the release strategy determination.
    At that point the system reads all the customising tables and you can see if it fails where it fails
    and why. Here is some information that can help you do this from ME21n after you save the PO:
    Main Program     SAPLMEPO
    Source code of   MM06EF0S_STRATEGIE_ERMITTELN
    form STRATEGIE_ERMITTELN
    *- Kommunikationsstruktur neu aufbauen --------------------------------*
         MOVE cekko TO *cekko.
          PERFORM strategie_cekko.
    CALL FUNCTION 'ME_REL_STRATEGIE_EKKO'     >>>>>>
    Step into function ME_REL_STRATEGIE_EKKO
    When successful the FR* fields will be filled in EKKO (FRGGR FRGSX etc)
    Hope it helps
    Kind regards
    Brian

  • PR Workflow for release strategy

    Hi,
    Could you please let me know the steps how to configure the workflow for the PR release strategy for both item level as well as header level.
    Thanks in advance
    Shp

    Hello,
    If you wish to work with procedure 1, define the following:
    Release codes
    Release indicators
    Assignment of release indicators
    Release prerequisites
    Determination of release strategy
    1. Release codes
    Create the release codes.
    2. Release indicators
    Define release indicators and branch to the detail screen. Here you define whether fixed purchase requisitions may be changed by Materials Planning, for example, and whether an RFQ or a purchase order may be created from the requisition.
    You can also determine the field selection here.
    In the area "Changes after the start of the release procedure", you specify whether a requisition may be changed after the release procedure has begun. You specify whether the strategy has to be redetermined after changes, or whether the release procedure has to start all over again from the beginning.
    This parameter bears a relation to the parameter "Value change". For example, previous releases are not cancelled if the value of the requisition item after the change does not exceed plus 10% of its original value.
    Attention:
    Be sure to create a release indicator (e.g. B for "blocked") that serves as the starting point for subsequent indicators. Do not set the indicators for release for the issue of RFQs and PO on the detail screen for this indicator.
    Also create a release indicator characterizing the released status. Set the indicators for release for the issue of RFQs and PO on the detail screen.
    3. Assignment of release indicators
    Assign a release indicator in dependence on the status of the release.
    Example:
    You create a release strategy S1 consisting of two release codes 01 and 02. Release with 01 is a prerequisite for release with 02. If release has been effected with 01, the requisition has been given the "all clear" for the issue of RFQs.
    You have created the release indicators B (blocked), 1 (cleared for issue of RFQs) and 2 (cleared for RFQs and PO).
    Now enter the following as assignment:
    Strategy   C1  C2  C3 ...
    S1                           B (blocked)
    S1         X                1 (RFQ)
    S1         X   X            2 (RFQ/PO)
    4. Release prerequisites
    Define which release codes are involved in a release strategy. Specify whether a code is set for a release status following release, and whether one release status is a prerequisite for another (+).
    Example:
    Strategy   Code  C1  C2  C3 ...
    S1         01    X
    S1         02    +   X
    5. Determination of the release strategy
    Determine the conditions under which each release strategy is assigned. The criteria are account assignment category, material group, plant, and value of the requisition item.

  • How to set the Release Strategy without classification for PR

    Hi,
    I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
    I crated the Release Codes, however not able to find what options to choose in the following steps :-
    Release indicator
    Assign Release Indicators
    Release Points: Prerequisites
    Determination of Release Strategy
    Regards,
    Yogesh

    1. Release codes                                                            
       Create the release codes.     For  Purch. Officer, Manager and Sr. Manager                                                                               
    Like PO, MG, SM                                      
    2. Release indicators                                                       
       Define release indicators and branch to the detail screen. Here you      
       define whether fixed purchase requisitions may be changed by Materials   
       Planning, for example, and whether an RFQ or a purchase order may be     
       created from the requisition.                                            
       You can also determine the field selection here.                                                                               
    In the area "Changes after the start of the release procedure", you      
       specify whether a requisition may be changed after the release           
       procedure has begun. You specify whether the strategy has to be          
       redetermined after changes, or whether the release procedure has to      
       start all over again from the beginning.                                                                               
    This parameter bears a relation to the parameter "Value change". For     
       example, previous releases are not cancelled if the value of the         
       requisition item after the change does not exceed plus 10% of its        
       original value.                                                                               
    Attention:                                                               
       Be sure to create a release indicator (e.g. B for "blocked") that        
       serves as the starting point for subsequent indicators. Do not set the   
       indicators for release for the issue of RFQs and PO on the detail        
       screen for this indicator.                                               
       Also create a release indicator characterizing the released status.      
       Set the indicators for release for the issue of RFQs and PO on the       
       detail screen.                                                           
    You can use sytem defined indicator in this case you don’t have to do anything                                                                               
    3. Assignment of release indicators                                         
       Assign a release indicator in dependence on the status of the release.                                                                               
    Example:                                                                 
       You create a release strategy S1 consisting of two release codes 01      
       and 02. Release with 01 is a prerequisite for release with 02. If        
       release has been effected with 01, the requisition has been given the    
       "all clear" for the issue of RFQs.                                       
       You have created the release indicators B (blocked), 1 (cleared for      
       issue of RFQs) and 2 (cleared for RFQs and PO).                          
       Now enter the following as assignment:                                                                               
    Strategy   C1  C2  C3 ...                                                
       S1                          B (blocked)                                  
       S1         X                1 (RFQ)                                      
       S1         X   X            2 (RFQ/PO)                                                                               
    4. Release prerequisites                                                    
       Define which release codes are involved in a release strategy. Specify   
       whether a code is set for a release status following release, and        
       whether one release status is a prerequisite for another (+).            
       Example:                                                                 
      Strategy   Code  C1  C2  C3 ...                                  
    S1         01    X                                               
    S1         02    +   X                                                                               
    5. Determination of the release strategy                            
    Determine the conditions under which each release strategy is    
    assigned. The criteria are account assignment category, material 
    group, plant, and value of the requisition item.                                                                               
    Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
    E.G if you will not define the Material group here but it will default in req in that case this will not work that’s the reason you have to work with Classification.               
    <b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

  • 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

  • How to determine the right PR Release strategy

    Hi Experts,
    Could u help me to solve this problem!
    As our business, we want the system automatically determine the right Release Strategy based on the total Amount(amt) of PR such as
    - if PR total amt <= 1000 USD --> must  checked by only Department Manager (DM)
    - if PR total amt >1000 USD --> must checked by  Department Manager (DM) and General Director (GD) 
    so i've already configured system like that:
    1. Create characteristic : CEBAN_GSWRT (Structure CEBAN ; Field GSWRT)
    2. create anew Class CEBAN_GSWRT, which associated with above Characteristic
    3. Create release Group "03", which associated with above Class (CEBAN_GSWRT) and cheked "Overall Release PR"
    4. Create Release Code DM ; GD
    5. Create two Release Strategy such as:
      5.1.  Strategy 01 - DM Only, which have only DM release code & assigned to class  CEBAN_GSWRT and the value identified here is <=1000 USD
    5.2  Strategy 02 - DM -GD , which have DM & GD release code & assigned to class  CEBAN_GSWRT and the value identified here is >1000 USD
    then, i created two PRs, one have amt <1000 USD , another >1000 USD, but the system alway get the same Release Strategy 01,its mean that system allway apply the first case Amt of PR <1000 USD.
    Note: In the Document Type i checked Overall Release also!
    So, pls help me to show out wrong or missing steps!
    Thanks in advance
    Vietttq.
    Edited by: viettq on Sep 1, 2009 4:32 AM

    Hi,
    Please open the below link, it will help you to understand the complete step by step  process:
    http://www.sap123.com/showthread.php?t=59

  • Release strategy for no determination

    Hi guys,
    I have a release strategy for PR that is determined based on the cost center, regarding the account assign. ctg. and the cost center. The problem is: when the release strategy is not determined - most of the times, it happens on the creation of a new cost center - the PR is born already released. I need to figure out a way to direct this situation to a strategy that nobody can approve.
    Thanks in advance.
    Regards,
    Marcelo Buosi.

    Hi,
    Ok. Check the below process & May helpful to you.
    Now Create purchasing Group for a departments ( Say example as E01 for Environment ) in OME4 t.code
    Create a Cost center for the department where cost going to capture ( Say in  Environment Department) and assign department to cost center in basis data TAB of cost center in KS01/KS02 t.code.
    Note:
    Create Characteristics in CT04 t.code {Table ECBAN & field name for department responsible }
    Create Class in CL02 t.code and assign Characteristics with other characteristics
    Create Release Groups, Release Codes, Release Indicator for PR and finally Release strategies u2026u2026u2026..in Classification view for each releases strategy keep the department responsible and other values.
    Regards,
    Biju K

  • PR Release Strategy Re-determining due to Change in Text

    The PR release strategy was configured by a previous company.  There are existing PRs that are not completely approved (Release Indicator = 2).  The SAP instanced was transitioned to the company that broke away.
    The PR release has now been re-configured with new release strategies (groups, codes..etc).  What we are experiencing is that the existing PRs that are "released" do not show the new release strategy when the combination of release strategy/release group does not exist- This OK as well.
    When a user made a change to the Item Text and nothing else, SAP re-determined the release strategy and started the release process over again.  Is there a way to stop these PRs from re-determining and therefore restarting?

    Hi There
    Though the release strategy is different, i think all the classifications are same or old classification (even 4 or 5 parameters) may also part of your new full release strategy(You may be trimmed from old release).
    So when you do any changes or just go to the change mode and Check (F7) , system may find the new rel strategy.
    i have not tested the above scenario, i could recall some older posting based on that i did suggest the above
    Thanks Senthil P

  • Error message if no release strategy is applied for PO

    Dear All,
    In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
    Is there any way to encounter this
    Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
    OR
    While making GRN against this PO, System will give message Like say ...  no release strategy is applied for the PO..
    Please reply  ...URGENT
    Regards,
    Rakesh Shelar

    Dear Thanx.
    my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
    In this, case  system is allowing to take GRN against such POs without release strategies

Maybe you are looking for