DataAndConsistencyChecks_RSTT

8/8/2019 DataAndConsistencyChecks_RSTT

1/33

Data Consistency Check with SAP NetWeaverBI Accelerator

For checking the consistency of data we recommend using the following reports andchecks 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 processchain)

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 theconsistency of the data.

Create reference data (REF mode) before you implement updates and compare itwith same query executions (CHECK mode) after changes like the implementation ofa BIA revision have taken place. A predefined SAP Business Content queryimmediately presents the results after execution of the test job in CHECK mode.

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

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

and/or BI SPS/SPo Execute the test job in CHECK modeo 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 betweenreference data registration and check execution

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

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

SAP DEVELOPER NETWORK | sdn.sap.com

2008 SAP AG 1


2/33

Steps

First of all create traces for your TOP 10 queries with selections and maybe onenavigational 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


2008 SAP AG 2


3/33

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


2008 SAP AG 3


4/33

1.2 Goto CATTtool wizard

Follow the wizard steps.


2008 SAP AG 4


5/33

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 entersomething here).


2008 SAP AG 5


6/33

No selections/changes are necessary here.

No selections/changes are necessary here.


2008 SAP AG 6


7/33

Here you have to record the reference data.


2008 SAP AG 7


8/33

Save the trace.


2008 SAP AG 8


9/33

1.3 Create a test package

Select Trace IDs.


2008 SAP AG 9


10/33

Choose playmode D (without aggregate) and save.


2008 SAP AG 10


11/33

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.


2008 SAP AG 11


12/33

Save the settings Go back and choose execute.


2008 SAP AG 12


13/33

Now the reference data is recorded (execution against database) and can be used asdata to be compared.

1.5 Check data

Nevertheless you could compare the execution immediately against BIA to see if BIAreturns the same data:

Goto test packages change aggregate mode to T (= with BI Accelerator Index).


2008 SAP AG 13


14/33

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


2008 SAP AG 14


15/33

1.6 Results

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


2008 SAP AG 15


16/33

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

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


2008 SAP AG 16


17/33


2008 SAP AG 17


18/33

1.7 Further information on RSTT

For further information on transaction RSTT please refer to note 998680 withattachments 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


2008 SAP AG 18
http://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155106/frameset.htm


19/33

2. Checks in the BIA consistency check center

Preparation

Before you schedule consistency checks, please check and, if applicable, implementthe following notes:

1026157 Extended BIA consistency checks1085358 BIA check "Random Queries" creates great load1095886 Checking the data consistency in BI Accelerator1060387 Analysis with incorrect results in BIA queries1147984 BIA random query check terminates with error message1116249 BIA - Tolerance during test for floating point key figures1163009 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 yettranslated)

Definition of checks in the consistency check center

Goto RSDDBIAMON2 Goto consistency checks


2008 SAP AG 19


20/33

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. Thereforewe recommend to execute some general checks regularly as described here and toexecute deeper analysis via checks only in case of incidents (see matrix). All checkresults are displayed in the logs.

Available checks in the data consistency check center are:

o Data Comparisono Totals in BIAo Totals in BIA and DBo Random Queries

o Index existence


2008 SAP AG 20
http://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a155369/frameset.htm


21/33

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

This test compares the contents of each individual table with the contents of thecorresponding index record-by-record. This check is only suitable for tables/indexesthat 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,000records.

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 usingprogram RSDDTREX_ADMIN_MAINTAIN.


2008 SAP AG 21


22/33

In tab strip Totals in BIA choose some of your important InfoCubes and check themwith a percentage of 20% with a drill-down to an InfoObject with few characteristicvalues.


2008 SAP AG 22


23/33

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


2008 SAP AG 23


24/33

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 althoughthe BIA values are correct.


2008 SAP AG 24


25/33

With report RSDRT_INFOPROV_RANDOM_QUERIES you can execute the querythat showed up with errors in the check protocol of the check center.

Enter InfoCube, Start Value and number of query with errors. With option Aggregateon /off you switch between execution against database and execution against BIA.


2008 SAP AG 25


26/33

In tab strip Index Existence the existence of the tables of the star schema of theselected InfoCubes is checked.

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


2008 SAP AG 26


27/33

3. Checks in RSRV

Please refer to the official SAP documentation to find the explanation for the differentchecks:

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 canbe scheduled via process chains. How to configure check sets and RSRV checks inprocess 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 andincluding the same in the process chain.


2008 SAP AG 27
http://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155106/frameset.htm


28/33

Enter check set ID and create a variant.

The check set can be included in a process chain.

Maintain variant.


2008 SAP AG 28


29/33

Enter the variant value.


2008 SAP AG 29


30/33

Check set is successfully included in a process chain.


2008 SAP AG 30


31/33

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 inSE38.


2008 SAP AG 31


32/33

Select test package and create a variant.

Now you can include it as an ABAP program process type in your process chains.


2008 SAP AG 32


33/33

Logs

The logs for the RSRV and consistency check center when scheduled via processchain can be found in transaction SLG1.

RSRV-Checks

Object: RSRVSubobject: BATCH

Check Center Checks

Object: RSDDTREXSubobject: TAGGRCHECK

DataAndConsistencyChecks_RSTT

Documents

Transcript of DataAndConsistencyChecks_RSTT