Beruflich Dokumente
Kultur Dokumente
BI Accelerator
For checking the consistency of data we recommend using the following reports and
checks that exist in your SAP NetWeaver BI system:
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.
First of all create traces for your TOP 10 queries with selections and maybe one
navigational step.
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.
Enter e.g. query variant and navigation step executed (it is not mandatory to enter
something here).
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).
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.
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/ed1942bcb35433e10000000a155
106/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/42/ed1942bcb35433e10000000a155
106/frameset.htm
Preparation
Before you schedule consistency checks, please check and, if applicable, implement
the following notes:
http://help.sap.com/saphelp_nw70/helpdata/EN/45/f9d95d34c606f7e10000000a1553
69/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.
o Data Comparison
o Totals in BIA
o Totals in BIA and DB
o Random Queries
o Index existence
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 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.
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.
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.
http://help.sap.com/saphelp_nw70/helpdata/EN/6b/cda64246c6c96ae10000000a155
106/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.
Use the program RSDDTREX_INDEX_CHECK for configuring the check sets and
including the same in the process chain.
Maintain variant.
Now you can include it as an ABAP program process type in your process chains.
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