BiLog: Best Practice...Investing in Report Object Structures (ROS)
PamDenny 270000BXV7 Visits (3037)
If they enter it…they will want a report on it. Mirrored off the infamous words ‘If you build it…they will come’ from the movie ‘Field of Dreams’ - these words were recently re-enacted to celebrate the 100th Anniversary of Fenway Park, Home of the Boston Red Sox.
Going back to reporting….If they enter it…they will want a report on it. We all know these words hold true with the never ending report requests we receive. Our users enter data in the various Maximo applications, and then want reports which detail and analyze those vast amounts of data. Over the last year, we have discussed multiple aspects of reporting in the BiLog (Business Intelligence) blog entries. Recently, we have talked about reporting best practices highlighted at IBM’s Pulse 2012 conference.
The three best reporting practices highlighted were: (1) Evaluate All Data Analysis Options detailed here (2) Invest in Report Object Structures and (3) Engage in On Line Resources
Today, the second best practice of investing in Report Object Structures (ROS) will be detailed. As previously noted, ROS are hierarchies of database objects joined together via maxr
1. Ad Hoc Reporting: Within the Version 7 applications, ROS enable users to create their own reports thru QBR, or Ad Hoc Reporting. It enables business users to create their own, individual reports on the fly without the need for technical skills or database knowledge. Ad Hoc reports are excellent for your user’s one-off, or project/business specific reports. You can find additional details on Ad Hoc Reporting here.
2. Cognos Reporting: With the Version 7’s Open Architecture, an integration to Cognos Reporting is enabled for you. This integration utilizes a metadata, which consists of pre-joined tables, so developers can quickly and consistently develop reports. To enable the metadata layer in the Cognos Integration, ROS are published directly to Cognos thru an API, which can significantly reduce your administration and setup time. You can learn more about Cognos Reporting here, or in the Cognos Integration Guide here.
3. Application Exporting: Finally, you can extend your ROS, by utilizing the Application Export functionality. This enables you to export fields directly from an application’s toolbar, including fields from related objects. To do this, you simply duplicate your ROS into object structures, with a consumed by of ‘Integration’. Then, enable the ‘Add/Modify Application Export Support’ Action for the selected applications, and resolve any alias fields the objects may share. You can find more details on using ROS for application exporting here.
To jumpstart your winning investment in Report Object Structures (ROS), please review the details and configuration options in the reference materials listed below
A. Understanding Maxrelationships in ROS BiLog
B. Understanding Cardinality in ROS BiLog
C. Adding Long Descriptions to ROS BiLog
D. Adding Audit Objects to ROS BiLog
E. Adding Multiple Objects to ROS BiLog
F. Impact of Complex Subqueries in ROS BiLog
G. Subquery Complex relationships at Grandchild ROS Level BiLog
H. Detailed documentation and screenshots on creating ROS are contained at the end of the Version 7.5 QBR guide located here or in the V184.108.40.206+ QBR guide here
Finally, don't forget to check out Jason Verly's presentation on using Ad Hoc Reporting at Davisco Foods located here (It's AMAZING!)