Maximo Open Forum

Hi everyone,

I am currently an intern learning IBM Maximo, and I have run into a persistent issue regarding custom follow-up Work Order creation. I would greatly appreciate any insights from the community.

The Objective: I was tasked with configuring Maximo so that when a custom "Follow-up" checkbox is checked and saved in the Actuals tab of a Work Order, a child follow-up Work Order is generated. This child WO needs to reference the parent WO and copy all WOACTIVITY records (tasks) from the parent's plans.

The Implementation & Misstep:

1. I initially created the custom checkbox in the Plans tab by mistake. After realizing this, I created the proper checkbox in the Actuals tab.

2. To handle the follow-up logic, I configured two Action Launch Points tied to an Automation Script to trigger the child WO creation.

3. This setup initially seemed to work. However, I then modified the automation script to additionally change the status of the copied tasks.

The Error: Immediately after that script modification, the application began throwing the following error upon saving: BMXAA3761E - The event has failed. Ensure that the event is registered correctly. See the log file in the APP HOME directory for more details about the error. null More information

Current Impact & Troubleshooting:

• Because of this error, my Maximo training environment will no longer allow me to save a Work Order if there is any entry present in the Plans tab.

• To isolate the issue, I deactivated the automation script entirely, but the application continues to throw the exact same error and blocks the WO save.

• My senior team members are currently looking into the server logs, but I am very curious to understand the mechanics behind this issue.

My Questions:

1. Since the automation script is deactivated, why might Maximo still be throwing this event failure error?

2. Could this be related to a lingering Action Launch Point configuration, Maximo caching, or a remnant of the initial checkbox I mistakenly placed on the Plans tab?

Thank you in advance for your time and guidance!

Hi Reddy,

It sounds like the automation script is deactivated, but it is possible the launch point still being active. I would confirm that Launch Points are made inactive as well as the Automation Script. You can look into the Automation Scripts app and the actions app. It is also possible that the error you are getting is not from the automation script but from Maximo logic itself. This can be largely true if your script modifid task/parent-child data.

The BMXAA3761E error is a very generic error. 

My guess is an Action Launch Point or Action record is still registered and firing during WORKORDER save, and it references something that is now invalid. The fact that the issue appears only when Plans records exist suggests the event is tied to a child relationship being processed during save rather than the checkbox itself.

If your team gets the stack trace from SystemOut.log or maximo.log, especially the lines immediately preceding BMXAA3761E, it might give you more information on around the object, launch point, or script that is failing.

Thank you,

------------------------------
Allan Henle
Naviam
------------------------------