New release strategie determination

Good morning,
I have a release strategie determination to purchase orders that works fine and in case of change of value a new strategie is determined.
However if I change another field that do not affect the total value (like material number field) the strategie don't reset and the document is not available to release again.
It is possible to do a new strategie determination if any field of the purchase order is changed?
Thanks for any reply.

Hello Sandrina Teresa Da Silva Dias,
I know it seems so crazy but
In this user exit or any other one you can not do this maybe. But  there is a new idea..
1-) You can add a new field (or indicator named changing flag ) to your PO by MM06E005 user exit.
2-) You can fill this field "if there were any change documents for this PO after it's creation date." via a user exit or BadI in PO.
3-) Then add this field to your characteristics. You should put it into cekko using M06E0004
I hope it helps...

Similar Messages

  • Create new characteristics for existing release strategies

    Dear experts,
    Whenever I have a roll-out, I have to create a new characteristic that is the purchase order value in local currency, that is to be assigned to the class used for the Release Strategies of purchase orders.
    The problem is that whenever I do this, all the existing release strategies have an additional characteristic to be maintained. Since I have more than 1.500 release strategies, I have to go through each one of them and except for the new release strategies, put >= zero in this new characteristic.
    Is there any way, that whenever I create this new characteristics, I can define a default value that will be assigned to every existing release strategies in the system?
    I've tried to use the default value, but it only works when I'm introducing the characteristics values for the first time in the release strategies.
    Any ideas?
    Thanks.

    Hi,
    You can try LSMW (Direct method) for uploading class values.
    Upload file can hae following structure:
    OBJEK     |     ATINN     |     KLART     |     ATWRT
    Release Grou+Release strategy |     Characteristic name     |     Class type     |     Class Value
    e.g. rel grp is PO, rel strategy is 01, characteristic name is EBAN_EKORG, and class value is 1000 then
    OBJEK     |     ATINN     |     KLART     |     ATWRT
    PO01     |     EBAN_EKORG |     032     |     1000
    multiple characterstics can be
    OBJEK     |     ATINN     |     KLART     |     ATWRT
    PO01     |     EBAN_EKORG |     032     |     1000
    PO01     |     EBAN_EKGRP |     032     |     100
    Regards,
    Yogesh

  • Pr& po -new release strategy?

    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

    Hi,
    First of all, if you would only like to create the new release strategies, then the only possible settings you should do are -
    1)   Create the new release code;
    2)   Create the new release strategy;
    3)   Assign the release characteristics values to your new release strategy in CL20N transaction.
    For those old PRs and POs (regardless of if they were released or pending for release), the same old release strategy remains unchanged (and therefore, you should be much careful if you wish to delete the outstanding release codes and/or release strategies through configuration).  Having said that if you would like to keep the same release strategy though changes are to be made to your old purchasing documents, then you will have to assign the proper value to the "Changeability" field of your "released" release indicator.
    In case of release strategy in support by workflow, basically, the workflow item will be triggered (in accordance with the pre-defined logics that you built in terms of task ID).  As soon as the approver determination is made in background, the workflow item will be then sent to such agent who will then take a proper decision (approve, reject or forward).
    Cheers,
    HT

  • Pr& po -new release strategy? released/locked/incomplete

    Dear MM experts,
    I would like to understand what it is meaning of
    released
    locked
    incomplete
    while doing assignment of object class thru cl24n for new release strategies,
    I am clear on released & locked, I would like to understand what is "incomplete" means as per SAP.
    kindly clarify
    thanks in advance
    srihari

    Incomplete means - When you go to CL02 or CT04
    you are entering the statu for calss or char as locked or released
    but when you are creating and that time if you have keep the status is in preparation  and without changing the status you start maintainig the data in CL24N than you will see the statu as incomplete.

  • Release Strategies in Purchase Order - possible values of caracteristics

    Hello,
    I have the following situation at hand.
    We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
    Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
    I can not change the caracteristics in the Release strateg because this would affect the already working strategies  and SAP does not allow to asign another Class to the PO release groups.
    Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
    Can I use something generic in the caracteristics field of the strategy?
    Thanks for any help. It would save me a lot of time!
    Aart

    Note 493900 - FAQ: Release Strategy
    1. Question :
    Why is the release strategy not determined?
    Answer :
    Please check the following points :
    You can not use Release without classification and Release with classification.
    If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
    If you use version management, the determination of the release strategy starts when the version is completed.
    You complete a version by setting the "version completed" indicator in the version tab.
    Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
    This is true for the other structures as well (CEKKO and CESSR). See note 52225.
    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 as one of your characteristics. If all items do not belong to the same plant 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. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

  • Purchase Order Release Strategies for Changed Amount

    Hi Gurus,
    We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
    Example: Configuration is PO total amount <$5K requires only L1 approval.  PO total amount >$5K requires L1 and L2 approval.  PO was created for $8K and was release using L1 and L2 approvals.  Receipts were posted to PO in the amount of $7K.  Now the buyer has added an additional line item for $1K.  The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item).  Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
    Has anyone done this before?  Any ideas??
    Thanks,
    Gabe

    from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
    User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
    This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
    The following user fields are available:
    USRC1
    USRC2
    USRN1
    USRN2
    In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

  • 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

  • PO release strategies with Contract

    Hi,
    implementing a PO release strategy (SAP-MM module)I need to consider the case in which a PO is assigned to a Contract.
    If so, different release strategies should be selected according to the PO value.
    Possible cases:
    S0-strategy 0: Contract does not exist, PO value>=0eur
    S1-strategy 1: Contract exists, PO value>=100eur
    S2-strategy 2: Contract exists, PO value>=200eur
    Is someone aware if it is possible to activate such release strategy without defining manually in the characteristic for CEKKO-KONNR field all possible contract single values (entire range)?
    Thanks a lot for helping!
    Regards,
    Elisabetta Rizza
    Please contact me at following mail addresses:
    [email protected]
    [email protected]
    Hi Elisabetta,
    I've moved this here because it is a more appropriate thread.  BPX is the place for discussing the role of the buisness process expert.  This is a MM question
    Message was edited by: Marilyn Pratt

    Dear Amit,
    Requirement: If GR posting date exceeded 45 days than delivery date set in PO, then delivery date in PO has to be changed to current system date and at the same time New Release Strategy (B1) has to be triggered with one release code (02) automatically.
    So in that case the values in Release Strategy (A1) and (B1) would remain same,,, as you suggested we will assign the value 01 u2013 USRC1 to Rel Strategy (A1) and 02 u2013 USRC1 to Rel Strategy (B1) and the same we will try to incorporate in the coding of Exit u2018'M06E0004'
    We will check the process and confirm the same.
    Thanks for your suggestion.
    regards,
    Urendra Kumar

  • Error while creating new release groups in PO release strategy

    Hi All
    I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
    But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
    Thanks for your support.
    Illan

    Dear,
    Please follow below mention path.
    *and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
    *- Follow below mention path.*
    *SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
    *Three steps involved in release process of purchase order.*
    **Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
    **Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
    *Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
    Now see each steps of Define release procedure of purchase order in briefly: -
    Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
    Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
    *Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
    Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
    Regards,
    Mahesh Wagh

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

  • Are these requisition release strategies common?

    All,
    I’m designing new requisition release strategies for indirect requisitions at a chemical industry client.  I’d like to know how often you have seen the following sorts of design before:
    Existing design: Item-based release with workflow, with three dollar levels.  At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic).  Characteristics assign several cost centers to each approver.  Strategies and codes are named for users, so we change configuration whenever someone changes jobs.  The codes are linked to positions, which are attached to user IDs.  Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
    Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic.  A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
    Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase.  I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
    Thanks for your help!

    Hi,
    No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
    In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
    Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
    The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
    Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
    For more refer a discussion:
    PR release: place holder for Cost center and Material grp
    NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
    You can also go for other concept designing of your Requisition release strategies
    Regards,
    Biju K

  • Purchase requisition : problem with check release Strategies

    Hi all,
    i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
    But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
    Is there a special value to give the release indicator 'released' ?
    Thanks for your help.
    Edited by: ToraTora on Mar 31, 2011 5:46 PM

    Hi,
    Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
    select release indicator
    by default, you will be having the following release indicators in the system,
    1     Request for quotation
    2     RFQ/purchase order
    3     RFQ/PO no change of date
    4     RFQ/PO no changes
    A     Fixed RFQ
    B     Fixed RFQ/purchase order
    X     Blocked
    please check whether you have got these or else create and then assign them to the release strategies.

  • Tables for Release strategies

    Hi ...
    I was referring to MM table doc , in that it is mentioned table EBELN & EBELP are for Purchase Order header / Line and BANFN & BNFPO are for PR header/ Line.
    But for release strategy ...people told me to refer CEKKO for PO and CEBAN for PR.
    does it mean that release strategy refers to different tables for execution ( and I believe these tables are used for release strategy purpose only and if Yes then at what point PO / PR data gets updated in these tables)
    Regards
    Suresh

    Hi,
    Please find release tables used in MM.
    EKAB       Release Documentation 
    EKEH        Scheduling Agreement Release Documentation 
    EKEK        Header Data for Scheduling Agreement Releases 
    T161E       Release Codes 
    T161F       Release Point Assignment for Purchase Requisition
    T161G       Release Prerequisite, Purchase Requisition 
    T161H       Fields for Release Procedure, Purchase Requisitio
    T161I        Determination of Release Strategy 
    T161S       Release Indicator, Purchase Requisition 
    T161U      Texts for Release Indicator 
    T163P        Release Creation Profile 
    T163S        Description for Release Creation Profile 
    T16FB        Release Indicators: Purchasing Document 
    T16FC        Release Codes 
    T16FD        Description of Release Codes 
    T16FE        Descriptions of Release Indicators: Purchasing Do 
    T16FG        Release Groups 
    T16FH        Descriptions of Release Groups 
    T16FK        Release Statuses 
    T16FS        Release Strategies 
    I think, it will help u.
    Ishu

  • 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

  • Restrcuturing of PR and PO release strategies - corporate policies

    Hello,
    I´m in a proyect where a multinational company wants to restructure its PR and PO release strategies.
    We are in the fase of defining corporate policies as guidelines for the new structure.
    The multinational Holding contains Productive companies, distribution companies and other type of companies like investigation companies.
    I would like to have some feedback about how to guide the company management in this process off defining corporate policies.
    How does one or can one estandardize the release levels, release codes and amounts which separate the levels, in a diverse multinational.
    Are there any paradigmas, methods to acomplish this.?
    If anyone has experience with these kind of processes, please give me some feedback on how they tackled these issues.
    Thanks,
    Aart

    Hi,
    Normally when a company is coming into the sap , which have many business at various locations / countries , a structure will be defined in the SAP for the company as company code under which the plant and below the structure will be defined .
    However when comes to purchasing and for PRs POs , SAP give a communication strusture called CBAN for PRs and CEKKO for POs which can be viewed at SE16 . Thease tables contains the fields upon which the release strategies can be made .
    For example , say for one of your productive company , the company code created is XXXX and the plant under which is YYYY say , the policy can be for a groups of buyers which comes under the plant for a PO level , who can be the approver . Here for differrant PO/PR values differrant approvers can be added as strategies and based upon which the approval can be happened . and the approvers be the release codes .
    There are no standard paradisms rather , prior come into purchasing the organization structure be made.
    After that based upon the business/product , with in that company code defined , the levels can be defined in that perticular business .for purchases .
    In purchasing , to fhe plant / purchase group / storage location etc plays important and normally for a set of buyers/p grps , in that plant or group of plants in that company code , the levels of the PO/PR values can be defined for differrant strategies .
    Once at corporate level , the company code / plant is defined and under that the release strategy is easy to define .
    Regards,

