Problem solve Get help with specific problems with your technologies, process and projects.

Using ODS objects for reporting purposes in BW

ODS objects support detailed information for reporting needs but can cause query performance issues. Peter Scott considers the options for BW reporting.

Our BW team uses ODS objects for most reporting purposes, which causes our database to grow at an alarming -- and probably unsustainable -- rate. Query performance is terrible, since many of these ODS objects are around 30 million rows in size -- yes, really 30 million. The team feels that they must use ODSs as they record data at the line-item level rather than at a more aggregated level.

Is there a better way to store and report on such detailed information? Personally, I feel that they are using BW in the manner which they used Business Objects and have applied the same logic. We really need to move them away from such large objects.

Usually, it is recommended that all reporting occur off of InfoCubes, as performance will be better. It is still necessary at times to look at line item details, but you're going to have performance issues, as you've identified.

There are many architectural considerations to your question as you may want to look at how you've modeled your data and how you have rolled up InfoProviders from a level of ODS objects to InfoCubes and again up to MultiCubes. With the right data architecture, you can push most reporting to a cube level and use jump targets or report-report-interfacing to access line item data is a controlled manner when required.

Dig Deeper on SAP business intelligence

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.