Skip to Content
Author's profile photo Arminda Jack

Transport of Release Strategies? Not a good idea

As many of you might already have experienced, if you try to transport the release strategy customizing, the data in the new system is inconsistent. 

The reason for this system behavior is that the classification data cannot be ‘transported’, it has to be sent by ALE. Therefore you could use transactions:

  •   BD91 for sending characteristics
  •   BD92 for sending classes
  •   BD93 for sending classifications.

The correct order is important here! Please proceed as in note 45951


You can review the following SAP notes for more information:
     365604     FAQ: Release strategies in purchasing  
     86900      Transport of Release strategies (OMGQ,OM
     45951      Transporting class data: system / client


You can read more about how to set-up ALE in the

R/3 Library -> CA – Cross Aplication Components -> Business Framework Architecture -> ALE Integration Technology -> ALE Quick start).


If you do not want to use the ALE to send the release strategy customizing, then the only other solution is to enter the data manually in the new system.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      I have reviewed the transactions to move the Characteristic and Class. What is the best method to move the release groups, relese codes and release strategies?