Technical Data
Function Is |
Changed |
In Release |
Software Component ● Component: SAP NetWeaver ● Release 7.0 |
Assignment to Application Component |
BW-BEX-OT-AGGR Aggregates (definition and structure) |
Country Setting |
Valid for all countries |
The change run, rollup, condensing and checking up multiple aggregates can be executed in parallel. Parallelization takes place using the aggregates. The parallel processes are continually executed in the background, even when the main process is executed in the dialog. This can considerably decrease execution time for these processes. You can determine the degree of parallelization and determine the server on which the processes are to run and with which priority.
Parallelization of the change run according to SAP Note 534630 is obsolete and is no longer being supported.
You can start multiple change runs simultaneously. The prerequisite for this is that the lists of the master data and hierarchies to be activated are different and that the changes affect different InfoCubes.
After a change run, all affected aggregates are condensed automatically. SAP Note 583202 is obsolete.
Up to now, the aggregate fact tables were partitioned if the associated InfoCube was partitioned and the partitioning characteristic was in the aggregate. Now it is possible to suppress partitioning for individual aggregates. If aggregates do not contain much data, very small partitions can result. This affects read performance. Aggregates with very little data should not be partitioned.
In InfoCube maintenance, you can now determine by InfoCube that the indexes not be deleted before writing and created again during rollup. During the upgrade, all InfoCubes are set so that the index is deleted (independent of the RSADMIN entry according to SAP Note 582529). SAP Note 582529 is obsolete.
If no setting is made, a maximum of three processes are executed in parallel. This setting can be adjusted for a single process (change run, rollup, condensing of aggregates and checks). Together with process chains, the affected setting can be overridden for every one of the processes listed above.
If a change run terminates, the same change run must be started again. You have to start the change run with the same parameterization (same list of characteristics and hierarchies).
Aggregates that are not to be partitioned have to be activated and filled again after the associated property has been set.
If you have set the RSADMIN parameter (see SAP Note 582529) so that the indexes of the F fact table are deleted and created again before rollup, you have to decide for which InfoCubes you want this to continue to occur. For these InfoCubes, you have to set the associated parameter in InfoCube maintenance.
