Show TOC

Modeling PropertiesLocate this document in the navigation structure

The modeling properties enable you to control how you use your DataStore object (advanced).

You can set the following modeling properties:

Activate/Compress Data
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. There are three options:
  • Write Change Log: If you choose this option, the delta (new and changed records) is saved in the change log. The change log is used to extract the delta. You can only delete data from the DataStore object if the object has a change log.
  • Keep Inbound Data, and extract from Inbound Table: If you choose this option, no data is saved in the change log. The extraction process always reads the data in the inbound table again - for delta extraction or full extraction.
  • Unique Data Records: If you only load unique data records (data records with non-recurring key combinations) into the DataStore object, you can select this property. This means the system does not check whether the record already exists. You have to be sure that no duplicate records are loaded. This means that the table of active data will only contain unique data records. Data aggregation is not allowed.
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 with the InfoCube.

Inbound Table as Extended Table
If you use SAP IQ as extended storage for your BW system, you can set the Inbound Table as Extended Table flag. This means that data is only saved in the persistency layer.