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

Similar Messages

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

  • PO release strategy for changes in price ($ and %)

    Hello,
    I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
    I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %.  I will need to calculate the difference in the total value between the original PO and the changed PO. 
    Example:
    Original PO total net value is $1000
    PO after a price change - total net value is $1500
    Total net value has increased by $500 or 50%.
    Tolerance for price change is $200 or $20, so tolerance has been exceeded.
    I know I will be using the total net order value (CEKKO-GNETW).  I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table.  I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not.  I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
    What I don't know is where will I find the previous total net order value once the PO has been changed?  Is the only place that information is stored in the change logs?  If so, what is the change log table name?  Or is there a different table that would contain this information?
    Thanks in advance for any help you can provide.
    Sincerely,
    Angela

    Update:
    I utilized function module EXIT_SAPLEBND_002 as a solution to this.  I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
    I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
    I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

  • What is the best strategy to use both Z10 and Q10?

    Assume I have both a Z10 and Q10 and I'd like to use it on alternate days, what's the best strategy to do so?
    BBM should be fine with the same BlackBerry ID and it can just keep switching between the 2 devices.
    If I am using local contacts and calendars, is there an easy switch to keep them sync on both Z10 and Q10?
    There are also other information to sync in Password Keeper, Remember...etc.
    Is there a solution?

    Hello,
    For calendar and contacts, there is this:
    http://supportforums.blackberry.com/t5/BlackBerry-Q10/How-To-OTA-Sync-BB10-and-non-BES-Outlook-Overv...
    With that, I actually keep all of the following in sync:
    Two instances of Desktop Outlook (2007 and 2010)
    Z10
    PlayBook
    Outlook.com
    And, before I decommissioned it, also an Android device. Any device that can synchronize with Outlook.com can use this solution to keep in sync for calendar and contacts. You, of course, need to not use solely local contacts and calendar but instead keep them synchronizing with Outlook.com.
    For the other things you mention, I know of no solutions other than backup/restore...but I do not recall if LINK offers the selective method for those.
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • 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

  • We couldn't release any transport request!

    Hi experts,
    We could't release any transport request on DEV from today.
    We could do it until yesterday.
    We have never changed any settings.
    Except release, we can use SAP system, and
    we can import released transport request to QAS .
    Also I could tp addtobuffer on DEV.
    [Operation]
    SE10 -> select transport request -> click [release] button
    and, we can see the error message as below.
    Error Message *****************************************************
    Test call of transport control program (tp) ended with return code
    [Transport Log]
    We can see the log as below.
    ERROR: No connect due to DbSl Load Lib Failure
    ERROR: environment variable dbms_type is not set.
    ERROR: Connect to RDV failed (20090220140504).
    ERROR: Connect to RDV failed (20090220140740), failed to read table SVERS.
    [Our Action]
    1. Change Environment variable & Restart SAP (note 351586)
    2. replace tp & saptrans
    3. change parameter (note 175627)
    4. add full control to everyone on sap/trans
    5. see note 534765，98678，128126，592514，799058，879941，508140，610640
    Thank you in advance.
    BR,
    Toshi

    Hi,
    Thank you for your reply.
    I did r3trans -d, and the result is as belllow.
    F:\usr\sap\RDV\SYS\exe\run>r3trans -d
    This is r3trans version 6.13 (release 640 - 07.01.08 - 14:25:00).
    unicode enabled version
    2EETW000 sap_dext called with msgnr "2":
    2EETW000 -
    db call info -
    2EETW000 function:   db_ntab
    2EETW000 fcode:      NT_RDTDESCR
    2EETW000 tabname:    TADIR
    2EETW000 len (char): 5
    2EETW000 key:        TADIR
    2EETW000 retcode:    2
    r3trans finished (0012).
    Also I checked TP_DOMAIN.pfl, but it seems that there is no problem.
    But I found doubtful point.
    It is environmental variable, and now it is differnt from last friday.
    Example,  last friday , there was variable as bellow,
    but today I couldn't find them
    In the meantime , I will deal with them.
    dbms_type=MSS
    MSSQL_DBNAME=RDV
    MSSQL_SCHEMA=rdv
    MSSQL_SERVER=<hostname>\RDV
    Toshi

  • Release strategy problem in Purchase order

    Hi Guys,
    I was trying to configure Release strategy for the purchase order and this button   is not triggering in my purchase order.
    I dont know where I was doing wrong and  where might be the problem  as I tried several times.
    Can someone give me some good idea about it  how to configure in a proper way.
    If you need any further information please let me know.
    Thanks
    Krishna

    Hi
    I hope you followed the following steps:
    1. Create Characteristic using CT04
    2. Create a class and link to the characteristic using CL02( class type: 32)
    3. Configuration of release procedure
        SPRO IMG->MM-> Purchasing -> PO -> Release Procedure -> Set up procedure
        A) Create release group and link to class
        B) Create release code
        C) Set up the release indicator
        D) Set up Release Strategies-> strategy and codes
        E) Set up Release Strategies -> pre requisites
        F) Set up Release Strategies -> status
        G) Set up Release Strategies -> values for strategy
    Regards,
    Subhashini

  • Release Strategy in Purchase Order

    Hi,
    Can any explain the usage of Release Strategy in Purchase Order.
    ganesh

    Hi Ganesh,
    Release strategy works the same way in purchasing documents (i.e. PR and PO). It is a form of control that company use to control the purchases made.
    In your scenario, a PO release strategy is used to control the PO release status for Good Receipt process. Once the PR is released by the relevant releaser, you will see that the PR is now unblocked for issuance of PO.
    Once the PO is issued with reference to the PR, it is now blocked again by a release strategy for user to perform Goods Issue. The releaser will evaluate the PO issued and determine if it is necessary to be released for GR / Service Acceptance process. At this stage, the releaser can still reject the PO although issued, and hence GR / Service Acceptance is not able to be performed. Different value will trigger different set of release strategy with different level of approvals, depending on how the PO release strategy is configured by the MM functional consultant. Usually, the PO release strategy has a flatter approving level as compared to PR release strategy, reason being that once the PR has been fully released by all releaser and the PO issued, usually the purchase is deemed necessary and PO releaser would usually consider to release the PO for GR  or Service Acceptance process, unless there is discrepancy or sudden change in decision of Management.
    Hence, all in all, the PO release strategy act as another form of control to the company to restrict the release of PO for GR or Service Acceptance.
    Hope this will give u a better understanding on the function of a PO release strategy.
    Rgds.

  • 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

  • PR Item Level Release WF not working after Release Strategy change

    Hi Experts,
               I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
    I really don't understand y after changing the release strategy workflow is not working and giving the following error.
    Even if i restart the workflow in SWPR the same error is occuring.
    Exception occurred    - Error when starting work item 000000390118
    PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
    CREATE                   -  Error when creating a component of type 'Step'
    CREATE_VIA_WFM  -  Agent determination for step '0000000003' failed
    EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
    AC00000148             -  Object type 'TS' not valid
    Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
    Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
    Regards,
    Hari

    Hello Hari,
    please set a breakpoint at function module
    ME_REL_GET_RESPONSIBLE
    and see what happends in section
        CASE t16fc-frgwf.
    * keine Ermittlung
          WHEN space.
            RAISE nobody_found.
    * Ermittlung über T16fW
          WHEN '1'.
    If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
    Best wishes,
    Florin

  • New release strategy should not trgger for PO released with old Rel Strategy

    Hi All,
    Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy  XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
    But requirement is if there is  any change or value decreasing in fully released Pos with old strategy  it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
    Please help me on this.
    regards,
    Rohit

    HI Rohit
    A reset of the release strategy only takes place if
           -  the changeability of the release indicator is set to '4' in
              case of a purchase requisition and '4' or '6' in case of
              another purchasing document (purchase order, request for
              quotation, contract, scheduling agreement),
           -  the document is still subject to the previous release
              strategy,
           -  the new TOTAL NET ORDER VALUE is higher than the old one.
    The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
    The commom steps are:
    1- make sure all of the old POs should have been released.
    2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
    3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
    Kind regards,
    Lorraine

  • Release Strategy for Credit Note un the QM Module

    Good SAP Guru's,
    I have a very important question for you:
    Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
    This should work on the same lines as the Purchase Order Release strategy.
    Any guide lines and/or assistance will be gratefully appreciated.
    Kind regards,
    Leslie

    Dear Leslie
    We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer  a notification will be trigered to manager and if he approves it will go for higher approval.
    Please find my suggestion for this development
    1) Make 3 task codes. for eg Task 1 for  credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
    2) According the need of the credit notes to be created let the user assign the task and release it.
    3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
    4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
    5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
    6) The credit memo creation will have to be  developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
    please let me know your apprehensions
    Regards
    gajesh

  • Release strategy for Future validity period- (Outline agreements)

    Dear All,
    I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
    E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
    I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
    How to set up release strategy in the above case.
    Thanks in Advance.
    Regards
    Amar

    Hi Amar,
    1) if you maintain a target value (EKKO-KTWRT) in the header of the            
    contract this value is the basis for the determination of the release          
    strategy. If the target value is 0, the system will cumulate the               
    values of the items and will use this value for the determination.                                                                               
    2) So if the target value is 0 and you change the price of a condition         
    with a validity period in the future the system will react in the              
    following way:                                                                               
    Example:                                                                       
       the contract contains one item with quantity = 100 and a net price          
    of EUR 5,-.                                                                    
       all contracts with a target value from EUR 0 - 1.000,- should be            
    subject of a release strategy                                                  
       the contract is created and released on October the 1st                     
       ME32K -> October the 2nd you define a new price of EUR 7,- with a           
    validity period from 03.10.09 - 30-10.09 -> you save the contract              
    -> the release strategy is not reset, as the start date is not                 
    reached yet (system date < startdate of validity period)                       
       ME32K October the 3rd you change a field in the contract -> the             
    release strategy is reset                                                                               
    This is system design that a release strategy can only be reset through        
    an action by the user. The determination of the release strategy can't         
    be triggered automatically in the background.      
    If you create a document which is subject of an overall release strategy      
    (e.g. p.o., contract) the determination of the release strategy takes         
    place when the user hits the 'save' button or chooses the 'check'             
    function.                                                                     
    So there must be a kind of event that tells the system that something         
    has changed.                                                                               
    Regards,
    Edit

  • New po release strategy

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

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

  • Release Strategy in PO for direct materials not driven by MRP

    We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
    Request you to let me know how I can make this work.
    I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
    request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
    Thanks and Regards
    Murali

    Hi Murali,
    Standard SAP provides PO release strategy at header level only and not at item level.
    So you can create a new PO document type and allow use of only this document type for manual PO creation.
    Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
    Hope this will fulfill your requirements.
    -Ravi

Maybe you are looking for