A DataStore object serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level.
This data can be evaluated using a BEx query.
A DataStore object contains key fields (for example, document number/item) and data fields that can also contain character fields (for example, order status, customer) as key figures. The data from a DataStore object can be updated with a delta update into InfoCubes and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
Unlike multi-dimensional data storage using InfoCubes, the data in DataStore objects is stored in transparent, flat database tables. Fact tables or dimension tables are not created.
The cumulative update of key figures is supported for DataStore objects, just as it is with InfoCubes, but with DataStore objects it is also possible to overwrite data fields. This is particularly important with document-related structures. If documents are changed in the source system, these changes include both numeric fields, such as the order quantity, and non-numeric fields, such as the ship-to party, status and delivery date. To map these changes in the BI system in the DataStore objects, the relevant fields in the DataStore objects must be overwritten and set to the current value. Furthermore, a source can be made delta-capable by overwriting it and using the existing change log. This means that the delta that, for example, is further updated in the InfoCubes, is calculated from two, successive after-images.
There are different DataStore object types:
...
· Standard (see Standard DataStore Objects)
· For direct update (see DataStore Objects for Direct Update)
· Write-optimized (see Write-Optimized DataStore Objects)
Differences between the DataStore Object Types:
Type |
Structure |
Data Supply |
SID Generation |
Reporting Possible? |
Standard |
Consists of three tables: activation queue, table of active data, change log |
From data transfer process |
Yes |
Yes |
For direct update |
Consists of the table of active data only |
From APIs |
No |
Yes |
Write-optimized |
Consists of the table of active data only |
From data transfer process |
No |
Yes |
The DataStore objects are fully integrated with BI Metadata. They are transported just like InfoCubes, and installed from BI Content (for more information see Installing Business Content). The DataStore objects are grouped with the InfoCubes in the InfoProvider view of the Data Warehousing Workbench - Modeling, and are displayed in a tree. They also appear in the data flow display.
The transformation rules define the rules that are used to write to a DataStore object. They are very similar to the transformation rules for InfoCubes. The main difference is the behavior of data fields in the update. When you update requests in a DataStore object, you have an overwrite option as well as an addition option.
See also Transformation Type.
The delta process , which is defined for the DataSource, also influences the update. When loading files, the user must select a suitable delta method so that the correct transformation type is used.
Unit fields and currency fields operate just like normal key figures, meaning that they must be explicitly filled using a rule.
The processes for scheduling the data transfer process for updating into InfoCubes and DataStore objects are identical. Error handling is an exception here. It cannot be used with DataStore objects.
It is also possible to schedule the activation of DataStore object data and the update from the DataStore object in the related InfoCubes or DataStore objects.
The individual steps, including the processing of the DataStore object, are logged in the Monitor.
There is a separate detailed monitor for executed request operations (such as activation or rollback).
In full-update mode, every transaction data DataSource contained in a DataStore object is updated. In delta-update mode, only those DataSources that are flagged as DataStore-delta compatible are updated.