Release Strategy - class error

Dear All
I have defined release strategy in my client 100
same i have transport to 101 and checked in the same client
its still working properly
but when i transport the same in client 201, even though all the data is transported strategy is not working
system showing me the following error while i checkiing the strategy in SPRO ( in client 201 - quality client)
while clicking on " Classification "
"Error in classification (Class CLL_PR class type 032)
after double click on above error: Procedure
Please check the specified class or class type in Customizing for the release procedure.
Please sudgest in the matter
Regards
Narendra

Dear Narendra,
We also faced same problem and found that the release strategy was not transported correctly .So my advice is that identify the correct transport and retransport it .Along with this please check all release strategy tables ,there  will be some entries missing.
Thanks,
AMIT

Similar Messages

  • Release strategy class

    Hi,
          Can we assign the two release class for the po release strategy.?

    HI,
    No,we can assign only one class.but we can assign multiple characteristics to this class.
    Characteristics are used to define the criteria on which you wish your purchasing documents are to be released. For example it can be plant , value, Document type, Material Group etc.
    The selection is based on the fields available in the tables for release, Like CEBAN for Requisitions and CEKKO for Purchasing documents.
    If you want that Value shall be a criteria for release then you will make a characteristic for value, and define the value or value ranges, you have the option of going foe single value or multiple values. Like wise you can make diff Characteristics as per the Client Requirement.
    Now all these characteristics can be grouped under a class.
    Now this class is assigned to a release group.
    Then when you create a release strategy, you can make many strategies under one group, where in you shall get the option of selecting value of Characteristic to be used in release stategy,
    For eg. say I have a characteristic Z_Value. with values 1- 10000, 10001 - 20000. and other characteeristic as Z_Plant, with values 1000 and 2000.
    Now you add this to a Class say Z_rel.
    Assign it to a Group say 01
    then while creating a release strategy say s1 unde group 01 you can choose plant value as 1000 and value as 1-10000.
    so whenever there is a PO of value b/w 1-10000 and plant 1000 it will go as per the release strategy s1.
    hope its useful for u
    Venkat.

  • 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

  • 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

  • PO Release Strategy on Value Based

    Dear All My Friends,
    i want to define the following Release Strategy, please advice how it will be done
    Person A will Release PO  value <=50,000/-
    Person B will Release PO Value >50000 and <=100000
    Person C will Release PO Value >100000
    please help me
    Thanks and Regards,
    Rajesh G

    Hi,
    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 total value. So you can create characteristic for Total net value. Take reference of CEKKO structure and GNETW field for Total net value in additional data of characteristic. E.g :- Total net value u2013 GNETWu2026Click on intervals allowed check box ..
    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 u2013 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 u2013 Purchase Head,
    Release group: -01, release code: - 02 u2013 Auditor.
    3) Release indicator: - In this step you have to define release indicator.
    Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
    4) Release Strategy: - This is the final step for release strategy.
    Assign release code 01, 02.
    Click on release prerequisites, select 02 u2013 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 Total net value for which you want to created release strategy.
    Person A will Release PO value <=50,000/-
    Person B will Release PO Value >50000 and <=100000
    Person C will Release PO Value >100000
    Utsav

  • Work flow for release strategy for PO & PR

    Hi Gurus
    Can anybody explain workflow for release strategy for PO and PR
    Thanks in advance.
    Atul Kulkarni

    Hi,
    First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
    For Work flow settings,You have to do follwoing configuration:
    MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
    Creation of work flow object,activation of workflow and other related settings will be done by Techinical  work flow consulant.
    Thanks,
    AMIT

  • Workflow for PR Release Strategy

    Hi Expert,
       Is there a way the scenario given  below will be possible to achieve..
       All the needed config for the  PR release strategy has been define... (release code, group,release strategy,class & characteristic)
      Parameter : Doc Type,
                      Amount
                      Acct Assignment Cat ( K,A,C)
                      Cost Center
                       Sales Order
    The challenge is that when the given
                   Doc Type - NB
                   Amount - >0
                   Acct Assignment Cat = C
                   Cost Center - Empty
                   Sales Order - 9999
    The PR will be subject for release strategy of Project Manager  ( Release Code :PM)
      The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
      9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
    She

    Hi,
    Thanks..but i have completed all the setting in PR release strategy ..  -
    Am looking for alternative/ ways that i can incorporate the partner function from SO using the sales order
      as the link from the PR  (charge to sales order) to trigger where the notification will flow through...
      This is more i think in the workflow or  userexit or abap, but i took  the libertly of posting it here perhaps some of the member had this requirement before and how it was accomplished..

  • PR Release Strategy work flow

    Hi Guys ,
    I have a work flow requirement , In Which i have to know in Purchase requisition items history . how to identify the new item and
    change items for triggering the work flow .
    Here i am using a badi to triger an event . ( BADI :  ME_REQ_POSTED )  
    Any idea , Plz share .
    THanks
    Nags

    Hi,
    First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
    For Work flow settings,You have to do follwoing configuration:
    MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
    Creation of work flow object,activation of workflow and other related settings will be done by Techinical  work flow consulant.
    Thanks,
    AMIT

  • Release Strategy disappear in a purchase requisition

    Please assist if a purchase requisition is created with different account assignments the release strategy disappear from the requisition.
    What might be the problem?

    I have the same problem.  If the purchase requisition contains 2 account assignment categories (K and Y), it does not create a release strategy.  I can create a new requisition and get a release strategy if I try to use them separately (not in the same req). 
    If i use CL24N, I can see where the RELEASE STRATEGY/CLASS R1 R1 shows a AccountAssignmentCategory value of K and Y.  Why can't I use them in the same purchase requisition?
    Thanks!

  • Re: PR Release Strategy with workflow

    Hi Expert,
       Is there a way the scenario given  below will be possible to achieve..
       All the needed config for the  PR release strategy has been define... (release code, group,release strategy,class & characteristic)
      Parameter : Doc Type,
                      Amount
                      Acct Assignment Cat ( K,A,C)
                      Cost Center
                       Sales Order
    The challenge is that when the given
                   Doc Type - NB
                   Amount - >0
                   Acct Assignment Cat = C
                   Cost Center - Empty
                   Sales Order - 9999
    The PR will be subject for release strategy of Project Manager  ( Release Code :PM)
      The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
      9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
    She

    hi
    i think u need workflow for release strategy
    Steps involved are :
    1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
    2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
    3) Go to OOCU > here under MM, go to MM-PUR,
    4) Click on "activate event linking"
    5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
    and Save.
    6) Click on "Assign agents" and proceed all above steps.
    BUS2012 is the relevant business object and Releasestep created is the event for the same.
    7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
    Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
    take help of ur BASIS person
    hope it clears
    regards
    kunal

  • SES release strategy being incorrectly triggered

    Dear All,
    We have maintained release strategy for Service Entry Sheet. In the SES release strategy class only the following characteristic is maintain
    a. Name of the person who creates the Service entry sheet
    In the release strategy only 'a', 'b' and 'c' users are maintained in the above characteristic. But in the system even if a user f creates the service entry sheet the system applied the release strategy on it too and asks for release code. The system should only ask for release code if a,b or c user creates SES.
    Thank you!

    Hi There
    Just a guess,,
    In CT04- for Name of Person who Created the SES (ERNAM)- in the values tab-
    Check the indicator-Additional Values is eanbled or not,, if enable remove it and try
    Thanks
    Senthil

  • 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

  • Class and release group and code in release strategy??

    hi experts ,
    Can some body explain me..
    I have created Characteristics and Class for for release strategy.
    But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
    I m using the same class what i have created for my company..
    So how to over come this issue
    Thanks

    Release Prerequisites
    Definition
    The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
    The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
    Release Indicator
    Definition
    When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
    When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
    What does the release indicator determine?
    Requisitions...
    External purchasing documents....
    Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
    Whether an RFQ or a PO may be created with reference to the item
    Whether the document may be changed by Purchasing after the start of the release procedure
    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
    Whether the purchasing document is released for transmission
    Alternative Release
    Definition
    Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
    Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
    The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
    An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
    Release w. Classification (PReqs./Ext. Pur. Docs.)
    Use
    The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
    The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
    Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
    If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
    Prerequisites
    The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
    If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
    How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
    This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
    Operation of Release Procedure w. Classification
    The characteristic values from a requisition or external purchasing document are passed on to the classification system.
    The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
    The persons responsible for the release codes process the document in the sequence defined in the release strategy.

  • Mm pr-po release strategy : error

    Dear MM experts,
    We already having MM-rel strategy for PR & PO with classification procedure and working fine,
    Now business requirement is to change the MM-Rel PR& PO strategy,
    New mm-rel strategy for PR customised in class 032  (not to use existing release groups & release strategies) 
    After doing config settings in customising client, the request moved to another client for testing.
    Testing client, request moved successful, and while checking the settings in testing client,
    in Release Strategies - details mode
    Informatination is available at Release pre-requisites, Release Statuses without any error,
    but when we try for Classification, we are getting the following error
    "Error in classification (class PRREL class type 032)"
    Can u please suggest what needs to be done so that we can go ahead further.
    Kindly note while doing config setting client, we did not encounter the above error, it has accepted all the settings (copy existing rel group & having differnt rel strategies, etc)
    pl help
    Thanks in advance
    Srihari

    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

  • Release Strategy with New Class and Char.

    Dear All,
    I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
    when i going to add in Release group.. system giving the error.
    Diagnosis
    Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
    My existing Characteristic for india :
    ZP0_GNETW     Total net order value     CURR     15     2     INR
    ZPO_BSART     Order type (Purchasing)     CHAR     4     0          
    ZPO_EKORG     Purchasing Organization     CHAR     4     0          
    ZPO_EKGRP     Purchasing group     CHAR     3     0          
    New Characteristic for South africa :
    ZPOSA_BSART     PO Order Type ATSA     CHAR     4     0          
    ZPOSA_EKGRP     Purchasing Group ATSA     CHAR     3     0          
    ZPOSA_EKORG     Purchasing Organization ATSA     CHAR     4     0          
    ZPOSA_GNETW     Total net PO value ATSA     CURR     15     2     ZAR
    ZPOSA_WERKS     Plant     CHAR     4     0          
    Please help me how do configure 2 release strategy for 2 country.
    I will be very thankfull to u.
    Regards,
    Vishal Garg

    HI Biju K,
    I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
    Please explain..
    And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
    Please explain in details.
    I will be highly thankfull to u.
    Regards,
    Vishal Garg
    9810402156

