BI Versioning Concept 

Preconfigured BI 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 BI objects for your information models. The BI versioning concept enables you to deliver the BI 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:

Version	Meaning	Relevant for…
		Delivery of BI Objects	Transport of BI Objects
D	Delivery version	X
A	Active version		X
M	Modified version		X
T	Transport version for the import of source-system dependent objects		X
Shadow version	Delivery version for source system-dependent objects	X
Pseudo D version	D version for source system-dependent objects that are created in the target system of the delivery	X

 Relationship between object version and object type:

The BI distinguishes between different object types: one object type for the active version and one object type for the delivery version. There are two logical transport objects for each BI object that is delivered: The transport object for the active version, the A-TLOGO object, and the transport object for the delivery version, the D-TLOGO object. In accordance with the system settings, the system writes the suitable TLOGO object to the transport request when transporting.

Overview of the logical transport objects in the BI system: Transportable Object Types.

Object versions D, A and M will be discussed below. Information about the object versions that are relevant in connection with source system-dependent objects: Enhancements to the BI Versioning Concept.

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

Use of the Version when Processing BI Objects

The following diagram 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 BI Objects

The following diagram illustrates the versions within 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-own objects and are executed as repairs.

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

       2.      These 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. Information about which object version is imported into the target system: Transportable Object Typess.

       3.      After importing, all BI 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.

Examples of transports in different versions

InfoCubes or InfoObjects are firstly 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: Transporting BI Objects    

Use of the Version when Delivering BI Content

The following diagram displays 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.

Some examples of objects imported into the active version are:

●        Currency translation type

●        InfoObject catalog

Some examples of object types that are imported into a modified version and are activated after the import:

●        InfoObject

●        InfoCube

       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.

■       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