Transport and change management enables and guarantees the distribution of software changes from the development environment to quality assurance and productive environments.
In most cases BI development projects are not usually performed in a productive system. Instead they are carried out - depending on your scope - in one or several development systems.
● If your development projects are carried out in one development system you have to transport the development to the target system (a test or productive system).
● You use the transport connection to collect newly created or changed BI objects in the respective development system. You transport them using the Change and Transport Organizer (CTO).
You can choose between the following transport strategies:
○ Standard transport
○ BI transport
For more information, see Transport Systems.
In the context of integrating BI content into the portal, you can export BI iViews to the source portal as portal content and import them to the target portal. For more information, see the “Export/Import” section under BEx Web Application or Query as iView in the Enterprise Portal
In order to change objects of a specific object type that are globally set to “not changeable” in BI systems of this type as well, you can set the individual object types to “changeable” in the Transport Connection function area of the Data Warehousing Workbench.
Note that these objects are no longer connected to the transport system. For this reason, we only recommend this process in productive systems.
For more information, see Object Changeability.