Release class

Hi friends
Do we have any way to use Two release classes for PO?

hi,
> You can haveonly one release class....but you can have more than one release groups assigned to release class....
Hope it helps..
Regards
Priyanka.P

Similar Messages

  • Why can we only use 1 release class for overall Release of Purchase Req?

    Hi,
    After realizing that it would be beneficial to use more than one release class for overall release of Purchase Requisition with classification, in use with release groups for overall release, I now ask if someone knows why SAP has chosen to only allow 1 release class for overall release of Purchase Requisition?
    In my scenario I would like Release group US, used for release strategies for US-plant to be able to use 1 release class with a specific set of characteristics.
    For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_USD including a characteristic PR_TOTVAL_USD looking at CEBAN-GFWRT. The chosen currency for this characteristic would be USD.
    I would then like to allow Release group FR, used for release strategies for FRANCE-plant to use another release class with another set of characteristics.
    For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_EUR including a characteristic PR_TOTVAL_EUR looking at CEBAN-GFWRT. The chosen currency for this characteristic would be EUR.
    In this way the release strategies for the respective release groups US and FR, could maintain their overall limit values in their respective release strategies in their own currencies.
    1. Observe that I do not want to use the same Release class for both release groups for overall release, even though I know that this is currently the only allowed option, as far as I've understood.
    2. Observe that I do not want to specify the two characteristics PR_TOTVAL_USD and PR_TOTVAL_EUR for overall value in the same release class, as this would lead to double maintenance for a large number of release strategies. Also consider the maintenance when new countries with new currencies want release strategies.
    3. Observe that I only want to use overall release.
    What I'm trying to avoid is having to continuously translate local business USD overall value limits to limits in the currency chosen for the overall value characteristic. If this for example is specified in DKK, this would lead to a need to adjust the overall value limits as soon as the exchange rate between USD and DKK changes in the system.
    Please consider this simple example:
    Local requirement is that USD purchase requisitions should be blocked when the USD value is above 1000 USD. However in my release strategy I would have to maintain a value of >5365 DDK, if DKK is chosen as the currency for overall characteristic.(e.g exchange rate 5,365).
    Next month the currency exchange rate in the system between USD and DKK has changed, and therefore I would have to go into CL24N and maintain the value to reflect the new exchange rate between USD and DKK. Lets say it has gone up to 5,435. I would now have to maintain a value of > 5435 DKK in my release strategy to correctly reflect the local business requirement of 1000 USD.
    So if anyone could please explain why SAP has taken the decision to make the Release class for overall release client specific that would be much appreciated and awarded accordingly. Also if you have any suggestion on how I could obtain the above scenario on maintaning overall value limits in different currencies than that would be awarded to.
    BR Jakob F. Skott

    You can give feed back to Apple from the iTunes drop-down menu in the iTunes menu bar..
    You can also contact the iTS Customer Service from the links on this page - http://www.apple.com/support/itunes/store/
    MJ

  • ALE methodology to transport the release class

    How can I use ALE methodology to transport the release class, release characteristics and release characteristic value assignment from one client to another client ?
    please explain with clear steps.

    Hi
    Step 1: Move Characteristics to the target system/client (ALE).
    i). In the source system/client, execute transaction BD91
    This generates one idoc (logical message type CHRMAS) for each characteristic.
    ii). In the source system, check the status of the outbound idocs using transaction WE05, selecting message type CHRMAS.
    All outbound idocs should be in status 03 (Data Passed to Port OK).
    iii). * Only exception is when target system is D94 client 110. In this case the idocs go to status 30 (IDoc ready for dispatch) and an extra step is required to release the idocs to the target system. In this case, using transaction SE38, run report RSEOUT00 to release the idocs. 
    iv). Check that the idocs were received and posted in the target system:
    Log on to the target system & execute transaction WE05, selecting logical message type CHRMAS.
    v). If any idocs are in status 64, run transaction BD87 to re-process these to status 53.
    Step 2: Move Classes to the target system/client (ALE).
    In the source system/client, execute transaction BD92
    This generates one outbound idoc (message type CLSMAS) for each Class.
    Step 3: Check Config & classification data in target system/client
    Hope it helps
    Thanks /Karthik

  • Pls check release classes

    Dear all ,
      when i create release group for pr when i assign it to class an error msg come  pls check release class(msg no me492)
    i create new release group & new release class which was not earlier created
    release group            rel obj              ovrr                             class
    zo                               1                        x                                 zpr_overall
    zi                                 1                      -                                 zpr_itemwise
    pls guide how to resolve this.
    Regards
    Amin

    Answered

  • Release object / release class

    Hello Sapians....
    I am trying to creat new class and assign it to new Rel Grp. but I am facing this error and does not let me save.. Please guide wht is the solution..
    *Please check release classes (see long text)*
                                                                                    *Message no. ME492*
                                                                                    *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.*
                                                                                    *Procedure*
                                                                                    *Assign the release groups that were created for overall release to one*
         *release class only. Assign the release groups that were not created for*
         *overall release to a different release class.*                                                                               
    Thanks
    Hiren

    hi Hiren
    U can use only one release class for Release strategy i.e 1 for PR 1 for external Purchase document ( PO,outline agreement,RFQ, and 1 for service
    in your case u are trying to use two diff classes for same release group  which is not possible
    U can use only one class in service release per release group
    Vishal...

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

  • Different Class for Different Release Group

    Dear All,
    I want to use different release class for a new group i am creating for Purchase Order Release.
    But it is not allowing me to save the same as the explanation given the overall release should not be there in one of the group created, but i am not able to find the overall release column while creating new release group.
    please help
    regards,
    Darshan

    Hi Darshan
    Can you please guide me ..
    I am facing the same problem assigning new class to new PO rel. Grp. and does not let me save...
    wht must have gone wrong...
    FYI: I am using sharing the charatersitics in both classes.
    Thanks
    Hiren

  • 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

  • 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

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

  • Contract & PO Release Strategy

    Hi All,
    We are in the process of designing the release strategy for contract and PO. I  would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
    The release conditions for Contract required are
    1)Porg
    2)Pgroup
    3) Value
    Also, for quantity contract how can we make the release strategy trigger based on value.
    The release conditions for PO required are
    1)Porg
    2)Pgroup
    3)Material Group
    4)Value
    The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
    Request your help.
    Regards,
    Kannan

    Hi Kannan
    Yes your requirement is possible...
    While creating Charectristics in CT04 for External Purchase Documents...Create one more Value  for your Document Category...ie) Table as :CEKKO   and Field  as BSTYP   and choose the Purchase Doc. Category  values K  and F.
    Then create Charecteris for  CEKKO - EKORG,  CEKKO - EKGRP   and   CEKKO - GNETW, CEKKO- MATKL...  and assign these all 4 Chareteristices in your release class.
    And Configure your release statergy according to your requirement...
    Reward if useful
    Regards
    S.Baskaran

  • 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

  • PR RELEASE STRATEGY PROBLEM

    I am getting the following two error messages in the error log, while creating the PR Release strategy,
    1.No release group exists
    2.Characteristic CG_COE_RS_1 not linked to communication structure CEBAN
    Please suggest

    Hi,
    Point wise answers as below:
    1) SPRO>MM>Purchasing>PR>Release Procedure>Set up Procedure with classification>Release Group and release code
    Create Release Group and also give release class, which you have created and assign this release group to your release codes.
    2) SPRO>MM>Purchasing>PR>Release Procedure>Set up Procedure with classification>Edit Characteristics or (T.Code:CT04).
    For the respective characteristic, in the additional tab you have to give Table name as "CEBAN" and field name as your corresponding field name
    Regards.
    Chinna

  • Release strategy problem in RFQ

    Dear cons
       In release strategy of P.O we are using  three characterstics. I.e- net order value, purchase group & plant. Wehave not made any Release strategy setting for RFQ..while we are creating RFQ the system ask to release the RFQ. wHY.wHAT IS THE REMEDY FOR THAT. BECAUSE WE DONOT WANT TO RELEASE THE RFQ. I saw which data I have entered  for P.O release strategy The same data is available In RFQ path.The path is img-material mang- purchasing- P.o- rel. PROCEDURE for P.O- DEFINE REL. PROCEDURE FOR p.o. you can check same data is avaiable in RFQ PATH.
    PL. GIVE ME SOME HINTS.

    Hi,
    Please use document category or document type or both as chanracteristics for the release class.

  • Release Procudure - Problem while creating Release Group:Reg-

    in release procedure char. were created and class also created and the char. were assigned to the class too.
    But when i am creating release group the below error was coming..
    Please check release classes (see long text)
    and if i am see long text the below is the error
    Please check release classes (see long text)
    Message no. ME492
    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.
    Procedure
    Assign the release groups that were created for overall release to one release class only. Assign the release groups that were not created for overall release to a different release class.
    Example:
    Rel. group Rel. obj. Overall rel.    Class       Description
    01 1 _   FRG_EBAN      Group 01
    02 1 _   FRG_EBAN      Group 02
    S1 1 X   FRG_GF_EBAN Group S1
    S2 1 X   FRG_GF_EBAN Group S2
    please see what can i do to solve the issue.
    Thanks and Regards,
    Rajesh.

    HI,
    It is not possible to have more than one class define in the release
    strategy but it is possible to define difference characterics within
    the same class.
    Please verify the following:
    1) As the long text of the message says, first check that one release
      class only is 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.
       This means you have to have one release class only for all the
       release groups for overall release.
       Assign the release groups that were not created for overall release
       to a different release class.
    Example:
    Rel. group,   Rel. obj.,   Overall rel.,  Class ,     Description
    01,,1,,_,    FRG_EBAN,      Group 01
    02,,1,,_,    FRG_EBAN,      Group 02
    S1,,1,,X,    FRG_GF_EBAN,   Group S1
    S2,,1,,X,    FRG_GF_EBAN,   Group S2
    2) If you have followed all the indications of the long text of the
       message and the error is still displayed, please try to create the
       new release group via the 'New Entries' button.
    3) If you tried to create the release group via this button and the
       error is still been displayed, please verify the implementation of
       note 125316 in you system.
    Best Regards,
    Arminda Jack

Maybe you are looking for