Maximo Open Forum

 View Only

 Error Message BMXAA0089 - Asset xxx is not a valid asset when creating/updating a work order

  • Administration
  • Assets
  • HSE/Oil and Gas
  • Work Management
Patricia Reutter's profile image
Patricia Reutter posted 01-16-2024 16:18

We are running Maximo Asset Management v7.6.1.0 with the Oil & Gas add-on.

If the asset or location uses the default value for OPERATING from the LOCASSETSTATUS domain, no error is displayed.  However, if any of the other 10 synonym values for 'OPERATING' are used on the asset or location, the error displays. 

The error doesn't happen when using the Duplicate work order action but does when generating work orders from PMs or create a new work order in the UI.

I unchecked the 'Active' checkbox on the launch point and also at the automation script level to troubleshoot but it didn't resolve the issue.

Are there additional steps needed to disable the automation script from firing?  

Has anyone had a similar issue or recommendations for finding the root cause?

Thank you!

Tim Ferrill's profile image
Tim Ferrill

Hi Patricia,

Unchecking the Active checkbox on the Launch Point should be all you need to disable the script. If you get the error even when the script is disabled I would assume it's not a script issue.

You might check the ASSET2WO domain to ensure the Validation Where Clause isn't too restrictive when excluding your Assets based on Status.

Patricia Reutter's profile image
Patricia Reutter

Thank you for recommendation Tim.

I checked the validation on the ASSET2WO domain and the validation where clause only references the assetnum and siteid.

Tim Ferrill's profile image
Tim Ferrill

Patricia,

Here's an IBM doc that may be worth looking into. Apparently this can happen when indexes are broken and you have record ids that are not unique.

Patricia Reutter's profile image
Patricia Reutter

Hi Tim - Thank you for your assistance.  It was actually the first suggestion you made but on a different domain.  The Validation Where Clause was too restrictive on the ASSETCROSSCI domain used on the workorder table. 

Tim Ferrill's profile image
Tim Ferrill

Hey Patricia, Glad you were able to figure that out!