What is DSO in SAP BW? Why Use It?

By : Jessica Blake Jessica Blake
Hours Updated

⚡ Smart Summary

A DataStore Object (DSO) in SAP BW is a two-dimensional transparent table that stores consolidated, cleansed transaction or master data at the lowest granularity, supporting overwrite functionality and detailed-level reporting before data moves to an InfoCube.

  • 🗄️ DataStore Object: A two-dimensional transparent table that stores cleansed data at the lowest granularity.
  • 🔍 Detailed Reporting: Data is held at detailed level, so document-level reporting is possible from a DSO.
  • 🔁 Overwrite Option: Unlike an InfoCube, a DSO can overwrite key figures when characteristics match.
  • 📥 New and Active: Loaded records sit in the new table until activation moves them to the active table.
  • 🗃️ Three Types: DSOs are classified as standard, direct-update, and write-optimized.
  • 🤖 AI Assistance: AI and SAP Datasphere use clean DSO data as a reliable base for analytics.
Read More

What is DSO in SAP BW

What is a DSO?

A DSO is a two-dimensional storage unit that mainly stores consolidated and cleansed transaction data or master data at the lowest granularity. DSO stands for DataStore Object.

  • It is a two-dimensional transparent table.
  • Data is stored at detailed level.
  • With a DSO, it is also possible to overwrite data fields.
  • Detailed-level reporting can be obtained from a DSO.

Why Use a DSO?

Take the example of sales order data, which is extracted from a SAP R/3 system (OLTP: Online Transaction Processing data that keeps changing) into BI. Sales orders created in R/3 can be edited at any time after the record is created. Initially the records are extracted into BI, and once they are changed in R/3, the changes need to be reflected in BI.

DSO in SAP BW

  • Data is extracted from the SAP R/3 system and loaded into the DataStore Object.
  • Initially, records are stored with New status in the new table.
  • Once the DSO data is activated, data is stored in the active table and the new table no longer holds it.
  • When records are changed in R/3, the changes are extracted into the DSO to reflect in BI.
  • The data is stored in the new table until the DSO contents are activated, then loaded into the InfoCube from which reports are delivered.
  • A DSO has overwrite and additive functionality. If all characteristics are the same, key figures are aggregated or overwritten based on the chosen functionality.
  • An InfoCube is additive in nature: if all characteristics are the same, key figures are aggregated.

RELATED ARTICLES

Types of DSO

DSOs can be classified into the following types:

  1. Standard DSO
  2. Direct Update DSO
  3. Write-Optimized DSO

FAQs

A DSO stores cleansed, detailed data in transparent tables and can overwrite key figures, supporting document-level reporting. An InfoCube stores summarized, aggregated data on the extended star schema and is additive. DSOs often feed data into InfoCubes.

Key fields make each DSO record unique, like a primary key. Data fields hold the remaining values, such as key figures and attributes. During activation, records with the same key fields are overwritten or aggregated based on the DSO settings.

With overwrite, a new record with the same key replaces the existing key figure value. With additive, the new value is added to the existing one. Overwrite suits changing data like order status; additive suits cumulative totals.

DSOs hold clean, detailed data that machine learning and SAP Analytics Cloud use for forecasting and anomaly detection. In SAP Datasphere, AI reads this trusted layer to surface insights and answer natural-language questions without manual queries.

Yes. Machine learning profiles DSO records to flag duplicates, missing keys, and outliers before the data is reported. This intelligent validation improves the reliability of the detailed data feeding InfoCubes and queries.

Summarize this post with: