Release Strategy Inconsistent

Hello Experts,
We have a release procedures configured and due to
some changes I have deleted one of the release procedure
in the system and transported to other clients. This
deletion has caused inconsistency in the system and
every time the deleted release procedure gets applied
with "Release strategy inconsistent" and system does
not show any release code or desription or status...
How do we handle this situation..I am sure some of you
might have gone thr this experience.
Your immediate help in this regards will be highly
appreciated.
Ehtesham R.Quraishi

How many change requests you have created for the release strategy deletion.
If more than one, please check the seqence of transport.
Transport the requests in sequence and then check.
Regards,
Rakesh

Similar Messages

  • Error in Release strategy : Inconsistent Characteristic Value assignment

    Hello Gurus ,
    Good Day ...
    Need your help in release strategy in purchase order .
    Thanks in advance .......
    Characteristics characteristics value
    R2R_PURCH_ORD_TYPE NB
    R2R_PURCH_GRP1 001
    R2R_PURCH_ORD_VALUE 0,00 - 1000,00 USD
    1001,00 - 2000,00 USD
    2001,00 - 10000,00 USD
    Class assigned char
    Z_CLASS R2R_PURCH_ORD_TYPE
    R2R_PURCH_GRP1
    R2R_PURCH_ORD_VALUE
    Rel grp assigned class
    PH Z_CLASS
    rel grp rel codes
    PH 1 -director/VP
    PH 2 - manager
    PH 3 - buyer
    rel grp rel strategy
    PH A1
    PH A2
    PH A3
    Now in SPRO -
    > define Release Procedures for Purchase ORder -
    > Release Strategies
    PH A1 Release Strategy 1 (rel. prereq , rel statuses, classification , rel simulation ) working fine
    PH A2 Release Strategy 2 (rel. prereq , rel statuses, classification , rel simulation )
    ERROR MSG: INCONSISTENT CHARACTERISTIC VALUE ASSIGNMENT
    DETAILS :
    You want to change the value assigned to a characteristic. However, the change causes inconsistency, so the new value is not allowed.
    The inconsistency may be for the following reasons:
    A precondition or selection condition is violated.
    The characteristic is a single-value characteristic, and different values have been set by constraints, actions, or procedures.
    In classification, inconsistencies occur when you change the value set of a characteristic if objects or classes have already been classified with values from the previous value set.
    Procedure
    Choose Inconsistencies to see what triggered the inconsistency. You can also use the explanation facility for more information.
    Delete the values that triggered the inconsistency.
    You can only change or delete a value or value set that has already been used to classify objects if you delete the existing allocations.
    PH A3 Release Strategy 3 -
    > SAME AS ABOVE
    regards,
    ajay

    Hi,
    Inconsistency  due to different "VALUE" in the Release Strategy & "VALUE" present in the Release Characteristics . Check details with value assignment with designed  Strategies.
    Also keep following VALUE Release Characteristics for  value
    <=1000,00.00 USD
    1000,00.01 USD- 2000,00 .00USD
    2000,00 .01- 10000,00.00 USD
    instead of (0,00 - 1000,00 USD,1001,00 - 2000,00 USD,2001,00 - 10000,00 USD )
    Regards,
    Biju K

  • Inconsistency for Previous Release Strategy of PO

    Dear colleagues,
    Is there any standard program to come up with new values and criteriau2019s for new release strategy if pre defined release strategy, with class, is deleted for PO approval.
    Best regards,

    Hello Metin,
    can you please elaborate your question, it is not very clear, as it is not showing the clear picture of your requirement.
    regards,
    Prashant Rathore.

  • Release strategy tab is not coming in SES

    Hi All,
    I am facing a issue where I have created an SES, and release strategy is assigned to this SES. Problem is somehow the user is not able to see the release tab when he go wants to release the SES. The release tab is missing from the SES.
      Am sure somebody has faced this kind of issue and have any idea how to correct this.
    Thanks

    Hi,
    The direct reason that there is no release icon available in ML81N           
    is inconsistency in the field ESSR-FRGRL for affected SES's.                                                                               
    This field should be filled with 'X' as all those SES are subject            
    for release.                                                                               
    Have you changed customizing for involved release strategy recently ?        
    If a relase strategy is created with a certain name and documents are          
    created with respect to it afterwards, this release strategy should be         
    changed then IF AND ONLY IF a NEW name is assigned to it as well. In           
    other words, if such a strategy is already use, it should be RENAMED           
    before applying the desired changes.                                                                               
    Otherwise you will run into the observed inconsistencies when trying to        
    edit documents which were created BEFORE the strategy was changed              
    (since the system at some point always checks the NAME of the strategy         
    to be changed, NOT the content).                                                                               
    So if this case happens only for already created SES a good solution           
    for it is to delete affected SES and create a new one with changed             
    release strategy.                                                              
    I would delete affected SES and create it again.           
    It seems to be the fastest way to resolve this issue.      
    If you need a correction for this inconsistency issue, please open a SAP ticket for your problem.
    Regards,
    Edit

  • Release strategy with classfication & w/o classfication problem

    Hello guys
    I am facing problem in setting up the release strategy .  ECC 6,0 came up default without classification. we need with classification.  i set up w/o classification, then delete it and then did with classification.. it works fine for me in the Sand Box ,  but in dev server it didn't work for me. It is working only w/o classification , When i am trying to set up with classification , it didn't work for me , i am getting the error message in the check release strategy as follows . How i can find which release group need to create ?
    Any help will be highly appreciated
    Thanks
    N
    Release code  for release group  is inconsistent
    Message no. ME_RELCHK057
    Diagnosis
    The release code  is not allowed because the associated release group  no longer exists.
    Procedure
    1. Recreate release group .
    Note
    The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group  in order to delete the release codes and release strategies.
    2. If necessary, delete the release strategies and the release codes for release group .
    3. Then delete release group .

    Hi,
    If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
    To set up a release procedure with classification, you please delete all entries in the Release codes and Release Groups for Purchasing Requisitions and start a fresh creation of new Release Codes and Release Groups.
    Hope you have followed the following procedure:
    1. Create characteristics and classes
    Note
    If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
    Otherwise, continue with step 4.
    2. Define organizational plan
    3. Assign standard tasks and activate event-receiver linkage.
    4. Set up release procedure with classification
    a) Create release group
    b) Create release code
    c) Create release indicator
    d) Create release strategy
    Note
    You need only carry out the following step if you wish to link your release procedure to workflow.
    e) Assign release code to a release point
    5. Check release strategies
    Hope, this time you will be able to perform the PR Release with Clasiification.
    Regards,
    Narayana.

  • Purchase Order - Release Startegies; Inconsistency error

    Dear all,
    I am changing our release startegy for the purchase orders. Therfore I added two characteristics:
    - Plant (Table EKKO and Field WERKS)
    - Material Number
    The problem is that I get the following error message:
    "Inconsistent characteristic value assignment"
    I only added the plant value so I do not understand why I get an inconsistency?!
    In the next step I also want to integrate the characteristic "materialnumber". Is it possible to define the value somehting like all values without 950*?
    Can anybody help me with this?
    Thank you very much.
    Best regards,
    Markus Sigl

    Dear Sasi,
    I checked the database and all parts of the strategy. There should be no inconsitency (all the codes. I still could not solve this problem, groups and so on should be ok).
    Have you got another idea?
    Thank you very much.
    Best regards,
    Markus
    Hi
    I think this may be because of inconsistency caused with tables. Kindly check all the tables related to release strategy and the entries.tables T16FK, T16FV, T16FS, T16FC and T16FG
    If you change any release strategy with fout following the sequence, the inconsistency in table will be created.
    Follow the sequence below for deletion or changes
    1. Delete the release strategies
    2. Delete the release indicators
    3. Delete the release codes
    4. Delete the release group
    5. Delete the class
    Hope this helps.
    Regards,
    Sasi

  • Error relate to PO Release Strategy

    Hi expert,
    I have a problem relate to PO release strategy. I try some of suggestions but nothing work. I hope you guy can help me to fix it.
    I have finished configuring PO Release Strategy and  Release Group is ZT with 2 release code (01, 02).
    After that i created some of other release groups and delete the first release group ZT (include release strategy). But whenever when i go to ME29N, ZT always appear in release group with it's release strategy even i already deleted it.
    Thanks for your help

    Hi,
    What procedure did you follow while deleting the release group ? The process for release group deletion should be as mentioned below.
    1. First delete the classification data for the release strategies you want to delete
    2.  Delete release strategies ( from detail view in SPRO )
    3. Then delete release codes ( including description in different languages - translation )
    5. Lastly delete release groups ( including description in different languages - translation )
    If you dont follow the above process inconsistency might be there.
    After deletion if you want to create new release groups follow the steps  in reverse  reverse order.
    1. Create Release group (  including description in different languages - translation ) Check table - T16FG
    2. Create Release Codes (  including description in different languages - translation ) - Check  table - T16FC/T16FD
    3. Create Release Strategies ( (  including description in different languages - translation ) - Check table - T16FS/T16FT
        - Assign codes to Release Strategies
    4. Maintain classification values - Tocode CL20N
    Please let me know ifyou need any further help.
    Regards
    Sayan
    Edited by: Sayan Pal on Dec 8, 2011 3:28 AM

  • PO Release Strategy error

    The following error showing up when I try to setup PO release strategy, Can someone help, please?
    I try to do the everything following error states, but no luck. I am getting all RED Lights..
    <b>Release strategy R for release group  is inconsistent
    Message no. ME_RELCHK058
    Diagnosis
    Release strategy R is not allowed because the associated release group  no longer exists.
    Procedure
    1. Re-create release group .
    Note
    The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group  in order to delete the release codes and release strategies.
    2. Delete the release strategies and release codes for release group .
    3. Then delete release group .</b>

    I tried that. Easy, but it didn't worked. Following is technical description of error
    Message Text
    Release strategy R for release group  is inconsistent
    Technical Data
    Message type__________ E (Error)
    Message class_________ ME_RELCHK (Check Customizing for Release Strategy)
    Message number________ 058
    Message variable 1____ 
    Message variable 2____ R
    Message variable 3____ 
    Message variable 4____ 
    Message Attributes
    Level of detail_______ 3 (Level of detail 3)
    Problem class_________ 
    Sort criterion________ 
    Number________________ 1

  • Verison Management with PO release strategy - CEKKO-REVNO

    Hello,
    I'm a bit stuck... I'm trying to do a PO release strategy using version management, were the PO goes through a release strategy if the PO gets changed (not the intial PO creation).. So once the field RENVO is greater then 0, it should go through R.S.
    I've read to create a characterstic CEKKO-REVNO and then assign it as a valuet <0...  I  intital;y created it with a NUM Data type, but the ABAP dictonary overides it with a CHAR instead... So I read to mark the value as a default value (<0)
    However, after I add it to my class, I go to the define release strategy - classifcation section (to add the value <0)  I'm getting  a value inconsistency check.
    How do i setup this characterstic so I can use it in release strategy?

    Based on adding 00000000 the release strategy will work when its version 0 (intial). However, I'm trying to have it so it goes through a release strategy when the version is 1 or greater...
    It seems like I cant get the strategy to work for more then one version... I can get it to work for version 0 but no others, or version 1 and no others etc...
    I need to have it some it works for anything greater then zero, in which i tried <0000000  and even >000000
    I also tried adding 000001, 000002, 0000003, 0000004 etc..  An although the release strategy tab is still applying, it will NOT result to a blocked status...
    I cant get this to work... How should the characterstic value look to get this requirement?
    Edited by: farmerj3 on Feb 20, 2012 3:16 PM
    Edited by: farmerj3 on Feb 20, 2012 3:43 PM

  • PURCHASE REQUISSITION RELEASE STRATEGY

    Dear All SAP Guru,
    I have created purchase requisition release strategy in quality same as in devlopment(testing).In testing it is flowing correctly, but in quality when i created pr it is not added to release strategy.I checked everything characterstics, class, release startegy and found that it is very similar with testing client.I doesnot know where is problem.
    Please suggest me solution
    Thanks and regards
    Mahesh Lotake

    Dear Mahesh Lotake,
    Sometime when you transport the DEV to QAS, you may missing the assignment value
    if you have not do it correctly. However you still can fill in the value manually. This
    can be done at CL24N -> and click the "Value of assignment" button. Also, make
    sure the status = 1(Active).
    You also need to check if any red trafic light to make sure you have no inconsistency.
    Execute the transaction OMGQCK or OMGSCK and ensure that the system does
    not show any red traffic lights.
    Best Regards,
    Ian Wong

  • PO release strategy - release code

    Hi Experts,
    I have completed the release strategy and transported to production.
    However noticed that the release codes that has been configured earlier wasn't in the production.
    Is there a way to update the release codes in the production besides using SPRO (no authorisation for maintaining - only display) like using CL24N to update the characteristics?
    Thanks and regards

    Hi,
    Please first check the attached notes that refer to transport issues.
      365604   FAQ: Release strategies in purchasing
      186809   OMGQ/CL24: Inconsistency for release strategy class
       86900   Transport of Release strategies (OMGQ,OMGS)
       45951   Transporting class data: system / client
       10745   Copying classification data to another client
    The classification data must be sent over using ALE. It does not get
    transported directly.  Notes 45951, 86900 and note 365604 should help.
    Please follow the instructions in note 45951.
    You can obtain more information about how to set-up ALE in the Online
    Documentation CD (R/3 Library > CA - Cross Aplication Components >
    Business Framework Architecture > ALE Integration Technology > ALE Quick
    start).
    However, if you can't set-up ALE, you can re-create the classification
    data agin in your target system. For that you have to:
      1- assign new values to the characteristic master data (t-code CT02)
      2- assign the new data to the classification system (t-code CL30)
      3- verify the consistency with t-code CL24. Please see note 186809.
    For more information, please see note 365604.
    The transport of release procedure customizing data can only be done
    in a restricted manner. Please take a look at attached Note 86900 and
    follow the procedure described in this note, in order to correctly
    transport your release strategies.
    Classification data can only be transported via ALE as per note 45951.
    Note 45951 explains what class data for the release strategy will be
    distributed from one system to another. It does not describe how to
    implement as this involves a lot of explanation and is truely a
    consulting issue.
    There is another possibility that you could take into consideration for
    the classification is to import them via batch input:
    RCCTBI01 for creating characteristics
    RCCLBi01 for creating classes
    RCCLBI03 for classification
    Best Regards,
    Arminda Jack

  • PR Release Strategy tab processor field is not getting displayed

    Hi Experts,
    While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
    SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
    release strategy - Release code  -work flow 1
    That processer name is not displaying
    Thanks
    chandoo

    This is the workflow forum.

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 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.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

    Hello everyone,
    I've run into an interesting problem:
    We have defined several PO release strategies.  Most of these work in the traditional manner, requiring manual approval by a given user.  One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
    We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
    If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
    If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
    What would cause this discrepancy?  The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
    Thank you ahead of time for your help.
    -Jarrod

    Configuration issue/user error.

Maybe you are looking for