Corporate Memory type of ADSOs

See more in our hbites Advanced DSO

Corporate Memory means storing the data as it is from source in the data warehouse.

In BW4HANA, SAP has provided three type of ADSO which have this function of storing granular data-

1. Data acquisition Layer (including Corporate Memory)
2. Corporate Memory with Compression Capabilities
3. Corporate Memory with Reporting Capabilities

First we will create Data Acquisition Layer type of ADSO

(Note: To learn more about the concepts of ADSO, please see the post here, and here)

Go to BW modeling perspective in HANA studio

Open your infoarea, right click and select, New – Advanced DSO

In the General tab, select the first template “Data Acquisition layer” and click on “Apply Template”

• Assign the infoobjects and fields in the ‘Details’ tab

• Click on save and activate
• Attach HANA system to your BW system
• Go to HANA modeling perspective, search your schema name (BW owner schema)
• in Tables and Views folders, filter on the ADSO name you have just created
• check the backend tables generated and their columns, you can also see these tables in the ‘Properties- DDIC’ tab
• Note that for this type of ADSO, only Inbound table is generated. Reporting View is same as inbound table less fields record and data packet ID. Extraction view is same as Inbound table.

• Load the data to this adso using file source system

• Go to GUI -> RSA1 and select MANAGE screen, note the options available (whether you can activate data for this type of ADSO?)

• Note Inbound table and extraction view has same number of columns, reporting view has 2 less columns (record and data packet id columns are absent in reporting view)

Understanding incremental loads to ADSO of type Data Acquisition Layer (including Corporate Memory)

Below data is changed in only units sold values, rest all field values are same-

Before values-

After values-

Now load this data to our ADSO created above-

The new data is not aggregated and is shown separately in Inbound table, separated by Request TSN-

This behavior is similar to PSA or Write Optimized DSO.

If we see the Inbound table structure in SE11-

We can see that Request TSN, Data packet and record number are the keys-

So, this type of ADSO is a corporate memory with all the versions of source data stored in it as it is.

If we want to aggregate this data, we need to select another type of ADSO which is Corporate Memory with Compression Capabilities, here when you activate the requests, the records are aggregated based on the semantic keys defined in the DSO and request TSN is deleted. Also the inbound table is deleted after activation.

So be very sure before activation that the data records are correct in the inbound table and loaded with all the delta records. Then only you should activate/compress the data.

Once the records are activated, you cannot delete them on request basis. Only you can do selective deletion.

ADSO of type Corporate Memory with Compression Capabilities

To check this in the system, create new ADSO of type corporate memory with compression capabilities (take above DSO as template)

You can see that only difference from earlier DSO is that the “Activate data” checkbox is enabled.

Leave all other settings as same and activate the ADSO.

Below error will be seen-

Hence for this type of ADSO, you must define the primary keys of your data. Go to Details tab and define the keys-

Click on Manage Keys

Select the key fields and click ADD

Now activate your ADSO

Load the data to this ADSO, you can do this from file or from previous ADSO

Note the tables created for this ADSO

Note that the records are not aggregated as in previous ADSO.

Now activate this request, the records will be aggregated based on the primary keys you selected while creating the ADSO-

Note that there are only 8 records in Active table

We can see that only after values are shown in the active table-

When we check the transformation, we can see that the key figure is set to Overwrite, hence only latest values are shown after activation-

On checking the drill down we can see that the summation option is also available-

Thus, if we select summation, the qty shown after activation will be summed up from the inbound table based on the keys.

Also, observe that the inbound table is deleted after activation-

ADSO of type Corporate Memory with Reporting Capabilities

Let’s load the same data to the ADSO of type Corporate Memory with Reporting Capabilities and see the difference

Create ADSO of this type, in the details tab, you can add infoobjects instead of fields to have more features in reporting

(Note: Infoobject can also be added to earlier two types of ADSO, but in staging layer we do use mostly fields to quickly load the data as in PSA)

Here the option ‘Keep Inbound data’ is checked.

Load the data, load from DSO of type 1 (Data acqusition type DSO ZAK_ADSO1 created above)

The data is first loaded to inbound table.

Activate the data.

Check the data in Inbound and Active tables.

The inbound table will have all the data history and the active table will only have latest data.

Try to delete the request after activation, the system will not allow you to do so-

In this case, you can right click and delete complete data or perform selective deletion of data-

The advantage of this type of ADSO is that the detailed data is not lost after activation. It is used for extraction to further data targets.

Also if we create queries on this type of ADSO, it fetched the aggregated data from the Active table.

See more in our hbites Advanced DSO