Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Overview:

As you may well know a Business Intelligence/Warehouse System can be used for a variety of tasks such as data analysis or data collection and easily compile them into easy to read reports but what if you would like to integrate those reports in one place where all the analysis is used from those reports for example a CRM System. This page explains how to do exactly that so that your businesses run simpler.

Requirements:

  1. To Integrate 3.x Reports:
    1. SAP BI System
    2. SAP CRM System
  2. To Integrate 7.x Reports
    1. Requires BI System 7.0 or higher
    2. BI Portal Integration
    3. SAP CRM System

Set up a Logical System:

  • Launch Transaction BD54
  • Enter your BI Logical System and a Name for the System

Figure: Logical Systems

  • Go to Transaction BD97 and you should see the BI Logical System that you have just set up
  • Select your system and add “Standard BAPI destination” and “Standard dialog destination”

Figure: Adding Standard Destinations for Logical Systems

  • You can also maintain the default BW System “CRMBWDEST” using these steps

Figure: Default BI RFC Destination

 

Create or Customize a BI Report

  • Go to Transaction CRMC_UI_BI to Create or Customize a BW Report
  • You can modify an existing BI Report or create a new report.

Figure: Define BI Reports

 

  • The following are mandatory fields under Define BI Reports:
    • BI Report ID
      You must define this unique ID when you create a BI report. You use this ID when calling the BI report component.
    • BI Object Type
      This defines the type of BI report. Currently Web Client UI Framework supports the following types:
    • ABAP based BI reports
      • Template 3.x - you have to specify the technical name of the BI template in the field BI Object Key.
      • Query views 3.x - this is the generic template for query views; specify the query view name in the field BI Object Key.
    • The following BI report types require a BI 7.0 system:
      • Template 7.x - you have to specify the technical name of the BI template in the field BI Object Key.
      • Query Views 7.x - this is the generic template for query views; specify the query view name in the field BI Object Key.
      • Query 7.x - this is the generic template for queries; specify the query name in the field BI Object Key.
      • Info Provider 7.x - this is the generic template for info provider; specify the info provider name in the field BI Object Key.
      • Enterprise Report 7.x - you have to specify the technical name of the enterprise report in the field BI Object Key.
  • BI Object Key
    This identifies the object based on the BI Object Type.
  • Optional fields:
    • BI System
      This determines the Remote Function Call (RFC) Destination of a BI system. It is only needed if the report is not started in the default BI system. For more information, see Default BI RFC Destination.
  • If you would like to Set Up Cross Navigational Link please see below

 

Displaying the BW Report in CRM WebClient UI

  • Go to Transaction “CRMC_UI_NBLINKS” and choose “Define Logical Links”
  • To Create a New Logical Link, Enter the following Parameters:

 

Field

Field Value

Type

BI Report

Target ID

DISPLAY

Parameter

<BI Report ID>

Parameter Class

CL_CRM_GEN_UI_BI_UTIL

Title

<Title> 
This is what is displayed in the Navigation bar.

 


Figure: Logical Link for BI Report

  • Assign your Logical Link to a Direct Link or Work Center
  • Assign the Direct Link or Work Center to a Navigation Bar Profile
  • Go to Transaction “CRMC_UI_PROFILE” and assign the Nav. Bar Profile to a Business Role
  • Do not Forget to “Adjust” your Direct Link or Work Center to “Visible”


Display a BI Report Inside of a Web Client UI Framework Component

To display a BI report inside of a component, you must create a component usage for every BI report that you want to show. This allows you to use it anywhere where a reuse component can be used.

Create a Component Usage for the BI Report

Using the Framework Enhancement Concept, do the following:

  1. In the runtime repository editor, select Component Usages and choose Add Component Usage from the context menu.
  2. Enter the following parameters:

Field

Field Value

Id

<unique ID inside of your component>

Used Component

GSBIRP

Interface View

MainWindow

  1. The new component will now appear in Component Usages with the ID that you assigned to it.
  2. Navigate to Interface View under your new component, select Inbound Plugs, and choose Add Inbound Plug from the context menu.
  3. Add the inbound plug DISPLAY, as you need it to navigate inside of your component to the embedded BI report.


Figure: Usage Definition

Set BI Report ID to Component Usage

If the BI report is displayed without navigation (as part of a view set, an overview page, or a dynamic page) you must specify the parameter REPID inside of the method WD_USAGE_INITIALIZE. The method can be found in the Component Controller in the component workbench (transaction BSP_WD_CMPWB).

The following is an example of the code:

Syntax

