Data Integrity Profile

The data integrity profile provides you with an easy way of testing the data integrity of a query, without the need to make separate expert data integrity or request status settings in the read mode, cache mode, cache usage mode and the InfoProvider grouping.

You can choose from the following profiles:

• ' ': Standard: No Profile (expert settings are used)

  The behaviour of the query is tested using the expert settings.

• 'G': Guaranteed Stable Data from Start of Query

  We only recommend this mode for queries with very few characteristics and restricted navigation, as it can take up a large amount of memory on the BW application server. It can even cause the query to terminate.

  If you choose this profile, the query will always show the data from when the query starts. When called for the first time, the system transfers a data snapshot of the query - which is requried for all possible drilldowns or navigation - to a memory segment of the BW application server. Every subsequent navigation step in the query is only performed on the transferred data set.

  Note that the initial reply time can be very long, as a snapshot of the data has to be created when the query starts. The system uses read modeQuery to Read All Data at Once (A).

  Restriction

  The following restrictions apply:

  • This setting is not possible for queries on InfoProviders that contain an aggregation level.

  • BW integrated planning is not possible in this mode.

  • It is not possible to add free characteristics in this mode.

  • It is not possible to use Operations in SAP HANA / BWA in this mode (with the exception of Optimized Access).

  • Whenever variables belonging to the query's static filter are changed, the system creates a new snapshot.

• 'S': Stable Data from Start of Query

  This mode offers stable data with adequate performance.

  DataStore objects (advanced) with modeling property All Characteristics are Key, Reporting on Union of Inbound and Active Table and InfoCubes are read with data integrity mode (or request status) All InfoProviders Up to Released Status (RQTS0). If InfoProviders cannot read old datasets, navigation steps could fail, and it might be necessary to set the Operations in SAP HANA / BWA option to Optimized Access mode. The system then changes the read mode from Query to read when you navigate or expand hierarchies (H) to Query to read during navigation (X).

  Restriction

  The following restrictions apply:

  • This setting is not possible for queries on InfoProviders that contain an aggregation level.

  • BW integrated planning is not possible in this mode.

• ‘P': Provider-Specific: Plannable (or transactional) InfoProviders with current data

  This mode implicitly offers the standard behaviour for the system, which is always applied if no expert settings are changed.

  InfoProviders that can read old datasets are read the same way as in profile 'S'.

  Plannable (or transactional) InfoProviders are read with data integrity mode (or request status) Real-Time InfoCubes up to Current Version. For plannable (or transactional) InfoProviders and InfoProvider that cannot read old datasets, cached data is used if available. If not, current data must be read. The Operations in SAP HANA / BWA option is not adjusted. If InfoProviders cannot read old datasets, the read is changed from from Query to read when you navigate or expand hierarchies (H) to Query to read during navigation (X).

• ‘C': Consistent Current Data

  This mode returns current data every time a new list is calculated. Operations that cause a new list to be calculated are all operations that affect the entire list. These include filters, changing characteristic properties, and changing the settings for row and column axese.

  Whenever hiearchy nodes are expanded or collapsed, the system keeps new numbers consistent with the numbers that are already in the list.

  DataStore objects (advanced) with modeling property All Characteristics are Key, Reporting on Union of Inbound and Active Table and InfoCubes are read with data integrity mode (or request status) All InfoProviders Up to Current Status (Qualok). Plannable (or transactional) InfoProviders with current data are read with data integrity mode (or request status) Real-Time InfoCubes up to Current Version. If InfoProviders cannot read old datasets, this can cause the system to change the Operations in SAP HANA / BWA option to Optimized Access mode, and to change the read mode from Query to read when you navigate or expand hierarchies (H) to Query to read during navigation (X).

• ‘M': Current Data

  This mode always displays new data and does not keep the data consistent in a list displayed if you drill down in the list.

  DataStore objects (advanced) with modeling property All Characteristics are Key, Reporting on Union of Inbound and Active Table and InfoCubes (including plannable InfoCubes) are read with data integrity mode (or request status) All InfoProviders Complete (Red Requests as Well). The Operations in SAP HANA / BWA option can be used without restrictions.

• ‘D': Uncleansed Data

  This mode behaves the same as 'M', but deactivates the cache in the Analytic Manager. The reply time can therefore be very long.