APAR status
Closed as program error.
Error description
DESCRIPTION: BMXAA3212E - Error while generating work order for PM xxxxxx. BMXAA4129E - The record for Item=xxxxxxx, Storeroom=xxxxxxx, Site=xx, Item Set=xxxxx already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique. Additionally, the issue appears to be that the entry in womatstatussync is not cleared in time during Work Order generation when multiple PMs generate against the same Job Plan or when multiple PMs generate with different Job Plans that have the same direct issue material. It is observed that all PMs that generate after the first with the same item will fail. The error occurs when Work Orders are generated either manually or with PMWoGenCronTask STEPS TO REPRODUCE: -Log in to maxdemo instance -Go To Inventory | Item Master -Common Actions | New Item -In the Item field enter "TESTITEM" -In the Order Unit field enter "each" and tab out -In the Issue Unit field enter "each" and tab out -Save the record -More Actions | Add Items To Storeroom -In the Storeroom field enter "central" and tab out -Click OK -In the Unit Cost field enter 1 -In the Current Balance field enter 12 -Click OK -Common Actions | Change Status -In the New Status field use the drop-down arrow and click Active -Click the checkbox for "Roll New Status to Organizations and Inventory?" -Click OK -Go To Planning | Job Plans -Common Actions | New Job Plan -In the Job Plan field enter "TESTJOBPLAN" -In the Job Plan Tasks section click the New Row button -In the Task 10 Description field enter "Task One" -In the Duration field enter 0:10 -On the Materials tab click the New Row button -In the Task field | Select Value | click 10 -In the Item field enter "testitem" and tab out -In the Item Quantity field enter 2 -Click the checkbox for Direct Issue -Save the record -Common Actions | Change Status -In the New Status field use the drop-down arrow and click Active -Click OK -Go To Preventive Maintenance | Preventive Maintenance -Common Actions | New PM -In the PM field enter "TESTPM" -In the Location field enter "br200" and tab out -Uncheck the checkbox for "Include this PM in the Forecast" -In the Job Plan field enter "testjobplan" and tab out -On the Frequency tab | Frequency field | enter 1 -In the Estimated Next Due Date field click the Select Date button -Click today's date -Save the record -Common Actions | Change Status -In the New Status field use the drop-down arrow and click Active -Click OK -More Actions | Generate Work Orders -Click OK -Click OK at the System Message -More Actions | Generate Work Orders -Uncheck the "Use Frequency Criteria" checkbox -Click OK RESULTS: System Message appears: "BMXAA3212E - Error while generating work order for PM xxxxxx. BMXAA4129E - The record for Item=xxxxxxx, Storeroom=xxxxxxx, Site=xx, Item Set=xxxxx already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique." EXPECTED RESULTS: Work Orders generated as expected REPORTED IN VERSION: 7.6.1.0-IFIX20181026-1239
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * maximo users who use the work order generation in PM * * application * **************************************************************** * PROBLEM DESCRIPTION: * * Users got the error "BMXAA4129E - The record for * * Item=xxxxxxx, Storeroom=xxxxxxx,Site=xx, Item Set=xxxxx * * already exists" when generating work orders for direct issue * * items in the PM application. The unique violation error was * * on womatstatussync table. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
This is fixed in code by rolling back 7610 apar IJ03992 which kept adding womatstatus records for each new wo generated for direct issue materials. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 7.6.1.1 Product
Temporary fix
Comments
APAR Information
APAR number
IJ13162
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
2019-01-31
Closed date
2019-03-31
Last modified date
2019-03-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
maximo
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":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
31 March 2019