Release strategy  Assign objects to class (CL20N)

Hi,
I am entering values for characteristics for release strategy in CL20N Transaction,
For purchasing group (characteristic) I need to enter all the purchasing groups in values. (Around 50 purchasing groups).
Now the requirement is user cannot able to enter purchasing groups every time in value (CL20N) so he need to enter asterisk "*" which should applicable to all purchasing groups.
For example: characterstics is Purchasing group and values are 001,002,003,....etc.
if we enter "*"  u2018(Asterisk).   Is that applicable for all purchasing groups?
Asterisk will allow in values?
If not what is the solution if any new purchasing groups used in PO it should trigger release strategy.
Please any expert gives solution for above issue.
Regards
Kumar

Hi,
Just like Sai mentioned its better to remove the Pur Grp from the Characteristics Value rather than entering all of them.
I would suggest to check if you have some additional Characteristics that would qualify to prevent Release Strategy from not populating on those documents example doc type or company code or item category or account assignment category.
Hope this helps.
Thx
MJ

Similar Messages

  • Assign Object to class with characteristic values ?

    Hi All,
    I want to assign object to class with characteristic values. I found CL20N transaction for performing the same. Is there any BDC , BAPI to upload the same.
    Thanks & Regards,
    Navneeth K.

    Hi,
    try as below
        CALL FUNCTION 'CLAF_CLASSIFICATION_OF_OBJECTS'
          EXPORTING
            classtext            = 'X'
            classtype            = w_classtype  "Class type
            language             = sy-langu
            object               = w_object     "Object Matnr + Batch
            objecttable          = 'MARA'     "As requirement
            change_service_clf   = 'X'
            inherited_char       = ' '
            change_number        = ' '
          TABLES
            t_class              = t_class
            t_objectdata         = t_objectdata
            i_sel_characteristic = i_sel_characteristic
            t_no_auth_charact    = t_no_auth_charact.
        IF sy-subrc <> 0.
        ENDIF.
    *     Create with reference-----------------------
          w_objectkeynew = wa_inputfile-to_matnr.
          CALL FUNCTION 'BAPI_OBJCL_CREATE'
            EXPORTING
              objectkeynew    = w_objectkeynew
              objecttablenew  = 'MARA'
              classnumnew     = w_classnum
              classtypenew    = w_classtype
            TABLES
              allocvaluesnum  = t_allocvaluesnum
              allocvalueschar = t_allocvalueschar
              allocvaluescurr = t_allocvaluescurr
              return          = t_lreturn.
    "or
    BAPI_OBJCL_CHANGE              Classification BAPI: Change Assignment
    Prabhudas

  • PR Release Strategy- transport of charact/class/ values using ALE

    Does anyone have the information relative to ALE set up for release strategy-
    I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
    I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
    This will be a great help.
    Thanks
    Raj

    Hi Raj,
    Please check the below notes for more inrofmation:
      86900 -  Transport of Release strategies (OMGQ,OMGS)
      799345    Transport of release strategy disabled
      10745     Copying classification data to another client
      45951     Transporting class data: system / client. - has details of what you are looking for.
    Hope this helps.
    Regards,
    Ashwini.

  • Assign Object to Class Type 026

    Dear Gurus,
    How can I assign objects to 026 type class ? because I tried CL2* transactions and all disallow me from accessing this 026 type class.
    Thank you.
    Best Regards,
    Kent.S

    Hi Kent,
    Class 026 is a reserved class for goods group ... look at Transaction WG21-Environment for hierarchy (we have a german system, so i don't know the correct items in the english menue).
    Best regards,
    Volker

  • Wrong release strategy assigned for a PM work order

    Hi
    Would like to seek your inputs on this.
    I have created a work order that has a settlement rule for a WBS element. I then created a material, RELEASE the work order then SAVE.
    I found out when going back inside the work order that the PR number generated was having a different release strategy, which is not appropriate for the approval.
    The only time when you can fix the issue is when you do a change on the work order or you have to create the order, save, then open again the work order then release it, and save.
    Have you had this same scenario? Can you please share any suggestion to address this issue?

    Hi Nazarene
    You may need to give us a background of how your organization have set up the release strategies. Some organization uses User Exits or Work Centers to set up release strategies. Either your work order is not picking the correct work Centre or if the work center is new you have to change the work order (IW32) and save it to pick the correct release strategy. 
    Alternatively you may need to check your workflow and the release limits.
    Regards
    Gibson

  • Why PO is automatically assigned with release strategy?

    I created a PO with PO document type NB and NB is not assigned with any release strategy.
    But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO.  Why?
    And only when the PO is in held status, there is no release strategy assigned to NB PO.
    Is the normal ERP behavior?
    I only assigned a release strategy to PO document type DB, which means dummy document type.

    Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
    Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
    Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

  • 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

  • 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

  • PO not subject to Release strategy but PR is.

    Hi Friends,
    I am trying to check what purchases have occured in my organisation which have not been authorised at some point.
    I first have done a search using table EKKO for PO's not assigned a release strategy and found many.  Therefore I thought well maybe they have been authorised at the PR level using a release strategy.  I looked at one and this seems to be the case.
    Am I right in thinking that what has happened in this scenario is that a PR has been created, been released via the appropriate release codes and then automatically become a PO but the PO has not met the criteria of a release strategy and so been released automatically?
    I'm a little confused because we only appear to have release strategies defined for PO so how would these pick up PR? 
    BTW our release strategies are classified on PO approval - reasons and PO approval - Plant.
    Last thing:
    So if I want to check which orders have not been authorised I was thinking of using table EKPO to look for PO documents with no PR (Do all PO's need a PR?) and no release strategy assigned to the PO.  Using table viewer SE16 how do I specify "null" i.e. no value?  Do I just type NULL?
    I guess then I need to look at all PR's that come out to see if they have got a release strategy assigned?
    Thanks for your help, sorry for the rambling question...
    Chris

    Chris,
    1. Your PRs might not be subject to release strategies at all
    Go to SE16 and look up T16FG, and run it wide.. look for the release object .. if you see "1" you have Release configured for PRs as well, else 2 is for POs
    2. Tcode ME2N, select dynamic selection  and under  PO header choose Release status and Subject to release indicator and play around with them the way you want.
    also, choose Purchasing item>> purchase requisition  and in teh field .. right click and choose options..= and leave teh field blank, that 'd mean null
    execute the report based on other criteria if any
    Not all POs require a requisition although they should theoretically.

  • New po release strategy

    hi,
    i am having xxxxx class for po release strategy with 3 characteristics-(plant, po value and document type)
    now i want to have only 2 characteristics with document type and PO value.
    again i want to use new release codes for my new strategy, keeping the same class for release strategy.
    can i define new release strategy using the new codes?, then what shall be the impact of the same on below
    1. already released PO, now want to amend,(after new release strategy implimented)- what would be the effect on PO?? which release codes shall hit the same?
    2. already release PO(i understand there wont be a problem in GR, as release ia already effected)
    3. new PO shall catch the new strategy- no problem with the same.
    for implimenting the new strategy using the same class, can i delete the old release strategy with codes or i just need to remove the value mentioned in the classification view of the release proceedure.

    thank u.
    my point is while re-defining the release proceedure.
    earlier i had 150 release strategies and arround 40-50 release codes. now only 12 release codes
    i just need to get confirm, if i create a new release code and assign a new release strategy using the same class(only deleting the plant characteristics), what will happen to old po(released) for which now we are amending.
    i assume i need to delete/remove all the data of old release strategy available in classification view, and keeping the release codes as it is in release pre-requisites fr old release strategy.
    or just any body briefe me what are all the condition for changing the exsiting release strategy.if i need to create new release code,release strategy by using the same release class.

  • 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

  • Assign Characteristic to Class

    Hi,
    I need a help on assigning characteristic to class in BDC programming. My BDC programming will handle around 8 transactions which are executed sequentially like CT01, CU01, CL01, CU41 etc...
    I have a newly created Characteristic which has to be assigned to a Class (which can be a newly created class or an existing class). Suggest me which transaction code ASSIGNS CHARACTERISTIC TO CLASS?
    Many a thanks.

    If you have to use a transaction you can use CL02 transaction and type in the list of CHAR's in the CHAR table after typing in the CLASS name on the top text fields.
    If you want to do it using BAPI's.
    BAPI_CHARACT_CREATE - To create a CHAR
    BAPI_CLASS_CREATE - To create the CLASS and also assign CHAR to the class.
    If you want to do it separately, you can call the BAPI_CLASS_CHANGE to assign new CHAR's to the class.
    To assign objects to classes, you can use BAPI_OBJCL_CREATE to do the same
    Regards
    Ravi
    Note : Please mark all the helpful answers

  • Why we Maintain the data in Trxn  # CL20N  / CL24N for Release Strategy ?

    Dear All Gurus,
    Please resolve my Query , that during maintaining the Release strategy for a P.O , i used to create characteristics for defined values such as plant , currency , doc. type etc, then creating class and assigning these characterstics with this class created.
    Now after this i had create Release Group , Release Code and Release Strategy and assigned the Rel. Code with the Rel . Str and in Classification tab i had manually mentioned all those created Characterstics in CT04 and finally saved this Process.
    Till now i had not at all made any entry in Trxn # cl20n.
    But when i had create a P.O with all  the values as same as defined in characteristsc , the Rel Str got triggered succesfully.
    My Question is that , what is the use of mainiating data in Trxn # CL20N & CL24N ?
    Please clarify my doubt.
    Many Thanx in advance.
    Rgds
    sap11
    Edited by: Rajeev Chaturvedi on Jan 20, 2011 5:08 PM

    it is just another way to maintain the same thing in the same tables. Classification notspecific to release strategies, materials and batches, vendors and customers can be classified too.
    You can do this from withion those objects, or from the central classification menu using the classification transactions.
    People here recommending this for production system after you have transported the strategy from developement to production. Becaues classification is master data and cannot be transported the usual way. And many here do not know how this can be done with ALE

  • 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

  • PO Release strategy, error: class POCLASS class type 032

    All SAP Gurus,
    We are configuring new PO release strategy.
    When we go to Release strategy - classification
    (Release procedure for PO - Define release procedure for PO - Release Strategies - classification)
    It gives following error: Error in classification (class POCLASS class type 032).
    Where we can maintain the classification?
    Regards,

    Dear,
    Please follow bellow detail.
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1)     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
    2)     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
    3)     Define Release Procedure of purchase order: -
    In this step four processes involved.
    1)     Release Groups
    2)     Release Codes
    3)     Release indicator
    4)     Release Strategies
    1)     Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2)     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.
    3)     Release indicator: - In this step you have to define release indicator.
    Like X - Blocked, I - Under process, S - Release.
    4)     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 continue
    Click on classification button, Enter values of purchasing group for which you want to created release strategy.
    Regards,
    Mahesh Wagh

Maybe you are looking for