Release strategy on the PO

Dear MM Gurus,
I tried to create a release strategy following the procedures per IMG, but my problem was that there was no display of that release strategy on the PO. What is the usual cause of this problem?
Regards,
Aktolga

Hi,
First, please kindly check note 365604 point 2(b).
b) The characteristics must be entered as they are specified on the
   database, that is, the item category must be entered in the
   internal format, for example (value 0-9), cost centers or
   material numbers must be entered with leading zeros..."
You can use transaction CL30N search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all." Please check  knowledge based article
1497235 .
Regards,
Ashwini.

Similar Messages

  • Source Determination resets the release strategy of the PR

    Hi
    I am trying to automate the Purchasing Cyle by running ME57 as a batch job along with ME59n for stock items on contract, however when I create the PR and approve it, when ME57 picks this approved PR it assigns the source automatically but removes the approval! I am having the ABAP consultants debug this, however is there something elementary that I have left out?
    Regards
    Thasmei Reddy

    Check if u have release strategy based on vendor - FLIEF. This could be a reason. When u change the vendor or assign a vendor, the release strategy is getting reset .

  • Add release strategy in the PO document type

    Dear all,
    I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type.
    Thanks
    Pauline

    Pauline,
    I would suggest you to please post this query in ERP MM forum to get it answered asap.
    Regards,
    Faisal

  • Release Strategy is not picking up in the PO.

    Hi All
    I have defined a Release Strategy for the Purchase Order.
    The Characteristics are
    PO category
    Pur Org
    Total Net Order Value
    All the lights are green which i check the release strategy.
    But the Release Strategy is not picking when PO is created.
    Kindly let me know what is the mistake i have dont or i need to make any corrections.
    Thanks in advance
    Renukaprasad.

    Hi Renuka,
    im using ECC6, my PO rel strategy dont have PO catergory,
    but you can try this:
    Maintained PO characteristics:
    PO doc type
    PO Plant
    PO Pur Grp
    PO total Value
    Once your PO meet this, Rel Strategy triggres.
    When you define the Rel Strategy, there is rel indicator Approved and Block, configure based on your requirement.
    Hope this helps a little
    Regards,
    Maia

  • The PO was printed straight away without going through Release Strategy.

    Hello,
    Purchase order was raised in March for over Rs 1,000,000/- and went through the Release Strategy for printing.
    The value of this order was changed today - about Rs 7,000/- was added in the purchase order.
    The Purchase Order was printed straight away without going through Release Strategy,
    In a customization we have maintained the Release strategy for the Purchase order
    Please provide the solution on this issue.
    Regards
    Sarin
    Edited by: sarin toms on Nov 26, 2008 1:57 PM

    Dear,
    Check at....OLME-->PO->Release Procedure->Configure Release procedure for PO> Release Indicator--> Pl. Check In Changebility of Release Procedure after release...here you have to give the option " 4".....and percentage of changebility also you have to take care...
    Apart from that...in OLME--> Messages--> Message output---> Message determination...you have to fine tune your message type for Change mode...
    Changeability 4 and percentage 0 will reset the release ONLY when the value of the PO increases. Any other change including decrease in value will not reset the release.
    You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
    Try with changeability 6 instead of 4. 4 will not reset the strategy if the PO is outputted (printed, emailed, etc)
    Please refer the note 662993 and  365604
    Regards,
    R.Brahmankar

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

  • ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

    Hi Guys,
    ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release  Strategy'.
    I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
    I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
    Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
    What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
    Please tell me how to select the lowest Release strategy using the CESSR structure ?
    Points will be awarded...
    Thanks
    Rahul

    Use this exit.
    MM06E005

  • What is the name of the table where Release Strategy changes are maintained

    Dear Friends,
                       Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

    Hi Chintan,
    I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
    In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
    Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
    I hope it clarifies.
    Regards
    sachin

  • 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 quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • 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

  • ME38 resets Release strategy of Scheduling agreement

    Hello,
    It seems when the users change the delivery date  in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
    I cannot understand why this happens.
    Has anyone encountered such a problem before.
    Thanks
    Sunil

    Below are the (changed) item fields :
    Purchasing Document Item Change Date   AEDAT
    Item Delivery Date   EINDT
    Schedule Line is "Fixed  "FIXKZ
    Below are the (changed) header fields :
    Release Indicator: Purchasing Document  FRGKE
    Release status  FRGZU
    Purchasing document processing state PROCSTAT
    Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on  document type level ,I am also confused on this .
      Please assist  on this

  • PO and SchdAgreem Release Strategy at Item Level

    Hello!!
    I have the request to setup a the release strategy for the PO and Schedule agreements at line item level....
    as far I know for PurReqs is possible to do that... but for PO and SAs it is only at header level...
    Do you know if is possible to do that in configuration??

    Hi,
    Release strategy for PO & SA is only at Header level, since these documents are external purchase documents.
    But, PR is internal purchase document and release strategy is possible at both item and header level.
    i think, it is not possible to do release strategy at item level for PO & SA as you said,
    Regards,
    Srinu.K

  • 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

Maybe you are looking for