We all want to make our Maximo reports as informative and readable as possible, but sometimes the available attributes for an Ad Hoc report don’t provide the information we want to see. For example, let’s look at a Work Order record. If I wanted to pull this Work Order into a report, I would have a hard time knowing what company is being used as the Vendor and which “Ed” is supervising the Work Order. So instead of using these attributes on our Work Order reports, why not use the display name of the Supervisor or the name of the Vendor company? In the steps below, I’ll use the “company name” example to demonstrate creating an Ad Hoc report with an attribute from a separate application. First things first, let’s see what it looks like if I try to create a report that includes the name of the Vendor company. There isn’t anything related to the Companies object on the left side panel, so I can’t access the attribute I need yet. However, we can see the description of our reporting Object Structure at the top. (We’ll save that piece for later!) For now, let’s grab the information we need to create a relationship between the Work Order object and the Companies object. I’ll have to use my trusty ALT+i shortcut to get the value of two different attributes: the attribute representing the record I want to access and the attribute on that record which is being displayed. In my case, the Work Order “VENDOR” attribute represents the record I want to reach and the “COMPANY” attribute stores that same value in the Companies object.       Now we can go into the Database Configuration and see if there is a relationship from the Work Order object to the Companies objects which uses these fields. Looks like there are none, so let’s create a new row and make it ourselves! I’ve filled in my details as shown below. Remember when creating a new relationship between objects, the Relationship should have the same name as the Child Object to avoid creating duplicates in the future. In your Where Clause, the value of the Child attribute is listed first and attributes on the Parent are retrieved using a binding ‘:’ symbol. Now that the Work Order knows how to access the Companies application, let’s go to the Object Structures application and use this relationship to alter the reporting structure we saw earlier. Scroll to the “Source Objects” section and create a new using the COMPANIES Object, the WORKORDER Parent Object, and the brand-new COMPANIES Relationship. Make sure to enter a Reporting Description so anyone creating an Ad Hoc report knows what this object represents. Finally, let’s go back to Work Order Tracking and create a new report. We can now see the new Vendor Information object in the structure and select it. This is where I can access any of the attributes that the Companies object has to offer. Once I’ve added the company Description to my report, I can go ahead and run a preview to see it in action. This version of my report is much easier to understand, and it saves me time digging around in Company records for more information. So, try creating new object relationships and adding to object structures to make your Ad Hoc reports the best they can be!