APAR status
Closed as program error.
Error description
Master PM changes do not reflect in the associate/duplicated PM's. Environment TPAE 7503 Transportation 71 ACTION TAKEN : Problem replicated with the following replication steps: 1. Create a Master PM with Work Order and Lead Information 2. Create a PM from Master PM. Please note that Work Order and Lead Time info are identical 3. Go to the Master PM and make changes to the Work Order and Lead Time info. 4. Master PM --> Where used tab details after Master PM has had changes made and data refreshed. Note Work type field has not changed 5. Any details changed on the other Master PM tabs, all do change on the associated PMs when the update is run. 6. Go to the PM after the Master PM changes have been made. 7. Note work order information and lead time is unchanged 8. Any details changed on the other Master PM tabs, all do change on the associated PMs when the update is run. Observation from L3: === Sounds like we will need to add a couple of attributes - Work Order and Lead Time 'Update Associate PMs' check boxes. This cannot be done in a hot fix, so this should be done for 7507 and onwards. === Further Observation from L3: === we cannot add columns to database tables in IFIXes so this cannot be done as a one-off if they want to have the option. Please request an APAR against the next fix pack (7.5.0.7). The fix in 7.5.07 will have the option. ===
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users of Master PM functionality * **************************************************************** * PROBLEM DESCRIPTION: * * Master PM work order information not copied to related PMs * * on 'Update Associated PMs' * **************************************************************** * RECOMMENDATION: * * Apply latest fix pack. * **************************************************************** 1. Create a Master PM with Work Order and Lead Time Information 2. Create a PM from Master PM. Work Order Information and Lead Time info is copied to the new PM so that the PM has the same values as its Master PM. 3. Go to the Master PM and make changes to the Work Order and Lead Time information. 4. Execute the Master PM menu action 'Update Associated PMs'. 5. Look at the PM created from this Master PM in Step 2. The Work Order Information modifications on the Master PM have not been applied to the PM. 6. In comparison, any Seasonal, Sequence, Frequency or Extended Date Information updates on the Master PM are propagated to PMs creaated from the Master PM as long as the boolean flags (for example, 'Update Time Based Information in Existing PMs ?' for FREQUENCY, FREQUNIT, ALERTLEAD and LEADTIME changes) are checked when 'Update Associated PMs' is executed.
Problem conclusion
Functionality to propagate work order information changes from Master PM to associated PMs when 'Update Associated PMs' is executed has been implemented. This fix requires that the new flag 'Update Work Order Information on Existing PMs?', which will now appear in the Work Order Information section of the main tab, is checked. Note: The propagation of Lead Time changes did not need a code fix as this part of the PMR was not a defect. In order for Lead Time information changes made on the main tab to be propagated to associated PMs, the 'Update Time Based Information in Existing PMs ?' flag on the Time Based Frequency subtab of the Frequency tab must be checked. This checkbox can be added to the Lead Time section of the main tab but this is not part of the fix. The fix addresses the propagation of work order information which was not working as expected. The fix for this APAR is contined in the follwing maintenance package: | release\fixpack\interim fix for 7.5.0.7
Temporary fix
Comments
APAR Information
APAR number
IV61532
Reported component name
MAXIMO PLANNING
Reported component ID
5724R46PL
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-06-16
Closed date
2014-08-29
Last modified date
2014-08-29
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 PLANNING
Fixed component ID
5724R46PL
Applicable component levels
R750 PSY
UP
[{"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":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
29 August 2014