Maximo Spatial Update field with current displaying error

While creating a work order using the pop up map to select asset it is usually possible to select the asset directly from map and update the field using the selected Asset on the Map using the Update field with current Option from the Results dialog box.






Unfortunately we were getting below error as popup as well as in the error logs. Application/exception loggers need to be in debug mode for it to appear in logs.

1.  [DEBUG] [MXServer] [] Generated exception

psdi.util.MXApplicationException: BMXAA0090E - Asset ACE is not a valid asset, or its status is not an operating status.



Instead of trying to set the asset num of the selected Asset it was trying to set the Site ID of the asset on the map the the selected field. For example in the below error ACE would be the Site ID. After digging deeper it turned out that Maximo was trying to set the 2nd attribute of the PRIMARYKEYCOLSEQ on the Asset Object.

Source of the issue seemed to originate from below OOB file
Line:2019 - psdi.webclient.controls.gis.SpatialDispatcherManager

SELECT m.OBJECTNAME , m.ATTRIBUTENAME , m.PRIMARYKEYCOLSEQ FROM MAXATTRIBUTE m 
WHERE m.PRIMARYKEYCOLSEQ IS NOT NULL 
 AND m.OBJECTNAME='ASSET'
ORDER BY m.OBJECTNAME , m.PRIMARYKEYCOLSEQ ;


After modifying the primary key column sequence and restarting the server the error seemed to have got resolved and we were able to set Asset Num using the map.






Comments

Popular posts from this blog

BMXAA6713E - The record could not be retrieved from the database. Error

Rebuilding Maximo Text Indexes due to Query performance issues

List of things checked by Maximo Integrity checker