
The prerequisites are described in detail in Migration of Documents into the CM Repository.
You want to migrate documents from the BW server into KM so that you can store and edit these documents on the portal.
Note: KM on the portal does not support language versions. If there is more than one version of a document on the BW 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).
In Customizing, choose . Or, on the portal, choose .
The migration iView user interface appears.
On the Migrate Documents screen, in the System Alias dropdown box, choose the system tjat you want to migrate documents from.
In the dropdown box for Source (BW Document Repository), select the repository for BW documents that you want to migrate the documents from.
In the Target (CM Repository) dropdown box, choose the CM repository into which you want to migrate documents.
Under Migrate, set the flag for the document classes that you want to migrate.
We recommend that you do not migrate documents for metadata if the documents are transported automatically with the metadata.
Under Other Options, set the Overwrite Existing Documents flag if you want to overwrite existing documents on the portal.
To perform the migration, choose Start Migration.
The system notifies you when the migration process has completed.
You have copied BI documents to the portal and physically stored them there. The BW system is modified automatically in the system landscape. The properties of the BW documents for InfoProviders, master data and metadata now contain the target (CM repository).
You can now edit the migrated documents on the portal and use them in BW Web applications. Changes are not written back to the BW system however and are therefore not visible in BEx Analyzer.
During migration, the system automatically enters the target CM repository in table RSPOR_T_PORTAL for the corresponding document class. This entry allows you to display documents coming from the Data Warehousing Workbench in the portal.