Sales document data in IC / DSO

[Former Member]

Hello gurus

I am having sales document( you can assume data to be header data / item level data) in my PSA.

I want to load this data into my infocube and standard dso.

But I am not creating any aggregates / roll up / compresison on my infocube.

Simply putting it I just want to load this data into the repsective infoproviders and then report upon it.

Could any one pls let me know whether I should go for Infocube or DSO?

If Infocube theny why and if DSO then why?

Please be specific with an example.

Points will be assigned immediately.

regards

krishna

[anshu_lilhori · Accepted solution]

HI,

It depends on your requirement.Normally if you follow LSA approach which is layered service architecture

In this data is stored in DSO and then to Cube.Detailed level information will be stored in dso and summarized information will be updated in Cube.

DSO is considered to be SPOT (Single point of truth)whenever there is a data mismatch then you can easily look the data store in dso and validate with R/3.

At first level store the data as it is coming from source then apply your business logics at second level.

This is considered to be best practice and again it varies from company to company and client to client.

In nutshell if you have detail level report requirement then do reporting on DSO and if its summarized level then Cube.

Hope that helps.

Regards,

AL

[esjewett]

This was posted in the Data Warehousing space but it belongs in the BW space. I have moved it. Please use the BW space for questions about BW in the future.

Also, do not offer or guarantee points when asking your question. It is assumed that you will assign points as necessary.

Regards,

Ethan

(moderator)

[former_member192933]

Hi,

In addition to what have already been mentioned;

The decision between a DSO or an Infocube not only matters with how you load the data, but also with the multi- dimensional analysis. DSO is not designed for this. If you try to run the report against non-key field values in the DSO, the report will take longer because as you might be knowing the DSO has 3 transparent tables and reporting on top of it creates joins between the tables.  So performance wise, Infocube is much better than DSO for reporting. In cases where the Standard DSO is not used for reporting and is just used for staging purposes, it is recommended to uncheck SID generation upon Activation checkbox in DSO settings.

Regards,

Anjali

[former_member210676]

Hi Krishna,

If reporting is the main purpose, please load these to infocubes, else if its for initial data staging, then load it into DSOs.

Cube - Read Optimized (Reads can happen quicker based on many dimensions)

DSO - Write Optimized (Loads are quicker, read is quick only if its based on primary key)

Yours,

Hari ...