BW DSO consolidation & trasnformations

[Former Member]

Folks

In our existing BI environment, there are 4 DSOu2019s namely: D101, D102, D201, D202.

D101, D102, D201 has Delivery, Delivery Item & Fiscal Year Variant as key fields

D201 has Sales Document, Sales Document Item, Fiscal Year Variant as key fields

D101 stores info on Drop ship delivery data

D102 stores info on Non Drop ship delivery data

D201 has consolidated Delivery item data coming from D101 & D102

D202 is fed through D201 through transformations.

In the data flow diagram, I had observed that D101, D102 are also feeding D202 along with D201.

1. I am wondering why there is a need for D101, D102 to feed D202 when D201 (which has consolidated data of D101, D102) is already feeding D202.

2. So, in general, if a DSO(202) already has a certain consolidated data coming from another DSO(201), what would the effect of having transformation between 101 & 202 , 102 & 202 ?? Doesnt this lead to a data duplication ??

3. For ex, I have following data :

D101(Drop ship )
-------
Deli. Doc, item, Qty, SO
D001, 10, 50, S001 
D002, 10, 20, S002

D102(Non Drop ship )
--------
Deli. Doc, item, Qty, SO
D001, 20, 60, S001
D002, 20, 40, S002

D201 ( Drop ship & Non Drop ship )
-------
Deli. Doc, item, Qty, SO
D001, 10, 50, S001 
D001, 20, 60, S001
D002, 10, 20, S002
D002, 20, 40, S002

D202 ( SO/delivery Item)
-------
Sales Order  Item Qty
S001, 10, 50
S001, 20, 60
S002,10, 20
S002, 20, 40

When 201 is linked to 202 & 101, 102 are also linked to 202, doesnt lead this do data duplication in D202 as below ??

Sales Order  Item Qty
S001, 10, *100*
S001, 20, *120*
S002,10, *40*
S002, 20, *80*

4. What is the advantage of this approach?

D101------>D202<------ D102
 |           |          |
 |---->----->D201<--<---|       

Thanks

Edited by: p706063 on Oct 28, 2008 3:37 PM

[Former Member · Accepted solution]

You are right, from what you observed, there is basically no necessity to keep either D202 or D201. However, what I have experienced is that since they have different keys, they might be used differently in further staging of data, eg into Sales Order vs. Fulfillment reporting cubes.

Might also be, that in D202 there are some calculations which are done in the transformation. The alternative then would be a loop load on D201 to do the calculations already there. But the way it is currently set up would provide better transparency, while increasing need for disc space.

Maybe you can give some more details, eg what the transformations are doing, or what different key figs you have in D201 compared to D202.

Cheers,

Klaus