Hello Friends,

Welcome Back. You might had come across many of my blogposts on HANA classic and HANA XSA,SAP BODS 4.2, SAP BTP and SAP CAI chatbots etc.

Well I also had worked on SAP BW, BWonHANA and now currently I am working on SAP S/4 HANA Embeded Analytics/SAC area.

Many may get confused by hearing this new word SAP S/4 HANA Embeded analytics but the underlying concept is both the OLTP and OLAP layers are sitting on 1 client. Which means ECC or the Suit 4 HANA and the data warehousing layer for SAP which is called Business warehouse are on a single client.

Why this move ? Little Back ground!

in the past when we have traditional ECC and BW both the OLTP and OLAP systems were on different client even now there are cases S/4 HANA and BW4HANA are also on different client then why S/4 HANA Embeded analytics ?

This is because of SAP’s in memory database called SAP HANA which is capable of doing multiple calculations on the fly by pushing the code deep into the database with the help of Code to data paradigm CDS views, ABAP managed database procedures for faster read and write, HANA DB’s in memory computing, data compression, delta merge and removal of many primary and secondary indexing tables etc., bidirectional modelling side CAR approach etc. etc. That is why HANA is called the FAST DB.

Because HANA is FAST database with excellent compression features  it makes no sense to have separate SAP OLTP and OLAP systems. Though keeping OLTP & OLAP systems separate have their own advantages but SAP S/4 HANA Embeded analytics came as a big move for SAP to do operational reporting on SAP UI5/Fiori based KPIs/chats/Tiles on top of CDS Views and Analytical reporting by loading data into SAP BW advanced Data Storage Objects aka. ADSOs(persistent staging area in SAP BW4HANA or SAP S/4 HANA Imbedded analytics.

You can read about my blog on why SAP S/4 HANA evolved from the traditional SAP ECC

The technological answer is in below article in a detailed manner ?

https://www.linkedin.com/pulse/s4-hana-digital-corewhy-technological-answer-narasingha-patro/

Ok Now you have got some idea about SAP S/4 HANA, BWONHANA, BW4HANA SAP S/4 HANA Embeded analytics.

Be it BWONHANA or BW4HANA or SAP S/4 HANA Embeded Analytics the most common thing is an ADSO which the  persistent staging area for the data to reside. This is the object where actual data resides in different tables.

in this blog we will understand little deep into ADSOs and it’s structure.

Purpose : ADSO is poised to replace all info providers that provide data in separate tables-for instance, Info cubes, DSOs and write optimized DSOs. The ADSO can consist of simple fields as well as InfoObjects.

In general, we have below mentioned layers that are available under EDW model Template in ADSO.

1. Data Acquisition Layer (Including corporate memory)
2. Corporate Memory – compression Capabilities
3. Corporate Memory – Reporting Capabilities
4. Data warehouse Layer : Delta Calculation.
5. Data warehouse layer – Data Mart.

now we would see how each layer is different from others with respect to its behavioral mechanism.

Before we get into the behavioral aspects, Please note the below tabular columns that depicts the system tables for their corresponding functionalities performed.

Create a test ADSO with reference to a cube (considered template as ZFIAR_C06 cube) in ADSO, HANA Studio under BW modelling perspective.

1)  Data acquisition layer (Including corporate memory):

This layer do not use Active table and has only Inbound table which means it is just an New Data/Activation table. Here you cannot find activation request. Inbound table contains Request Transaction Number(TSN), Data Packet and Data Record Number. This is in general used as Persistent Staging Area(PSA) and in the 1st Layer of EDW Architecture.

Example :

2) Corporate Memory – Compression Capabilities 

This Layer contains the loaded data in Inbound and Active table. Upon activating the request, Inbound data will be deleted and the system loads data Active Table. This layer does not use Change log table.

In short, this layer is used if you want to save space but do not required to track load requests. We can go with this kind of layer wherein, we no need to trace it back and can afford save space by activating it and not using change log.

Steps:

Create a ADSO with selection on Corporate memory -compression capabilities as shown, for instance Z_T_CM_CC as technical name. By default Activate data is selected.

Note : If we Key definition is not specified, on activating this, it will throw error as depicted in below screenshot.

3) Corporate Memory – reporting capabilities 

The only difference between the corporate memory -compression capabilities and this layer is, this layer holds both Inbound and active data as the “Keep Inbound Data, extract from Inbound Table” is turned on, which means when these kind of ADSOs are activated , the system does not erase the data from inbound table. Instead keeps data both in Inbound as well as Active Data Table. No Change log data available.

Steps :

Create ADSO

Technical Name : Z_T_CM_RC

Description : Corporate Memory – reporting Capabilities

Info provider template as a cube ZFIAR_C06

Maintain Keys if they are n’t

Select the required Chars and add them as Key in Manage Keys(Steps in detail is shown in Layer 2).

4) Data Warehouse Layer – Delta Calculation:

This layer is modeled like a Standard DSO. That means that these types of ADSOs have a change log table for delta extractions, as Inbound table and an active data table that is used for reporting and full loads.

In short, this layer can be functioned as a central object from which only new and changed records are loaded to the next layer.

Steps:

ADSO Creation

Technical Name Z_T_DW_DC

Description : Data warehouse layer – delta calculation.

Template Info provider : ZFIAR_C06

5) Data warehouse Layer – Data Mart

This layer stores data in Inbound table before activation but once activated data from Inbound table is deleted and data is stored in Active Data Table. No Change Lo data. The important feature for this layer is the system “Unions” both the inbound and active data table together for reporting and extraction. This layer functions as Info Cube in which Inbound table acts as F- Table and the active data table as E-table.

Steps

ADSO TECHNICAL name Z_T_DW_DM

Description : Data warehouse Layer  data mart

Template Info provider : ZFIAR_C06

We can see in this layer, all chars are key and are defined automatically for which the manage keys icon is disabled, which means it does not allow as to manually select the key records.

conclusion : These above are the different layers while creating an ADSO. Based on your business case you may choose the layer for the ADSO.

Thank you,

Narasingha