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

Similar Messages

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

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

  • Release Strategy - Object "ZX NX" already classified with same characterist

    Hi Gurus
    While modifiying the exist release strategy the following error occurs.
    Object "ZX NX" already classified with same characteristic values
    Message no. C1818
    Diagnosis
    Object ZX NX was already classified with the same characteristic values. In class maintenance, you define whether a warning message or error message is displayed in these circumstances. This message draws your attention to the possibility of data redundancy.
    Procedure
    Change the assigned characteristic values, so that you do not have redundancy in your system.
    Perhaps the object you are classifying is not necessary, because it can be replaced by the object found by the system.
    Please advice on this.
    Thanks in advance
    ARAS

    Hi
    Thanks for your input. I will test this and come back.
    Experts, any further inputs...
    Regards
    Aras

  • HR organisation Structuer Link with PR release Strategy

    Dear Gurus,
    As per our organisation, once the PR is created, it has go to  the Cost Center Owner and it has to follow the HR organization structure. we have 200 Cost centers in different departments.
    Please help me how to configure this with HR organization structure
    Your help is most appreciated and Full point will be rewarded.
    Thanks
    RS

    Neetu,
    Hi Neetu,
    My Release strategy working fine and nothing wrong with it. My question is, why only NB type is falling for Rel Strategy. I think I found answer from Rosa's Answer. If you check overall release at Document Type, then that document type falls for Release Strategy.
    Thanks all. I am closing this with Answered and points goes to Rosa...

  • Purchase Order Release Strategy Approval

    HI All,
    I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
    Level one will have 1 approver
    Level two must have two approvers.
    The scene is:
    Level one will approve all purchase orders betwee 400 to 5000 euros.  1 approver only
    Level two will approve all purchase orders above 5000 euros.  2 approvers.
    The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
    Pur. group G70, Release Group GC and release strategy DF.
    I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
    CL20N is completed for both levels and works correctly for level one approval but not for level two
    Can any please help
    Leslie

    Hi,
    May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
    1. PO Order Type (ZPO_BSART),
    2. Company Code (ZPO_ BUKRS),
    3. Purchasing Organization (ZPO_EKORG),
    4.Plant (ZPO_WERKS)
    5. Purchasing Group (ZPO_ EKGRP) and
    6. Total net PO Value (ZPO_GNETW)
    Create one release class ZPO_CLASS & then add all above release characteristics
    And then design your release strategies as required.
    AND under release characteristic for PO Value (ZPO_GNETW) keep following values
    A. <= 400 EUR
    B. 400.01- 5000 EUR
    C. >5000 EUR
    As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
    NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
    In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
    Regards,
    Bijju K

  • Relase strategy characteristic with several material groups

    Dear Experts,
    Actually I'm implementing the MM Module, 6.00 version and I have the following issue:
    I created the release strategy Purchase Order, with these characteristics:
    - Material group
    - Net total purchase order
    - Plant
    The error consists in the Material Group characteristic don't run with several Material Groups. It seems that it could be possible only with one Material Group.
    If you know how I could work the characteristics with several material groups, pleas tell me.
    Thanks in Advance,
    Adriana Corredor
    MM SAP Consultant

    Hello, Adriana,
    it isn't clear what you mean by "characteristic don't run with several Material Groups":
    - is it that you cannot enter multiple values in classification? Then check whether you chosed "Multiple Values" in "Value assignment" subscreen of characteristics maintenance, transaction CT04;
    - is it that your release strategy isn't assigned to PREQ with several items with different MATKL values? It is neccessary to realize that if you use the coverall release of PREQ (which I guess you are using), the values of items has to be "summarized" (for purpose of release strategy assignment) into structure CEBAN "Communication Release Strategy Determination: Requisition"; the release strategy classification are then evaluated against this structure; if there is any field which differs for items, it is passed to structure CEBAN as empty; so either you have to have release strategy with MATKL empty, or you can modify the CEBAN content by enhancement M06B0001 "Changes to communication structure for release of requisitions", or you can prevent creation of PREQ with certain not-allowed combination of MATKL via user-exit or badi;
    Kind Regards
    TomT

  • Requisition without release strategy

    Hello everybody
    Is it possible to block create purchase orders with reference to requisition without release strategy?
    Example:
    1. Purchase Requisition 100887 with release strategy R1 <> Purchase Order 300 created with reference to PR 100
    2. Purchase Requisition 100888 without release strategy <> Purchase Order cannot be created.
    Thank you for help in advance
    Arek

    Hi,
    If you have seperate document type for PR's for release strategy
    You can remove the link of PR document types to purchase order document types
    other than release startegy in
    Purchase order document type customizing spro>mm>purchasing>PO>define doc types>link to PR
    this will not allow PO's to be created without Pr's having release strategy
    BR
    Diwakar
    reward if useful

  • 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

  • Release Strategy Error

    Hi All, 
    We are in Classic scenario and for the PO in backend we have applied Release Strategy. However, for the PO with approval we are getting error as per the below screenshot. Could you please let me know the possible reason?
    Thanks,
    Sunil

    Hello Sunil,
    click onto the hyper-link from step in error to get error details.
    Regards.
    Laurent.

  • Purchase requisition release strategy tab missing

    Hi all
    I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

    hi,
    check few reasons:
    1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
    2. check the release strategy OMGSCK, is there any problem with your release strategy...
    3. Check whether you have maintained all the classified field in the document or not..
    4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
    regards
    Priyanka.P

  • Transportation of release strategy

    Hi guys,
    We heard that in ECC 6.0, we can transport release strategy for PRs and POs along with characteristics and classes.  I have the following doubts on this
    1) Can we transport the values assigned in the strategies also with this functionality ?
    2) From MM side can we configure the strategies in the normal way i.e. creating characteristics, creating classes, creating release groups, creating release indicators, configuring release strategies (or) we need to follow any other procedure for transporting the strategies
    Any suggestions on this

    Hi
    I dont think this functionality exits of transporting the charcterisitcs & classes.
    In ECC 6.0 also this functionality does not exist as per my knowledge.
    Jurgen Thank you for the SAP note
    Thanks & Regards
    Kishore

  • Purchase requisition  - release strategy statistic

    Anyone knows if exists a standard program/tr/utility for monitoring the use of release strategies
    for purchase requisitions ?
    In our system there are a lot of release strategies obsolete or used for few cases, so
    we would check the effective use of release strategies.
    Regards.
    Riccardo Galli

    hi,
    check few reasons:
    1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
    2. check the release strategy OMGSCK, is there any problem with your release strategy...
    3. Check whether you have maintained all the classified field in the document or not..
    4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
    regards
    Priyanka.P

  • Error in Release strategy

    Hi,
    If I assign the following in a Class, the release strategy is trigger in the PRS with out any enty of the given objects in the Class.
    Purchase Requisitioner
    Plant
    Value
    Pl help me out

    Hi
    Check on it:-
    http://www.sap-basis-abap.com/sapmo017.htm
    http://www.sap.com/services/pdf/BWP_WP_Release_Strategy.pdf
    http://sapdocs.info/wp-content/uploads/2009/07/PR-Release-Strategy-Guide-a-case-study-Free.pdf
    http://www.google.co.in/url?sa=t&source=web&cd=13&ved=0CB8QFjACOAo&url=http%3A%2F%2Fwww.sdm-c.com%2Ffiles%2FBarcelona_Mazliach_Automate_Your_Purchasing.ppt&rct=j&q=sap-Release+strategy&ei=6IAYTJ2DHJi80gTx7JS_Cw&usg=AFQjCNGi6UQkRdPdIeVmt7mqSiwZr04-Sw&sig2=rJsnJKRW-_8CQebhDq66Tw
    pherasath

Maybe you are looking for