cancel
Showing results for 
Search instead for 
Did you mean: 

ODS between Delta and Info-cube.

Former Member
0 Kudos

Hi Gurus,

In most of the BW delta extraction scenairos we have ODS between Delta and Info-cube.

Can anybody explain me why?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Nrupal

Normally we say that we use ODS for Data consolidation,granular data,DW layer...and so on....but sometime it is mandatory to use ODS....yes we don't have any option for using cube only.....its because of the images sent by the source system. If image is in overwrittem mode we have to have ODS in flow as ODS supports overwritten ( Cube dont)

To make you understand

There is a table ROSOURCE in R/3 which define which data source support which delta.There is RODELTAM table which defines what is the images of a particular Delta searched in ....

So if the image is such that it is overwriting the data target than ODS is must as cube only support addition......

This is the reason most of the FI DS has ODS in between their data flow.....

Also follow below link for images

Hope it will help you

Thanks

Tripple k

Answers (2)

Answers (2)

Former Member
0 Kudos

Nrupal,

Hope the below stuff will answers both you r questions:

BW Delta Process: Record Mode

This attribute describes how a record in the delta process is updated. The various delta processes support different combinations of the seven possible characteristic values. If a DataSource implements a delta process that uses several characteristic values, the record mode must be a part of the extract structure and the name of the corresponding field must be entered in the DataSource as a cancellation field (ROOSOURCE-INVFIELD).

The seven characteristic values are as follows:

' ': The record delivers an after image.

The status is transferred after something is changed or added. You can update the record into an IncoCube only if the corresponding before image exists in the request.

'X': The record delivers a before image

The status is transferred before data is changed or deleted.

All record attributes that can be aggregated have to be transferred with a reverse +/- sign. The reversal of the sign is carried out either by the extractor (default) or the Service API. In this case, the indicator 'Field is inverted in the cancellation field' must be set for the relevant extraction structure field in the DataSource.

These records are ignored if the update is a non-additive update of an ODS object.

The before image is complementary to the after image.

'A': The record delivers an additive image.

For attributes that can be aggregated, only the change is transferred. For attributes that cannot be aggregated, the status after a record has been changed or created is transferred. This record can replace an after image and a before image if there are no non-aggregation attributes or if these cannot be changed. You can update the record into an InfoCube without restriction, but this requires an additive update into an ODS Object.

'D': The record has to be deleted.

Only the key is transferred. This record (and its DataSource) can only be updated into an ODS Object.

'R': The record delivers a reverse image.

The content of this record is the same as the content of a before image. The only difference is with an ODS object update: Existing records with the same key are deleted.

'N': The record delivers a new image.

The content of this record is the same as for an after image without a before image. When a record is created, a new image is transferred instead of an after image.

The new image is complementary to the reverse image.

The table RODELTAM determines which characteristic values a delta process uses (columns UPDM_NIM, UPDM_BIM UPDM_AIM, PDM_ADD UPDM_DEL and UPDM_RIM). The table ensures that only useful combinations of the above values are used within a delta process.

When extracting in the 'delta' update mode in the extracted records for the indicator, a DataSource that uses a delta process can deliver only those characteristic values that are specified in the delta process.

Definition

This indicator describes how a record in the delta process is updated. The various delta processes support different combinations of the seven possible characteristic values. If a DataSource implements a delta process that uses several characteristic values, the indicator must be a part of the extract structure and be entered in the DataSource as a cancellation field (ROOSOURCE-INVFIELD).

The seven characteristic values are as follows:

' ': The record delivers an after image.

The status is tranferred after something is changed or added. You can update the record into an IncoCube only if the corresponding before image exists in the request.

'X': The record delivers a before image

The status is transferred before data is changed or deleted.

All record attributes that can be aggregated have to be transferred with a reverse +/- sign. The reversal of the sign is carried out either by the extractor (default) or the Service API. In this case, the indicator 'Field is inverted in the cancelation field' must be set for the relevant extraction structure field in the DataSource.

These records are ignored if the update is a non-additive update of an ODS object.

The before image is complementary to the after image.

'A': The record delivers an additive image.

For attributes that can be aggregated, only the change is transferred. For attributes that cannot be aggregated, the status after a record has been changed or created is transferred. This record can replace an after image and a before image if there are no non-aggregation attributes or if these cannot be changed. You can update the record into an InfoCube without restriction, but this requires an additive update into an ODS Object.

'D': The record has to be deleted.

Only the key is transferred. This record (and its DataSource) can only be updated into an ODS Object.

'R': The record delivers a reverse image.

The content of this record is the same as the content of a before image. The only difference is with an ODS object update: Existing records with the same key are deleted.

'N': The record delivers a new image.

The content of this record is the same as for an after image without a before image. When a record is created, a new image is transferred instead of an after image.

The new image is complementary to the reverse image.

'Y': The record is an update image.

This kind of record is used in the change log of an ODS object in order to save the value from the update. This is for a possible rollback and roll- forward for key figures with minimum or maximum aggregation. This record also has the update value for characteristics (in this case, it is the same as the after image). Null values are stored for key figures with totals aggregation. An update image is only required when the value from the update is smaller or larger than the before image for at least one key figure with minimum or maximum aggregation.

The table RODELTAM determines which characteristic values a delta process uses (columns UPDM_NIM, UPDM_BIM, UPDM_UIM, UPDM_AIM, PDM_ADD, UPDM_DEL and UPDM_RIM). The table ensures that only useful combinations of the above values are used within a delta process.

Former Member
0 Kudos

- >EDW Enterprise Datawarehouse

ODS acts as a staging layer an additional store of data which is essential.

Stores Granular data ( Document Level Data )

Loads deltas to Cube if the datasource is not delta enabled.

Overwrite Functionality - Change Log