Start of Content Area

Integration of Documents (Changed)  Locate the document in its SAP Library structure

Technical Data

Function Is

Changed

In Release

 Software Component

●      Component: SAP NetWeaver

●      Release: 7.0

Assignment to Application Component

BW-BEX-ET      End-user technology

BW-WHM   Warehouse Management

BW-WHM-DOC Documentation

Country Setting

Valid for all countries

Use

Integration of BI Documents into the Portal-Based Knowledge Management (KM)

The BI documents for Metadata, Master Data and InfoProvider Data can be integrated into the portal-based KM in different ways:

...

       1.      With the Repository Manager for BI Documents. In this case the documents are physically stored on the BI server in the SKWF framework. The repository manager for BI documents is available in the portal with Release SAP NetWeaver '04.

       2.      With a migration of documents into a CM repository. In this case, the documents are physically stored in the portal. This allows the documents for master data and InfoProvider data to be assigned on the hierarchy node level as well (in addition to the characteristic values).

       3.      With the repository manager for BI metadata. In contrast to manually created documentation for metadata, the HTML-based documentation for the BI metadata will continue to be generated automatically from the metadata repository as needed. The repository manager for BI metadata is available in the portal with Release SAP NetWeaver 2004 (with SAP BW 3.5).

KM integration makes all of the KM services available for BI documents (for example, text search, text mining, subscription, rating, personal documents, discussions).

Documents in Web Applications

For the new Web applications in the new BEx Web runtime (Java) (see Business Explorer (Changed)), there are new versions of the Web items for document that were available for SAP NetWeaver ’04 or earlier SAP BW Releases. From these Web items, the KM applications can be started to display the documents and their details. Furthermore, it is possible to call the following KM dialogs to create new documents from the Web items.

●      New comment (text editor)

●      New HTML document (simple inplace HTML editor)

●      Upload document from local PC

●      Create new link (only CM Repository)

The BAdI RSOD_WWW_DOC_MAINT is no longer supported in the BEx Web runtime (Java). This BAdI is mainly used to pre-allocate the content or the name of a new document or to forbid creation under certain circumstances.

 

The new Web items include the following changes:

List of Documents

●      This Web item can display the columns “Name”, “Content”, “Assignment (to the BI Data)” and “Author/Change Date”. The columns can be switched on and off online or in the configuration. This means it is possible to display the contents of the documents in the list of documents only. The latter is especially useful for comments.

●      You are no longer able to display or change the selection of documents in the Web item. To change the selection of documents, it is necessary that you execute a navigation step for the associated data provider.

●      There is no correspondence to the BAdI RSOD_ITEM_DOC_LIST. This BAdI is used to change the output of the Web item according to customer. The main requirements that could be covered with the implementation of the BAdI (such as display of the document content) are now being covered by the Web item itself.

Single Document

●      Documents of all formats can now be embedded inplace. You do not need to create frames or Iframes in the Web application.

●      In addition to the document, the properties can also be displayed (such as last changed by, change time).

●      A context menu can also be displayed in addition to the document. With the context menu, you can delete or change the document or call the detail display.

●      There is no correspondence to the BAdI RSOD_ITEM_DOC. This BAdI is used to change the output of the Web item according to customer. The main requirements that could be covered by implementing the BAdI are now being covered by the Web item itself (as described above).

The old Web items from SAP NetWeaver ’04 or earlier SAP BW Releases (BAdIs in particular) continue to run on the runtime for SAP NetWeaver ’04 or earlier SAP BW Releases. There is no difference to SAP NetWeaver ’04.

Miscellaneous

●      The control as to whether characteristics are document properties can now be defined on the InfoCube, MultiProvider and Data Store level.

●      BAdI RSOD_DOC_BADI is not supported in the BEx runtime (Java) for migrated documents and is only partially supported for documents on the server. With this BAdI, during the selection and while saving properties or content of the document, you can intervene and also control the hierarchy expansion. Some of this functionality is now being supported by default. This means the control of hierarchy expansion is no longer necessary because documents can also be assigned on the hierarchy node level after migration.

●      Only documents in the BI server can be accessed using the Data Warehousing Workbench (functional area: documents). To manage the migrated documents, use KM iViews.

●      The “Generation of Documents for Metadata“ in the administration of document management (transaction RSODADMIN) is no longer supported because it was replaced with the new metadata search (see Indexing of Documentation for Metadata (Deleted)and Metadata Search (New)).

Overview Diagram

This graphic is explained in the accompanying text

Effects on Existing Data

BEx Web Runtime (ABAP)

There are no effects on existing data. The documents can remain on the BI server. You can continue to run BEx Web runtime (ABAP) without additional effort.

BEx Web Runtime (Java)

Initially, there are no effects on existing data. The documents can remain on the BI server. In order to use the documents in the BEx Web runtime (Java), however, you have to configure the repository manager for BI documents and integrate the documents into the portal-based KM.

Effects on Data Transfer

Migration of Documents into the CM Repository

When you migrate documents they are stored in a special CM repository that is only used for BI documents. After the migration, you should make sure that the documents are only changed in the BEx Web runtime (Java). Changes in 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 to the documents on the server (for example, from the BEx Analyzer) have no immediate effects on the documents in the portal; they are not visible in the BEx Web runtime (Java). However, you can migrate the documents that have been changed on the server to the portal again.

We thus recommend the following procedure:

●      Documents for master data and InfoProvider data

We recommend migrating the documents for master data and InfoProvider data to the portal into a CM repository especially configured for BI over the medium term. A larger number of functions are available to you then. There is also a migration iView that can be started from the Implementation Guide (IMG). This iView reads the data on the BI server using the repository manager for BI documents and copies it to the CM repository.

●      Documents for metadata

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 located in the portal. Documents on BI metadata can be distributed in the KM using ICE with the Content distribution 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.

Effects on System Administration

Indexing Jobs for Documents

The indexing job for documents is then only necessary when the search for documents in the old Web items or in the Data Warehousing Workbench is used. If only the BEx Web runtime (Java) is used, the documents in the portal should be indexed. The indexing job for documents on the BI server can be deleted in this case.

Effects on Customizing

If you use the BEx Web runtime (Java) with documents, you have to make the following configurations:

●      Set up repository manager for BI documents (KM configuration in the portal)

●      Enter the root node of the repository that contains the BI documents into the BI systems in the Portal Content Directory (PCD).

●      Set up CM repository for BI documents (KM configuration in the portal). This is a standard CM repository specially configured to the BI in which only BI documents can be stored. It has a fixed folder structure and uses the BI Security Manager for authorization checks. This point is only necessary if documents are to be migrated.

 

 

 

End of Content Area