Purpose
In most cases, Business Information Warehouse development projects are not carried out in a productive system, rather in one or, depending on their scope, several development systems.
If you carry out your development projects in a development system, then you must transport the developments into the target system (test or productive system).
You can use the transport connection to collect newly created or changed Business Information Warehouse objects in the respective development system, and subsequently transport them in connection with the Change and Transport Organizer (CTO).

You can find additional information about the SAP Change and Transport System (CTS) in the Basis documentation under
Transport Organizer
Transport Strategy in CTS
Process
The following diagram illustrates the transport process:
A typical system landscape consists of a development system, a consolidation system and a productive system. You can only transport between either OLTP systems (O1,O2,O3) or between BW systems (B1,B2,B3). Communication between OLTP systems and BW systems takes place using the RFC (Remote Function Call) during uploading.

On the Administrator Workbench: Modeling screen, select Tools -> Logical System Name Conversion. You then reach the View "Source System Name Conversion After Transport" screen.
Replicate the metadata prior to the first transport between BW systems (B1 in B2, B2 in B3) from the connected OLTP system into the corresponding BW target system.

When a transfer structure is transported for example, it can only be activated when the corresponding DataSource has already been made available in the target system.
You have the following option to change objects of a specific Object type even in systems set globally to "not changeable":
Note that these objects are no longer connected to the transport system. For this reason, this process is only recommended for productive systems.

You can find additional information about the advantages of using each of these processes under
.