You may want to include long descriptions in your reports. To enable this, add the Long Description Object as a child to the Application Report object structure (ROS). The example below steps you through how to enable the Work Order ROS to include the child Long Description object.

1. In Database Configuration application, verify that a relationship exists between the parent Work Order and the child Long Description. In this example a relationship does not exist, so you add one for reporting as shown in this screenshot.

2. Add the new child table of Long Description to the Work Order ROS. To do this, go to Integration > Object Structures. Filter on Consumed By for 'reporting' to see a list of the Report Object Structures (ROS).

3. If you are working in Base Services release 7.1.1.6 or later, select the Work Order ROS. Add a new Long Description object under work order, as shown in this screenshot. Make sure to specify the cardinality and type of database join properly. Note: You use scripts to specify these two values in releases before 7.1.1.6.

4. Select Exclude/Include Fields from the Select Action menu to exclude any attributes from the Long Description Table that you do want to display. For example, you may want to exclude attributes like LONGDESCRIPTIONID.

After the Long Description Child has been added to the Work Order Parent, it is available in the QBR for the application.

When users build a QBR Report, and select the Long Description field, it displays similar to what is shown below.

NOTES:

1.  If object contains multiple ld attributes (ex.  Incident) than the where clause you create between the object and ld needs to include the attribute

2.  In the Maximo 76 release, a number of application long description relationships have been added.   You may want to review these relationships before creating new ones.