Show TOC

Configuring Operational Data ProvisioningLocate this document in the navigation structure

Use

Before you can use operation data provisioning, you must first configure the relevant settings. The use of SAP HANA or SAP NetWeaver Business Warehouse (BWA) is optional. If you are using SAP HANA or BWA for operational data provisioning, you need to perform additional configuration steps.

Prerequisites
  • You have installed the usage types AS ABAP and BI ABAP.

  • If you want to index data for better analysis performance, you must have installed SAP HANA or SAP NetWeaver BW Accelerator 7.2.

    Note

    Be aware of the licensing conditions when using SAP HANA products.

Procedure

To configure operational data provisioning on your system, perform the following steps:

  1. Make the following general settings that you need to use the embedded search. You can find the following settings in Customizing under Start of the navigation path Search and Operational Analytics Next navigation step General Settings for Operational Analytics and Embedded Search End of the navigation path:

    Note

    Once you have configured the general settings for the embedded search, go straight to the next step and configure the specific settings for operational data provisioning.

    1. Assign the SAP_ESH_LOCAL_ADMIN role to the administrator. This role contains the authorizations required to configure and manage Embedded Search and operational data provisioning.

      For more information, see Customizing.

    2. Activate the required Web dynpro services.

      More information: Activating Web Dynpro Services

    3. Optional: If you want to use SAP HANA or BWA, configure the connection and indexing settings as follows:

      1. Create a connection between the ABAP system and the SAP HANA and enter it as the TREX destination in Customizing.

        • For SAP HANA, you need a database connection. Enter the database connection as a TREX destination using the following format: :DB:<name of database connection> (for example, :DB:HANA_ODP).

        • For the BWA, you need an RFC connection to the ABAP system.

        For more information, see Customizing under Creating a Connection Between the Embedded Search and TREX/BWA.

      2. Optional: Define the server group for indexing jobs.

        For more information, see Customizing.

      3. Specify the user to be used for the indexing tasks in real time.

        For more information, see Customizing.

  2. If you want to use operational data provisioning without SAP HANA or SAP NetWeaver BW Accelerator, navigate to Customizing and enter NO TREX as the TREX destination. Operational data providers without SAP HANA or BWA can only be used if this destination is specified.

    For more information, see Customizing under Start of the navigation path Search and Operational Analytics Next navigation step General Settings for Operational Analytics and Embedded Search Next navigation step Configuring TREX and Indexing Next navigation step Specifying a TREX Destination End of the navigation path.

  3. You perform the basic configuration for operational analytics in Customizing. Use the basic configuration report to specify the BW client and activate the required technical content.

    The following prerequisites are required to perform the basic configuration:

    • It must be possible to maintain cross-client objects from the SAP repository.

    • The namespaces with the prefixes /BI0/ and /BIC/ must be flagged as changeable.

    For more information, see Customizing under Start of the navigation path Search and Operational Analytics Next navigation step Operational Data Provisioning for Operational Analytics Next navigation step Basic Configuration for Operational Analytics End of the navigation path.

  4. In Customizing, specify the modeling client that you want to use as the client for ODP metadata access. Enter an RFC destination that points to this client.

    For these settings, you need the transaction authorization (S_TCODE) for Customizing transaction RODPS_ODP_IMG.

    Note

    ODP metadata is automatically read from the BW client, provided that no modeling client is specified in Customizing.

    More information can be found in Customizing under Start of the navigation path Search and Operational Analytics Next navigation step Operational Data Provisioning for Operational Analytics Next navigation step Specifying a Modeling Client End of the navigation path.

Result

Once you have completed all of the configuration steps, you need to perform further settings to be able to use operational data provisioning for operational analytics. More information: Operational Analytics with Operational Data Provisioning.