See more in our hbites Advanced DSO
Advanced dso is the basic data target in BW 7.5 which can be used to store data in different layers of datawarehouse. It is used in modeling extensively for storing and transferring data to further data targets.
SAP has simplified its modeling objects by bringing up different types of ADSO which can be used as standard dso, infocube, PSA, write optimized, planning cube, direct update, inventory cube etc.
Thus, we do not have to create different objects for different functions, simply we have to select appropriate template while creating ADSO.
Below objects can be modeled using ADSO:
- PSA for data storage as it is from source (Data Acquisition Layer)
- Standard dso for delta calculation (change log) with overwrite functionality (Datawarehouse Layer – delta calculation)
- Corporate memory with reporting capabilities
- Corporate memory with compression capabilites
- Direct update dso for planning
- Standard Infocube with summation functionality, non cumulative key figures (Datawarehouse Layer – data mart)
- Planning Infocube
So, in this way, we can see that there are 7 types of advanced dsos.
Whenever we create an advanced dso, below backend objects are created irrespective of the type of ADSO
- /BIC/A<ADSO tech name>1 – This is the activation queue or New table also called as Inbound table
- /BIC/A<ADSO tech name>2 – This is the active table
- /BIC/A<ADSO tech name>3 – this is the change log table
- /BIC/A<ADSO tech name>6 – this is the Extraction View
- /BIC/A<ADSO tech name>7 – this is the Reporting view
These tables and views can be seen in the HANA database under the corresponding ABAP schema.
now we will see the significance of these tables and views, there are lot more changes as previous versions and you should understand clearly the usage of these backend objects.
- If your ADSO is of type cube, then the inbound table act as F table, once you activate data, this acts as compression and data is moved to active table which acts as E table in this case. The data is available for reporting and extraction both from the inbound table as well as the active table.
2. If your ADSO is of Write Optimized or PSA (Data acquisition layer), then inbound table data used for storing the data. Active table is not used.
3. If your ADSO is of type Corporate Memory with compression capabilities, then inbound table is used to store granular data, when activated, this data is deleted and moved to active table
4. If your ADSO is of type Corporate Memory with Reporting capabilities, then granular level data is stored in inbound table, when we activate data, it is compressed based on semantic keys and stored in active table, but the data in inbound table is not deleted after activation. When we load data to further targets, the data is extracted from inbound table. Active table is accessed for reporting purposes.
5. If your ADSO is of type standard DSO, then inbound table stores the records initially, then this data is deleted after activation. Active table and change log are used for reporting and extraction purposes.
6. If your ADSO is of type direct udpate, then inbound table and change log table is not used, only active table is used to store data and for extraction and reporting purposes.
Please note here the terminology to understand the types of ADSO-
ADSO of type Data Acquisition Layer (including CM) is same as Write optimized DSO
ADSO of type Datawarehouse layer-delta calculation is same as Standard DSO (classic)
ADSO of type Datawarehouse layer-data mart is same as Infocube
Please check next post on creating and loading data to ADSO and checking the above functionalities.
See more in our hbites Advanced DSO