07.02.2013 Views

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Activating and filling<br />

In order to use an aggregate in the first place, it must be defined, activated, and<br />

filled. When activated, the required tables are created in the database from the<br />

aggregate definition. Technically speaking, an aggregate is actually a separate<br />

BasicCube with its own fact table and dimension tables. However, aggregates<br />

might share the dimension tables of the corresponding InfoCube if those tables<br />

have the appropriate structure.<br />

Upon creation, every aggregate is assigned a technical name, which is a unique<br />

number consisting of six digits where the first digit is always set to 1. The table<br />

names that make up the logical object that is the aggregate are then derived in a<br />

similar manner, as are the table names of an InfoCube.<br />

For example, if the aggregate has the technical name 100001, the E- fact tables<br />

have the following names: /<strong>BI</strong>C/E100001 and /<strong>BI</strong>C/F100001. Its dimensions,<br />

which are not the same as those in the InfoCube, have table names such as<br />

/<strong>BI</strong>C/D100001P, /<strong>BI</strong>C/D100001T, and so on.<br />

When you fill an aggregate, you load it with data. This action can only be<br />

triggered from the aggregate maintenance. Also note that an aggregate can be<br />

filled from the data of a larger aggregate that is already filled. This means that<br />

very highly summarized aggregates, as a rule, can quickly obtain data from other<br />

aggregates. In contrast, it can take a long time to build aggregates from the<br />

InfoCube.<br />

Because of this, all aggregates are filled in background processes. If there are<br />

several aggregates scheduled to be filled in one process, a hierarchy sequence<br />

<strong>for</strong> the aggregates is determined first, and it is then processed sequentially. This<br />

guarantees that very highly summarized aggregates are built from the more<br />

detailed aggregates.<br />

Roll-up<br />

If aggregates are defined, new data packets that are loaded into the InfoCube<br />

cannot be used <strong>for</strong> reporting until they are written to the aggregates by a roll-up.<br />

During this process you can continue to report <strong>using</strong> the data that existed prior to<br />

the recent data load.<br />

There are three different options <strong>for</strong> rolling up data:<br />

► You can set up the InfoCube so that every data packet is automatically rolled<br />

up into the aggregate if it is technically correct and the quality has been<br />

ensured.<br />

► The roll-up can be also started manually from the Administrator Workbench.<br />

This is appropriate if the data of several packets <strong>for</strong>m a logical unit and are<br />

only valid if they are released together.<br />

Chapter 12. Concepts, activities, and terminology 271

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!