BW Reporting
Get the Best Results When Reporting on Transactional Data

  • by Gary Nolan, SAP BI Strategic Architect, Sapiex Associates LLC
  • June 1, 2005
How you categorize your transactional data in the SAP Business Information Warehouse data model affects the amount of reporting flexibility you have. It might also have an impact on query performance.
Key Concept
The InfoCube is a core building block of SAP Business Information Warehouse. It contains user-defined data sets against which you can perform queries. Data in InfoCubes can come from a wide variety of sources, including transactional systems or master data tables.
SAP logistics and supply chain reporting is increasingly dependent on SAP Business Information Warehouse (BW). This means that you must communicate effectively with your BW team when giving them your requirements, particularly when it comes to modeling your data. Understanding and planning your BW data model is the single most important way to ensure that BW can meet your organization's current and future reporting requirements.

Gary Nolan

Gary Nolan is an SAP NetWeaver BW-certified consultant and author of Efficient SAP NetWeaver BW Implementation and Upgrade Guide and Efficient SAP NetWeaver BI Implementation and Project Management. Gary specializes in gathering and evaluating requirements, configuring SAP NetWeaver BW, and providing project management, performance management, and data architecture and data modeling expertise. A former platinum consultant with SAP America, Inc., Gary has more than 20 years of SAP experience, working with SAP NetWeaver BW since version 1.2B.

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.