Show TOC

BW Versioning ConceptLocate this document in the navigation structure


Preconfigured BW objects are delivered within BI Content as part of the ready-made information models for analyzing business issues. You can use these objects in your system directly or revise them. You can also create your own BW objects for your information models. The BW versioning concept enables you to deliver the BW objects in a system landscape and to use them in a consistent manner. This concept is an enhancement to the standard transport system.

The following object versions are used:



Relevant for…

Delivery of BW Objects

Transport of BW Objects


Delivery version




Active version




Modified version




Transport version for the import of source-system dependent objects



Shadow version

Delivery version for source system-dependent objects



Pseudo D version

D version for source-system-dependent objects that are created in the target system of the delivery




Relationship between object version and object type:

BW distinguishes between 2 different object types: one object type for the active version and one for the delivery version. This means that there are 2 logical transport objects for each BW object that is delivered: the transport object for the active version (A-TLOGO object) and the transport object for the delivery version (D-TLOGO object). In accordance with the system settings, the system writes the suitable TLOGO object to the transport request when transporting. For more information about the logical transport objects in the BW system, see Transportable Object Types.

Object versions D, A, and M are discussed below. More information about the object versions that are relevant in connection with source-system-dependent objects, see Enhancements to the BW Versioning Concept.

The figures below explain the use of the object versions for objects that support the M version. The M and A versions are combined in the figures and the activation step is omitted for those object types that do not support a modified version.

Use of the Version when Processing BW Objects

The figure below illustrates how to work with active and modified versions:

When a BW object exists in a modified version (M version) and is activated, the dependent objects (DDIC or program objects) are also generated upon activation. Activation is only possible when the object is consistent.


Make sure that the object is active before transporting it.

Use of the Version when Transporting BW Objects

The figure below illustrates the versions during the transport:

  1. Only those objects that are in the active version are exported from the development system.


    Make sure you use customer-specific packages when transporting your objects. These begin with Y or Z. Objects assigned to SAP packages are seen as SAP objects and are considered to be repairs.

    For example, the A version of BI Content must be assigned to a customer package, whereas the delivered D Version remains an SAP object.

  2. Exported objects are either imported into the target system in either the A version or in the M version, depending on the type. Source-system-dependent objects are transported in their own version, the T (transport) version.


    InfoCubes and InfoObjects are imported into the target system in the M version and activated after the import automatically, since tables (and additional Dictionary objects) are created during activation.

    The currency translation type and the InfoObject catalog are transported to the target system in the A version. This is because these object types do not require an activation step and therefore do not support the M version.

    More information about which object version is imported into the target system: Transportable Object Types.

  3. After importing, all BW metadata objects are automatically activated using the after-import method RS_AFTER_IMPORT. After importing, the dependent DDIC or program- objects are generated in the target system.

More information: Transporting BW Objects

Use of the Version when Delivering BI Content

The figure below illustrates the BI Content versions:

The black arrows show how the versions are used in the delivery process:

  1. First delivery

    • SAP delivers BI Content objects in the D version.

    • The objects are saved in the M version during BI Content installation.

    • The M versions that were created are activated and saved in the A version.

      Only those objects that are stored in the A version are exported from the development system. When importing into the target system, these objects (depending on object type), are either imported directly into the active version or into a modified version.

      More information about which object version is imported into the target system: Transportable Object Types.

  2. Second delivery (BI Content upgrade)

    • SAP delivers BI Content objects in a new D version.

    • You can compare the new BI Content with your active customer version and either adopt the new version or merge it with the existing version. You can use the following functions here:

      • Install: The customer version is deleted and replaced by the new BI Content version.

      • Merge: The two objects are merged and stored as a new customer version.


        For example, when you merge characteristics, an attribute join is built. For some characteristics you can select which you want to copy in a dialog.

        Whether or not merging is supported is a property of the object type. More information: Transportable Object Types.

More information: Copying BI Content to the Active Version