Show TOC

 Integration Using KM ContentLocate this document in the navigation structure

Use

The KM Content iView from the Content Administration portal role is the central environment in the portal for creating and managing content in Knowledge Management. You have access to the various Knowledge Management functions.

Features

The iView enables you to manage documents and links and their properties (authorizations, and so on). KM Content provides access to various BW documents in Knowledge Management:

  • BW documents using the Repository Manager for BW documents
  • BW metadata using Repository Manager for BW metadata.
  • Precalculated BEx Web applications or queries with historical data as documents
  • BEx Web applications or queries with current data as online links
  • Precalculated BEx Analyzer workbooks with historical data as documents
  • Other documents and links from other sources (other repository managers in Knowledge Management)

For example, you can add additional BW documents, the corresponding documentation for the BW metadata, or other documents to a KM folder in which you have stored precalculated documents and links from BEx Web applications using the BEx Broadcaster.

  1. In the KM folder, choose Folder → New → Link.
  2. Under Target, enter the path to the document manually. Note the link conventions specified below.

We advise against using input help in this case. Due to the flat folder hierarchy, a directory can contain a large number of objects, which makes searching for particular objects time consuming.

  1. Save your entries.

The Path to Document property can also contain other values, such as:

BW documents:

  • Documents for InfoProvider data: /<BI_DOCUMENT_PREFIX>/InfoProviderData/…
    • Documents that are assigned to InfoProviders and queries: /<BI_DOCUMENT_PREFIX>/InfoProviderData/<INFOPROVIDER>/<QUERY>/<DOCUMENT>
    • Documents that are only assigned to InfoProviders (cross-query): /<BI_DOCUMENT_PREFIX>/InfoProviderData/<INFOPROVIDER>/<DOCUMENT>
    • Cross-InfoProvider documents: /<BI_DOCUMENT_PREFIX>/InfoProviderData/<DOCUMENT>
  • Documents for metadata: /<BI_DOCUMENT_PREFIX>/MetaData/<ObjectType>/<ObjectName>/<DOCUMENT>
  • Documents for master data: /<BI_DOCUMENT_PREFIX>/MasterData/<CharacteristicName>/<CharacteristicValue>/<DOCUMENT>

BW metadata:

  • Documentation for metadata: /<BI_META_DATA_PREFIX>/active Version/<ObjectType>/<ObjectName>/documentation

Documentation for Web templates: /<BI_META_DATA_PREFIX>/activeVersion/WebTemplate/<TEMPLATE_ID>/documentation

  • Online link to Web templates, queries, or workbooks: /<BI_META_DATA_PREFIX>/activeVersion/<ObjectType>/<ObjectName>/launch

Online link to query: /<BI_META_DATA_PREFIX>/activeVersion/Query/<QUERY_ID>/launch

The placeholder <DOCUMENT> must be replaced with the technical name (ID) of the document in Knowledge Management. Launch is a document that automatically calls the Web template in BW as a BEx Web application.

 

More information: Calling with KM Folders .

For more information about configuring Repository Manager for BW documents and BW metadata, see Automated Configuration of BI Java . The prefixes <BI_DOCUMENT_PREFIX> and <BI_META_DATA_PREFIX> are also specified in the configuration for the repository managers.

For more information about KM content, see Content Administration .