Aggregates

An aggregate is a materialized, summarized view of the data in an InfoCube. In other words, it consolidates
and stores a subset of InfoCube data into a database. This subset of data is redundant and persistent. When
we execute a query on an InfoCube with appropriate aggregates, the query reads the summarized data
directly from the database thus eliminating the need to perform any processing related to summarization
during query runtime.

Aggregates creation is highly recommended when :

• Query execution and navigation requires speeding up.
• Navigational attributes are required to be used in the queries.
• Hierarchies used in the queries need to be speed up – you can aggregate on specific hierarchy levels.

There are a few disadvantages

They increase load time

• through data packages uploads;
• through the hierarchy/attribute change run after loading master data;
• through adjusting time-dependent aggregates.

Roll up

If the InfoCube has aggregates that have aggregates already filled, then data that has been recently loaded 

into an InfoCube is not visible for reporting, from the InfoCube or aggregates, until an aggregate roll-up takes 

place.

During this process you can continue to report using the data that existed prior to the recent data load. The 

new data is only displayed by queries that are executed after a successful roll-up.

Change Run

A Change Run is executed only in the event of change in the master data. As changes in the master data 

also trigger changes in navigational attributes or hierarchies, it is recommended that data in the aggregates 

is adjusted after master data load. This ensures consistency in Reporting results.

The change run adjusts the data in the aggregates and turns the modified version of the navigational

attributes and hierarchies into an active version. During the change run process, you can carry out Reporting 

on old master data and hierarchies. 

Building Aggregates

select the InfoCube you wish to create the aggregates on in the Modeling-InfoProvider 

tab. Right click and select ‘Maintain Aggregates’.

You are prompted to select the option to create ‘Proposals for Aggregates’.

If you select ‘Generate Proposals’ that system helps us derive the proposals for various aggregates 

depending on the statistics data and the input provided by you.

we will create the aggregates manually, so we select the option ‘Create by 

Yourself’.

In the ‘Maintenance for Aggregates’ screen, the system displays list of characteristics, navigational attributes 

and hierarchies.

List of Objects that qualify for creating aggregates can be viewed by expanding the dimensions in the 

template.

We will manually create aggregate on the Characteristics ‘Plant’ – 0PLANT. Select 0PLANT from the 

template on the left hand side and drag it onto the right hand side screen.

You are prompted to enter description for the aggregate.

Enter the descriptions, short and long, for the aggregate and Continue

You can now see the aggregate added onto the right hand side. ‘Red’ indicators tell us that the aggregate is 

not active/filled up.

You have the option of looking at the following parameters for each of the aggregates:

 Status – Could be created, changed, Save and active.

 Filled/Switched Off – On - Could be not filled / Filled with data – Switch on or off for the queries.

 Selection Type - the system aggregates according to the values of the selected objects: * All 

  characteristic values, H Hierarchy level, F Fixed value

 Hierarchy – Name of the Hierarchy selected, if any.

 Fixed Value – Fixed value selected, if any.Valuation

 Records - Number of records in the filled aggregate. 

 Records Summarized - Number of records read on average from the source to create a record in 

  the aggregate. (This value should never be equal to 1)

 Usage - Number of uses (in queries).

 Last Used

 Last Roll-up - When was data last entered for the aggregate? 

 Last Changed on

From the top-menu , select ‘Aggregate’ tab which displays a list of sub-menu.

Select ‘Activate and Fill’ .

Post processing that could take a few minutes, we are now prompted to run the Aggregates filling and 

activation job.

Click on Start

Refresh the screen a few times to get the latest Status and the Aggregate Filled indicators.

Remember that we can create multiple aggregates based on our requirements and opt for simultaneous 

Activation and Fill up process. 

Go back to the DW Workbench – Select the InfoCube under consideration.

And refresh the tree structure to Obtain…

The ‘Aggregate’ availability indicator next to the InfoCube

Aggregates Roll up

Although, aggregates can be rolled up manually, it is highly recommended that a process chain is used to 

execute this process. Using the data package roll up in a process chain helps eliminating errors during 

complex flows either by automating related processes and/or by ensuring that dependent processes are 

integrated with each other.

Roll up Through Process Chains

The system recommends the greatest possible value for Rollup in the ‘Request ID’ . You can manually set 

the same.

Now choose the option ‘Process Chain Maintenance’.

You are now taken to the RSPC transaction screen and the list of associated process chains is displayed. If 

you do not have the relevant chain, you can create a new chain.

Want to learn SAP from Experts? - Archon Solutions

Best SAP training in Kerala

Best SAP training in Kochi

Best SAP training in Ernakulam

SAP FICO, SAP MM, SAP SD, SAP PP, SAP ABAP, SAP Basis, SAP SAC, S4Hana