DSO or Cube for reporting only characterstics values.

[Former Member]

Dear Experts,

We have a requirement where a report only has characteristics and no key figures and this report is transactional report(transaction level Detailed).

My question is that as this is a detailed report with no key figures, does loading this data to cube will be of any use in terms of query performance or can I report directly on DSO as performance is achieved on cube as it aggregates or compress the key figures but we don't have any key figs here.

So in this case does it make any sense to load the data to cube from DSO to improve query performance as I don't want to utilize additional background process to drop the cube data and do a full load daily if there is no improvement in performance.

Please let me know if I didn't explain my query well.

Many thanks.

[ccc_ccc · Accepted solution]

Hi John,

DSO: Advantages:

1. First decide what are primary keys of your report
2. Create DSO with decided primary keys by placing key fields, remaining fields place in data fields so that if any changes it will get overwrite so that you can get only new status records
3. No need to maintain key figure if you go with DSO, in case of cube you have to keep at least one key figure
4. Since your report does not have any key figure no need to go for cube, so that we can avoid data redundancy (keeping same kind of data in both tables(dso, cube)) waste of process and disk space also
5. Change log will available for any reconciliation purpose

DSO: Disadvantages:

1. Data request activation time
2. If they want maintain key figure in future, full drop and reload required.

InfoCube: Advantages:

1. Based on volume of data, if it less you can directly load data into infocube by deleting previous request ( to avoid conflict with previous and current status data)
2. We can avoid Data request activation process.
3. For future prof , if business want to maintain key figure it will be very easy to maintain key figure since we are daily deleting and reloading.
4. We can also combine infocube with another infocube for analysis purpose and include in multiprovider.

InfoCube: Disadvantages

1. If it huge amont of data , its very diffuclt load daily

Infoobject:

1. You can include all primary keys in compounding tab, load the data and activate
2. We cannot see change log here
3. It will available to include in any infocube/dso for any future purpose

ABAP Program:

1. If you know that all information is already available in BW in different data targets just write ABAP program to read data from multiple tables and display,
2. Instead of extracting data from source system and maintain in separate data models.
   

Please check in all aspects, take decision.

Thank you,

Nanda

[Former Member]

Dear Experts,

Many thanks for your valuable inputs.

So I think I am very much  clear on the modeling part i.e. to go with a DSO.

Still a doubt which remains is the query performance........In scenarios like this...Even if I create a dummy key figure and go ahead with cube....does cube has any advantage in terms of query run time than DSO ? I mean I heard people saying Cube has index and so query performance would be much better than DSO......is this true ? What if I create secondary index on DSO ....still cube will be better in terms of performance or ???

Regards.

[Former Member]

In your case DSO is as good as Cube, Query restrictions and filters should be reflected in the secondary index of DSO.

With DSO model - You can always transition into a cube model in future if required.

[KodandaPani_KV]

HI,

with out key figures we can not create the cube but we can create the DSO with out key figure values.

DSO have the operational reporting.

it was two dimensional model.

DSO level have detail level data.

'

CUBE

it was multi dimension model.

it will store the aggregated data.

for your point don't have any key figure values, DSO will create with out any key figure values.

but CUBE we can't create the with out key figure. required one key figure mandatory.

if don't have any key figure values go with the DSO reporting.

select the DSO setting - SID generation upon activation.

Thanks,

Phani.

[fcorodriguezl]

Hi John,

No sense.

BW is only for analytical information, and you only need create a Query without keyfigures.

I recommend use your ODS to create this report.

Regards.

[Former Member]

John,

Use DSO for reporting , define a good key structure.

Define as many secondary index as permitted.

Cube load is not appropriate unless to make it look complex, but you can use cube too with a dummy KF(say count).

Gopi

[Former Member]

with out key figures

how can you create aggregates and compression on info cube ?

Is not possible with out key figure created  data loading into info cube

aggregates property summarized key figures based on same characteristic values.

compression property reduced the number of records by combining records with same key ,Requst id deleted

data records moves from f table to e table

[former_member227168]

Hi John,

Have you create cube without key figure ?

If create report based on CHAR and KEY figure i think key figure display properties will be hide in reporting.

either no data loading CUBE amd DSO,

Please check data available in PSA level in key figure,

There is no diffrent reports used based on CUBE or DSO.

Thanks,

Ram's.

[Former Member]

Hi John,

I think keeping the data in DSO is the best way in your case as far as I understood. Because you have no keyfigure. addition to this, infocube is set of relational tables as well. So you will increase complexity.

Cheers,

Sarhan.