Depending on which Maximo Feature Pack that you are using, you may run into an issue with the View Asset Status History dialog in the Assets application. There was an issue discovered with the 7.5.0.x Feature Pack versions whereby the status history data for Assets would only display data for Calibration assets in the View Asset Status History dialog within the Assets application:
This was corrected via APAR IV65532, which was made available after the release of the 18.104.22.168 Feature Pack, but some clients may be running into this if the Maximo environment is not using one of the most recent fix packs. There is, however, a manual workaround that can be implemented to get around this issue until your environment is updated to a more current version.
The issue stemmed from when the Calibration product became integrated with the base Maximo product - this introduced the design component of having the the asset status data stored in the PLUSCASSETSTATUS table instead of the previous design of using the ASSETSTATUS table. The issue being discussed here was caused by the GUI (the View Asset Status History dialog) reading the asset.xml, which initially had some incorrect code still intact from when the Calibration was not integrated. The result of the code (shown in the xml further below) will only display the status history for assets flagged as Calibration.
You can use the following procedure to manually correct this issue:
1. Open the asset.xml presentation in the Application Designer application
2. Click 'Export Application Definition' and save it locally as asset.xml
3. Open asset.xml in a text editor
4. Search for the string, "id="viewhist" (use the double-quotes in the search string)
5. Remove the string highlighted, "licensekey="CALIBRATION", and save the file
6. Import the updated asset.xml via the Application Designer application
Tom Richardson is an IBM Maximo Support Engineer and frequent contributor to the Asset Management Blog community. For a complete index of links to his articles, visit
Index of articles by Tom Richardson, Support Engineer