You are on page 1of 1


An aggregate saves the dataset for an InfoCube redundantly and persistently to the

Aggregates make it possible to access InfoCube data quickly in Reporting.
Aggregates are therefore tools for improving performance.

It is advisable to construct aggregates if:

A lot of data is saved in the InfoCube

You often use attributes in queries

You want to speed up Reporting using characteristic hierarchies by

aggregating specific hierarchy levels

There are delays with the execution and navigation of query data in a group
of queries

You want to speed up the execution and navigation of a specific query.

Types of Functions for Aggregates

If you have created aggregates for an InfoCube, Reporting automatically accesses
these aggregates.

If new data is loaded in data packets (Requests) in the fact table of the InfoCube, it
will not be considered first by Reporting.

The new data packets for the InfoCube are loaded into the aggregate table at a
defined time. This process is known as roll-up.

This procedure ensures that the data for an InfoCube can be navigated consistently
at all times.

The roll-up of data packets in the aggregates can occur either manually or
automatically. I

n the InfoCube maintenance, you can use the function Manage InfoCube to decide
for each InfoCube whether you want the data to be rolled up automatically into the
aggregate, or if you want to trigger it yourself. You can also schedule the same
function when directly carrying out a report, by entering the program name

You can also create the program regularly as a background job as well as in a chain
of events.