ROS - Report Object Structures
Report Object Structures (ROS) are hierarchies of database objects joined together via maxrelationships. ROS are created in the Object Structure application, where Object Structures are also created for Integration and Migration Manager. Once a ROS is created - - it can be used in different ways to meet the never-ending report requests you have. This becomes a key best practice - because if you invest your time in developing a powerful ROS, you can utilize it in three very different ways detailed below
1. QBR or V7 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. More details on QBR reporting are available 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 here on using ROS for application exporting
ROS enable users to select fields from multiple categories (objects) for their QBR or Ad Hoc reports. Additionally, ROS are designed to enable users to visualize application categories and their parent/child relationships. These ROS are displayed as a category drilldown in the Select tab of the Query Based Report window in the top-left side. An example of an ROS for the Asset application is shown below.
To find additional detailed information on creating ROS for QBR reporting, access the version-specific guides below.
For the Maximo 7.6 releases, reference the QBR guide here
For the 7.5 releases, reference the 7.5 QBR guide located here.
For the 22.214.171.124 release and later, reference the document titled V7 QBR_Ad Hoc Reporting_7116 located here.
Report Object Structures (ROS) can be used to dynamically create the Maximo Cognos Packages or Metadata. These enable your report developers to quickly begin creating reports in Cognos Report Studio and Cognos Query Studio. An example of an ROS which has been published to Cognos for use in the Query Studio application is shown below.
To find additional detailed information on using ROS for Cognos reporting, access the version-specific guides below.
For the Maximo 76 releases, reference the Maximo Cognos integration guide here
For the 7.5 releases, reference the V75 Maximo Cognos Integration Guide located here.
For the 126.96.36.199 release and later, reference the document titled V71 Maximo Cognos Integration Guide located here.
You may want to modify or create additional ROS for your environment. It is recommended that this work be done by a developer or administrator who is familiar with the Maximo database and database concepts. Without this knowledge, the ROS can be set up incorrectly, leading to bad or misleading data in your reports