APAR status
Closed as program error.
Error description
DESCRIPTION: When a Preventive Maintenance record has the Seasonal Date option- "Schedule Early on Frequency Conflict?" checked, the Associated PM's cannot be updated from a Master Preventive Maintenance application even when the Frequency is set to more than 7 days. STEPS TO REPRODUCE: 1) Go to Preventive Maintenance; Master PM Application; (i) Create a new Master PM: Let's say: 1002; Select Item: FIRE-100; Item Set: SET1 (ii) Switch to Frequency Tab; Set Frequency: 7; Frequency Unit: DAYS; Save (iii) From More Actions; Select "Create Associated PM's"; Select as Asset; Let's say, we select: Asset: 1004 with Site: BEDFORD; Click Ok (iv) As system message is generated as below: BMXAA2753I - Created PM 1025 for asset/location 1004. 2) Navigate to this PM record (i) Go to Preventive Maintenance; Preventive Maintenance Application; View the record: 1025 (ii) Observe it has, Master PM as: 1002 and Asset as: 1004 (iii) Switch to Frequency Tab; Observe Frequency is 7 DAYS as expected. (iv) Switch to Seasonal Dates Tab; Observe there is a check box for "Schedule Early on Frequency Conflict?" Tick the check box so that it is marked as "YES"; Save. Note: This checkbox is editable only when the frequency is more than 7 Days. 3) Navigate back to Master PM Application; MASTERPMNUM: 1002 (i) Switch to Frequency Tab; Frequency: 1; Frequency Units: MONTHS; Save (ii) From More Actions; Select "Update Associated PMs"; Select the Site for which we want to update, in this case: BEDFORD; Click Ok RESULT: We get an error "BMXAA7429E - The frequency is invalid because the Schedule Early on Frequency Conflict check box is selected on the Seasonal Dates tab. The minimum frequency is 7 days". EXPECTED RESULT: We should be able to update the Associated PM's and this error should not come as we are updating the PM using the Update associated PM option and Master PM has a frequency of 1 Month which is greater than 7 days. REPORTED IN VERSION: Tivoli's process automation engine 7.6.1.2
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users * **************************************************************** * PROBLEM DESCRIPTION: * * Associated PMs cannot be updated from their Master PM * **************************************************************** DESCRIPTION: When a Preventive Maintenance record has the Seasonal Date option- "Schedule Early on Frequency Conflict?" checked, the Associated PM's cannot be updated from a Master Preventive Maintenance application even when the Frequency is set to more than 7 days. STEPS TO REPRODUCE: 1) Go to Preventive Maintenance; Master PM Application; (i) Create a new Master PM: Let's say: 1002; Select Item: FIRE-100; Item Set: SET1 (ii) Switch to Frequency Tab; Set Frequency: 7; Frequency Unit: DAYS; Save (iii) From More Actions; Select "Create Associated PM's"; Select as Asset; Let's say, we select: Asset: 1004 with Site: BEDFORD; Click Ok (iv) As system message is generated as below: BMXAA2753I - Created PM 1025 for asset/location 1004. 2) Navigate to this PM record (i) Go to Preventive Maintenance; Preventive Maintenance Application; View the record: 1025 (ii) Observe it has, Master PM as: 1002 and Asset as: 1004 (iii) Switch to Frequency Tab; Observe Frequency is 7 DAYS as expected. (iv) Switch to Seasonal Dates Tab; Observe there is a check box for "Schedule Early on Frequency Conflict?" Tick the check box so that it is marked as "YES"; Save. Note: This checkbox is editable only when the frequency is more than 7 Days. 3) Navigate back to Master PM Application; MASTERPMNUM: 1002 (i) Switch to Frequency Tab; Frequency: 1; Frequency Units: MONTHS; Save (ii) From More Actions; Select "Update Associated PMs"; Select the Site for which we want to update, in this case: BEDFORD; Click Ok RESULT: We get an error "BMXAA7429E - The frequency is invalid because the Schedule Early on Frequency Conflict check box is selected on the Seasonal Dates tab. The minimum frequency is 7 days". EXPECTED RESULT: We should be able to update the Associated PM's and this error should not come as we are updating the PM using the Update associated PM option and Master PM has a frequency of 1 Month which is greater than 7 days.
Problem conclusion
The fix for this APAR will be contained in a future release.
Temporary fix
Comments
APAR Information
APAR number
IJ36231
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-11-22
Closed date
2022-10-09
Last modified date
2022-10-09
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:
09 October 2022