ODS Object Structure

Definition:
“An ODS object (Operational Data Store) acts as a storage location for consolidated and cleaned-up
transaction data (transaction data or master data, for example) on the document (atomic) level.
This data can be evaluated using a BEx query.” (1)

ODS Structure:

There can be two types of ODS objects:

1. Standard ODS (this is the default type)

2. Transactional ODS

The Transactional ODS is made up of one transparent table on the database known as the “Active table”
while the Standard ODS is made up of 3 transparent tables:

1. Active Table
2. Activation Queue (also known by developers as New Data Table)
3. Change Log

Data loaded to the ODS but not activated, enters the New Data Table, where it awaits activation.
Upon activation of the data in the ODS, the records in the New Data Table are transferred into the
Active Table and the Change Log is updated. The records are deleted from the New Data Table.

When reporting is done on the ODS, it is the Active Data table that is used.

This graphic shows how the various tables for the ODS object work together during data loading. (1)

Figure 1.0 (Source:http://help.sap.com)

Dimuthu Wijeyesekera Page 1 of 12 3/20/2007

ODS Object Structure

Scenario to show the functionality of the 3 ODS tables:

Part 1: Uploading data to ODS for the first time

Data is uploaded into an ODS for the

first time.

The ODS settings and InfoObjects

are shown on the right.
Note that uploaded data will not be
automatically updated since the
setting “Activate ODS…” is not
ticked.

Figure 1.1

The text file format is:

DateOfRecord
CustomerNo
Quantity_ordered
Units
Keys are shown underlined.
Figure 1.2
There are 2 records in the text file.
Since each record is unique, no
overwriting will occur.

Note:
Overwriting can occur at the Update Rules stage as well as in the ODS itself.
At the Update Rules stage, if the data request has records having the same key, these will be
overwritten.
At the ODS Level, it is the “Active Table” that will get overwritten.

Dimuthu Wijeyesekera Page 2 of 12 3/20/2007

ODS Object Structure

By going to the “Monitor”, we can

see that the 1st request has been
carried out successfully.

Note the icon showing that data

has not been activated.

We will do a manual activation at a

later stage (by clicking the
“Activate” button in the
“Requests” tab, or by right-
clicking the ODS and selecting
“Activate data in ODS”.)

Figure 1.3

Note that 2 records have entered

the PSA, then the Transfer Rules
and lastly the Update Rules before
entering the ODS.

At the Update Rules stage, no

overwriting took place as the
records had unique keys.

Figure 1.4

Dimuthu Wijeyesekera Page 3 of 12 3/20/2007

ODS Object Structure

This part of the document will focus on the data in the 3 tables that constitute the ODS,
BEFORE activating the ODS data.

After the Update Rules, data enters

into the New Data Table.
This can be viewed by clicking the
“New Data” button.

Figure 1.5

The “New Data Table” contains the 2 records that were uploaded.

Figure 1.6

The “Active Table” contains no records. It will only be populated once the data in the ODS has been
activated.

Figure 1.7

Dimuthu Wijeyesekera Page 4 of 12 3/20/2007

ODS Object Structure

The “Change Log” has not been activated yet.

Figure 1.8

Dimuthu Wijeyesekera Page 5 of 12 3/20/2007

ODS Object Structure

This part of the document will focus on the data in the 3 tables that constitute the ODS,
AFTER activating the ODS data.

After activating the data in the

ODS, the following icon appears:

Figure 1.9

We will go through the 3 tables

once again.

New Data Table should
now have 0 records as it
writes to the Active Table
and clears its own
contents.

Active Table gets
populated with the 2
records that were in the
New Data table.

Change Log gets updated
too.

The “New Data Table” now has 0 records

Figure 2.0

Dimuthu Wijeyesekera Page 6 of 12 3/20/2007

ODS Object Structure

The “Active Table” now has 2 records.

Figure 2.1

The “Change Log” too has been updated with 2 records.

Note that the field Recordmode reads ‘N’ meaning “New Image”.

Figure 2.2

Figure 2.3: Record Modes

Dimuthu Wijeyesekera Page 7 of 12 3/20/2007

ODS Object Structure

Part 2: Subsequent data loads to the ODS

Data is uploaded into the ODS for

the 2nd time.

Note that the 3rd text file record

will overwrite the 2nd text file
record. This will happen at the
Update Rules stage itself.
Figure 2.4
Overwriting will also happen at the
ODS Level when the 3rd record in
the text file updates the record with
the same key in the “Active Table”
of the ODS.

The data upload is successful.

Note that the data in the ODS

hasn’t been activated yet.
(The green light above it shows the
1st request has now been activated)

Figure 2.5

Note that 3 records have entered

the PSA, then the Transfer Rules
and the Update Rules but only 2
records have entered the ODS.

At the Update Rules stage,

overwriting took place as the 2nd
and 3rd records had identical keys.

Figure 2.6

Dimuthu Wijeyesekera Page 8 of 12 3/20/2007

ODS Object Structure

This part of the document will focus on the data in the 3 tables that constitute the ODS,
BEFORE activating the ODS data.

We will go through the 3 tables

once again.

Figure 2.7

The “New Data Table” contains the 2 records that were uploaded by the 2nd request. (The 1st request
has been erased from here.)

Note that the overwriting that happened at the Update Rules stage can be seen here. The 3rd record has
overwritten the 2nd one.

Figure 2.8

“Active Table”  unchanged (Since 2nd request not activated yet)

It still contains only the 2 records from the 1st request.
The data from the 2nd request hasn’t entered this table yet, since the 2nd request hasn’t been activated.

Figure 2.9

Dimuthu Wijeyesekera Page 9 of 12 3/20/2007

ODS Object Structure

“Change Log”  unchanged (Since 2nd request not activated yet)

The “Change Log” too, still contains only the 2 records from the 1st request.
It hasn’t been updated since the 2nd request hasn’t been activated.

Figure 3.0

This part of the document will focus on the data in the 3 tables that constitute the ODS,
AFTER activating the ODS data.

The 2nd request has now been

activated.

Figure 3.1

The “New Data Table” now has 0 records as it writes to the Active Table and clears its own contents.

Figure 3.2

Dimuthu Wijeyesekera Page 10 of 12 3/20/2007

ODS Object Structure

“Active Table”  Now changed (after data in ODS has been activated).
Note the overwriting, now at the ODS Level.

Figure 3.3 (After activating) Figure 2.9 (Before activating)

“Change Log”  Now changed (after data in ODS has been activated).

Since overwriting has occurred in the “Active Table”, the “Change Log” has been updated with the Before Image
and After Image of the changed record.
The 4th record is the B.I. (X = Before Image)
The 3rd record is the A.I. (‘’ = After Image)

Figure 3.4

Dimuthu Wijeyesekera Page 11 of 12 3/20/2007

ODS Object Structure

Appendix:

1. Information:
The 3 ODS tables (and the Rollback Table) can be viewed in t.code SE11 as well.
The Change Log name can only be obtained after data in the ODS has been activated. (The 1st data load
can be activated and the Change Log name found.)

Syntax for Table Names:

New Data Table: /BIC/Aods_name40

Active Table: /BIC/Aods_name00

Change Log: /BIC/Bsystem_generated_number

Rollback Table: /BIC/Aods_name50

Figure 3.5
(In t.code SE11)

2. References:
(1) http://help.sap.com/saphelp_sem40bw/helpdata/en/1c/cb753cb4495864e10000000a114084/frameset.htm

Dimuthu Wijeyesekera Page 12 of 12 3/20/2007