BEx Web Application or Query as iView in the PortalLocate this document in the navigation structure

Use

BEx Web applications and queries that are displayed on the Web can be displayed as iViews in the portal. Enterprise reports can also be used in the portal as a special form of BEx Web applications and dashboards. Unlike BEx Web applications, dashboards are Web applications that are created with BusinessObjects Dashboard Design and also display data from the BW system.

Features

A BEx Web application or query as an iView can, together with other iViews, be part of a portal page or can take up the complete content area. There is then a direct call of the BEx Web application or query in the BW system which the current data is displayed with. When using the portal cache, there can be a delay before data updates appear.

For more information about configuring the portal cache, see Configuring Caching.

An iView with a BEx Web application or query can be generated using BEx Web Application Designer, BEx Query Designer, or Portal Content Studio.

More information: Generating BEx Objects and BW Objects for the Portal.

There are three general integration scenarios for BEx Web Application iViews, depending on which portal the iViews are displayed:

Details about BEx Web Applications iViews in a BW-specific portal

The iViews are of type BEx Web Application iView and have the code link com.sap.portal.appintegrator.sap.BWReport. You must choose the required version of BEx Web: BEx Web Application iView (SAPBW 3.x format) or BEx Web Application iView (SAP NetWeaver 7.0 format).

The two most important properties, System and BEx Web Application Query String, are set automatically for BEx Web Application Designer and BEx Query Designer. You need to enter these properties manually in the Portal Content Studio.

  • The System property contains the alias to the BW system. The system alias is based on the BW system that was defined in the portal.

    For more information, see Maintaining a System Alias List , Defining the System Landscape, Running the System Landscape Wizard, and Automated Configuration of BI Java.

    With the BEx Web Application iView (SAP NetWeaver 7.0 format) version, any BW system that is specified as a BW Master System is automatically used in the portal system landscape.

  • The BEx Web Application Query String property must have the following values for the BEx Web Application iView (SAP NetWeaver 7.0 format) version:
    BEx Object Value

    Web Template

    template=<TEMPLATE>

    Query

    query=<QUERY>

    Query View

    initial_state=VIEW&initial_state-view=<VIEW>

    InfoProvider

    initial_state=INFOPROVIDER&initial_state-infoprovider=<INFOPROVIDER>

    Bookmark

    bookmark=<BOOKMARK_GUID>

    Report

    report=<REPORT>

    Dashboard

    dashboard=<DASHBOARD>

  • The BEx Web Application Query String property must have the following values for the BEx Web Application iView (SAP BW 3.x format) version:
    BEx Object Value

    Web Template

    template_id=<TEMPLATE_ID>

    Query

    infocube=<INFOCUBE>&query=<QUERY>

    Query View

    data_provider_id=<VIEW>

    Bookmark

    bookmark_id=<BOOKMARK_ID>

<…> are placeholders that have to be replaced with the name of the required object.

You can add further URL parameters for BEx to the BEx Web Application Query String property, to set filter values for example. The URL parameters are separated by an ampersand (&). More information: Using Parameters to Call Web Applications.

You can use the Application Parameters property to specify more BEx URL parameters.

For more information about additional iView properties, see iView Properties and Editing iView Properties.

See also:

Creating BEx Web Application iViews