Management of DataStore Object (DSO)

(1)

Management of DataStore Object (DSO)

Applies to:

SAP ECC 6.0

Summary

The article describes the attributes of the DataStore Object (DSO). It also discusses the management of the DSO.

Author: Christy Mathew

Company: Applexus Technologies Pvt Ltd Created on: 30 September 2011

Author Bio

Christy Mathew is a B.Tech graduate and currently working as SAP BI Consultant in Applexus Technologies Pvt Ltd.

(2)

Introduction

The article describes the attributes of the DataStore Object (DSO). It also discusses the management of the DSO.

What is DataStore Object (DSO)?

A DataStore object serves as a storage location for consolidated and cleansed transaction data on a document (atomic) level. It contains key fields (such as document number, document item) and data fields that, in addition to key figures, can also contain character fields (such as order status, customer).

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.

This data can be evaluated using a BEx query.

Create DSO

In the Create DSO option there are six fields:

 Object Information

 Settings

 Key fields

 Data fields

 Navigation attributes

 Indexes.

(4)

Object Information

There are three functions in this that specify the version of the object (for example, modified or in process, whether the object is saved or not and the current status of the object).

Settings

The Settings option has several functions. Additionally, there are three types of DataStore objects as stated below.

Standard DataStore object

 Data provided using a data transfer process.

 SID values can be generated.

 Data records with the same key are aggregated during activation.

 Data is available for reporting after activation.

Write-optimized DataStore object

 Data provided using a data transfer process.

 SID values cannot be generated.

 Records with the same key are not aggregated.

 Data is available for reporting immediately after it is loaded.

DataStore object for direct update

 Data provided using APIs (Application Programming Interfaces).

 SIDs cannot be generated.

 Records with the same key are not aggregated.

SIDs Generation upon activation

This indicator determines whether SIDs are generated when the data in the DataStore object is activated. If the indicator has not been set, no SIDs are generated and the activation process is completed in less time.

Unique Data Records

The DataStore object can be used for loading unique data records. This indicator determines whether only unique data records are posted in the DataStore object. The performance of activation can be increased considerably in this way.

Set Quality Status to 'OK' Automatically

Use this indicator to set the status of data to OK (green) automatically after it has been loaded into the target.

(5)

Update Data Automatically

Use this selection to determine that data is updated automatically from the DataStore object to the connected InfoProviders. DataStore object data can be updated, only after it has been activated. There can be no automatic update if the activation process terminates.

Key Fields

To this field we have to drag and drop the InfoObject key characteristic.

Data Fields

To this field drag and drop the rest of the characteristics and the key figures.

Indexes

Under Indexes call the context menu to create secondary indexes. This improves the load performance and query performance of the DataStore object. The system automatically creates primary indexes.

Management of DSO

Under the Manage option there are three tabs:

 Contents

 Requests

 Reconstruction.

Contents

This function checks to see whether the data loaded into the DataStore object contains any errors. It is also possible to selectively delete requests from the DataStore object.

In the Content tab page there is a list of InfoObjects for the DataStore object. Use this to check whether the data loaded into the DataStore object is free of technical errors. If the table contains more than 40 fields suitable for selection, select the fields first.

(6)

Logs

Choose Logs to view the logs for requests that have been deleted, activated, reconstructed, or added.

New Data

Choose New Data to display the contents of the activation queue table. If this new data is activated, the system promptly deletes the activation queue and moves the data to the active data table.

Active Data

Choose Active Data to view the contents of the table containing active data (A table).

Change Log

Choose Change Log to display the change log table. This table contains the change log requests that are created each time data is activated.

Selective

Selective deletion is used only when individual fields are not required and need to be deleted from the request. Selective deletion allows deletion by characteristic as well as by request. Selective deletion only deletes from the table of active data. The activation queue and the change log remain unchanged. Before deleting data selectively, all data must be activated. The deletion is logged and it can be retraced using Log.

Request

The Request tab provides information about all requests that have run in the DataStore object. Deleting requests or scheduling an update can also be done here.

(7)

Data Mart Status of the Request

When a request from a DataStore object is updated into additional InfoProviders, the data mart status of the request is displayed.

Load Monitor

Choose Monitor to jump to the extraction monitor and determine the location of the errors that occurred.

Logs for DSO-Request Processing

Display a detailed overview of request processing for all request operations by choosing Log. Trace the start and end times of the steps in request processing, such as status changes and activation.

DTP/InfoPackage

This field displays the description of InfoPackage.

Transferred Records

This column displays the number of records transferred to the BI system. The records are usually written to the PSA first of all.

Added Records

This column displays the number of records that were written into the InfoProvider. This number can differ from the number of transferred records if records were filtered out or added during the transformation.

Source/InfoSource

An InfoSource is a grouped quantity of logically related information for a unit. InfoSources can either encompass transaction data or master data. An InfoSource is always a quantity of InfoObjects. An InfoSource always refers to a scenario from an application (for example, Financial Accounting).

(8)

Reconstruction

Use this function to fill a DSO object with requests that have already been loaded into a BW system, or into another DSO object. Reconstructing the ODS object provides data from the change log, so the deltas can be loaded into the reconstructed DSO object.

Selection

Choose Selection to restrict the display of the request for a DSO object, an InfoCube, an InfoSource, or a source system. All the requests that have already been loaded for our selection are displayed here.

Individual requests can be selected and used to reconstruct the DSO object.

Subsequent Processing

In this area, specify the events to carry out once the process is complete. Either start loading the ODS object immediately, or schedule the load as a background job.

Parallelism

Here it is necessary to provide the process variant (Name of the process).A variant is always uniquely defined in connection with the type.

Process Chain Maintenance

This is used to jump to process chains. A process chain is a sequence of processes that wait in the

background for an event. Some of these processes trigger a separate event that can start other processes in turn.

(9)

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Management of DataStore Object (DSO)