Data Consistency Check with SAP NetWeaver BI Accelerator · The recording of reference data and the execution of the checks has to take place in ... 1.1 Activate Trace User with option

Data Consistency Check with SAP NetWeaver BI Accelerator For checking the consistency of data we recommend using the following reports and checks that exist in your SAP NetWeaver BI system:

1. Transaction RSTT: CATT traces of your TOP 10 business queries (scheduling of test jobs)

2. Transaction RSDDBIAMON2: Checks in the BIA consistency check center (scheduling of check set jobs e.g. in a process chain)

3. Checks in transaction RSRV (create packages and include them in a process chain)

1. Create a set of CATT traces in transaction RSTT Purpose When new software updates (e.g. support package stacks or new revisions for BIA) or critical notes are implemented in your system you could immediately verify the consistency of the data. Create reference data (REF mode) before you implement updates and compare it with same query executions (CHECK mode) after changes like the implementation of a BIA revision have taken place. A predefined SAP Business Content query immediately presents the results after execution of the test job in CHECK mode.

o Define Top10 business critical queries with selections and one navigation step e.g.

o Trace the queries o Create new reference data before the implementation of a new BIA revision

and/or BI SPS/SP o Execute the test job in CHECK mode o Compare the reference data with the results of the execution of the set of

traces Constraints

o No data changes (roll up, change runs etc.) have taken place between reference data registration and check execution

o The queries once have to return from database (first execution in trace tool always goes against database)

The recording of reference data and the execution of the checks has to take place in the same logon language.

SAP DEVELOPER NETWORK | sdn.sap.com © 2008 SAP AG 1

Steps First of all create traces for your TOP 10 queries with selections and maybe one navigational step. Open transaction RSTT. 1.1 Activate Trace User with option “Activation for Test Generation”

Goto RSRT and execute the first query with your selection and one navigational step.

The query is executed against the database and traced. Choose back back and traces


The list of traces with the generated ID can be found under Trace Tool Traces.


1.2 Goto CATTtool wizard Follow the wizard steps.


Change trace name and description and change trace type to OLAP trace.

Enter e.g. query variant and navigation step executed (it is not mandatory to enter something here).


No selections/changes are necessary here.

No selections/changes are necessary here.


Here you have to record the reference data.


Save the trace.


1.3 Create a test package

Select Trace IDs.


Choose playmode “D” (without aggregate) and save.


1.4 Create a job for the test package Choose trace type CATT Trace and Process Mode “REF”. Define a variant and the number of parallel processes.


Save the settings Go back and choose “execute”.


Now the reference data is recorded (execution against database) and can be used as data to be compared. 1.5 Check data Nevertheless you could compare the execution immediately against BIA to see if BIA returns the same data: Goto test packages change aggregate mode to “T” (= with BI Accelerator Index).


Goto Test Jobs and change the process mode to Check mode (Test Trace) execute test job.


1.6 Results The results of the comparison are shown in query 0RSTT_C01/0RSTT_C01_Q002.


Should you encounter derivations (Message type “Error”) Goto CATTtool CATT traces and choose the relevant trace. The relevant Trace ID which has shown errors can be found in the query by drilling down to field “Trace ID”.

For a detailed analysis of the derivations in transaction RSTT choose CATTtool and the trace ID you found in the query before check and change play settings to “with BI Accelerator Index” execute. In case of errors, an error list is displayed and can be analyzed further.



1.7 Further information on RSTT For further information on transaction RSTT please refer to note 998680 with attachments and to the official SAP documentation: http://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htm http://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htm


http://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htm




2. Checks in the BIA consistency check center Preparation Before you schedule consistency checks, please check and, if applicable, implement the following notes: 1026157 Extended BIA consistency checks 1085358 BIA check "Random Queries" creates great load 1095886 Checking the data consistency in BI Accelerator 1060387 Analysis with incorrect results in BIA queries 1147984 BIA random query check terminates with error message 1116249 BIA - Tolerance during test for floating point key figures 1163009 Using BIA in check center even if it has status "Inactive" 1170858 BIA Random Query check terminates:

CX_SY_CONVERSION_OVERFLOW 1174578 BIA Random Query Check zeigt Fehler an - Fehler im Check (not yet

translated) Definition of checks in the consistency check center Goto RSDDBIAMON2 Goto consistency checks


For details please refer to note 1026157 and the official SAP documentation: http://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htm As the checks compare data in detail most of them are time-consuming. Therefore we recommend to execute some general checks regularly as described here and to execute deeper analysis via checks only in case of incidents (see matrix). All check results are displayed in the logs. Available checks in the data consistency check center are:

o Data Comparison o Totals in BIA o Totals in BIA and DB o Random Queries o Index existence


http://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htm

In the first tab strip choose an InfoCube which contains master data that is regularly changed. Choose single tables to be checked (e.g. S/X/Y tables for one master data and the package dimension table).

This test compares the contents of each individual table with the contents of the corresponding index record-by-record. This check is only suitable for tables/indexes that do not have large amounts of data: Dimension tables, some SID, X, or Y tables, but normally not Fact tables. A table is not checked starting with a size of 10,000 records. In case you are using this check in case of an incident (suspicion of wrong data e.g.) with very large tables you might have to increase the parameter “maxlines” by using program RSDDTREX_ADMIN_MAINTAIN.


In tab strip “Totals in BIA” choose some of your important InfoCubes and check them with a percentage of 20% with a drill-down to an InfoObject with few characteristic values.


In tab strip “Totals in BIA and DB” select the same InfoCubes with the same small InfoObject but only with a percentage of 5%.


In tab strip “Random queries” choose 3-10 queries and an initial value.

In the check center in tab strip “random queries” the queries are executed against DB and BIA. Please use this check only after you have implemented note 1174578. Otherwise the result could show derivations between BI and BIA execution although the BIA values are correct.


With report RSDRT_INFOPROV_RANDOM_QUERIES you can execute the query that showed up with errors in the check protocol of the check center. Enter InfoCube, Start Value and number of query with errors. With option “Aggregate on /off” you switch between execution against database and execution against BIA.


In tab strip “Index Existence” the existence of the tables of the star schema of the selected InfoCubes is checked.

Should you mark the check boxes “execute after rollup/change run” please be aware that whole process chains for those actions will take longer. In fact time for rollup/change run stay the same. When the check e.g. contains 4 InfoCubes to be checked and the “Maximum Degree of Parallelization” is set to 4, the batch job will split up 4 dialog processes.


3. Checks in RSRV Please refer to the official SAP documentation to find the explanation for the different checks: http://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htm The RSRV checks as well as the check sets from the consistency check center can be scheduled via process chains. How to configure check sets and RSRV checks in process chains will be described in the following. How to configure check sets in a process chain Use the program RSDDTREX_INDEX_CHECK for configuring the check sets and including the same in the process chain.


http://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htm

Enter check set ID and create a variant. The check set can be included in a process chain.

Maintain variant.


Enter the variant value.


Check set is successfully included in a process chain.


How to configure RSRV tests in a process chain Create a test package for each RSRV check.

Save the package.

Configure the test package as a variant using program RSRV_JOB_RUNNER in SE38.


Select test package and create a variant. Now you can include it as an ABAP program process type in your process chains.


Logs The logs for the RSRV and consistency check center when scheduled via process chain can be found in transaction SLG1. RSRV-Checks Object: RSRV Subobject: BATCH Check Center Checks Object: RSDDTREX Subobject: TAGGRCHECK


Documents

Data Consistency Check with SAP NetWeaver BI Accelerator · The recording of reference data and the execution of the checks has to take place in ... 1.1 Activate Trace User with option