PR Release Strategy Characteristic Changes

I created several characteristics for a purchase req. release strategy. I added an incorrect value and then deleted it on one of the characteristics. Is there anything else that needs to be done to ensure that value is really deleted?
I'm receiveing an error when I ALE that I have documents that won't post for the error:
REQ_PURCH_ORG : Value "Structure Exists " not found
Structure exists is not a value associated with this characteristic.

Thanks for the solution that helped me to understand PR Release much better.
Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
In my PR Release strategy with 2 levels I have these below things:
Rel Groups : 1 Group with name AA
Rel Codes: For AA is A1, For another AA is A2.
Rel Indicator: nothing is selected, am not sure what to do in this step.
Rel Strategy : For AA is S1, For another AA is S2.
I created class Z_GFWRT but am not sure which group I should assign  it AA or I have to create another new group for Overall release.
After I checked the release strategy the system is giving me this below message.
No release group exists
Message no. ME_RELCHK014
Please can you walkme through in this process. This is first time I am creating a PR Release.
Thank you Very Much
Imraan

Similar Messages

  • PO Release Strategy not changed after deletion of few line items with less

    Subject : PO Release Strategy not changed after deletion of few line items with less Total PO
    Dear Friends
    We have issue with PO Release strategy. We have created the PO. with release strategy  with multiple approvers.  After approval of first approval manager , one of the PO line item got deleted and Total PO value is reduced . The new PO value should have changed the PO release strategy. But it is not changed. Old release strategy only showing in the PO which is wrong. 
    Details of the PO
    PO no 4500000123 with 5 line items Total PO value : 100,000 USD Release strategy : AB
    PO line item 5 deleted. Now total PO value changed to 50,000 USD and the PO release strategy should have been changed to AA but not changed. Still showing PO release strategy AB only.
    Are there any OSS notes available to correct his bug.
    Please let me know if you need more details
    Thanks in Advance
    Thanks
    MVS

    Hi,
    release indicators  change it to 4.It may works. Please explore to all 6 indicators..........
    i.e,
    1-cannot be changed
    2-changable,no new determination of strategy
    3-changable,new release in case of strategy
    4-changable,new release in case of strategy or value change
    5-changable,new release if new strategy/outputted
    6-changable,new release if new strategy or value changed/ outputted......
    And check   Characteristic description and value in Classification  of Release strategies ........
    I hope this will help you. Thanking you.
    Regards,
    Venkat.

  • Release Strategy Characteristic Upload through LSMW.

    Release Strategy Characteristic Upload through LSMW.
    Introduction:
    In case of Purchase order, we need to maintain Release Strategy each year. This is due to organizational changes. Due to huge organization, this is around one week activity for us. Reason, we need to maintain characteristics for around 300 different release strategies. Since, we can't transport "Characteristics" from one system to other, we need to maintain them in Quality as well as in Production system.
    Issue: We tried to use option of LSMW to maintain these "Characteristics". But, system is giving error as "Logical Path is not available".
    Question: Who is responsible to create this "Logical Path" and where it can be done?

    Hi,
    I think you moved LSMW from test to production and this might be happening due to this fact. Please redo steps in LSMW for:
    Specify Files
    Assign Files
    Read Data
    Create completely new paths, and allow system to recreate (you need the right authorization). This might help I hope.
    Regards,
    Tomek

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

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

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

  • PR release strategy-characteristic values

    Hi All
    Is there any data base table in which Release strategy characteristic values are stored.
    Gobinathan G

    Hi Gobinathan,
    Go through the following link for complete procedure for PR Release.
    http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
    Check table CAWN.
    Regards,
    Nani.

  • PR Release Strategy-Characteristic Z_GSWRT must be linked with CEBAN-GFWRT

    Dear Experts,
    I did a simple config for PR Release strategy. using Plant(Z_WERKS) and Item values(Z_GSWRT )
    chose overall PR Release. During simulate release
    the second level release its not able to simulate and it says check Prerequistie for second level
    Can somebody expain why the system is giving me this below message.
    Characteristic Z_GSWRT must be linked with CEBAN-GFWRT
    Message no. ME_RELCHK056
    Thank you
    Imraan

    Thanks for the solution that helped me to understand PR Release much better.
    Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
    In my PR Release strategy with 2 levels I have these below things:
    Rel Groups : 1 Group with name AA
    Rel Codes: For AA is A1, For another AA is A2.
    Rel Indicator: nothing is selected, am not sure what to do in this step.
    Rel Strategy : For AA is S1, For another AA is S2.
    I created class Z_GFWRT but am not sure which group I should assign  it AA or I have to create another new group for Overall release.
    After I checked the release strategy the system is giving me this below message.
    No release group exists
    Message no. ME_RELCHK014
    Please can you walkme through in this process. This is first time I am creating a PR Release.
    Thank you Very Much
    Imraan

  • PO release strategy for changes in price ($ and %)

    Hello,
    I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
    I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %.  I will need to calculate the difference in the total value between the original PO and the changed PO. 
    Example:
    Original PO total net value is $1000
    PO after a price change - total net value is $1500
    Total net value has increased by $500 or 50%.
    Tolerance for price change is $200 or $20, so tolerance has been exceeded.
    I know I will be using the total net order value (CEKKO-GNETW).  I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table.  I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not.  I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
    What I don't know is where will I find the previous total net order value once the PO has been changed?  Is the only place that information is stored in the change logs?  If so, what is the change log table name?  Or is there a different table that would contain this information?
    Thanks in advance for any help you can provide.
    Sincerely,
    Angela

    Update:
    I utilized function module EXIT_SAPLEBND_002 as a solution to this.  I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
    I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
    I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

  • Changing release strategy - PR change history

    Hello,
    I have following situation.
    I changed release strategy for PR by adding one new release level.
    The change effected unreleased PR's and of course new strategy is valid for new PR's. This is ok.
    But, the problem is that I lost change history for PR's from the past. There is no change history log for items from old PR's. Also, tables cdhdr and cdpos lost change information, these tables are empty for old PR's after inserting changed release strategy.
    Do you know how can I add new level in release strategy without losing PR change history?
    br
    Dragan

    Hi,
    Are you sure the change log was deleted due to new release effected in PR?
    Does the change log was certain fields for PR.
    Do refer the below KBA, which explains the change that there is no change log updated for certain fields.
    KBA : 1895575 - ME5*N/ME2*N : No change log for certain fields

  • Purchase Requisition Release Strategy not to run when change to PGrp

    We have buyers that are required to change the purchasing group on the purchase requisition before a PO is created.  We would like to allow them to do this without triggering the release strategy.  Any ideas??  Thanks.

    release strategy will change only in the case if you cahnge value or oquntity other wise it will not retrggering.
    If you change the Purcvhase group system will not tregger the release
    let me know if oyu have any other problems

  • 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

  • Release Strategy - question about requisitioner??

    Hello,
    I have set up a release strategy for my PR based also on the requisitioner (CEBAN/AFNAM).
    If specific requisitioners (listed into my characteristic RELEASE_REQUISITIONER) create a PR, the PR should be released before creating the PO.
    BUT if an other requisitioner who creates a PR doesn't belong to my release strategy, this requisitioner is allowed to create this PR without any release procedure behind it, and then he's free to create the PO.
    How can I avoid this ?
    How can I say to my characteristic to take in charge ALL requisitionner (I tried with * or xxxx or... but however I don't know if there is a specific word to say "all").
    Thank you for your help...
    François.

    Unfortunatelly this is not the case.
    On the PR, when I change the requisitioner with one who doen't belong to the defined release strategy, the release strategy tab disapears from the PR and I get this warning "Requisition not subject any release strategy following changes"
    The PR is automatically ready for PO....
    In fact I would like to work like this:
    If requisitioner is AAA or BBB, work with release strategy X
    For all other requisitioner from my company, work with release strategy Y
    But this is "all other requisitioner" I cannot translate to my release strategy...
    Thank you for your help

  • User  exit for release strategy

    Dear Sappers
    I want to reset the release strategy after change in price field for PO or Scheduling agreement .( When the price less than the ex-price then PO never goes to release )
    For this, We have to required the user exit can u please tell me which user exit is suitable for this.
    Or
    Any other solution .
    Thanks
    Prashant

    Hi
    User exits avialbale are
    M06E0004
    Changes to communication structure for release of purchasing document
    M06E0005
    Role determination for release of purchasing documents
    You can use the user exits & change your RS determination & role determination
    Thanks & Regards
    Kishore

  • New release strategy / Old PReqs

    Hi,
    New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
    But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
    Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
    Many thanks in advance for your clues.
    Regards,
    Grzegorz

    Hi,
    Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

  • 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

  • User exit for Release Strategy in PM Work Order

    Dear all,
    Please help me with the following issue:
    My client want to change the approval route of the release strategy of the Work Order. The release is based on the PM Activity Type. Now, I am brand new on the project, I have no documentation and I have no access to CMOD so I don't know where to find the cusomised release strategy for change it.
    Please, can you advise on this?
    Thank you very much.
    Sorin

    Dear,
    to have release strategy based on "PM ACTIVITY TYPE", i suggest you two ways
    Option-1:
    1) Have permit system with classification as per the approval hierarchy.Create permits as per approval levels.
    2) Once maintenance order is created, system will assign the permits to that maintenance order at the time of saving.
    3) Now approvers will approve the permit with respect to Maintenance order PM activity type.
    Note: If your client wants to have mailing functionality to their out look or other mails, put logic in save exit after assignment of permits to maintenance order, with the help of ABAPER and also the sequence of approving the permits.
    Option-2:
    1) Create user status profile as per approval hierarchy with number assignment.
    2) Create "Authorization code" for the user status number.
    3) Provide "Authorization code" to the SAP user ids as per approval hierarchy.
    or
    If you have only one app rover, provide authorization of creating order to one user  and "Releasing" the order to other user.
    Regards,
    pardhu

Maybe you are looking for