Maybe you are looking for

  • Flash won't update for Firefox (works in IE)

    ok ok, im not the greatest when it comes to stuff like this, but here's my problem listening to music on myspace isn't really my #1 concern when getting on the computer, but adobe hasnt been updated for SO long now that it's getting old ive installed

  • Really ticked off:

    I got a used Samsung SCH-U750 phone in the spring, I upgraded to unlimited data -- as the phone REQUIRES a data plan.  This phone was just a place-holder until an Android phone I liked came out.  Now that the Nexus is available, I went to the Verizon

  • Slow load + Can't save

    Hi all, I am working on my first Premiere Pro project after switching from FCP (so I am new to the software). The project was going great until this morning when everything started slowing down. First the Auto Save started taking longer. I tried a re

  • Problem with jasper. Help needed urgently!

    Hi everybody. I'm trying to run jasper reports in a new web applicattion i've done. The problem is that the jasper runs perfectly in my pc i've developed the apllicattion but it doesn't work in the server. The error message that I show is: [Error de

  • PL-SQL mass update help.

    I want to do a mass update with PL-SQL on a table with different values using one SQL QUERY. Here is the table and some sample records USER_TABLE USER_ID | ACCOUNT_ID | ROLE | CREATED_TIMESTAMP | 101 | 999 | ADM | 01/20/2009 102 | 999 | SUB | 01/20/2