What is Direct Update DSO in SAP? How to Create One?

By : Jessica Blake Jessica Blake
Hours Updated

⚡ Smart Summary

A Direct Update DSO in SAP BW stores data in a single active table written directly through APIs, with no change log or SID generation, making loaded data immediately available for analysis processes and reporting.

  • 🗄️ Single Version: A direct-update DSO holds data in one active table, exactly as written by the application.
  • 🔌 API Driven: Data is filled and deleted through RSDRI_ODSO APIs, not standard DataSources.
  • 🚫 No Change Log: There is no change log or SID generation, so delta updates are not possible.
  • 📊 Analysis Process: It is often used as the target of the Analysis Process Designer (APD).
  • ⚡ Immediate Data: Loaded data is available for reporting immediately after it is written.
  • 🤖 AI Assistance: AI writes scored or predicted results into a direct-update DSO for reporting.
Read More

What is Direct Update DSO in SAP

What is a Direct Update DSO?

A standard DSO differs from a direct-update DSO in how data is processed. In a standard DSO, data is stored in different versions (active, delta, modified), whereas a direct-update DSO contains data in a single version. Data is stored in precisely the same form in which it was written to the DSO. It consists of an active data table for direct update by the application and retrieves its data from external systems through fill or delete APIs.

The Available APIs

  • RSDRI_ODSO_INSERT: inserts new data that does not exist in the system.
  • RSDRI_ODSO_INSERT_RFC: similar to RSDRI_ODSO_INSERT, but can be called remotely.
  • RSDRI_ODSO_MODIFY: modifies existing records; if a new record comes in, it is inserted.
  • RSDRI_ODSO_MODIFY_RFC: similar to RSDRI_ODSO_MODIFY, but can be called remotely.
  • RSDRI_ODSO_UPDATE: modifies existing records.
  • RSDRI_ODSO_UPDATE_RFC: similar to RSDRI_ODSO_UPDATE, but can be called remotely.
  • RSDRI_ODSO_DELETE_RFC: deletes records.

Direct Update DSO Properties

  • It contains data in a single version, stored in precisely the form in which it was written by the application.
  • Records with the same key are not aggregated.
  • SIDs cannot be generated.
  • Data from it can be updated to additional InfoProviders.
  • It is available as an InfoProvider in the BEx Query Designer and can be used for analysis.
  • It is an additional function used in special application contexts.
  • It loads data quickly without using the extraction and load processes of the BI system.
  • It can be used as a data target for an analysis process.

RELATED ARTICLES

Direct Update DSO Functionality

  • It can update the direct-update DSO data to additional InfoProviders.
  • It can be used as an InfoProvider for the BEx Query Designer and for analysis processes.

Advantages:

  • It is structured to access data easily.
  • Data is available for analysis and reporting immediately after it is loaded.

Drawbacks:

  • The loading process is not supported by the BI system (DataSources do not provide the data).
  • Therefore these DSOs are not displayed in the administration or the monitor.
  • Since a change log is not generated, a delta update to InfoProviders is not possible.

Creation of a Direct Update DSO

Step 1)

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

Creation of Direct Update 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 Direct Update DSO

Step 3)

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

Creation of Direct Update DSO

Step 4) Click on the Edit button of “Type of DataStore Object”.

Creation of Direct Update DSO

Step 5) Choose the type “Direct Update”.

Creation of Direct Update DSO

Step 6) Activate the DSO.

Creation of Direct Update DSO

FAQs

A direct-update DSO stores one data version written through APIs, with no change log or SID generation. A standard DSO uses three tables, is loaded by a data transfer process, supports overwrite, and generates a change log for delta updates.

Data is written through the RSDRI_ODSO function modules, such as RSDRI_ODSO_INSERT to add records, RSDRI_ODSO_MODIFY and RSDRI_ODSO_UPDATE to change them, and RSDRI_ODSO_DELETE_RFC to remove them. Each has a remote-enabled (_RFC) variant.

It is mainly used as the target of the Analysis Process Designer (APD) and for applications that write results directly, such as planning or scoring. Because data is available immediately, it suits fast, application-driven reporting.

Yes. Machine learning and analysis processes can write scores, forecasts, or segments into a direct-update DSO through the RSDRI APIs. The results are then immediately available as an InfoProvider for BEx queries and dashboards.

Machine learning and the Analysis Process Designer (APD) read BW data, apply data-mining models, and write the scored output to a direct-update DSO. The results are then immediately available as an InfoProvider for reporting, without a standard extraction and load.

Summarize this post with: