Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Overview (BW75)

Basically the Data Integrity Profile defines how the query should behave when the underlying data is changed during query navigation. The data integrity profile provides you with an convenient way to choose a certain behavior without the need to make separate expert settings in the read mode, cache mode, cache usage mode and the InfoProvider grouping. The setting can be changed in transaction RSRT and the Query Tool of the HanaStudio, see screenshots.

You can choose from various profiles(see Data Integrity Profile):

  • ' ': Standard: No Profile (expert settings are used)
  • 'G': Guaranteed Stable Data from Start of Query
  • 'S': Stable Data from Start of Query
  • ‘P': Provider-Specific: Plannable (or transactional) InfoProviders with current data
  • ‘C': Consistent Current Data
  • ‘M': Current Data
  • 'D': Uncleansed Data

the most important ones are

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

In this case you can change the seperate experts setting as desired. The default settings are

  • Read Mode:  H
  • Cache Mode:  D
  • Cache Usage Mode: ' ':  data from query start if possible, otherwise current data
  • Update Cache Objects in Delta Process: Yes

With these settings the following happens(during query navigation) when a request is deleted or added to the provider, respectivelly.

Example: The last request(available for reporting) in a Cube has the number 10.

  • Request (11) Added
    • - if propper cache object exists, it is used(so , old data up to request 10 is displayed)
    • - in case there is no cache object, the query accesses the database but only retrieves the data for all requests less or equl to 10.
    • - query restarted: current data is displayed; query used old cache object and retrieved only the data from the new request from the db(this delta is then merged with the old cache object)
  • Request (5) deleted(or selective deletion used)
    • - if propper cache object exists, it is used(so, data,including the deleted request 5, up to request 10 is displayed)
    • - in case there is no cache object, the query terminates with error: Data deleted from InfoProvider... Read request cannot be executed(DBMAN 027).
    • - query restarted: current data is displayed; query retrieved data from the database(old cache object got invalidated)
'G': Guaranteed Stable Data from Start of Query

In this case, the query always shows data from query start. When called for the first time, the query transfers a data snapshot required for all possible drilldowns / navigations(may cause performance/memory issues!) into a OLAP cache object. Every subsequent navigation of the query will the work on the cache object.

Derived Query Properties

  • Read Mode:  A  <- !
  • Cache Mode:  D
  • Cache Usage Mode: S:  Always display data from query start(stable data)
  • Update Cache Objects in Delta Process: Yes

With these settings the following happens(during query navigation) when a request is deleted or added to the provider, respectivelly.

Example: The last request(available for reporting) in a Cube has the number 10.

  • Request Added
    • if propper cache object exists, it is used(so , old data up to request 10 is displayed)
    • in case there is no cache object, the query accesses the database but only retrieves the data for all requests less or equl to 10.
    • query restarted: current data is displayed; query used old cache object and retrieved only the data from the new request from the db(this delta is then merged with the old cache object)
  • Request 5 deleted(or selective deletion used)
    • if propper cache object exists, it is used(so, data,including the deleted request 5, up to request 10 is displayed)
    • in case there is no cache object, the query terminates with error: Data deleted from InfoProvider... Read request cannot be executed(DBMAN 027).
    • query restarted: current data is displayed; query retrieved data from the database(old cache object got invalidated)
‘C': Consistent Current Data

This mode offers current data each time a new list is calculated, while keeping the list consistent. Operations that trigger calculation of a new list are all operations like for example filtering, changing characteristic properties, changing the setup of row or column axis.

Derived Query Properties

  • Read Mode:  H
  • Cache Mode:  D
  • Cache Usage Mode: C:  Always display current data
  • Update Cache Objects in Delta Process: Yes

With these settings the following happens(during query navigation) when a request is deleted or added to the provider, respectivelly.

Example: The last request(available for reporting) in a InfoCube has the number 10.

  • Request Added
    • if proper cache object exists, it is used but the delta(data from new request retrieved from db) is added. The (Yellow) result rows are recalculated as well.
    • in case there is no cache object, the query accesses the database and retrieves the data for all requests(including the new one).
    • if a hierarchy node is expanded, the system retrieves only the corresponding delta(ReadMode H) and does not include the new data. Only when the entire hierarchy is expanded to a certain level, the new request is taken into account.
    • query restarted: current data is displayed; query used old cache object(if proper existed) and retrieved only the data from the new request from the db(this delta is then merged with the old cache object)
  • Request 5 deleted(or selective deletion used)
    • if propper cache object exists, it is used(so, data,including the deleted request 5, up to request 10 is displayed)
    • in case there is no cache object, the query terminates with error: Data deleted from InfoProvider... Read request cannot be executed(DBMAN 027).
    • query restarted: current data is displayed; query retrieved data from the database(old cache object got invalidated)
‘D': Dirty Data - no caching

This mode switches off the OLAP cache which can lead to a long query runtime. Normal and transactional InfoCubes are read with data integrity '9 including red requests'. Use of operations in BWA/HANA is not limited.

Derived Query Properties

  • Read Mode:  H
  • Cache Mode:  I (cache is inactive)
  • Cache Usage Mode: unassigned
  • Update Cache Objects in Delta Process: No

With these settings the following happens(during query navigation/refresh) when a request is deleted or added to the provider, respectivelly.

Example: The last request(available for reporting) in a InfoCube has the number 10.

  • Request Added
    • in this case there is never a cache object, the query accesses the database and retrieves the data for all requests(including the new one even when the request status is 'red').
    • query restarted: current data is displayed;
  • Request 5 deleted(or selective deletion used)
    • in this case there is never a cache object, the query displays the new data along with the warning: Data has been deleted from InfoProvider...reporting continous(DBMAN 028).
    • query restarted: current data is displayed; query retrieved data from the database.

Remarks

Aggregation Levels: Aggregation Levels cannot be controlled by the data integrity profile. Therefore, if the query is defined directly on an aggregation level, the data integrity profile settings are not offered at all. If it is defined on a multiprovider that contains an aggregation level, the settings are only applied to the partproviders that are not aggregation levels. In queries on multiproviders containing aggregation levels the data integrity profiles 'G: Guaranteed Stable Data from Query Start' and 'D: Dirty Data' are not offered.

BW74 and Request Deletion: The description from above is only valid for BW75 systems(and higher releases). In BW74, the query does not detect any data deletions. Hence, instead of the error 'Data deleted from InfoProvider....' the query displays the current data without warning. This can lead to incorrect query results - see Example.

Documentation

See F1 help to this setting in transaction RSRT and SAP Online documentation

Data Integrity Profile

SAP Consulting Notes

2385259 Data Deletion and Data Integrity Profile

1136163 RSRT query settings -> properties 

 

 

  • No labels