Show TOC

Using Analytic Queries for Operational Data ProvidersLocate this document in the navigation structure


For reporting and analysis on a TransientProvider derived from an operational data provider (ODP), you can either use an analytic query (query) as delivered for your operational analytics application or define a query of your own.


You create queries based on an ODP's TransientProvider in BEx Query Designer. Here, all available TransientProviders are displayed grouped in InfoAreas. An InfoArea name is derived from the application component that is assigned using the package assignment to the underlying search and analysis model. The InfoArea name for an ODP's TransientProvider is 2O<Name der Anwendungskomponente>. The InfoArea description is also derived from the application component. In the InfoArea hierarchy, application components are added to the first level as root nodes. They are sorted alphabetically here according to their technical name. At a deeper level in the hierarchy in the InfoArea tree, the tree structure of the application component hierarchy is displayed.

Im BEx Query Designer, the InfoObjects belonging to the TransientProvider are displayed under InfoProviders. The InfoObjects are displayed here structured by key figures and the dimensions (Data Part, Key Part and Unit) for the characteristics. The key dimensions contain the fields that are flagged as key fields in the ODP or in the associated nodes in the search and analysis model. You can also see the division into key figures and characteristic dimensions in the TransientProvider preview. More information: Displaying the TransientProvider Preview.

Like with query definition for a BW InfoProvider, all authorization-relevant characterstics must also be available in the queries on TransientProviders. As with queries for BW InfoProviders, you can also use variables with processing type Authorization.


You can execute the query directly in Query Designer in SAP Business Explorers or in BI tools that use analytic queries as the query layer.

Query Behaviour When Using SAP HANA or SAP NetWeaver BWA

When the query accesses the data, a distinction is made between transaction data access and master data access:

  • During transaction data access, key figures are determined, and the participating operational data Providers are read. Depending on the query, these are transaction data ODPs and/or master data ODPs. Master data ODPs are read for transaction data access if they provide navigation attributes or are used for temporal joins, or if master data reporting is being performed.

  • During master data access, the texts and display attributes are read for the keys that were determined during transaction data access.

The query behaviour when using SAP HANA or SAP NetWeaver BWA (BWA) depends on whether the access is transaction data access or master data access.

Is the index used in the query?

If you use SAP HANA or BWA, you can check the Currentness of Data/Data Integrity property while executing the query to see whether the data is being read from SAP HANA or BWA or by direct access: If master data access is made from SAP HANA or BWA, the Currentness of Data/Data Integrity property in the query displays the time stamp from the most recent indexing. Otherwise, the time stamp displays the time when the query was executed.

When is the index used?

Whether SAP HANA or BWA is used in the query depends on whether all required indexes have been created. For transaction data accesses, these are the indexes for the transaction data ODPs and/or master data ODPs (for navigation attributes, temporal joins or master data reporting. You can tell which master data ODPs contribute navigation attributes or temporal joins by checking if the symbol for navigation attributes () or temporal joins () is displayed for the characteristics in question in the TransientProvider preview.

For transaction data accesses, the system also checks whether the query's static filter is contained in the selections for the relevant indexes. Only then will the SAP HANA or BWA be used for transaction data access. Checking the static filter (characteristic restrictions in the query) rather than the dynamic filter (default values for the query) ensures that either SAP HANA, BWA or direct access is used consistently in any given session for reading transaction data while navigating in a query.

For master data accesses (display attributes and texts), the index is always used if created. The query selections are not checked here.

More information: Defining Selections for Indexing.

How can the query behaviour be changed?

You can change the query behaviour and define that the query reads the current transaction data by direct access instead of reading the data from SAP HANA or BWA. To do this, open BEx Query Designer and set the Request Status (Currentness of Data/Data Integrity) property in the properties of the query on the Extended tab page to a value with a technical name that is greater than 1.

As an alternative to setting this value directly in BEx Query Designer, you can use a variable for the request status. Set the variable value for the request status to "X". The transaction data is then read by direct access.


Note that these settings do not affect master data accesses for display attributes and texts.

For more information about the request status, the documentation for BEx Query Designer, under Specifying Data Integrity.

How can the query behaviour be checked without using indexes?

For support purposes, a setting can be made in the Query Monitor (transaction RSRT) so that the use of all indexes (for both transaction data and master data access) is deactivated fro a session. To do this, run the query in debugging mode and select Do Not Use BWA.

More Information

For more information about creating queries, see the documentation for BEx Query Designer.

For more information about authorizations, see Authorizations in the Analytic Query.

For more information about variables, see Variables in the Analytic Query.