Find Reporting and Performance Problems Before Your Users Do

  • by Joerg Boeke, Independent BW Senior Consultant and Solution Architect
  • November 1, 2003
Problems with the reports or routines you build are not always obvious until they are in live use. In some cases, performance might be slower than it should be, or in other cases incorrect data finds its way into important reports. The author shows you how to create an audit workbook, which bundles all your test queries, so that you can automate your testing process. You will also learn how to audit BW metadata and query performance.


Has a user ever called you about a reporting performance problem even though all your scheduled tasks ended properly? Or, has a reporting user complained to you about obviously false data in a report? More and more important decisions are being made based on BW reports, but problems with query performance and data correctness make your BI installation less reliable (and your job less enjoyable).

For example, what about the case where an InfoPackage for loading data into an InfoCube ends properly, when the data in the InfoCube is visible, but either the performance is nasty or the data itself is buggy due to a failure in processing or booking data into an InfoProvider without causing a short dump? Your manual checks, process chains, or third-party scheduling tool do not spot the problems.

Joerg Boeke

Joerg Boeke is an SAP NetWeaver BW solution architect and senior consultant working with BIAnalyst GmbH & Co.KG, with 19 years experience in SAP NetWeaver BW, having worked on it since SAP BW 1.2A. He offers significant expertise in the SAP NetWeaver BW reporting area, including design, data integration, data visualization, performance optimization, and the cleanup of existing SAP NetWeaver BW systems. He is the author of SAP BW 7.x Reporting - Visualize your data.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.