Maybe you are looking for

  • BAPI_GOODSMVT_CREATE using A10 Place in Storage

    Hello experts, I want to do MIGO using A10 Place in storage, and i put this parameters: goodsmvt_code    = '04' ITENS t_saida-matnr  TO t_bapiitem-material, t_saida-werks  TO t_bapiitem-plant, t_saida-lgort  TO t_bapiitem-stge_loc, t_saida_move_type

  • Regually getting spinning rainbow ball

    I've had my macbook since it was released last year and in recent months, when browsing the internet, I see the spinning rainbow ball thing so opening new pages is taking a few seconds longer than normal. It doesn't happen all the time but I'd say 70

  • Action vs ActionListener

    I am curious if there are any best practices for using the action property vs the actionlistener property to execute some managed bean code when clicking on a button? Should you only use the actionlistener if you need to do something with the action

  • Java 3D with .obj files

    Hi, I'm pretty new to Java3D and so on a bit of an unphill struggle right now. I am trying to load a 3d obj file (that i created myself) into my program. It is a simple boat with a sail and a hull, I am trying to animate these parts of the object sep

  • Listen for time of day

    Hi, all! Is there a way you can listen for a time of day with Java? For example, display a dialog box when it is 4:00 P.M. If you could direct me to and API or resource, that would be great. Thanks!