Making the Source System Anonymous

Use

The information about the source system is made anonymous when BI Content is shipped. When a source system is imported or replicated to the target system of the shipment, the anonymous information is compared with the properties of the source system to create the delivery version of the objects that are source system-dependent. These objects can be copied to the active version.

In the DataSource maintenance on the General tab page, you can display how the source system is made anonymous for a given DataSource based on the following BI Content properties of the DataSource:

BI Content Release Type
BI Content Version

When the shadow object of the DataSource is created, these two fields replace the source system. This means that the source system is also made anonymous by this information for all other objects that are DataSource-dependent (transformations, data transfer processes, InfoPackages, 3.x transfer rules and 3.x transfer structures).

Example

This is shown in the following example:

If the DataSource 0EXAMPLE has the same content release type and content version in both source systems AAACLNT000 and BBBCLNT000, transformations A and B as well as the DataSources in the delivery coincide.

The resulting conflict is handled differently for each object type. Such a conflict should be avoided when you develop BI Content.

When you create the delivery version (pseudo D version), the system determines whether the content release type and content version of an existing shadow object corresponds to a given source system. This shadow object is copied to the pseudo D version for this source system.

BI Content Release Types

The following content release types are available:

R/3

This release type is used for DataSources in which the BI Content version corresponds to the Basis or SAP NetWeaver-Release of the SAP source system containing the DataSource.

DataSources with this type were either developed prior to PI-Basis 2005.1 and therefore have no explicit version, or a version was not maintained when the DataSource was developed in the SAP source system.

When the pseudo D version for a DataSource and a source system is created, the system defines all the shadow objects that have R/3 as the BI Content release type and whose BI Content version is less than or equal to the Basis or SAP NetWeaver release of the source system as suitable.

Note

If there are multiple shadow objects with different versions, the system uses the one with the highest version to create the pseudo D version.

SAP

This release type is used for DataSources for which an explicit BI Content version was defined during BI Content development in the SAP source system.

The version is independent of the SAP system release in which the DataSource was developed. The version reflects the development status of the particular DataSource. The version is in the data part of the BI Content object (OSOD) in the source system, and is not part of the key. As a result, there can be only one version for each source system. This means that the version that should currently be used for a given DataSource should not be ambiguous.

When the pseudo D version for a DataSource and a source system is created, the system defines the shadow objects whose BI Content release type and content version agree with the type and version of the DataSource as suitable.

Note

Notes about developing DataSources in SAP source systems

We recommend that you assign an explicit BI Content version for new and further developments of DataSources in the SAP source system. In this way the DataSource is not coupled with a Basis release. This makes it easier to deliver BW objects that are based on such a DataSource.

Even if the 3.x objects do not adhere to this BI Content version concept and continue to use the Basis release to make the source system anonymous, you nevertheless should assign a content version in the SAP source system. This creates a base for migrating the transfer rules into transformations that can be created depending on the BI Content version at a later time.

On the other hand, the BI Content version of a DataSource in the SAP source system should not be reassigned or changed within a development since the previous shadow versions of the assigned BW objects would become obsolete and unlinked if the previous BI Content version of the DataSource were not delivered separately. When the assigned BW objects are activated again, a new shadow version is created, but the previous one is also retained.

Other

This release type is used for DataSources from non-SAP source systems.

You can define the BI Content release type and version in the Data Warehousing Workbench when you create the source system and also subsequently from the Assign Release context menu entry of the source system.

When BI Content is developed, the DataSources and the DataSource-dependent objects inherit this type and release as their release type and version.

When the pseudo D version for a DataSource and a source system are created, the system defines all the shadow objects whose BI Content release type is the same as that of the source system and whose BI Content version is less than or equal to the release of the source system as suitable.

Note

If there are multiple shadow objects with different versions, the object with the highest version is used.

Caution

If you want to create content other than file content for a non-SAP source system, you must define a BI Content release type and version for the source system.