Transportation of release strategy

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

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

Similar Messages

  • Can i transport PO Release strategy in a request

    Hi Gurus,
                     I have done po release starategy in dev can i transport the release strategy in a request to quality client or should i do the same setting again in quality server.
    Regards,
    Dheepak

    hI
    1- Release classification is a master data which you can not transport and need to maintain in each client.
    2- Goto Txn -- CL24n in Qly or PRD
    3- Enter release class and class type then enter ,there you will get all your strategies select the strategy you want to maintain and details there you can maintain the values.

  • Transport of Release Strategy Classification

    Hi Experts,
    Is there any way to transport Release Strategy Classifications.
    Regards,
    AKS

    You cannot transport them (Class and characteristics) . But There is a way to send them accross systems by ALE   . ref SAP link http://help.sap.com/erp2005_ehp_04/helpdata/EN/24/903b39878f4205e10000000a114084/frameset.htm .  You will need help of an Abaper who has worked on ALE .
    If the data isnt large, its safest to manually create class and chars and assign in CL24N .

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

  • SES Release Strategy

    Hi,
    Need to configure release strategy for SES unfortunately SPRO setting for the configuration are closed on live client.
    How can i get the client open, Do i need knowledge of specific objects?
    Alternatively can i configure and transport the release strategy from a dev. client where SPRO is open ?
    Any help would be appreciated

    HI,
    Make use of this path
    SPRO-> IMG-> Materials Management-> External Services Management-> Define Release Procedure for Service Entry Sheet
    You are not allowed to touch the configuration part in the production client. for that matter nobody will have.
    what you have to do is that you have to config in the development and create a transfer request and then transfer this request to the Quality test the release process if everything is proper then transfer the request to production from development with proper approval
    Thanks & regards,
    Kiran

  • Transport request in PR release strategy

    Hi Experts,
    While configuring characteristics and classes for release strategy in PR, system is not giving prompt for transport request.
    What could be the reason? Is it standard functionality or something has to be done at our end.
    Kindly suggest
    Rgda

    Hi,
    Check the following SAP notes.
    10745
    45951
    86900
    Hope it helps,
    Regards,

  • How to apply newly transported release strategy to existing POs ?

    Hi,
    We transported a new release strategy to production
    The new POs created are catching the rel strat B if they meet criteria
    But some of the existing POs also meet the criteria for B and they should also take up this new release strategy
    We cannot change the POs in ME22N, busines refuses to make any change to POs
    How can we apply our new rel strategy to these POs ? has the SAP provided any standard function module to report?
    thank you
    B

    thankyou for the replies.
    finally we got minor price change done manually in all the POs to get the new rel strategy on them
    Open POs , no change done - Did not pick release strategy (then it was no problem at the first place)
    Open POs , change done in price - picked the new release strategy
    Open POs ,  no change done but click on 'check' button in change mode - Could not test this one bcoz all POs are now converted. But I put break point in save user exit (which also plays part in determining the new release strategy) it did not stop at the break point and I gave message 'No data changed' so I think this action will not redetermine release strategy. It was very useful if it did though.
    thank you.

  • Release strategy for Transport requests

    Hi,
    Can anybody give me the detail steps to configure release strategy for transporting requests?
    we are having Dev and Prd systems.
    Regards,
    Vinnu.

    Hello,
    I hope you have configured TMS for two system landscape.
    Just make the transport routes also, make DEV system as a Domain Controler.
    Then transport requests will automatically come in to the request queue.
    Using tx stms_import , import those request sequentially !!
    Note: Points always encourage me to reply !!

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

  • P Req. Release Strategy not Transported

    Hi,
    For Configuring the Purchase Requsition Release Strategy, We have Created Characteristics and Class in the Configuration Development Client. Created Release Groups, Assigned Release Codes with the Release Group, and Assigned Release Group with Release Strategy with Classification. Tested PR Release Strategy for the given Classification Values the Release Strategy triggered.
    We have Created same Charateristics and Class in the Testing Development Client (Since the Characteristics and Class are not Transportable). Transported Release Groups, Release Codes and Release Strategy from Configuration Development Client to Testing Development Client. When we check the Release Strategy Classification in the Testing Developmemnt Client, system showing Classification Error.
    Please let us know whether the Release Strategy Classification Requests are Transportable or not.
    Ravi

    Dear Ravi,
    The Release Strategy Configurations can be transported, in respect to the requests transported.
    But the assignment of the Characteristic Values to the respective classes needs to be done in respective destination clients. Since teh assignment will get transported.
    To Do the same, please use transaction CL24N, Enter the classes Used in your release strategy and assign the respective Characteristics Values.
    Hope this will serve the need.
    Njoy SAP
    - Regards,
      Saravanaganesh

  • Release strategy transport using BD91/ BD92 and BD93

    I would like to move Characteristics/ Class and Release strategy using ALE transactions BD91/ BD92 and BD93.
    The question I have is that do I run the ALE transaction from the Source enviornment( Development box) to export it toTarget box( QA)?
    Or do I run it in Target box (QA) to import it from DEV box?
    Thanks
    Raj

    Hello,
    You need to setup Customer Distribution Model (BD64) and Partner Profiles  in DEV (Outbound) and QA (Inbound) systems with ALE Port. Then run the transactions BD91, BD92 and BD93 in DEV. If the partner profile in DEV is setup to transfer immediately, IDOCs will be transferred to QA.
    Thanks,
    Venu

  • Problem in purchase requisition release strategy code

    Hi
    We are facing a problem in purchase requisition, a new release strategy was created and change request transported but when PR is displayed in release strategy chart a same user is showed in different release strategy code.
    Note: new strategy was copied from other.
    Thanks in advance.

    hi,
    As you said tht you have copied the release stategy n created the new one...
    If you do so, you would have copied the class also...to which the release group is attached...
    If this is the case, then system doesn't recognise the new one, and inorder to solve it you have to define the new characteristic and class...then assign this class to the release group and make your release strategy again...
    Once you do this check the release strategy at OMGSCK...and then try at PR...
    You do all settings at :
    SPRO >> IMG>> MM >> Purchasing >> PR >> define release strategy >> W/o classification >> here edit characteristics/class and all other link are provided...
    Regards
    Priyanka.P

  • Release strategy tables

    Please tell me the tables used for release strategy of PR, PO, service PR, sercice PO, RFQ, contract, and delivery schedules.
    Is there a method of finding out the table by some methodology. It is not possible to remember all the tables.
    In case of PR item level release is required. Give some guidelines as to how to activate item level guidlines. it is possible both with and without classification.
    Regards

    HI,
    Release strategy tables
    Release strategy without classification
    • T161I as described above.
    • T161E Release code and Description
    • T161S Release indicator
    • T161G Assignment to release indicator
    • T161F Prerequisites
    Release strategy with classification
    • T16FG, T16FS as described above.
    • T16FH description of the release group
    • T16FT description of the release strategy
    • T16FC Release code
    • T16FD Description of the release code
    • T16FV Prerequisites and actions
    • T16FK Assignment to release indicator
    • T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
    • T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
    Other tables are
    EKBE History per Purchasing Document
    EKBZ History per Purchasing Document: Delivery Costs
    EKKN Account Assignment in Purchasing Document
    EKPA Partner Roles in Purchasing
    EKPB "Material Provided" Item in Purchasing Document
    EKPV Shipping Data For Stock Transfer of Purchasing Document Item
    EKRS ERS Procedure: Goods (Merchandise) Movements to be Invoiced
    EKUB Index for Stock Transport Orders for Material
    EBAN table has fields for release status and indicator.
    To See the tables
    goto Transaction SE11, in the field Table click F4, Click on Information system
    In the applciation Compnnets enter the following & execute
    MM* Materials Management
    MM-CBP* Consumption-Based Planning
    MM-PUR* Purchasing
    MM-SRV* External Services
    MM-IM* Inventory Management
    MM-IV* Invoice Verification
    MM-IS* Information System
    MM-EDI* Electronic Data Inter
    MM-FT* Foreign trade
    OR
    goto SE16 Click F4, You have two options Information system & Sap Applications.
    Click on SAP Applications & selec the application you wnat to see, for E.g Purchasing you can click on materials managemnt, Purchasing if you drill down you will see the list of tables....
    http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Check release stratergy with and w/o classification
    Thanks & Regards,
    Kiran

  • Item wise release strategy

    Hi Experts,
    I made item wise release strategy and used material group in class ,however when add this CEBAN-MATKL it doesn't find release strategy  when remove this release strategy is working  is it need to add something into material master data ?Need your advice
    Thanks in advance

    create release class, FRG_EBAN is available in system
    create release characterisitics .. here what ever name you give, you have to make it 'reference to table CEBAN' and corresponding CEBAN field , in additional data
    create a release group and attach the release class created
    create release codes, and while doing it you have to specify for which release group it is valid
    create release indicator , here specify the changeability
    create release strategy with release codes, release prerequisites, release statuses etc
    if you are transporting this, in the operational client, using CL24N  assign char values for each characterisitcs of release strategy. ( you need not assign char value when that characterisitic is not present int he document e.g.if account assignment is a char, then for release strategy for document without account assignment should not have any value for that char)
    if you ensure this much your release strategy should work ok

  • PO Release strategy question

    Hi,
    In PO release startegy,
    Plant- XXXX
              YYYY
              BLANK
    Purchase group, Total net order value, order type are the characteristics currently defined.
    PO is created at company code level..with multiple plants-i mean, XXXX, YYYY.
    rekease strategy does not work in case, if line items have account assignment and item category.
    pl help

    CEKKO is a structure for purchase order header.
    The plant in purchase order header is only filled in case of UB stock transport order, where you do not have a vendor, here you would only have the supplying plant.
    You are talking about plant in item level, which is requesting plant, not the supplying plant.
    You can never reach your goal until you CHANGE your design.
    you either create only POs which have only items of one single plant (must be controlled via user exit) or you just cannot have a release strategy that works. It is just black or white.

Maybe you are looking for