Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Applies to:

SAP NetWeaver Business Warehouse (formerly BI). This will work on SAP BI  7.0 and further versions.

Summary :

This document will help to understand the various steps which happen during a data gets loaded to DSO and further to the cube.

We are focussing on the role of tables of standard DSO here .

Author: Arpit Khandelwal

Company: Accenture Services Pvt. Ltd.

Author Bio:


Arpit Khandelwal is a SAP BI Consultant currently working with Accenture Services Private Limited. He has around 2 years of experience in BW/BI implementation and support projects. He has been particularly involved in Archiving Activities in SAP BW system.

Detailed Working ::

We have a simple data flow to explain standard DSO table’s working in a very simple manner.The document might be very long but each step has been explained very clearly to make the readers understand the process in a much better way.

Simple initial requirements to understand this document is that a standard DSO has 3 tables :

1) New Data

2) Active

3) Change Log

We will use the flat file load to explain the working of Delta load in standard DSO.

The snapshot of our initial Info Package (here after referred to as IP)

We are taking only a single record in our flat file to load the data in DSO.


After loading this in our standard DSO, we check all the 3 tables of the DSO to understand working of DSO here.

Before Activation

a) Data in New Table :


b) Data in Active Table :


c) Data in Change- Log table :


After Activation

a) Data in New Table :


b) Data in Active Table :

c) Data in Change- Log table :

So, when we are activating the data , it is moving from new table to Active and Change Log tables.

Note that the Record Mode here in Change Log table is N.

Loading this data to further Cube ::


The data is same in cube as that in the DSO. This covers our half portion of the document.

Now, loading new data for same fields (account, center,etc.) in a new flat file ::


After loading this in our standard DSO, we will again check all the 3 tables of the DSO to understand working of DSO here.

Before Activation

a) Data in New Table :


b) Data in Active Table :


c) Data in Change- Log table :

So now before carrying out the activation, there will be no change in Active & Change Log table while the new data loaded will come till the New Table only.

After Activation

a) Data in New Table :


b) Data in Active Table :

c) Data in Change- Log table :

Here , we will get two entries each of the 1st file and 2nd file as RECORD MODE N and a negative value for 1st record already in Change-Log table as RECORD MODE X.


  1. RECORD MODE N -  New image is created when a new record comes in Change-log table.
  2. RECORD MODE X -  Once the data is already there in Change-log table it will get as reversed image in the next load to avoid duplicity of data in load to cube further.


This is necessary because the data which goes to further cube will be decided by the record mode only.

Loading this data to further Cube ::

The data is same in cube as that in the DSO’s Change-log for new image.



10 Comments
Labels in this area