What is Standard DSO in SAP?

By : Jessica Blake Jessica Blake
Hours Updated

⚡ Smart Summary

A Standard DSO in SAP BW stores consolidated, cleansed transaction data at detailed level across three tables, the activation queue, active data, and change log, supporting overwrite, delta loads, and detailed-level reporting.

  • 🗃️ Three Tables: A standard DSO has an activation queue, an active data table, and a change log.
  • 🔁 Activation: Data moves from the new table to the active table and then to the change log.
  • 📝 Change Log: The change log records delta history and supports delta loads to other targets.
  • 🔑 Key and Data Fields: Key fields make records unique; data fields hold attributes and key figures.
  • ⚙️ Settings: Options control SID generation, unique records, and automatic activation.
  • 🤖 AI Assistance: AI monitors load and activation jobs and flags data quality issues early.
Read More

What is Standard DSO in SAP

What is a Standard DSO?

A standard DSO is the most common DataStore Object. It has three transparent tables on the database:

  1. Activation Queue: holds the records that are to be updated but have not yet been activated.
  2. Active Data: the table that holds active data.
  3. Change Log: holds the change history for delta loads.

Process of Data Transfer to a DSO

  • Data is first loaded into the activation queue, also called the new data table.
  • Upon activation, data is transferred from the new data table to the active data table.
  • And then to the change log table. The change log table holds the changed or corrected data.

Note: the data in the change log table is stored redundantly and can be deleted after the records have been activated.

Process of Data Transfer to DSO

Creation of a Standard DSO

Step 1)

  1. Go to transaction code RSA1.
  2. Click the OK button.

Creation of Standard DSO

Step 2)

  1. Navigate to the Modeling tab -> InfoProvider.
  2. Right click on InfoArea.
  3. Click on “Create DataStore Object” from the context menu.

Creation of Standard DSO

Step 3)

  1. Enter the Technical Name.
  2. Enter the Description.
  3. Click on the “Create” button.

Creation of Standard DSO

RELATED ARTICLES

Settings in a DSO

  1. Type of DataStore Object: changes the type of DSO. By default, Standard DSO is chosen. This can be changed to write-optimized or direct-update DSO.
  2. SID Generation upon Activation: generates the Surrogate ID (SID) for each master data value when this option is checked.
  3. Unique Data Records: used when the DSO will never hold duplicate values.
  4. Set Quality Status to OK Automatically: sets the quality status after data loading completes.
  5. Activate Data Automatically: automates DSO activation.
  6. Update Data Automatically: loads the data in the DSO to target objects automatically.

Including Key Fields and Data Fields in the DSO

A DSO contains two kinds of fields: key fields and data fields. The key field is used to make records unique. Other fields can be included as data fields.

Step 1) Right click on “Key fields” and choose the option “InfoObject Direct Input”.

Including Key Fields and Data Fields in the DSO

Step 2) The following pop-up opens. Here you can input the technical names of the InfoObjects to include and press Enter.

Including Key Fields and Data Fields in the DSO

Below shown are the key fields added in the DSO.

Including Key Fields and Data Fields in the DSO

Step 3) Navigational attributes are viewed in the DSO by default, but the ON/OFF check box has to be chosen if a navigational attribute is to be used in reporting.

Step 4) The DSO structure design is complete. Activate the DSO by clicking the Activate button.

Including Key Fields and Data Fields in the DSO

FAQs

During activation, records move from the activation queue (new table) to the active data table, and the before-and-after images are written to the change log. The change log enables delta updates to InfoCubes and other targets.

A standard DSO has three tables and requires activation, which allows overwrite and delta handling. A write-optimized DSO has only the active table, needs no activation, and loads faster, but it cannot overwrite records.

When SID Generation upon Activation is checked, SAP creates Surrogate IDs for each master data value during activation. This speeds up later reporting but slows activation. It can be switched off if the DSO only stages data.

Yes. Intelligent automation schedules loads and activation, while machine learning predicts long-running jobs and flags failures. The SAP Joule AI copilot can answer setup questions, reducing manual monitoring of nightly DSO loads.

Machine learning checks incoming records for duplicates, missing keys, and outliers before activation. This intelligent cleansing raises the trustworthiness of the active data that feeds InfoCubes and BEx queries.

Summarize this post with: