So this is not something that is setup OOB for Maximo but will be extremely useful if you are using failure codes (Problem/Cause/Remedy). Problem already exists OOB in Maximo but for some reason cause/remedy where not. Follow the steps in the link above to implement this into your system.
To summarize what needs to happen
- You will be creating two new relationships on the workorder table. That will link back to failurereport table. One for Cause and one for Remedy.
- You will create two new lookups in the lookups.xml for your system that will be used in your advanced search dialog (searchmore)
- You will update your application wotrack or plusgwo (or your equivalent industry solution module) advanced search dialog to use the new relationship and lookup.
It’s a fairly simple change and you shouldn’t need to take the server down or move it into admin mode. Remember follow your change management rules.
Here is a fun little trick. If you are using SSO but want to sign in using form based trying modifying your url.
login/login.jsp?appservauth=true will force Maximo to go through the form.
If you run into this issue you might be able to check the search type of the attribute they are wanting to filter on check out the IBM document on how to update this.
As an example REPORTEDPRIORITY attribute is Read Only in SR Object. And if you want to update the attribute of REPORTEDPRIORITY to WILDCARD.
Back up your Database. Login to your Database as maximo user. Run update as below.
update maxattribute set searchtype = ‘WILDCARD’ where objectname=’SR’
update maxattributecfg set searchtype = ‘WILDCARD’ where
objectname=’SR’ and attributename=’REPORTEDPRIORITY’
After updating the database you need to stop the application server and re-start.
The search Type will be updated to WILDCARD