BI Content Delivery by SAP in OLTP Systems 

Purpose

The standard procedure used in the delivery of BI Content by SAP is the model for the delivery of content by customers and partners. The basis of this process is also object versioning in the OLTP system.

The DataSources delivered by SAP with BI Content are in the delivery version (D version). If you want to transfer data from an OLTP system to a BI system using a BI Content DataSource, you have to first transfer this DataSource from the D version to the active version (A version).

DataSources are assigned to application components in the OLTP system. You also need to transfer the application component hierarchies from the D version to the A version of the merged application component hierarchy (APCO_MERGED).This enables you to display the DataSources in this hierarchy in the OLTP system and in the source system view of the Data Warehousing Workbench - Modeling. 

Upgrading BI Content has no effect on objects that you already use productively, since only the D version is overwritten.

If you activate the application component hierarchy and DataSources for BI Content, the active customer version is overwritten when you install the D version.

The extract structure (object type R3TR TABL) and extractor (object type: LIMU FUNC) behave differently. These objects do not have a D and A version. For this reason, we recommend a versioning with content generation. This prevents incompatible changes to the productive scenario from arising.

The following figure shows how BI Content objects (DataSources and application component hierarchies) are used in a customer system with double delivery:

Process Flow

In the SAP content delivery system, the A and D versions of DataSources and application component hierarchies are stored in identical forms. There are two transport objects for each object: an A and a D object. During the transport, the system writes the suitable object to the transport request according to the system settings. If a content development system is involved, the system chooses the D object.

The next figure illustrates how BI Content (DataSources and application component hierarchies) is delivered by SAP:

For objects that are seen as content objects in a system (with a changeable namespace and where the system is a content development system), the system automatically activates the DataSource in an after-import method for the D version.
More information about the activation of BI Content in customer OLTP systems: Installing Application Component Hierarchies and Installing BI Content DataSources. In this customer system, BI object changes are saved in the active version. The D version remains unchanged.