Troubleshooting (BI Content Activation)

Use

You can find out if errors occurred during the installation of BI Content in the active version by choosing Log to display the log. Correct the error depending on its cause. Then try to install the BI Content again.

The errors and their possible causes are listed below. You can correct some of the errors in the system in which the BI Content should be activated. You can then activate the BI Content again. Some errors must be corrected in BI Content development. In this case, contact the organization that developed the BI Content.

Procedure

Error messages when copying a large set of objects

Possible Cause	Procedure	Where Error is Corrected
-	To restrict the error, look for the incorrect object using the error message or by searching for the inactive object in the center screen area. In the left navigation pane, select the view Object Types and collect only the required objects of the incorrect object. Copy it to the A version.	In the system in which the BI Content is to be activated.

DTP / Transformation / Transfer Rules (3.x) / InfoPackage not found when collecting objects

For all source system-dependent object types

Possible Cause	Procedure	Where Error is Corrected
You did not select the correct source system for the BI Content when you collected objects for BI Content activation.	In the function area BI Content, select the source system by choosing . More information: Defining the Target Source System	In the system where the BI Content is to be activated.
The release of your source system is less than the smallest release in BI Content. More information: Making the Source System Anonymous	Upgrade the source system or select a different source system in the function area BI Content by choosing .	In the system in which the BI Content is to be activated.
The source system-dependent object is not available in the pseudo D version. More information: Enhancements to the BW Versioning Concept	Create the pseudo D version of the relevant object. Normally the pseudo D version of an object is created by the following functions: Replication of the corresponding DataSource or source system for replicating source systems (SAP systems) Activation of the source system for non-replicating source systems (non-SAP: file, UD Connect, DB Connect, Web Service) If these functions do not correct the problem, you can execute a function module or a report for some object types. The information about how pseudo D versions are created is available in the documentation for the source system-dependent objects in the table entry Pseudo D Version: DataSource InfoPackage Transformation Data Transfer Process Source System-Dependent 3.x Objects	In the system in which the BI Content is to be activated.
There is no corresponding DataSource in the pseudo D version for the selected source system or it is not available in the active version.	For more information, see section DataSource not found when collecting objects in this chapter	In the system in which the BI Content is to be activated.

Additional information for InfoPackages

Possible Cause	Procedure	Where Error is Corrected
The cross-reference table between the shadow version and the pseudo D version is incorrect. For more information about object versions, see Enhancements to BW Versioning Concept	In the ABAP Editor (transaction SE38) execute program RSSM_SHIPDVERS_CLEANUP.	In the system in which the BI Content is to be activated.

Possible Cause

Procedure

Where Error is Corrected

The cross-reference table between the shadow version and the pseudo D version is incorrect.

For more information about object versions, see Enhancements to BW Versioning Concept

In the ABAP Editor (transaction SE38) execute program RSSM_SHIPDVERS_CLEANUP.

In the system in which the BI Content is to be activated.

DataSource not found when collecting objects

For DataSources of All Types of Source System

Possible Cause	Procedure	Where Error is Corrected
The shadow version of the DataSource (R3TR SHDS) was not shipped (the object was assigned to package $TMP).	Ship the object.	In the development system
A migration was performed without shipping the obsolete shadow mappings (SHMP) as deletion. In this case the 3.x D versions remain in the customer system since they are still valid.	Delete the obsolete 3.x objects from the BI Content and ship the deletion.	In the development system

Additional information for DataSources of replicating source systems (SAP systems)

Possible Cause	Procedure	Where Error is Corrected
The pseudo D version does not exist because the DataSource was not (yet) replicated.	Replicate the DataSource. You can replicate a DataSource in the maintenance transaction for the DataSource (transaction RSDS) or replicate the source system in the Data Warehousing Workbench. More information: Replication of DataSources	In the system in which the BI Content is to be activated.
The corresponding D version is not available in the source system.	Select a different source system with or import the DataSource (R3TR OSOD) into this source system. More information: Defining the Target Source System	In the system in which the BI Content is to be activated.
A BI Content version was subsequently inserted in the source system DataSource so that it no longer matches the BI Content. More information: Making the Source System Anonymous	Remove the BI Content version from the source system DataSource in the original system or create the corresponding BI Content in the original system by activating the objects again with a version reference. Ship the changes.	In the development system
The BI Content was ported to a lower release without creating the shadow objects again (these are not relevant if for example the object key contains `R/3 710` but the real logical source system is a `700` system).	In the original system of the source system DataSource, assign a BI content version and activate the BW objects again. This recreates the BI Content with a new version reference. Ship the changes.	In the development system

Additional information for DataSources of non-replicating source systems (file, UD Connect, DB Connect, Web Service)

Possible Cause	Procedure	Where Error is Corrected
The correct BI Content release type and version was not assigned to the source system. For more information, see Making the Source System Anonymous in section BI Content-Release-Types: Others.	Assign the source system in the source system tree of the Data Warehousing Workbench a release type and version from the context menu entry Assign Release. Activate the source system again.	In the system in which the BI Content is to be activated.
The BI Content has either an incorrect or no BI Content release type and/or version.	In the original system, assign the source system in the source system tree of the Data Warehousing Workbench, assign the correct release type and version from the context menu entry Assign Release. Create the corresponding BI Content in the original system by activating the objects again with a reference to the version. If necessary, manually delete the incorrectly shipped shadow objects from the database tables. Ship the changes (new objects and possibly deletions of the old objects).	In the development system

Possible Cause

Procedure

Where Error is Corrected

The correct BI Content release type and version was not assigned to the source system.

For more information, see Making the Source System Anonymous in section BI Content-Release-Types: Others.

Assign the source system in the source system tree of the Data Warehousing Workbench a release type and version from the context menu entry Assign Release. Activate the source system again.

In the system in which the BI Content is to be activated.

The BI Content has either an incorrect or no BI Content release type and/or version.

In the original system, assign the source system in the source system tree of the Data Warehousing Workbench, assign the correct release type and version from the context menu entry Assign Release. Create the corresponding BI Content in the original system by activating the objects again with a reference to the version. If necessary, manually delete the incorrectly shipped shadow objects from the database tables. Ship the changes (new objects and possibly deletions of the old objects).

In the development system

Process chain is incorrect and copying the process chain from BI Content again does not solve the problem

Possible Cause	Procedure	Where Error is Corrected
The incorrect version of the process chain is retained after another copy.	If you copy the BI Content again in order to repair the process chain, make sure that the comparison indicator ( Match) is not set.	In the system in which the BI Content is to be activated.

Routines in the transformation contain errors after BI Content installation

Possible Cause	Procedure	Where Error is Corrected
The Match (X) or Copy checkbox was selected (by default) for the transformation when the BI Content was installed. In this case, all existing transformation rules - including routines - are retained and are not replaced. When the match operation is performed, only new rules are added (for example, fields that are populated by new routines).	Run the BI Content installation for the transformation again. Deselect the Match (X) or Copy checkbox. The existing transformation rules are overwritten by the BI Content. Make any necessary changes to the routines.	In the system where the BI Content is to be activated.

Possible Cause

Procedure

Where Error is Corrected

The Match (X) or Copy checkbox was selected (by default) for the transformation when the BI Content was installed. In this case, all existing transformation rules - including routines - are retained and are not replaced. When the match operation is performed, only new rules are added (for example, fields that are populated by new routines).

Run the BI Content installation for the transformation again. Deselect the Match (X) or Copy checkbox. The existing transformation rules are overwritten by the BI Content.

Make any necessary changes to the routines.

In the system where the BI Content is to be activated.