BEx Web Application or Query As Document or
Link in KM
You can include a BEx Web application or query that is displayed in the Web as a precalculated document or link in Knowledge Management in the form of an iView on a portal page.
The precalculated documents with historic data are stored in Knowledge Management (not in the BI system). The links in BEx Web applications or queries access the BI system indirectly through the BI Metadata Repository Manager and then display the current data.
A BEx Web application or query as a document can be generated with the BEx Broadcaster and as a link using the BEx Web Application Designer or the BEx Query Designer. For more information, see Creating Content from BI for the Portal.
The documents and links are only located in Knowledge Management (not in the BI system).
You can use the Portal Content Studio to create iViews with documents and links. The iViews are of type KM Document iView and have the code link com.sap.km.cm.docs.
The most important property is the path to the document.
● With a precalculated BEx Web application or query as document, the path is independent of the selected folder in Knowledge Management. You specify the folder in the BEx Broadcaster in the Target in Portal tab page (see Broadcast to the Portal).
● With a BEx Web application or query as a link, the path to the document is independent of the selected prefix for the BI Metadata Repository Manager and the template ID of the BEx Web application. You have to enter the value /<BI_REPOSITORY_MANAGER_PREFIX>/activeVersion/WebTemplate/<TEMPLATE_ID>/launch as the path to the document.

The designations in brackets are placeholders for technical names.
For more information, see the SAP Reference IMG → SAP Customizing Implementation Guide → SAP NetWeaver → Business Intelligence → Settings for Reporting and Analysis → BEx Web → Integration into the Portal → Set Up Repository Manager for BI Documents and BI Metadata in the Portal.
You can use the Integration Using KM Content iView from the Content Administration portal role to determine the path for the document.
For more
information about other iView properties, see
iView
Properties.
For more information on displaying folders for Knowledge Management with documents, links and folders, see Calling With KM Folders.
For more information on using Knowledge Management, see Integration Using KM Content.