When you load new data packages (requests) into the InfoCube, these are not immediately available in reporting for use in an aggregate. In order to supply the aggregate with the new InfoCube data, you first have to load these into the aggregate tables for a set time frame. This process is known as roll up.
New data packages (requests) have been loaded into an InfoCube.
Aggregates for this InfoCube have been activated and filled with data.
In InfoCube maintenance, you can specify how the data packages are rolled up in the aggregate. You can do this on an InfoCube-by-InfoCube basis.
You are in the Data Warehousing Workbench in the Modeling functional area. In the context menu of the required InfoCube, choose Manage.
The system copies the InfoCube data into the table at the top of the screen.
To optimize data load performance, you can specify that you want to automatically delete indexes before the load operation and recreate them when the data load is complete. You do this on the Performance tab page. Building indexes in this way accelerates the data load process, although it has a negative impact on system performance when the data is read. Only use this method if no read process takes place during the data load.
If you want to switch on index building during roll up anyway, choose Create Index (Batch) and select the required options: Delete InfoCube Indexes Before Each Data Load and then Refresh or Also Delete and then Refresh Indexes with Each Delta Upload.
Type of Execution |
Procedure |
Include roll-up of the data packages as a process in a process chain Recommendation
We recommend use in a process chain · with complex schedules · where there are difficulties with automations and event collectors · for all new development |
|
Start data package rollup manually Note
Use this procedure especially when the data from several data packages create a logical unit, and they therefore only need to be released. Note
Different plants deliver their data at different points in time. The data needs to be visible first, however, in the InfoCube if all plants have loaded their data into the InfoCube. |
|
The following procedures are also possible but should not be used for new scenarios.
Type of Execution |
Procedure |
Postprocessing |
|
Roll up each data package in the aggregate automatically Note
The InfoCube must be technically correct and you must be sure of its quality. Note
Only use automatic roll-up if you load requests into the InfoCube in such a way that there is no time overlap for the load process, the roll-up and other automatisms in the InfoCube. For more information, see Automatic Further Processing. |
|
Program RSDDK_AGGREGATES_ROLLUP |
You can also run roll up using program RSDDK_AGGREGATES_ROLLUP (see Direct Execution - Reports). Note
You can schedule this program as a regular background job. |
The new data is available in reporting for queries that are started after the rollup.
More information: