Specifying Data Integrity

Using the Data Integrity setting on the Advanced tab, you can select how recent the data for an InfoProvider is to be when displayed.

This setting is applied to all InfoCubes and VirtualProviders that have implemented interface IF_RSD_DELTACACHE_SUPPORT and to all MultiProviders that contain the corresponding InfoCubes or VirtualProviders. For other InfoProviders (such as DataStore objects, master data, and InfoSets), the values of this field have the same effect.

In an InfoCube, the system can read data with different request statuses. You make this setting in the context menu of the rows in the table view of the InfoCube. The following request statuses are possible:

• Green: Request loaded successfully
• Yellow: Request not loaded successfully (still loading)
• Red: Request not loaded successfully

Assuming the option is supported for the InfoProvider, select the required setting for the Data Integrity option in the query properties on the Advanced tab.

You can either select a fixed requests status or define a variable. The procedure is the same as described for Query Properties.

The following options are supported for InfoProvider data integrity:

• All InfoProviders Up to Released Status (RQTS0) (0)

  The system reads all data rolled up in the BW Accelerator index or in the aggregates. If there is no BW Accelerator index or if there are no aggregates, all data up to the first incorrect request or open request is used. This is the default setting for queries.

• Real-Time InfoCubes up to Current Version (1)

  In addition to the All InfoProviders up to Securely Accessible Status (RQTS0), for real-time InfoCubes, the system also reads the data up to and including the first open request.

  Note

  The "Real-Time InfoCubes up to Current Version" setting should be used for queries that are based on a MultiProvider for example, which contains the plan data in a real-time InfoCube and contains the actual data in a standard InfoCube.

• All InfoProviders Up to Current Version (to Qualok) (2)

  The system also reads:

  • requests for an InfoCube with aggregates that are not yet rolled up, provided that these requests are from before the first incorrect request.
  • the missing requests (in the InfoCube) from the change log of the DataStore object (for a HybridProvider based on a DataStore Object).
  • the missing data (in the InfoCube) of the VirtualProvider (for a HybridProvider based on direct access). With delta-enabled VirtualProviders, the delta (changed data) is read and with non delta-enabled VirtualProviders, all the data is read.
• All InfoProviders Up to Current Version (All Green Requests) (3)

  The system reads all requests that have no errors (all green requests); this includes requests created after requests with errors or requests that were not completed.

• Every InfoProvider in MultiProvider According to its Setting (7)

  The system reads the data from all InfoProviders of a MultiProvider according to their request statuses. This setting is only possible for MultiProviders.

• All InfoProviders Complete (Red Requests as Well) (9)

  The system reads all available data; all incorrect requests and all open requests for a query are included.

  Note

  Data integrity "0" offers the best performance. In all other modes, the data from aggregates and data that has not been not rolled up is read from the fact tables of the InfoCube.

  Caution

  Note that only two of the request statuses mentioned are available for variables. This increases usability for the end user:

  • Read Current Data: This corresponds to the setting All InfoProviders Up to Current Version (to Qualok) (2).
  • Standard: This corresponds to the setting Real-Time InfoCubes up to Current Version (1).

More information: SAP Note 1136163.

Specific rules apply to CompositeProviders; see CompositeProvider.