APAR status
Closed as program error.
Error description
When a work order has a safety plan with a hazard having 2 Tag Outs after deleting one tag out an error is received when deleting or modifying a Lock Out. STEPS TO REPRODUCE: 1. Open the Assets application 2. Open the details for one asset, e.g. 11430 3. Click on tab Safety then on sub-tab Lock Out/Tag Out 4. Make sure it is added a hazard with 2 Tag Outs. Use <New Row> in Hazards area to add a hazard and <New Row> in Tag Out area to add a Tag Out e.g.: a. Hazard: ELECTRIC b. Tag Outs: NOFLOW01 and TAG333 5. Open the Safety Plans application and add a new safety plan: a. Safety Plan: TESTSP1, Test Safety Plan b. Click on Tag Outs tab c. In Hazards are click on <New Row> and add the following: i. Hazard: ELECTRIC ii. Related Asset: 11430 iii. Save, the NOFLOW01 and TAG333 Tags Out are added plus the corresponding Lock Out operations 6. Open the Work Order Tracking application 7. Create a new Workorder and fill in: a. Description: Test WO with Safety Plan b. Asset: 11430 c. Safety Plan: TESTSP1 d. Save 8. Click on tab Safety Plan then on sub-tab Lock Out/Tag Out ? the hazard ELECTRIC with the 2 Tag Outs and the corresponding Lock Out operations are added a. Delete one Tag Out b. Save c. Do either of: i. Remove one Lock out operation ii. Edit 'Apply Sequence' at Lock Out Operations. iii. Save ? a system message is displayed "BMXAA4650E - A tag out was specified, but this hazard is not tag out enabled." iv. Click <OK> d. Click on <Remove Safety Plan> e. Click <OK> to confirm ? the same system message is displayed (for the client the message was "BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code -4470. 9. Click on List View without saving the work order 10. Reopen the work order and click again on <Remove Safety Plan> - this time the safety plan is removed successfully. 11. Repeat steps 7 and 8 without intermediate savings, click Save only after deleting or modifying Lock Out operations ? no error is received 12. Open Safety Plans application and open the safety plan TESTSP1 13. Click on tab Tag Out a. Add a new hazard with <New Row>, FLOW, Related Asset: 11430 b. Save c. Delete the hazard just added and save 14. Open the Work Order Tracking application 15. Any attempt to add the safety plan TESTSP1 in new work order will generate the error message: "BMXAA4674E - The asset or location that is specified for this tag out must be the same as the asset or location that is specified for its hazard." RESULT: When a work order has a safety plan with a hazard having 2 Tag Outs after deleting one tag out an error is received when deleting or modifying a Lock Out. EXPECTED RESULT: When a work order has a safety plan with a hazard having 2 Tag Outs after deleting one tag out no error is received when deleting or modifying a Lock Out. REPORTED IN VERSION: Tivoli's process automation engine 7.6.1.2
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** * PROBLEM DESCRIPTION: * * On a WO with multiple hazards, an error BMXAA4650E is thrown * * on save after deleting one hazard, saving, and * * deleting/modifying a tag out on another hazard. * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenance package: release\fix pack for Release 8.x Product
Temporary fix
Comments
APAR Information
APAR number
IJ32490
Reported component name
MAXIMO ASST MGM
Reported component ID
5724R46AM
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-05-04
Closed date
2023-03-06
Last modified date
2023-03-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MAXIMO ASST MGM
Fixed component ID
5724R46AM
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
06 March 2023