Using the Standard DataStore Object

Standard DataStore Objects in SAP BW/4HANA are primarily recommended for delta loading processes. So-called record processing then takes place within the DataStore Object (advanced) in order to process the different delta data sets correctly from a business perspective.

A Standard DataStore Object is used to store consolidated and cleansed data (transactional data or master data) on a document level (atomic level). A Standard DataStore Object primarily stores detailed transactional data. They can be used to support detailed operational reporting, or can be part of the warehouse, where they can be used to hold years of data that may be needed.

A Standard DataStore Object is designed in the same way as a table, it contains key fields (for example, document number and item) and data fields. Data fields can be all InfoObject types like Key Figures, Units, Time Characteristics, and other Characteristics (for example, order status, customer, or time). Defining key fields makes it easier to identify your documents.

When updating data in a Standard DataStore Object, records can be overwritten. Characteristics that are not part of the key are always overwritten. The update behavior of Key Figures can be set to Overwrite, Add or Not Update.

Let's have a look at the usage of the tables that belong to the Standard DataStore Object.

A Standard DataStore Object consists of the following three tables:

• Active Data

  In this table, the current status of the data is stored. The table contains a semantic (business-related) key that can be defined by the modeler (order number, item, or schedule line, for example). The modeler must define the key correctly because a match on the key initiates special delta processing during the activation phase (this is discussed later). Only the active data table is visible in reporting. Therefore, you have to activate requests to view their data in reports.

• Change Log

  During the activation run, changes are stored in the change log. In this table, you can find the complete history of the changes, because the content of the change log is not automatically deleted. If supplied with data from the DataStore Object (advanced) in the delta method, connected targets are updated from the change log. The change log has a technical key consisting of a request, data package, and data record number.

• Inbound Table

  During the DTP, records are written first to this table. During the activation process, the data records are then written to the Active Data table and the Change Log table.

Later in this course, we'll load transactional data. When we discuss data loading, request handling will be covered as well. However, first we need to model a DataStore Object (advanced), to store cost center plan line items.

We'll define the DataStore Object (advanced) as a Standard DataStore Object. The main focus in our scenario is loading cost center plan items, which are changed by offering a flat file with updated data. So we need a DataStore Object (advanced) with delta capabilities.