Show TOC

Creating DataStore Objects for Direct UpdateLocate this document in the navigation structure

Context

The DataStore object for direct update differs from the standard DataStore object in terms of how the data is processed. In a standard DataStore object, data is stored in different versions (active, delta, modified), whereas a DataStore object for direct update contains data in a single version. Data is thus stored in precisely the same form in which it was written to the DataStore object for direct update by the application. The DataStore object for direct update consists only of a table for active data and usually receives its data from external systems through APIs for filling or deleting.

Loading data by DTP is not supported. DataStore objects for direct update are therefore not displayed in the administration tools or in the monitor. However, you can update the data in DataStore objects for direct update to additional InfoProviders. Since no change log is generated, however, you cannot perform a delta update to the InfoProviders at the end of this process.

If you switch a standard DataStore object that already has update rules to Direct Update, the update rules are set to inactive and can no longer be processed.

Note

You can only switch between DataStore object types Standard and Direct Update or change the Planning Mode indicator if the DataStore object does not contain any data yet.

In the context of BW-Integrated Planning, you can use a DataStore object for direct update if the Planning Mode indicator is set. In this case, data can only be written to the DataStore object using BW-Integrated Planning or the Analysis Process Designer. The APIs that were designed for the DataStore object for direct update without planning mode cannot be used in planning mode. This is due to the fact that only BW-Integrated Planning can ensure that all SID values exist for the characteristic values stored in the DataStore object. BW-Integrated Planning also ensures consistency with the planning model (characteristic relationships, data slices).

More information: InfoProvider

You can also use the DataStore object for direct update as a data target for an analysis process.

More information: Analysis Process Designer

The DataStore object for direct update is also required by various applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.

Procedure

  1. Follow the general procedure for creating a DataStore object. More information: Creating DataStore Objects
  2. On the editing screen for the DataStore object, choose Start of the navigation path Settings Next navigation step Type of DataStore Object Next navigation step Change End of the navigation path. The default setting is Standard. Change this to Direct Update.
  3. If you want to use the DataStore object for BW-Integrated Planning, set the Planning Mode indicator under Properties.
  4. Write-optimized DataStore objects have the folder Characteristics as Key Numbers. If the data fields of a DataStore object contain characteristics, the system adds these fields under this folder. These objects have the technical name 1KYF_Merkmalsname. If you activate the flag after the technical name, the characteristics are used as key figures. This means the characteristics have the standard aggregation and the exception aggregation NO2; in other words, they cannot be aggregated.
  5. Save and activate the DataStore object.

Results

The DataStore object for direct update is available as an InfoProvider in BEx Query Designer and can be used for analysis purposes. If the Planning Mode indicator is set, this DataStore object can also be used as the basis for defining aggregation levels.