Use of the Data Mart DataStore Object
The Data Mart DataStore Object is used for reporting and analysis.
If the reporting performance is poor because of the volume of data or complex calculations, you can decide to store the aggregated data in a Data Mart DataStore Object.
When you create a Data Mart DataStore Object, you can assign Characteristics and Key Figures to groups. The groups are only used as a sort criterion to provide a clearer overview when creating a Query.
No additional keys can be specified for a Data Mart DataStore Object, but the records are treated as if all Characteristics are in the key (logical key). The data is aggregated, so only additive deltas can be loaded (for Key Figures only the aggregations maximum (MAX), minimum (MIN), and summation (SUM) are allowed). Therefore, Key Figures cannot be overwritten.
Let's have a look at the usage of the tables that belong to the Data Mart DataStore Object.
In a Data Mart DataStore object, data is always loaded to the inbound table and can be optionally moved to the active table by activating the request(s). Activating compresses the data so it is stored more efficiently, removing the technical loading information from the records. The requests that have been activated are then deleted form the inbound table.
The change log is not used.
All data of the active data table and inbound table is merged, and is visible in reporting. Therefore, you do not have to activate requests to view their data in reports.
Note
We'll discuss the usage of these tables in more detail in the next unit, when data will be loaded into the Data Mart DataStore Object.Scenario
Later in this course, we'll load transactional data. When we discuss data loading, request handling will be covered as well. However, first we need to model a DataStore Object (advanced), to store transactional data related to cost center actual postings.
We'll define the DataStore Object (advanced) as a Data Mart DataStore Object. The main focus in our scenario is reporting on this actual data where no delta capabilities are needed. This makes sense, because, in finance, corrections never overwrite existing actual amount postings, but will create additional lines, which can be added to the Data Mart DataStore Object in SAP BW/4HANA.