Start of Content Area

BI Accelerator (New)  Locate the document in its SAP Library structure

Technical Data

Function is

New

For Release

Software Component

●      Component: SAP NetWeaver

●      Release: 7.0

Assignment to Application Component

BW-BEX-OT OLAP Technology

Country Setting

Valid for all countries

Use

BI accelerator is used to improve the read performance of BI queries on InfoCubes. It enables quick access to any data with a low amount of administrative effort and is especially useful for sophisticated scenarios with unpredictable query types, high data volume and high frequency of queries.

BI Accelerator Index and BI Accelerator Server

A BI accelerator index is a redundant data store of a BI InfoCube on the BI accelerator server. The BI accelerator server is a specific part of the server for the SAP NetWeaver Search and Aggregation Engine (TREX). The data from the BI InfoCube is located in the BI accelerator index in a compressed but not aggregated form. This means that the BI accelerator index contains the data in the same granularity as the InfoCube.  With an active BI accelerator index, BI queries do not read the data from the database; instead they read it from the BI accelerator server.

Aggregation, filtering, selection and certain cell-based sorts from the analytical engine are performed by the BI accelerator engine in the BI accelerator server during query runtime.

Maintenance Processes for BI Accelerator Indexes

Because a BI accelerator index, like the relational aggregates, is a redundant downstream data source to improve query performance, the maintenance processes are based on the usual processes of aggregate maintenance in the previous SAP NetWeaver ’04 and earlier SAP BW Releases, or are integrated into them. The amount of effort required for converting relational aggregates into BI accelerator indexes is thus quite low.

Constraints

A BI accelerator index is only possible for InfoCubes with cumulative key figures, not for InfoCubes with non-cumulative key figures.

 

Effects on Existing Data

You can continue to also have relational aggregates for an InfoCube for which you have created a BI accelerator index. However, since queries always access the BI accelerator index first, this modeling is not worthwhile.

Effects on Customizing

Initial Settings

Communication between the BI system and the BI accelerator server takes place using RFC modules. In order to connect a BI accelerator server to the BI system, first you have to maintain the following settings for the RFC destination:

●      Set up the RFC destination for the BI accelerator server (transaction SM59)

●      Set the RFC destination for the BI accelerator server (transaction RSADMIN, the parameter ”HPA RFC Destination” has to correspond to the above RFC destination)

Note on System Landscape

Only one BI accelerator server can be used for each BI system. This is because the master data tables stored in the BI accelerator server can be used by multiple BI accelerator indexes. However, this does not work if the data is distributed across various BI accelerator servers.

However, various BI systems can store their data on the same BI accelerator server and access it there as long as there is enough room on the server. It is thus not necessary for each BI system in the productive landscape to have its own BI accelerator server. The system ID is used to keep the indexes separate.

 

For more information, see Customizing under SAP Customizing Implementation Guides ® SAP NetWeaver ® SAP Business Intelligence ® Connection of TREX:

●      Installation of TREX search engine

●      Creation of an RFC destination in the BI system for the TREX search engine

 

 

End of Content Area