Architected Data Mart Layer

Business Transformation Layer

In the Business Transformation layer, the data is transformed based on business logic. The data in the previous layer (Data Propagation layer) should not be transformed based on business logic, to ensure that the data can be used again. It may be the case that DataStore objects in this layer are needed to compile data from several DataStore objects in the Data Propagation layer.

Reporting Layer

The Reporting layer contains the objects that are used to perform queries for analysis. This layer is modeled mainly using InfoCubes. These cubes save data in BWA. To improve the database performance, you can semantically partition the InfoCubes. Special InfoCubes enable you to create planning scenarios here. Using this InfoCubes as a basis, you can create data views (in the form of aggregation levels) and methods to change data (for example, planning functions and planning sequences). VirtualProviders allow you to access source data directly. Different composite objects (HybridProviders, InfoSets) provide benefits for analysis. Depending on the scenario, you can use these composite InfoProviders.

Virtualization Layer

Queries should always be defined on a MultiProvider for reasons of flexibility. These queries form the Virtualization layer.

Operational Data Store

The Operational Data Store supports operative data analysis. Data can be updated to an operational data store, on a continual basis or in short intervals, and then read for operative analysis. You can also forward the data from the Operational Data Store layer to the data warehouse layer at set times. This means that the data is stored in different levels of granularity. For example, whereas the Operational Data Store layer contains all the changes to the data, only the day-end status is stored in the data warehouse layer.