Migrating Documents into the CM
Repository
We recommend only migrating documents to
the CM repository if necessary for performance reasons.
In BEx Web runtime (Java), you can integrate content from BI by migrating documents to the portal. You can migrate documents from the BI server to a special CM repository configured for BI. This repository is used exclusively for BI documents. This storage improves performance and allows documents for master data and InfoProvider data to be assigned on hierarchy-node level (as well as on characteristic-value level).
The migrated documents are not available
in BEx Analyzer. Only migrate the documents if you do not use BEx Analyzer or
only use it in connection with documents.

KM in the portal does not support language versions. If there is more than one version of a document on the BI server, only one version is migrated. This version is determined as follows: The system uses the logon language of the user executing the migration to search for the most recent version of the document in this particular language. If no document is found, the most recent version of the document is migrated (regardless of the language).
The following prerequisites apply for migrating documents:
● You have performed the necessary steps for integration into the portal. For example, you have set up the SAP NetWeaver Portal and Knowledge Management (KM). You perform these steps in Customizing, under SAP Customizing Implementation Guide → SAP NetWeaver → Business Intelligence → Settings for Reporting and Analysis → BEx Web →Integration to the Portal.
● A configured BI system exists in the system landscape.
● You have set up the BI Document Repository Manager and have entered values for the properties of BI documents for the BI system InfoProviders, master data, and metadata. More information: Repository Manager for BI Documents.
●
You have
configured a
CM repository
manager for BI documents in the portal. You have set the persistence mode
of the CM repository to Save All Data (Documents,
Folders, and Metadata) to the Database (DB). You have configured a
security manager for the CM repository manager using BI
Security Manager for Documents. This ensures that migrated BI documents
are protected against unauthorized access (you can only set up the security
manager after migration; this improves system performance during
migration).
● In Knowledge Management, you have assigned the required portal authorizations to the user who is performing the migration. These are:
○ Authorizations for reading and writing document properties. Choose System Administration → Configuration → Content Management → Utilities → System Principals → System User. Enter the user, and in the Resource Permission column, assign read, write, and delete authorizations.
○ Authorizations for changing the BI system in the PCD. Assign the user read and write authorizations.
You can find the required settings in Customizing, under SAP Customizing Implementation Guide → SAP NetWeaver → Business Intelligence → BI Documents → Create a CM Repository for Documents and Migration of Documents to the CM Repository.
During migration, documents from the BI server are copied to the portal-based KM and are stored there physically in the CM repository. The CM repository has a fixed folder structure and uses the BI security manager for authorization checks. You can migrate each document class individually or migrate several document classes simultaneously. You can display documents from the SAP GUI in the portal and make changes to migrated documents. Document migration makes a more comprehensive set of functions available: you can assign documents for master data and InfoProvider data on hierarchy-node level (as well as on characteristic-value level).
Displaying Migrated Documents in the Portal
You perform document migration in the portal. When migrating documents, the system automatically enters the target CM repository in table RSPOR_T_PORTAL. You can then display Data Warehousing Workbench documents in the portal.
Changing Migrated Documents
When you make changes to migrated documents in the portal
● the changes are not written back to the BI system
● the documents are not visible in BEx Analyzer
● the changes to documents on the server are not visible in the portal after migration If you want to make these changes available in the portal, you have to migrate the documents into the portal again.
For more information about migrating documents, see Migrating Documents.