Advanced DSO (ADSO) is the primary artifact for persisting data in SAP BW 7.4 onwards. It combines functions from the Infocube/DSO and provides further enhancements such as modeling on Infoobjects as well on simple fields.
Till B4HANA 1.0, ADSO model types were determined by selecting the appropriate settings shown in the below image. In addition to that, SAP provided predefined templates which when chosen, the settings will get adjusted accordingly.
In B4HANA 2.0, the modeling screen has undergone a change. Our blog discusses each ADSO types in detail and the corresponding setting that needs to be chosen in B4HANA1.0 and B4HANA 2.0.
Data acquisition layer (including corporate memory) / Write optimized DSO
This is similar to the write optimized DSO which contains only the inbound/new table and no change log or active table. You can use this ADSO as the staging area in your data warehouse model.
Corporate memory – compression capabilities
Corporate memory enables you to store the entire history of the data for reconstruction purposes, without the need to extract it from the source system. ADSO also enables you to compress this data, thereby reducing the overall data footprint. However, you will not be able to trace the record back to its load after enabling this option.
This ADSO contains the inbound and active table and upon activation, data in the inbound table is cleared and the active table gets compressed by aggregating record based on their semantic key, which is basically overwriting the previous record with the value present in current load. For key figures, the aggregation depends on the type (Overwrite/Summation) selected in the transformation.
Corporate memory – reporting capabilities
The only difference between this ADSO and the one above is that after activation, data remains in the inbound table. This will enable you to trace records back to their corresponding source data loads.
Data is extracted from the inbound table and reporting is done on the active table.
Data warehouse layer – delta calculation / Standard DSO
This setting will enable the ADSO to behave like a Standard DSO, which means it will have a Change log table for delta extraction, Inbound/New table and active table for reporting and full load.
Data warehouse layer – data mart
The data mart option enables the ADSO to behave just like an Infocube, it does not have any Changelog. The inbound table acts like an “F table” and active table acts like the “E table” for compressed data. Upon activation of the request, the inbound table is cleared.
Planning on Infocube – like
This ADSO is modeled like the Data mart ADSO. It has an Inbound table and active table. All characteristics are marked as key fields in the active table which is a necessary requirement for planning.
Planning on Direct Update
This setting allows planning on a direct update ADSO. Data is loaded directly into the active table using DTP or an API. This DSO has an overwrite option unlike the Planning on Infocube model which avoids duplicate records.
In order to use non-cumulative key figures, we must select “Inventory-Enabled” setting on the ADSO. As of now, this is supported for Standard ADSO’s and cube type ADSO’s.
Know more about our SAP BW Services offerings here.