APAR status
Closed as program error.
Error description
Problem Description User is facing a wrong date in Calibration Next Due Date after completing work order. Calibration Next Due Date is not following the PM frequency in work order if there is a work order with same wonum in a second site. STEPS TO REPRODUCE: .Log in Maximo with Maxadmin .GO TO >> ADMINISTRATION >> ORGANIZATION .Bring up EAGLENA .Click in Sites tab .Click New Row under Sites section .Site: SITE-A .Active?: YES .Click New Row again .Site: SITE-B .Active?: YES .Save .MORE ACTIONS >> AUTONUMBER SETUP >> SITE LEVEL .Click in SITE-A, Click New Row .Autonumber Name: WORKORDERNUM .Seed: 1,000 .Click in SITE-B, Click New Row .Autonumber Name: WORKORDERNUM .Seed: 1,000 .Click OK .Click in Profile >> DEFAULT INFORMATION .Default Insert Site: SITE-A .Storeroom Site For Self-Service Requisitions: SITE-A .Click OK .GO TO >> ASSETS >> ASSETS .Create a new Asset .Asset: A001 .Enter a description .Calibration?: YES .Change status to ACTIVE .Create a second Asset .Asset: A002 .Enter a description .Calibration?: YES .Change status to ACTIVE .GO TO >> PREVENTIVE MAINTENANCE >> PREVENTIVE MAINTENANCE .Create a New PM Record .Asset: A001 .Lead Time (Days): 30 .Job Plan: BREAKINSP .Work Type: CAL .Work Order Status: APPR .Click on Frequency tab .Uncheck the option 'Use Last Work Order's Start Date to Calculate Next Due Date?' .On Time Based Frequency section .Frequency: 20 .Frequency Units: DAYS .Target Start Time: 12 AM .Estimated Next Due Date: [EMPTY] .SAVE .COMMON ACTIONS >> CHANGE STATUS .Select Active .Click OK .Create a second PM Record .Asset: A002 .Lead Time (Days): 30 .Job Plan: BREAKINSP .Work Type: CAL .Work Order Status: APPR .Click on Frequency tab .Uncheck the option 'Use Last Work Order's Start Date to Calculate Next Due Date?' .On Time Based Frequency section .Frequency: 10 .Frequency Units: DAYS .Target Start Time: 12 AM .Estimated Next Due Date: [EMPTY] .SAVE .COMMON ACTIONS >> CHANGE STATUS .Select Active .Click OK So far, we have the following scenario. Site-A PM1 WITH A001 ASSET PM2 WITH A002 ASSET .Click in Profile >> DEFAULT INFORMATION .Default Insert Site: SITE-B .Storeroom Site For Self-Service Requisitions: SITE-B .Click OK .Sign out and sign in back .GO TO >> ASSETS >> ASSETS .Create a new Asset .Asset: A001 .Enter a description .Calibration?: YES .Change status to ACTIVE .Create a second Asset .Asset: A002 .Enter a description .Calibration?: YES .Change status to ACTIVE .GO TO >> PREVENTIVE MAINTENANCE >> PREVENTIVE MAINTENANCE .Create a New PM Record .Asset: A001 .Lead Time (Days): 30 .Job Plan: BREAKINSP .Work Type: CAL .Work Order Status: APPR .Click on Frequency tab .Uncheck the option 'Use Last Work Order's Start Date to Calculate Next Due Date?' .On Time Based Frequency section .Frequency: 15 .Frequency Units: DAYS .Target Start Time: 12 AM .Estimated Next Due Date: [EMPTY] .SAVE .COMMON ACTIONS >> CHANGE STATUS .Select Active .Click OK .Create a second PM Record .Asset: A002 .Lead Time (Days): 30 .Job Plan: BREAKINSP .Work Type: CAL .Work Order Status: APPR .Click on Frequency tab .Uncheck the option 'Use Last Work Order's Start Date to Calculate Next Due Date?' .On Time Based Frequency section .Frequency: 5 .Frequency Units: DAYS .Target Start Time: 12 AM .Estimated Next Due Date: [EMPTY] .SAVE .COMMON ACTIONS >> CHANGE STATUS .Select Active .Click OK Now we have the following scenario. SITE-A PM1 WITH ASSET A001 PM2 WITH ASSET A002 SITE-B PM3 with ASSET A001 PM4 with ASSET A002 .Bring up PM1 again (PM FROM SITE-A) MORE ACTIONS >> GENERATE WORK ORDERS Uncheck flag 'Use Frequency Criteria' Click OK Work order was generated (BMXAA3208I PM1 created work order 1001.) .Bring up PM2 (PM FROM SITE-A) MORE ACTIONS >> GENERATE WORK ORDERS Uncheck flag 'Use Frequency Criteria' Click OK Work order was generated (BMXAA3208I PM2 created work order 1002.) .Bring up PM3 (PM FROM SITE-B) MORE ACTIONS >> GENERATE WORK ORDERS Uncheck flag 'Use Frequency Criteria' Click OK Work order was generated (BMXAA3208I PM3 created work order 1001.) .Bring up PM4 (PM FROM SITE-B) MORE ACTIONS >> GENERATE WORK ORDERS Uncheck flag 'Use Frequency Criteria' Click OK Work order was generated (BMXAA3208I PM4 created work order 1002.) .GO TO >> WORK ORDERS >> WORK ORDER TRACKING .Bring up the work orders generated by PM (ie 1001 and 1002 for both sites) Target Start Date on WO 1001 \ SITE-A will be current date. Next Calibration Due Date on SITE-A \ A001 is current date. Complete WO 1001 (A001) from SITE-A. It must be done in the next day. .Bring up the work orders 1001 from SITE-A .Change status to INPRG .Change status to COMPLETE SITE-A RESULT WO 1001 - NEXT CALIBRATION DUE DATE is 6/19/23 12:00 AM ASSET A001 - NEXT CALIBRATION DUE DATE is 6/19/23 12:00 AM PM1 - Estimated Next Due Date is 7/10/23 RESULTS: The Next Calibration Due date WO 1001 for SITE-A should be July 10, 2023, which will match with the frequency in PM, 20 days ahead. EXPECTED RESULTS: The Next Calibration Due Date is still the date which work order was generated which its not the same in work order tracking and PM application. REPORTED IN VERSION: Tivoli's process automation engine 7.6.1.3-IFIX20230324-1804 IBM Maximo Calibration 7.6.1.0
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users * **************************************************************** * PROBLEM DESCRIPTION: * * The Calibration Next Due Date is incorrect on the Work Order * * after completing the Work Order * ****************************************************************
Problem conclusion
The fix for this APAR will be included in a future Release
Temporary fix
Comments
APAR Information
APAR number
IJ47272
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
2023-06-20
Closed date
2023-06-30
Last modified date
2023-06-30
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:
01 July 2023