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:

• 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.
• Snapshot Support: If your DataSource only allows full update, you can use the Snapshot Support flag to make sure that deleted requests are still updated. Upon activation, the system recognizes records that are in the inbound table but not in the load request. These are written to the change log as reverse images.
  Note Make sure that all records are contained during every load, as data could otherwise be lost.

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.

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.

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.