Skip to Content
Author's profile photo Paulo Junior

New SAP Note – 1516916 – RSAU_UPDR_REACTIVATE_ALL doesn’t activate inactive upd. Rule

In a previous Programs for Activating BW Objects in a Productive System, I composed a list of programs that can be used to activate/re-activate BW objects. As stated in the same post, the report RSAU_UPDR_REACTIVATE_ALL cannot activate inactive update rules.




This is a question that is often raised at Primary Support. After discussing this subject with developer of this program, I created the following SAP Note:


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


Part of the reason I created this weblog post, is to announce this SAP Note. 


HOWEVER… we all know though that these reports are very useful on productive systems, to quickly activate them, if, for some reason, they get inactive.


In some forums, I saw some created a Z report based on RSAU_UPDR_REACTIVATE_ALL and made it able to activate inactive update rules as well. I cannot suggest that you do the same, though.


Program to activate Update rules


Has any of you faced a situation where several update rules all got inactive and you had to lose some time to reactivate them? Were you able to find out why it got inactive?


If I can collect some cases, I may be able use them as arguments and bring this topic to discussion once more.
I hope to receive some feedback from you on this post.


Updated on 2011-01-07: I have received feedbacks from the experts and developers. This feature won’t be changed. The update rules always need to be checked if they are inactive. Reactivating them “blindly” may cause inconsistencies. Therefore, as mentioned before, it isn’t that safe to use the workaround from the SDN forum thread above.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Bhanu Gupta
      Bhanu Gupta
      Yes, I have had this situation more than once. At one time I needed to activate 4 update rules feeding 0Material for a quarterly update process. The UR were inactive because someone had made a change to 0MATERIAL and forgot to move the activated URs. I thought an emergency transport with the active versions would get me going, but I could not do that due to other development that was going on the same objects in Dev and under UAT in Q. Those changes required a datasource transport on ECC…too many dependencies and we could not roll back the development or move it forward. The quarterly process was stalled and had to be done in the next month. If I could have just activated those UR in production, would have saved a lot of hassle!
      Author's profile photo Former Member
      Former Member
      Thanks for bringing this issue up and I hope it does get some atention from SAP BI Developers.

      I would go one step further to say that this is not just a issue related to update rules becoming inactive in a production environment but the overall impact on dependent objects when changes are made to some high level structure in BI. For ex : changing a cube deactivates all dependent multiproviders , Adding a Nav Attribute causes IMPACT on lower level objects and so on.

      So it would be ideal if a holistic approach could be adopted to this entire change management process with tools to easily identify and either manually or automatically re-activate them in any system. We infact tried to investigate on our own how to identify all IMPACT changes and build some automated process around it but could not get much far along.

      We are on the latest release of BI and have faced on multiple occasions situations where even displaying a update rule in Prod. deactivates them apparently because the IMPACT was not fully "transmitted" from the higher level change. And if people fail to notice this someone gets a call @ 2 am to fix the failed load for busines critical reporting needed the next day.

      Author's profile photo Bruce Foxall
      Bruce Foxall

      And yet there are programs available to reactivate Transformations, and even Transfer Rules 'blindly'. Not sure why the same logic wouldn't apply in those cases, nor why it would be necessary to deactivate update rules when simply switching on a nav attribute in a cube.

      In any case, we will have a small program to check rstran and rsupdinfo for inactive rules which we can schedule to alert us when update rules/transformations are about to cause problems.