With this function you verify whether the data that you loaded in the InfoCube is free of errors. You have the option of reporting on recently loaded requests.
With a few restrictions, you can execute queries on the InfoCube, by selecting navigation attributes, characteristics and key figures of the InfoCube, which you want to appear in the display. You can also specify characteristics and navigation attributes if necessary.
The InfoCube content maintenance is divided up into 3 areas:
1. Restrictions for the characteristics and navigation attributes
2. Selecting the field of the characteristics and key figures for the output list
3. Additional options
If the InfoCube is too large, you must make a preselection of the characteristics, navigation attributes and key figures. You can only choose the selected objects, or specify them for these restrictions.
Using the InfoCube Contents pushbutton you can display the contents of the InfoCube on the Contents tab page.
You can use all characteristics, navigation attributes and key figures for the selection. You determine the characteristics and key figures that are to be displayed in the output list. Aggregation is carried out using the characteristics that you do not want in the list.
With this function you can check how the data is stored on the database. The data is displayed in the format which they take on the database.
The date is displayed on the database in the format 19991230 while it is displayed as 12.30.1999 in BW (this depends on the settings made in the user master record).
A currency key figure has 2 decimal places on the database. Since some currencies have a different number of decimal points, the values are saved accordingly on the database. 1000 lira would, for example, be saved as 10.00 lira, abut 1000 USD would be 1000.00 USD.
The conversion is switched off by default.
You determine whether defined aggregates are to be used for the InfoCube when staging the list output. If you choose Use Materialized Aggregates, the request is not executed directly on the fact table, but aggregate tables that you created are used instead and the performance is improved. You can also use this option to check the consistency between the fact table and the aggregation table.
Deactivate this option if you want to check the data in the fact table.
With this option you specify if you want all the records that agree in your key to be grouped together, or whether each record should be written separately.
Deactivate this option if you want to check individual records and the exact content of the database.
With the Maximum number of hits, you determine what maximum quantity of data is returned. This is important if you have very large InfoCubes and want to avoid, for example, millions of records being returned.
If you have activated the option DB aggregation, several records are taken from the database and brought together in one row of the list. If you choose the option ‘Output number of hits’ then an additional key figure is generated in the output list that shows from how many records the respective record has been taken, i.e. how many data records it took to produce the output record.
You can also use this option to determine how many records are in a particular selection condition in the InfoCube. Enter a selection condition, but do not select any characteristics or key figures. In the return list you then only get the column Row Count with the number of hits and the number of entries that match this selection condition.
When uploading master data these are initially stored in the modified version. Only after activating the master data are these older entries replaced and the new ones can be used in the BEx Analyzer for Reporting. If you choose Modified structures, you can already check at this point how the data would look in Reporting once activated.
Using Key date for time-dependent characteristics, you determine at which time you want to read time-dependent master data. The current date is entered as default.
The attribute values for a characteristic are valid from 01.01.2000 until 06.01.2000, after which time the attributes have new values. If you choose the key date between 01.01.2000 and 06.01.2000, you get a different result in the list output than if you choose a later date.
In support of the debugging function, you can display the SQL query, which is generated according to the field selection and restrictions, and sent to the database. The SQL query is displayed in an Editor.
For each query the database optimizer can decide on how it collects data. To understand exactly what the database optimizer does, you can display the run schedule.
You can, for example, determine whether the database uses indices for procuring data with a particular selection, or whether it reads the entire table.