Advanced DSO Models – Part 2
Previous Blog discussed about ADSO how to act as Standard DSO
SAP BW on HANA Advanced DSO – Part 1
now will disucss ADSO how to act as INFO CUBE.
Advanced DSO have persistent object is combination of below objects
- 1. Field based structure of PSA ( filed based modeling)
- 2. No activation required for like WDSO (update property)
- 3. 3 table have (active, new, change log table ) like standard DSO (over write property)
- 4. Info cube model – select setting – all char are keys ( addition property)
Advanced DSO 2nd Model
Previous blog discussed about ADSO first model like standard DSO
Now will discuss about ADSO like act has Info cube
Go to the BW Modelling tools in HANA Studio -> select info area -> click on the Advanced DSO
Select the option All characteristics are key, reporting on union of inbound and active table
If you select above option ADSO like act as Info cube
After insert the info objects into ADSO like below
Here one important thing Keys option disable means all the objet like act as Keys we cannot define particular object as keys
Under setting options below options is available
We can do partitions and indexes on ADSO
Transformation mapping form data source to ADSO with only one option SUMMATION
Means it will like act as Info cube
Under Rule type we can do read records form the ADSO Model – Active data table
While designing the ADSO all the tables will generate but change log table not in used
Sample PSA data with 3 customers
After loading Active data table records
After 2nd loading values is addition for ZIA_AMT amount key figure.
Next Blog will discuss about ADSO how to act as Write optimize DSO.
Nice blogs Phani 🙂
Nice blog pani
I have a question and maybe you can help. I would like to model an aDSO to behave like a classic cube and to use (range) partitioning as we are load large amounts over data (2bn+ records). Classic cubes do not require activation, i.e. data is written directly into the fact table (simply by adding the records). With an aDSO however I have only two options:
a) Use no key fields at all --> No partitioning is possible (and I do not have to activate)
b) Use key fields --> I have to activate the data as only the 2-table has range partitions. However if I activate the system needs to move the data and will aggregate it, i.e. the object will behave differently as compared to the cube.
Any ideas? Am I missing something?
SAP said ADSO can replace PSA, does it mean we can extract (Full/Delta mode) data directly into ADSO from source system without PSA? Or it just mentioned ADSO can based on fieled, while PSA still needed?
Could you tell me about how ADSO act as PSA? many thanks
I have an observation I would like to share with you and to know if your systems shows the same behavior:
When I create ADSO as InfoCube (Activate data + all characteristics are key, reporting as unions on inbound + activate table) I do not have the option to maintain any key in the BW modeling tools. The active table itself in HANA database also shows no keys at all for active table.
However, in SAP DDIC / SE11 I can see the characteristics are ticked as key for the same active table. Now, when I add characteristics to the DSO, table propoerty in HANA DB remains same (no keys like in BW modeling tools), but in SE11 these new fields are added as data fields! This concerns me a lot as I would expect the new fields as part of the key.
Can you check in your system?
How do you evalute this?
Hi Lars-Oliver Kamp
were you able to resolve your issue? is there any note which can correct this behavior?
Kishore Kumar Challa
It is Very Nice doc..Phani