QBR Ad hoc reporting overview

 View Only

QBR Ad hoc reporting overview 

Fri March 20, 2020 03:13 PM

Query Based Reports (QBR) are ad hoc reports designed to meet the dynamic data analysis needs of your users.  QBR’s enable users to create their own unique reports by selecting columns, specifying sorting and grouping, and the query the report will run against.   Once the user saves the report, this information is fed through an API to create an xml report design file, which is then executed thru the report engine. 


This functionality is intended for users to create their own custom reports.  This is critical for many reasons, including

  • Enables users to quickly create their own reports for their unique business needs
  • Does not require technical, development skills, like Java, to create the report
  • Does not consume development hours in creating and maintaining large numbers of unique reports, which may only be used by a very small number of users


QBR’s are different than traditional, enterprise reports for the reasons listed below.


How they are developed 

Enterprise reports are developed by a developer in the Design Tool, versus QBR reports are initiated by a user and created On the Fly within the applications.


Who uses them

Enterprise reports are developed for a large number of users, and are enabled for quick access.  QBR reports are developed for a single user or business case, and are not designed for mass distribution.


Who has the ability to delete them

Enterprise reports can only be deleted by an Administrator who has access to the Report Administration application, or the database.  QBRs can be deleted either by the User who created the Report, or by the administrator in the Report Administration application.


The Type of Security they have

Enterprise reports have group level security, where groups can be granted access at either an individual report level, or an application level.  QBRs however are unique because they may be for a user’s individual business needs, which may not want to be shared with others.  Because of this requirement, QBR’s utilize user level report security, which can be expanded to enable public and/or group security access.


Both Enterprise reports and Ad Hoc reports have their unique, individual business needs that they must meet.  Enterprise reports are intended for access by high volumes of users, and their focus is on heavily formatted, detailed reports with complex sql code optimized for performance.  Conversely, Ad Hoc reports are intended for access by a small number of users to meet their individual business needs, and they may only need to be executed for a short time period.  These use cases are often referred to as ‘one off’ business needs. 

Because of their unique business needs, the process to develop an Enterprise report from an Ad Hoc Report differs significantly.

Enterprise reports require a significant investment in resources to define the requirements, design the report specification and then require an experienced developer to create the report design files.  This process is typically iterative - meaning a report will evolve once it is developed, and may need to go thru a series of test cycles.    Once an enterprise report is complete, it uses a set of files to enable it to be imported into the Maximo database for report execution.  The administrator then utilizes the Report Administration application to set security access, and modify any property or application settings. 


With ad hoc reports, this work is all done on the fly by the user in Maximo.   No design or development resources are required.   This frees up significant development time, and enables users to get the information they need immediately.  


The cornerstone of the QBR functionality are Report Object Structures (ROS).  ROS contain the pre-joined tables of data that the user can select his report fields from.  ROS are created in the Object Structure application, and stored in the database.  ROS enable users to select fields from multiple database objects thru their use of maxrelationships defining the object joins.   This eliminates any sql issues or unknowns that a user may have, and insures consistency of data across all QBR reports. 

More information on QBR ad hoc reporting can be found throughout these pages or in this reporting reference worksheet



0 Favorited
0 Files