When a BI transformation gets de-activated due to a transport, display the transformation generated program and activate it.
It is common to get transformation de-activated after a related transport: either by changing the transformation source, target or a related InfoObject. The person that is responsible for the causing
transport should create a new transport with the affected transformation to permanently correct the situation. Depending on the size and controls of a specific landscape, this can take a while. A workaround is to display the transformation in BI transaction RSA1 and select the menu option Extras -> Display Generated Program. Then click on the 'match' button to activate or Ctrl-F3.
This may save you in some situations, but not all. If the transport deactivated the associated DTP you may not be able to load data.
Another temporary option is to open the system (Basis) and activate.
You can also run the ABAP/4 report RSDG_TRFN_ACTIVATE with transaction SE38 to attempt to activate the transformation in the target system. Depending on the system setting and the 'correctness' of the transformation, it will activate or fail. The transformation ID can be found in table RSTRAN (first field), based on the source and target objects. This program also activates the affected DTPs. See SAP Note 1408161
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.