Transport Landscape
The figure below outlines the transport process in a BI landscape:
A typical system landscape consists of a development system, a consolidation system, and a productive system. You can only transport either between source systems (O1, O2, and O3) or between BI systems (B1, B2, and B3). When we refer to source and BI systems in this documentation, we are referring to the systems in their specific roles. However, BI and source systems can actually be the same systems (Myself system). The communication between the source systems and the BI systems takes place when the metadata is replicated and the data is loaded using an RFC (Remote Function Call).
● Extractor enhancements and metadata changes are automatically written to transport requests in the source systems. These have to be transported from the development source system to the consolidation source system and from here to the productive source system.
● BI objects that are directly or indirectly dependent on the source system need to be handled differently. This ensures that the BI objects recognize the current source system names in the target system landscape.
More information:
Special Features of Source-System-Dependent Objects
Defining the Target Source System
● The DataSource metadata has to be transported from the original source system to the specified target source system and is replicated during import postprocessing of the assigned BI objects. Make sure that the DataSource exists in the target source systems before you import the dependent BI objects.
For example, if a transformation with a DataSource as the source is transported, the transformation can only be activated if the corresponding DataSource exists in the target system.
● In the consolidation system, you can test how the transports affect system functions.
● BI objects are transported as logical objects (TLOGO objects) from an original system to a target system.
More information about transportable object types in BI: Transportable Object Types
● You can choose the following transport strategies:
○ Standard Transport System
When you create an object, you specify a package for the object and write it to a transport request.
○ BI Transport System
When you create an object, it is automatically assigned to a local package. You can subsequently use the BI transport connection to collect all the objects relevant for a scenario, assign them to a package, and write the objects to a request.
More information about the advantages of using each of these procedures and about how you can specify the procedure:
Defining the Recording Time for Transports
● If you want to change objects for a specific object type in systems that are set globally to "Cannot be Changed", you can set the changeability of these objects in the system.
More information: Defining Object Changeability