Maximo Open Forum

Hi

Has anyone extended the PM search function in the More Search fields dialog

Maximo provides an inbuilt search option to search by location hierarchy and returns all PM's linked to all locations in the selected location hierarchy

It does not also select PM's associated to assets which are linked to the locations or any locations in the hierarchy

Can any one suggest how this can be done - preference is for a preset search rather than dedicated Saved queries. 

Hi Geoff, 

Are you looking to implement the relationship in the Preventative Maintenance application? Or are you looking to implement the relationship in the Location or Assets application. 

OOB relationships between the LOCATION, ASSETS, and PM objects exist. Your requirements will help me point you in the right direction if one exists, or build you guidelines to implement it if one does not exist.

Hi thanks for reply

we have a set of PM records assigned to Locations at different levels in a Hierarchy. OOB maximo returns a result using the standard Search Location Hierarchy field found in advanced search

We also have some PM's linked to Assets which are connected to Locations in the same hierarchy

OOB maximo does not return those records when queried using a location Hierarchy.

We don't want to change the asset to location on the PM record but want to view a result set that contains both sets of records with the Search Location Hierarchy function

Thanks

He wants to put a location code on the list or searchmore screen and have it search both assets and locations together in one thing.

It is trival from reporting to do this but nearly impossible from Maximo if you have a large dataset.  I got it working in our Dev environment but it is horribly inefficient.  

You need to setup a relationship between PM and LocAncestor that adds a sub-query between that searchs Location and Asset together using a Nvl(:assetnum, :location).  The problem is the perspective and how Maximo treats it. The perspective is the PM table and finding the matching LocAncestor records not the other way around.  

I am using Oracle and maybe it is different with a different database but I doubt it.  What Maximo does is convert that relationship into a correlated sub-query using an exists clause and does a full table scan.  For 80k locations and 400k assets it took about 6 minutes which is just not acceptable.