DataStore Object Settings

DataStore Object Type

Select the DataStore object type. You can choose between Standard, Direct Update, and Write-Optimized, where Standard is the default value, while Direct Update is only intended for special cases. You can switch the type as long as there is still no data in the DataStore object yet.

More information: DataStore Object Types

Type-Specific Settings

The following settings are only available for certain DataStore object types:

For Write-Optimized DataStore Objects:

Allow duplicate data records

This flag is only relevant for write-optimized DataStore objects. With these objects, the technical key of the active tables always consists of the fields Request, Data Package, and Data Record. The InfoObjects that appear in the maintenance dialog in the Semantic Key folder form the semantic key of the write-optimized DataStore object.

If this flag is set, no unique index is generated with technical name "KEY" for the InfoObjects in the semantic key. This means that there can be more than one record with the same key in the active table of the DataStore object.

DataStore Objects for Direct Update:

Planning mode

The following applies to DataStore objects for direct updates using the planning mode flag:

• Use of characteristics:

  All characteristics must be contained in the key of the DataStore object. This also applies to characteristics that contain currencies and quantities.

• Use of key figures:

  All key figures in a data part, which are valid for the direct update of the DataStore objects without planning mode, can be used. In addition, key figures with standard aggregation no aggregation (X, if more than one value) (NO2) can be included in the data part. However, BW-integrated planning only allows you to change key figures with standard aggregation SUM and NO2.

For Standard DataStore Objects:

Creating SID Values

With the Generation of SID Values flag, you define whether SIDs are created for the new characteristic values in the DataStore object when the data is activated.

There are three options:

• During Reporting: When data is activated in the DataStore object, no SIDs are retrieved for the new characteristic values. This reduces the runtime during activation. The SIDs are generated during query execution.

• During Activation: The SIDs are generated when the data is activated. This reduces runtime when executing the query.

• Never Generate SIDs: SIDs are never generated.

  This is the best option for all DataStore objects that are likely to be used for further processing in other DataStore objects or InfoCubes. If you create a query for a DataStore object with this property, the query cannot be executed. You can still define InfoSets with this DataStore object and execute queries for it.

Loading Unique Data Records

If you only load unique data records (data records with non-recurring key combinations) into the DataStore object, performance is improved if you set the Unique Data Records flag in DataStore object maintenance. This setting is displayed as the default setting when activating data in administration or the corresponding process in the process chain. You can also overwrite this setting there if required (for initial data loading for example).

The records are then updated more quickly because the system no longer needs to check whether the record already exists. You have to be sure that no duplicate records are loaded because this leads to termination. Check whether the DataStore object might be write-optimized.

Options for 3.x Data Flows: Automatic Further Processing

If you still use a 3.x InfoPackage to load data, you can activate several automatisms to further process the data in the DataStore object. If you use the data transfer process and process chains that we recommend using, you cannot use these automatisms.

We recommend always using process chains.

More information: Including DataStore Objects in Process Chains

Settings for automatic further processing:

• Automatically Setting Quality Status to OK

  If you set this flag, the system automatically will set the quality status to OK after loading data into the DataStore object. You should activate this function. You should only deselect this flag if you want to check the data after loading.

• Activating the DataStore Object Data Automatically

  If you set this flag, data with quality status OK is transferred from the activation queue to the active data table, and the change log is updated. Activation is carried out by a new job that is started after loading into a DataStore object is complete. If the activation process terminates, there can be no automatic updating.

• Updating Data from the DataStore Object Automatically

  If you set this flag, the DataStore object data is updated automatically. Once the data has been activated, it is posted to the relevant InfoProviders. An initial update is carried out automatically with the first update. If the activation process terminates, there can be no automatic updating. The update is carried out by a new job that is started once activation is complete.

  Note

  Only activate automatic activation and update if you are sure that these processes do not overlap.

For information about other settings, see Performance Tips for DataStore Objects and

Runtime Parameters of DataStore Objects