Skip to Content

Programs for Activating BW Objects in a Productive System

Programs for activation of Business Warehouse Objects in a non-changeable system are very useful after performing a system copy or upgrade.

This list includes all them and may be very helpful for BW, BASIS and also SAP Support consultants… why not?

Communication Structures :



               RSDS_DATASOURCE_ACTIVATE_ALL (for 7.X DataSources)

This report reactivates only A versions of DataSources according to the selection.

               RS_TRANSTRU_ACTIVATE_ALL (for 3.X DataSources – same report for Transfer Rules)

Data Transfer Processes (DTP):


Data Store Objects (DSO/ODS):

                RSDG_ODSO_ACTIVATE (single object only – no mass activation)

During activation the M version will be read.

The flag “Clean Up DDIC Structures” deletes old generated tables. This was necessary only in previous releases. 



If the A version is activated it will not affect the M version. If the M version is activated it will overwrite the A version with the M. 


                RSDG_IOBJ_ACTIVATE (single object only – no mass activation)

In the expert mode the processing lock can be swithed off, however it is not suggested to use. 





Transfer Rules / Transfer Structures:


If the option “Lock” is flaged during activation the object is locked. If only inactive transferstructures should be activated the flag “Only Inactive” can be checked. 



In case you need to reactivate an already active transformation you need to put the parameter Object status (OBJSTAT) as ‘ACT’ for that particular Transformation (TRAN_ID). DTP’s containing transformation of source – / target type ‘InfoSource’ will also be re-activated.


This is a new program, which is delivered and corrected by the following SAP Notes:

              1408161 – Program for transformation activation.            

              1434801 – Automatic Adjustment of Transformation for ISET.

              1471117 – SP25:RSDG_TRFN_ACTIVATE skips if M version has OBJSTAT ‘INA’.

              1493850 – Consulting: Transformations inactive after system copy.

             1507043 – RSDG_TRFN_ACTIVATE: Enhancements.


Update Rules:


This report reactivates only already active update rules.  The possibility of changing this behavior has been revised a few times, and the decision was to keep it activating only the already active versions. The reason is Update Rules should always be checked when they get deactivated. Blindly reactivating them may cause inconsistencies.

1516916 – RSAU_UPDR_REACTIVATE_ALL doesn’t activate inactive upd. Rule.

Some have created a Z-Version for this standard program and changed a few lines to make it also also reactivate the inactive update rules. That’s not an approach SAP Support would recommend, though. Reference: Program to activate Update rules.

You must be Logged on to comment or reply to a post.
  • Thanks a lot Paulo for this very useful list!

    I just would like to mention that the screenshot for the Cube program shows the one for DataSources.

    Also, I am curious to know what this "expert mode" is about in RSDG_IOBJ_ACTIVATE. Do you know?

    • Oopps... Thanks for pointing it!

      The expert mode, from what I can see, is obsolete. It shouldn't affect the execution at all. It's old 3.X legacy stuff.

    • Hmm... I put the screen-shot only in the Transformation section. Same with the 3.X Datasources (transfer structures).

      Since you have asked, I think it's better to replicate the screen-shots.

  • Hey Paulo, Thank you for sharing the list of programs.. it is really good.

    Is there any program which can activate InfoSets without asking Transport request?

    Thank you,

  • I recommend using these programs only if you spend the time to understand them.  One of my clients ran RSDG_IOBJ_ACTIVATE in production after a transport had deactivated a critical infoObject.  The program dropped the /BI0/X and S tables for that master data object and recreated SID values.  This action corrupted all data relationships between that master data object and the transactional data in reportable DSOs and Cubes.  This resulted in several days of reloading...