Transferr clasification of release strategy

Dear all,
I want to transfer the clasification of my Release strategy to the productive system.
Is it possible? only the release codes are transferred through requests.
How can i transfer it, as i do not have permission at my client's productive system to maintain it.
Thanx in advance

Aldais
SAP Note 86900 explains that you cannot transfer classification. IF you dont have access to service sap give me you email ID i can forward that note.
Summary
Symptom
The transport of Customizing data in the release procedure area 'Release strategies' can only be used in a restricted manner. The 'Transport' function displayed in Customizing under 'Table view' only takes the release strategies into account but not the dependent data of the release prerequisites, the release statuses and classification data.
Thanks
Reeves

Similar Messages

  • Transport characteristics+classes of clasification system: release strategy

    Hello,
    Someone know how I can transport the characteristics+classes of classification system for the MM release strategy.
    I think that the values must be assigned manual in each client but I do not have to recreate manually the characteristics+classes.
    Cheers,
    Marta

    Hello,
    The OSS solution to transport the clasification is via ALE.
    I will create a LSMW batch to load the clasification system.
    Thank you very much for your comments.
    Marta
    The classification data need to be transported by ALE as described in
    notes 86900 and 45951. The only other solution is to enter the data
    manually.
    You can obtain 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 again in your target system.
    For that you have to:
    1. assign new values to the characteristic master data (trx. CT02)
    2. assign the new data to the classification system (trx. CL30)
    3. verify the consistency with trx. CL24. Please see note #186809.
    For more information, please see note #365604.
    Please check the answer from development regarding this issue:
    "The transport of release procedure customizing data can only be done ina 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. Customer may consider
    remote consulting to do the set up."

  • Purchase Order not subject to release strategy

    Good day everyone!
    I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
    After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
    My question is: How to assign purchasing document to release strategy?
    Please help. Thank you in advance.
    Anisah

    hi
    yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
    now below i am giving u one by one steps , follow and let me know .
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order.  There is only one characteristic created in this example.  For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic   e.g.  NETVALUE
    Click Additional data Table name CEKKO      Field name  GNETW    and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X    Mutliple values
    X    Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group   Rel. Object   Class                 Description
      02                                 REL_PUR        Rel. Strategy for PO
    Release codes - New entries
    Grp         Code
    02           01
    Release indicators
    Release indicators           Release        Description
          0                                                        Blocked
          1                                     X                Release
    Release Strategy
    Release group   02
    Rel.strategy    01
    Release codes   01
    Release status   0
                            1
    Classification   Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header.  This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order. 
    regards
    ravikant dewangan

  • PO release strategy Classification

    Dear all,
    I have a question about PO release strategy would like to ask, hope you can give me some advice.
    I have about ten release strategies which is used for different requirements.
    For each release strateg, there are several Classification.
    I am going to set a new release strategy, which only concern some of the Classifications, for the non-used Classifications, I have set a '*' to be the value, but the release strategy does work.
    I would like to know is it all Classification should be provided a value?
    Many Thanks
    Sunny

    Hello Biju,
    Firstly, many thanks of your idea.
    Let me make an example.
    I have a clasification (GROUP 1) which has predefined values ('A', 'B', 'C', 'D', 'E', ' ' ), and this clasification was already used in many release strategys.
    A release strategy is defined to trigger the release when the value of the clasification (GROUP 1) is value 'A' and a release strategy is defined to trigger the release when the value of the clasification (GROUP 1) is value 'B' ..etc.
    For this new release strategy, it does not concern the values of the clasification (GROUP 1). In my setting, if I set a value '*' in the release classification, the release never triggers. What should I set if I would like to ignore this classification for this release strategy?
    Thanks your advice again
    sunny

  • PR Release strategy

    Dear All,
    We want that if any user change account assignment(Cost center,G/L.Order etc..) in PR the release should reset and need reapprovals.
    Please let me know how we can achieve this.
    Thanks.

    Hi ,
               In standard design system only considers characteristics from         
    CEKKO structure for release strategy consideration. But it will not              
    stop us  in selecting the other characteristics.                                                                               
    Please go through the IMG help of release strategy, will give good               
    information.                                                                               
    I think you have already read the note:                                                                               
    The characteristics of the class used must all be linked to the           
           corresponding fields of structure CEBAN or CEKKO (for purchase            
           orders)...."       
    Characteristics which are created for the release strategy with           
    classification MUST access communication structures CEBAN or CEKKO since  
    during the strategy determination, the system cannot access any other     
    tables or structures.                                                     
    If the characteristics refer to fields which are not contained in              
    structures CEBAN or CEKKO, the corresponding fields can be added to            
    communication structure CEKKOZZ or CEBANZZ, or an append structure can         
    be created for CEKKO or CEBAN in which new fields can be included.             
    If you want to use new defined fields as part of the                           
    release strategy clasification, you should use enhancement M06E0004            
    (User exit "exit_saplebnd_002").This user exit allows you to use the           
    user fields in strucure CEKKO to include additional data.                      
    Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and        
    control them through user exit "EXIT_SAPLEBND_002. Otherwise new field         
    will not work.                                                                 
    As you very well know SAP has provided the following customer exits     
    which allow us to change the communication structure for determining    
    the release strategy                                                    
    Purchase requisition                                              
                           M06E0002 - for item wise release             
                           M06E0005 - for overall release                                                                               
    External purchasing document                                      
                           M06E0004                                                                               
    I hope this helps!
    Regards
    Vijayesh V V

  • PO Release Strategy for 3 company codes

    Hi
    I am working on PO release procedure for 3 company codes in a client.I have created a one charecteristics called Order Type & assigned to class -POVALUE_NEW .I am using the same charecteristics & class in 3 company codes. I have created a different Rel Group & release Codes & assign as shown below 
    Group                       Class
    AA     2     POVALUE_NEW
    AB     2     POVALUE_NEW
    F1     2     POVALUE_NEW
    F2     2     POVALUE_NEW
    V1     2     POVALUE_NEW
    V2     2     POVALUE_NEW
    Group     Rel Code
    AA     L1
    AA     L2
    AB     L1
    AB     L2
    F1     F1
    F2     F2
    V1     A1
    V1     A2
    V2     A1
    V2     A2
    Created a Rel strategy  as below
    Group       Strategy
    AA     P1------Vendor PO
    AB     P2-------STO PO
    F1     F1------Vendor PO
    F2     F2-------STO PO
    V1     V1------Vendor PO
    V2     V2-------STO PO
    I have maintained all the Doc type in value coloum of the cherecteristics .For vendor PO combination of Group & strategy , I have selected the respective Doc types in clasification .*When I raise the PO I am not getting the Release Strategy Tab in PO header* & when I remove the value in clasification any strategy , I will get the Rel Strategy Tab but this will appear in all  company code POs .I want to give different lease codes for each company codes  I am unable to find a solution to this issue . I am looking for a valuable suggesion from you all .
    Thanks
    Venkat

    Hi,
    1.in addition to existing Characteristic, create one more characteristic for Co. Code. Table CEKKO Field: BUKRS
    2. Assign this new char. to your PO Release Class
    3. Define your Release Codes for each Co. Code.
    4. Define Strategies with characteristic values Co. code and Doc. Type.with co. code relevantRelease codes.
    Ex: Co. Code1   Rel Grp-1 G1; Codes: A1, A2, A3
          Co. Code2   Rel Grp-2 G2; Codes: B1, B2, B3
          Co. Code3   Rel Grp-3 G3; Codes: C1, C2, C3
    Strategy-1:
                  G1   S1     A1 A2 A3;   values: CCd-1, Doc. type1
    Strategy-2:
                  G1   S2     A1 A2    ;   values: CCd-1, Doc. type2
    Strategy-3:
                  G1   S3     B1 B2 B3;   values: CCd-2, Doc. type1/Doc Type2
    Strategy-4:
                  G1   S4     B1 B2 ;   values: CCd-2, Doc. type2/Doc Type3
    Like this you can make as many strategies to meet your requirement.

  • PO Release strategy workflow configuration

    Hi All,
    I am doing PO release strategy workflow configuration in PFTC, Please tell me in this which all configurations come in workbench transport request and which all come in automatic transport request.
    Please guide me
    Thanks in advance
    Pavan

    The PR WS00000038 standard Workflow is very simple, you don't have to create a new one, it works, the think is that you need to make some configs in the SPRO
    spro
    Material Management/Purchaising/Purchase Requisition/ Release Procedure / Procedure With Clasification / Set up procedure with classification/ Workflow
    In this config you need to add the: Release Group / release code / object type( US for user id's) / and the User. You have to add one line for each release code that you configured in your release strategies.
    After that you have to review the linkage table Tcode: SWETYPV, find the object type BUS2105 and activate the linkage for the event releaseStepCreated, in this you will see the WS00000038.
    Now you can start to testing the notifications in the inbox(SBWP) for the configured users using the me51 tcode.

  • PR Release Strategy tab processor field is not getting displayed

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

    This is the workflow forum.

  • Release strategy for purchase requisition does not kick in

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

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • Release strategy for PO and Contract

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

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

  • PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

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

    Configuration issue/user error.

  • PO Release strategy

    Hi,
    I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
    Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
    After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
    Any suggestions are highly appreciated to fix this issue.
    Regards
    Sudhakar

    Hello,
    After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
    regards
    anand

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • 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

  • Release Strategy for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

Maybe you are looking for