BiLog: Dissecting...QBR Ad Hoc Reporting and the Database
PamDenny 270000BXV7 Visits (14144)
I dissected our kitchen junk drawer this weekend. Although I’m not a hoarder, I did find a 41 golf pencils, $1.53 in Change and and 3 postcard stamps!
While on this clearing spree, today’s Bilog dissects how QBR reports are stored in the database to clear up any confusion you may have.
QBR, or Ad Hoc reports, enable you to create reports ‘on the fly’ without technical database or report development skills. In this previous BiLog entry, best practices were reviewed to detail which specific users you may want to grant QBR security privileges to. Once these privileges are granted, you or your users can build QBR reports by adding fields, sorting, grouping and many other features until you design a report that meets your individual needs.
Once you have built your report, you can either discard it – or save it to run again, or to share with others. If you save the QBR report, the report is saved to the Maximo database. This enables the report to be executed in the future, or for a developer to export the xml from the database and extend it in the Report Designer.
REPORTDESIGN: XML report file designed by QBR creator
REPORTLABEL: Text for report name and column descriptions
REPORTDEPEND: Dependencies on Maximo System Libraries
REPORTLOOKUP: Optional report parameter (filter) values
REPORTADHOC*: Enable future editing of the QBR
REPORTADHOCFIELD*: Enable future editing of the QBR selected fields
REPORTADHOC and REPORTADHOCFIELD were added in the Version 7.5 release for QBR Editing.
For more details on creating QBR Ad hoc reports, click on the link below to download any of the three guides for the specific version of Maximo you are using.
For details on extending the saved QBR report to add graphs, calculations or other report modifications, see the section titled ‘Use Ad Hoc Reporting as a base for Custom Report Development ‘ in each of the guides above.
And for more details on Maximo reporting, please reference the wiki site here. Thank you!