Start of Content Area

Function documentation Integration Using KM Content Locate the document in its SAP Library structure

Use

The iView Structure linkKM Content from the Content Administration role of the SAP Enterprise Portal is the central environment in the Enterprise Portal for generating and managing Content in Knowledge Management. You have access to the various functions of Knowledge Management.

Features

The iView enables the management of documents and links, as well as their properties (authorizations, etc.). In KM Content, you get access to the various BW documents in Knowledge Management:

·        BW documents, using the Repository Manager for BW documents

·        BW metadata, using the Repository Manager for BW metadata

·        Precalculated BEx Web Applications or queries with historic data as documents

·        BEx Web Applications or queries with current data as online links

·        Precalculated BW workbooks with historic data as documents

·        Other documents and links from other sources (other Repository Managers in Knowledge Management)

For example, you may want to add additional BW documents or the appropriate documentation on 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. When doing this, note the link conventions specified below.

Recommendation

SAP recommends that you avoid using input help in this case. Because of the flat folder hierarchy, a very large number of objects can exist in a directory and searching for the required objects can be time consuming.

       3.      Save your entries.

The path to document property can also contain the following values, for example:

BW documents:

·        Documents for InfoProvider data: /<BW_DOCUMENT_PREFIX>/InfoProviderData/…

¡        Documents that are assigned to InfoProviders and queries: /<BW_DOCUMENT_PREFIX>/InfoProviderData/<INFOPROVIDER>/<QUERY>/<DOCUMENT>

¡        Documents that are only assigned to InfoProviders (cross query): /<BW_DOCUMENT_PREFIX>/InfoProviderData/<INFOPROVIDER>/<DOCUMENT>

¡        Cross-InfoProvider documents: /<BW_DOCUMENT_PREFIX>/InfoProviderData/<DOCUMENT>

·        Documents for metadata: /<BW_DOCUMENT_PREFIX>/MetaData/<ObjectType>/<ObjectName>/<DOCUMENT>

·        Documents for master data: /<BW_DOCUMENT_PREFIX>/MasterData/<CharacteristicName>/<CharacteristicValue>/<DOCUMENT>

BW metadata:

·        Documentation for meta data: /<BW_META_DATA_PREFIX>/active Version/<ObjectType>/<ObjectName>/documentation

Example

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

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

Example

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

The placeholder <DOCUMENT> has to 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.

 

For more information, see Calling from KM Folders.

For more information about the configuration of the BW Document Repository Manager and the BW Metadata Repository Manager, see Structure linkSetting Up Repository Managers for BW Documents and BW Metadata. In the configuration of the Repository Manager, the prefixes <BW_DOCUMENT_PREFIX> and <BW_META_DATA_PREFIX> are also determined.

For more information about the KM Content, see Structure linkContent Administration.

 

End of Content Area