BI documents for metadata, master data, and InfoProvider data can be integrated into the portal-based KM in various ways:
The migrated documents are not available in the BEx Analyzer. Documents that are stored in the BI system are available in the BEx Analyzer. After migration, the documents are available on the portal and can be edited using Web applications and KM iViews. The integration with KM means that all KM services are available for BI documents (such as text search, text mining, subscription, rating, personal documents, discussions).
For more information, see BI Documents in Knowledge Management.
General Practices with Migration
When you migrate documents, they are stored in a special CM repository that is used for BI documents only. After migration, you should make sure that the documents are changed in the BEx Web runtime (Java) only. Changes made to the migrated documents have no effect on the documents on the BI server; they are not visible in the BEx Web runtime (ABAP) or in the BEx Analyzer. Conversely, changes made to the documents on the server (for example, from the BEx Analyzer) have no immediate effects on the documents on the portal; they are not visible in the BEx Web runtime (Java). However, you can migrate the documents changed on the server to the portal again.
We therefore recommend the following procedure:
We recommend that you temporarily migrate the documents for master data and InfoProvider data to the portal into a CM repository especially configured for BI. A larger number of functions are then available. There is also a migration iView that can be started from the Implementation Guide (IMG). This iView server uses the BI Document Repository Manager to read the data on the BI server and copies it to the CM repository.
If the documents for metadata are to be automatically transported with the metadata, we recommend leaving them on the BI server. An automatic transport would not be possible if the documents were on the portal. Documents for BI metadata can be distributed in the KM using ICE with the content exchange service (see Content Distribution), however, not in an integrated transport: In this case two "transports" would be necessary, one in the BI system and one in the KM.
For more information, see Integration into the CM Repository Using Migration.