SAP BW on HANA Advanced DSO – Part 1
SAP BW on HANA 7.4 SP10 new changes has happened, will create Advanced DSO, composite provider and Open ODS view will create only in BW molding tools not in SAP GUI
Look forward will use only 3 objects BW data models
1. Advanced DSO – Persistent layer
2. Open ODS view – Virtual layer
3. Composite Provider- Joins/unions
This blog will describe Advanced DSO.
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 tables have (active, new, change log table ) like standard DSO (over write property)
4. Info cube model – select setting – all char are keys ( addition property)
Below is the changes are happened in object level
System version BW 7.40 SP10
Advanced DSO tables and purpose to use
Below tables are generated while activating the Advanced DSO (ADSO Name – ZODS_PAN1)
In this documents will discuss about, I can say Advanced DSO first model.
While creating the ADSO will select the active/compress data with check box write change log data.
If you select above options it will act as the standard DSO and it will generate 3 tables + 2 tables.
Modeling ADSO in Eclipse using BW modeling tools
Go to HANA STUDIO -> BW Modeling tools
Select the info area -> right click -> select Advanced DSO object
Below screen will appear
Ex ADSO Name – ZODS_PAN1
Create form templates
- None – will not select any object
- Data Source – if you select the data source need to give the source system name and data source name -> will create ADSO using the data source but data source has to create with respective source system.
- Info provider -> can use the existing info providers.
Click on finish then below screen will appear
Write change log table -> if you select data will insert into table
Keep inbound data, extract form inbound table -> if you select will keep the data in bound table and available for reporting
Unique data records – if you select duplicate records not allowed.
All char are keys, reporting on union of inbound and active tables – if you select this option ADSO will act as CUBE.
Extended table – The extended table’s concept relates to warm data and optimize the main memory resource management in SAP HANA by using extended tables
I will discuss about first model – write change log table with activate/compress data
Go to details tab -> below screen will appear
Add the info objects and key figures
Then select the keys for ADSO according to Keys data will transfer.
Selected customer as key fields in ADSO will use 120 key fields as maximum
Then create the data source in BW system and map the transformation form data source to ADSO
Aggregation type – overwrite and summation
ADSO Manage screen
Request generated as timestamp nothing but RTSN (Request Transactional Serial Number) while RTS Number we can find easily when it was loaded.
Another advantage for request generation in standard DSO while loading it will generate the BI_REQ but ADSO have Request TSN – Request transactional serial number.
When you activate a transformation, the system checks whether it can be executed in SAP HANA.
Whether this will be possible basically depends on the operations and objects used.
The following operations and objects are not supported for executing the transformation in SAP HANA:
ABAP routines are not supported HANA database and it will process in application layer.
(rule type, routine, routines for characteristics, start, end, and expert).
only one to one mapping objects process in HANA data base.
Next Blog will discuss ADSO 2nd Model.