The modeling properties enable you to control how you use your DataStore object (advanced).
You can set the following modeling properties:
In general, the data is always written to the inbound table. If you choose Activate Data
, the data is written to the table for active data (during the activation/compression process) once it arrives in the inbound table. You have the following options here:
With this property, you create a DataStore object (advanced) for direct writing. The data is then written directly to the table of activate data using a DTP or an API.
All Characteristics are Key, Reporting on Union of Inbound and Active Table
If you select this property, all the characteristics are included in the key. The system accesses the inbound table and the active table (using a union across both tables) in the query. In this case, you should only load additive deltas. The data is aggregated. The properties are comparable to the InfoCube.
If you set the Planning Modeflag, you can use the DataStore object (advanced) for planning.
If you set the Inventory flag, you can use non-cumulative key figures in your DataStore object. You can then add non-cumulative key figures to the DataStore object (advanced) and define validity characteristics.
SAP HANA Dynamic Tiering
If you use SAP IQ as extended storage for your BW system, you can set the SAP HANA Dynamic Tiering flag. The data is then only saved in the persistency layer. If you set this flag at a later point in time when the tables already contain data, a remodeling request is created, which you can start in the Remodeling Monitor. Otherwise, the tables are written directly to SAP IQ. If the definition of the DataStore objects (advanced) necessitates activation, this is performed in ABAP.