Skip to Content

This Blog is very useful for SAP BW consultant switch to BW on HANA platform.Today We are going to see BW on HANA ADSO Types,Function and how it will work.

Below i have mentioned for ADSO Function and Types. It will be easy to understand for ADSO Function.

FUNCTION TYPE CHECK BOX WORKING FUNCTIONALITY FIELD/INFOOBJECT KEY MANADRY DATA ACTIVATION OVERWRITE/ADDITIVE FUNCTION INBOUND TABLE DATA AVAILABILITY ACTIVE TABLE DATA AVAILABILITY CHANGE LOG TABLE DATA AVAILABILITY DATA LOAD PROCESS BEX REPORT AVAILABILITY ADDITIONAL OPTION
* ENTERPRICE DATA WAREHOUSE ARCHITECTURE:
1. DATA ACQUISITION LAYER-INCLUDING CORPORATE MEMORY NO Need to Enable any check box Like a PSA No(KEY option is Disable) No need Active Data ADDITIVE(Aggregation) YES NO NO DIRECTLY LOAD TO INBOUND TABLE.
NO NEED TO ACTIVE DATA.
YES We Can Do,
1. Partitions
2. Hash Partitions Criteria
3. Index
2. CORPORATE MEMORY-COMPRESSION CAPABILITES Active Data Like a Write-Optimized DSO(BW 7.x Function) YES YES OVER WRITE NO YES NO WE NEED TO MOVE DATA FROM INBOUND TO ACTIVE TABLE.
FIRST DATA LOAD TO INBOUND THEN WE NEED TO ACTIVE DATA.
YES We Can Do,
1. Partitions
2. Index
3. CORPORATE MEMORY-REPORTING CAPABILITIES 1. Active Data
2. Keep Inbound Data Extract from Inbound table
New Concept:
* Its working like Write-Optimized DSO.
* But here Data Will Store from Inbound table and Active table.
* In Inbound table data will added(like a PSA)
* In Active table data will over write(like Write-Optimized DSO)
YES YES OVER WRITE YES YES NO FIRST DATA WILL LOAD TO INBOUND TABLE(ALL THE DATA LIKE HOW PSA STORE).
SECOND WE NEED TO MOVE ADD, NEW OR CHANGED RECORD ONLY IN TO ACTIVE TABLE.
IN THIS CASE WE NEED TO ACTIVE THE DATA.
YES We Can Do,
1. Partitions
2. Index
4. DATA WAREHOUSE LAYER-DELTA CALCULATION 1. Active Data
2. Write Change Log
Like a Standard DSO YES YES OVER WRITE NO YES YES SAP BW STANDARD DSO HOW WILL WORK SAME FUNCTION. YES We Can Do,
1. Partitions
2. Index
5. DATA WAREHOUSE LAYER-DATA MART 1. Active Data
2. All Characteristics are Key, Reporting on Union of Inbound and Active table.
Like a Info Cube No(KEY option is Disable) YES ADDITIVE(Aggregation) NO YES NO SAP BW INFO CUBE HOW WILL WORK SAME FUNCTION YES We Can Do,
1. Partitions
2. Hash Partitions Criteria
3. Index
* PLANING:
1. PLANNING ON DIRECT UPDATE 1. Direct Updte
2. Planing Mode
Like a Direct Update YES No need Active Data OVER WRITE NO NO NO IN THIS FUNCTION WE DON’T HAVE A TABLE(ITS VIRTUAL)
BUT WE NEED TO TRIGGER DTP.
YES We Can Do,
1. Partitions
2. Index
* CLASSIC OBJECTS:
1. STANDARD DSO 1. Active Data
2. Write Change Log
Like a Standard DSO YES YES OVER WRITE NO YES YES SAP BW STANDARD DSO HOW WILL WORK SAME FUNCTION. YES We Can Do,
1. Partitions
2. Index
2. WRITE OPTIMIZED DSO NO Need to Enable any check box Like a PSA No(KEY option is Disable) No need Active Data ADDITIVE(Aggregation) YES NO NO DIRECTLY LOAD TO INBOUND TABLE.
NO NEED TO ACTIVE DATA.
YES We Can Do,
1. Partitions
2. Hash Partitions Criteria
3. Index
3. INFO CUBE 1. Active Data
2. All Characteristics are Key, Reporting on Union of Inbound and Active table.
Like a Info Cube No(KEY option is Disable) YES ADDITIVE(Aggregation) NO YES NO SAP BW INFO CUBE HOW WILL WORK SAME FUNCTION YES We Can Do,
1. Partitions
2. Hash Partitions Criteria
3. Index

 

I hope this will help you for BW on HANA preparation.

 

Thanks &  Best Regards,

Gokul Rajasekar.

 

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Sebastian Gesiarz

    Hi Gokul,

     

    Could you please tell what is the reason you suggest that CORPORATE MEMORY-COMPRESSION CAPABILITES aDSO is the same as write-optimized?

    Write optimized DSO does not have activation step at all, it has only one active data table like DATA ACQUISITION LAYER-INCLUDING CORPORATE MEMORY.

     

    Thanks,

    Sebastian

    (0) 
  2. Former Member

    Hi Gokul,

     

    Can you please elaborate step 3,

    New Concept:
    * Its working like Write-Optimized DSO.
    * But here Data Will Store from Inbound table and Active table.
    * In Inbound table data will added(like a PSA)
    * In Active table data will over write(like Write-Optimized DSO)

    Both 3rd and 4th points are same i guess, in PSA and WDSO there will be technical keys only. So why to put the data twice in a same DSO?

    Or  in 4th Point you want to mention like Standard DSO?

    (0) 
    1. Gokul Raja sekar Post author

      Hi,

      Sorry for the delay Replay,

      For your doubt,

      Step 3:(CORPORATE MEMORY-COMPRESSION CAPABILITIES ADSO)

      Please consider below is our source data.

      COMPANY CODE VALUE
      CC1 10
      CC1 10
      CC2 20
      CC3 30

      If we load the data to “CORPORATE MEMORY-COMPRESSION CAPABILITIES ADSO”, Below are the format data we will get in the ADSO.

      INBOUND TABLE: (Once we active the data request. Data will move to Active table and here it will over write the data. but in Inbound table data will be same. Means data didn’t delete from the Inbound table)

      COMPANY CODE VALUE
      CC1 10
      CC1 10
      CC2 20
      CC3 30

       

      Active Table:

      COMPANY CODE VALUE
      CC1 10
      CC2 20
      CC3 30

       

      Step4: (DATA WAREHOUSE LAYER-DELTA CALCULATION)

      It’s Purely Standard DSO Functionality. Don’t mix it with 3 and 4 step.

       

      Thanks & Regards,

      Gokul R

      (0) 
  3. Gokul Raja sekar Post author

    Hi Sebastian Gesiarz,

    Sorry for the delay replay.

    As you mentioned, why i have compared CORPORATE MEMORY-COMPRESSION CAPABILITIES ADSO is the same as write-optimized?

    In Write-Optimized DSO have only Active table(No New table, Change log table at same time no activation data process also).

    But in Compression Capabilities ADSO one additional step we have to do for active the data.(In Compression Capabilities ADSO also have New table and Active table).

    Note: This document for just reference to understand, the BW on HANA Target how it’s work.

     

    Thanks & Regards,

    Gokul

    (0) 

Leave a Reply