METHOD wd_usage_initialize.

 

  DATA: bicontext TYPE REF TO cl_bsp_wd_context_node.

  CASE iv_usage->usage_name.

    WHEN 'ZBIREPORT_1'.

      TRY.

          bicontext = iv_usage->get_context_node( 'BIREPORT' ).

          bicontext->set_s_struct(

             attribute_path = '' component = 'REPID' value = 'ZSAMPLE6' ) .

        CATCH cx_root.

      ENDTRY.

  ENDCASE.

ENDMETHOD.

ZSAMPLE6 must be replaced with the BI Report ID.

If you want to navigate to the BI report, you can also pass a collection with the navigation (for example, a view that is called using an inbound plug). The collection can be created with the static method CL_CRM_GEN_UI_BI_UTIL ->CREATE_COLLECTION.
The following is an example of code that can be used in an event handler or outbound plug:

Syntax

DATA: lv_bo_coll TYPE REF TO if_bol_bo_col.

      lv_bo_coll = cl_crm_gen_ui_bi_util=>create_collection( 'ZSAMPLE7' ).

      view_manager->navigate( source_rep_view = rep_view

                              outbound_plug   = 'NAVLINK'

                              data_collection  = lv_bo_coll  ).

ZSAMPLE7 must be replaced with the BI Report ID you have defined in Basic Customizing.
NAVLINK must be replaced with the name of the navigational link in your component, that navigates to the BI Report Component.

Optional: Specify Additional Parameters

The SAP Business Information Warehouse (BW) Templates URL allows you to set variable values (similar to select options) and filter values. It also offers some additional settings that would allow you to, for example, skip the first screen in a navigation.
These URL parameters for 3.x BI Reports are specified in the BI Web API Reference (also available in a German Version). For 7.x you should read the BEx Web Documentation.

To use those parameters you would need to build a string with the additional parameters according to the BI documentation. The following is an example of how to filter on a specific country (given the report has a characteristics 0COUNTRY):

Syntax

DATA:

    lv_parameter TYPE string,

    lv_bo_coll TYPE REF TO if_bol_bo_col.

 

  lv_parameter = 'FILTER_IOBJNM=0COUNTRY&FILTER_VALUE=DE'.

  lv_bo_coll = cl_crm_gen_ui_bi_util=>create_collection(

      iv_id = 'ZSAMPLE7'

      iv_addparameter = lv_parameter

  ).

  view_manager->navigate( source_rep_view = rep_view

                              outbound_plug   = 'NAVLINK'

                              data_collection  = lv_bo_coll  ).

ZSAMPLE7 must be replaced with the BI Report ID as defined in Basic Customizing.
NAVLINK must be replaced with the name of the navigational link that navigates to the BI Report Component.

Optional: Specify RFC Destination for BI System

In some cases it may be necessary to determine the BI system at runtime, for example, if the customer has multiple systems. If this is required, you can specify the parameter BISYSTEM as the name of a Remote Function Call (RFC) destination (maintained in transaction SM59 under ABAP Connections) for the BI system. If set at runtime, the BI default destination or destination defined in Basic Customizing is overwritten.

You can set the parameter in two ways:

  • In method WD_USAGE_INITIALIZE using the first code sample in Set BI Report ID to Component Usage:

bicontext->set_s_struct( attribute_path = '' component = 'BISYSTEM' value = 'SYSCLNT###' ).

  • In navigation by changing the CREATE_COLLECTION method to the following:

lv_bo_coll = cl_crm_gen_ui_bi_util=>create_collection(

      iv_id = 'ZSAMPLE7'

      iv_bisystem = 'SYSCLNT###'

   ).

  • SYSCLNT### must be replaced with the name of the RFC destination or a variable that has the same name.

Show BI Report in Dynamic Pages

Once you have created a component usage for the BI report, you can use it in dynamic pages. The following dynamic pages can include component usages:

  • Overview Page
  • Work Center Page
  • Home Page
  • Report and Dashboard Page

 

Set Up Cross Navigational Links:

A cross navigational link is based on a characteristic's name (the technical name of an InfoObject) in SAP NetWeaver Business Intelligence (SAP NetWeaver BI). It is possible to define several cross navigational links for one InfoObject. You can make these settings in customizing. Choose Define Cross Navigational Links for InfoObjects. You can modify an existing cross navigational link or create a new entry.
To create a cross navigational link, you must define the following:

  • InfoObject
    This is the technical name of the characteristic that you want to navigate from.
  • Nav. Link ID
    This is the ID of the individual cross navigational link for a characteristic. Since you could define more than one entry per characteristic we need an identifier for separating these entries.
  • Sequence
    This is a number that is used to sort the menu entries within the BI report's context menu.
  • Object Type
    This is used to determine the target of the navigation. (see Cross Navigation)
  • Object Action
    This is used to determine the target of the navigation. (see Cross Navigation)
  • Object Key Name
    This is the name of the field that corresponds to the value that was selected in the BI report. In the above example, you clicked on a business partner in the BI report. This is typically the ID of a business partner (not the GUID), so you need to tell the framework that the value that is passed is an ID.
  • Menu Text
    This is the text that appears in the BI report's context menu.

