Procedure documentationCreating DataStore Objects Locate this document in the navigation structure

 

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

A DataStore object contains key fields (for example, document number/item) and data fields that can also contain character fields (for example, order status, customer) 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. Furthermore, you can use an overwrite and the existing change log to render a source delta enabled. This means that the delta that is further updated to the InfoCubes, for example, is calculated from two successive after-images.

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 is possibly for standard DataStore objects only.

    More information: Using Semantic Partitioning.

  3. Copying InfoObjects:

    Note Note

    There must be at least one key field.

    Further Restrictions: You can

    - 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)).

    - You can create a maximum of 749 fields

    - You can use 1962 bytes (minus 44 bytes for the change log)

    - You cannot include key figures as key fields

    End of the note.

  4. Using Settings you can make various settings and define the properties of the DataStore object. See also DataStore Object Settings.

  5. Under Indexes, call the context menu to create secondary indexes. 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 from the dialog box. Note that errors can occur during activation if the values are not unique.

    The description of the indexes is specified by the system. To create a folder for the indexes, choose Continue from the dialog box. Now you can transfer the required key fields into the index folder using drag and drop.

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

    For more information see Indexes.

  6. Use Check (Check) to make sure that the DataStore object is consistent.

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

Result

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.