Show TOC

Creating DataStore ObjectsLocate this document in the navigation structure

Context

A DataStore object serves as a storage location for consolidated and cleansed transaction data or master data at document (atomic) level. This data can be evaluated using a BEx query.

A DataStore object contains key fields (document number/item for example) and data fields that can also contain character fields (order status or customer for example) as key figures. The data in a DataStore object can be updated with a delta update into InfoCubes (standard) and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.

Unlike multidimensional data storage using InfoCubes, the data in DataStore objects is stored in transparent, flat database tables. The system does not create fact tables or dimension tables.

The cumulative update of key figures is supported for DataStore objects, just as it is with InfoCubes, but with DataStore objects it is also possible to overwrite data fields. This is particularly important with document-related structures. If documents are changed in the source system, these changes include both numeric fields, such as the order quantity, and non-numeric fields, such as the ship-to party, status and delivery date. To reproduce these changes in the DataStore objects in the BW system, you have to overwrite the relevant fields in the DataStore objects and set them to the current value. By overwriting and using the existing change log, you can also make a source delta enabled. This means that the delta that is further updated to the InfoCubes, being calculated from two successive after-images for example.

Procedure


  1. Follow the general procedure for creating an InfoProvider. All DataStore object-specific settings are described below.

    More information: Creating InfoProviders

  2. You can specify that the DataStore object is to be partitioned semantically. This can only be done for standard DataStore objects.

    More information: Using Semantic Partitioning.

  3. Copying InfoObjects:

    Note

    There must be at least one key field.

    Further Restrictions: You can

    - Create a maximum of 16 key fields (if you have more key fields, you can combine fields using a routine for a key field (concatenate)). If you are using a SAP HANA database, you can add more than 16 characteristics in the key in a DataStore object for direct updating in planning mode.

    - Create a maximum of 749 fields

    - Use 1962 bytes (minus 44 bytes for the change log)

    - You cannot include key figures as key fields

  4. Using Settings you can make various settings and define the properties of the DataStore object. More information: DataStore Object Settings.

  5. Under Indexes, you can create secondary indexes from the context menu. This improves the load and query performance of the DataStore object. Primary indexes are created automatically by the system.

    If the values in the index fields uniquely identify each record in the table, select Unique Index in the dialog box. Note that errors can occur during activation if the values are not unique.

    The description of the indexes is preset by the system. To create a folder for the indexes, choose Continue from the dialog box. You can now drag the required key fields over to the index folder.

    You can create a maximum of 16 secondary indexes. These are also transported automatically.

    More information: Indexes.

  6. You can use Check to check whether the DataStore object is consistent.

  7. Save and activate the DataStore object. When you activate the DataStore object, the system generates an export DataSource. You use this to update the DataStore object data to further InfoProviders.

Results

You can now create a transformation and a data transfer process for the DataStore object to load data.

If you have loaded data into a DataStore object, you can use this DataStore object as the source for another InfoProvider. See: Further Processing of Data in DataStore Objects. You can display and delete the loaded data in DataStore object administration. More information: DataStore Object Administration.