The parameters Object TypeObject Action, and Object Key Name let the framework create the entity based on the value it receives from BI for the receiving component. (see Object Mapping)

For example, the business partner ID 01234567890 is selected in the BI report. The framework passes the value to the object mapper class to create a Business Object Layer (BOL) entity of the correct type based on that ID. The created entity is passed to the receiver.


Figure: Cross Navigation Definition

 

Using a Cross Navigational Link

To use a cross navigational link within a BI report, it must first be assigned to the report. You can do this is in the BI report customizing. Select a BI report ID and choose Assign Cross Navigation Links. You can modify an existing link assignment or create a new entry.


Figure: Cross Navigation Assignment

Report Replacement

This feature is made for customers who want to replace any delivered customizing. You can define BI report replacements in BI report customizing

Example
SAP delivers the BI report ID __TOP10_OPPORTUNITIES, which calls BI template 0TPLI_TOP10_Q0001_V01 (Note: this is not a real template name). The customer has created their own version of the BI template with name ZTPLI_TOP10_Q0001_V01. To display their version in the Web Client UI, the customer needs to define a report replacement.

First, the customer needs to create a copy of the basic customizing for the BI report ID TOP10_OPPORTUNITIES, for example, ZTOP10_OPPORTUNITIES. They change the BI Object Key to ZTPLI_TOP10_Q0001_V01 and save it.
Now the customer creates a new entry in Define BI Report Replacement of TOP10_OPPORTUNITIES to ZTOP10_OPPORTUNITIES.


Figure: Report Replacement



Common Issues:

First check if the issue exists BI Report Standalone using KBA  2472925If it does exist in the BI then it is not a CA-WUI-BI issue. Please check the Guided Answers for the correct component.

  1. RFC connections:
    1. Check RFC connection between CRM and BW (In SM59 + TEST)
    2. Check RFC user authorizations (In SM59 + menu Utilities-> Test -> Authorization)

  2. Logical System:
    1. Check CRMBWDEST is maintained as per SAP Note 1069281

  3. If using a web dispatcher or proxy for CRM and BI:
    1. Check SAP Note: 1242033 - BI report integration in complex system landscapes

  4.  If trusted connections are used:
    1. Check wiki Create an RFC trust relationship between 2 SAP systems

  5. BI system destination 'XXXXX' cannot be reached:

    1. Check that “Target system” is maintained correctly. Refer to SAP Knowledge Base Article 1934440 – 7x BW Reports & Templates are pointing to the wrong target system

    2. Using Portal:
      1. Check RFC connection between CRM and Portal as per SAP Knowledge Base Article 1898854

  6. Loading Bar:
    1. Check SAP KBA 1820992 if loading bar does not go away

  7. BI Reports are not High Enough:
    1. 2270585 Report Height is not updated in IE11 (Part 2)
    2. 2075571 BI report height adjustment bug in IE11
    3. If issues persist, check SAP Knowledge Base Article 1138613

  8. Domain Relaxation:
    1. Both CRM & BI have to be in the same domain. This done by cutting of the server name from the path of the server. For example: server.domain.com will be domain.com (please see SAP Note 1138613 for details).
    2. Both CRM & BI have to be in the same Security Zone.
    3. Both CRM & BI have to use the same protocol (HTTP or HTTPS).

  9. Internet Explorer:
    1. Check if IE is executed in Standard mode:
      1. Logon to CRM - WUI and select a Business Role.
      2. Press F12 (Developer Toolbar) and check the Document Mode value being passed.
      3. If it passes the Value as 11/10/Edge - It works in Standards mode of rendering
      4. If it passes the Value as 8 - It works in Compatibility mode of rendering
      5. If it passes the Value as 5 - It works in  Quirks mode of rendering
    2. IE9+ Standards Mode support, for BI integration in CRM:
      1. Refer to Note 2094302

  10. Error loading template 0TPLB_CRM*:

    1. The web template is not activated in the corresponding BW system see KBA 2501834.

  • No labels