IBM Support

IV23783: CANNOT USE THE COMPLETE ACTION BETWEEN PRIMARY AND SECONDARY PM'S.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM / CLIENT CONCERN:
    
    Cannot use the COMPLETE action between Primary and Secondary
    PM's.
    
    Environment
    
    ACM 7.1.1.1 Build 20100509-1059
    Mobile 7.1.1.0
    Scheduler 7.1.1.0
    TR 7.1.1.0
    
    BS 7.1.1.6 - LA20100510-1134 - build 20091208-1415
    
    Problem Details:
    
    When using the COMPLETE action between 2 PM (one principle and
    one
    secondary), generated by 2 Master PMs, if you complete the Main
    work
    order, the secondary work order is automatically completed, but
    the
    Maintenance Plan for the asset doesn't contain the next event
    regarding
    the Main PM. For the secondary PM, the event has been recreated.
    
    Maximo Asset Configuration Manager 7.1.1.1-20110222-1608 Build
    20100509-1059 DB Build V7121-06
    Base Services 7.1.1.6 Build 20091208-1415 DB Build V7116-173
    
    
    Replication Steps:
    
    1. Go to "Master PM (CM)"
    2. Add a new Master PM, with a frequency in DAYS, 15
    3. Add a CM Item corresponding to an Asset (CM)
    4. Save the record
    5. Then, repeat these actions to create another Master PM, for
    the same
    CM Item, but with a frequency in DAYS, 30
    
    Master PM (secondary)
    
    - screen shot
    
    Main Master PM (principle)
    For this Master PM, in the PM Actions table, add a row using the
    COMPLETE action, for the secondary Master PM created previously:
    
    - screen shot
    
    Then, generate the 2 associated PMs using the 'Select Action" >
    Create
    Associated PM CM Item
    
    
    
    The following PMs are created by Maximo (Go To Preventive
    Maintenance
    (CM)):
    
    SECONDARY PM
    
    - screen shot
    
    Main PM
    
    - screen shot
    
    Find the secondary PM, and generate the work order using the
    'Select
    Action' > Generate Work order", untick the Use Frequency tick
    box. A new
    work order is generated by Maximo.
    
    
    Go To Asset > Asset (CM) and fing the right assetnum. The click
    the View
    Tab > Maintenance Plan sub-tab. Find the Main PM, and modify the
    Activation Date in the past (2 months ago for instance) in order
    to have
    the Due Date in the past.
    
    Right-clic on the Asset node in the View tab, and use the BDI
    Status
    (Mapping) action in the Contextual menu in order to run the BDI
    for this
    asset.
    
    A new work order is generated for the Main PM.
    
    
    Go To Work Order > Work Order (CM).
    
    Find the work order attached to the main PM, and change the
    status of
    the Work Order to COMP (Completed).
    The work order attached to the secondary PM is automatically
    completed
    (working as designed, it is OK).
    
    But now, Go To Asset > Asset (CM), and retrieve the Asset
    associated to
    the CM Item attached to the PMs :
    Maintenance Plan
    
    As you can see, the event for the Main PM has not been created
    by Maximo
    (KO).
    
    
    
    
    
    Asset (CM) > Maintenance History :
    As you can see, the work orders for the 1004 and 1005 PMs have
    been
    completed (the corresponding events are in the history)
    
    
    Screenshots:
    /ecurep/pmr/3/2/32846,661,706/0-all_data
    
    ACTION TAKEN :
    
    - Problem replicated.
    - ACM L3 has authorized APAR creation.
    
    ACTION PLAN :
    
    Create APAR.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Master PM (CM) and PM (CM) with PM  *
    *                 Actions of type COMPLETE.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a PM Action of type "COMPLETE" has *
    *                      been defined between 2 PMs (primary and *
    *                      secondary) if you complete the  work    *
    *                      order associated with the primary PM    *
    *                      the system does not create the next     *
    *                      Maintenance Event (PLUSALFEVENT) for    *
    *                      the primary PM. The Maintenance Event   *
    *                      for the secondary PM is created as      *
    *                      expected.                               *
    *                                                              *
    *                      Also the Maintenance Event for the      *
    *                      secondary PM should be marked as        *
    *                      "CLAIMED" when the associated Work      *
    *                      Order is completed by the primary.      *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    Maintenance Event of primary PM is not recreated when Work
    Order is completed.
    

Problem conclusion

  • Code modified to achieve correct behaviour.
    
    
    
    
    
    The fix for this APAR is contained in the following maintenance
    package:
    
      | release\fix pack | Hotfix for Release 7.1.1.2 of Asset
    Configuration Manager
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV23783

  • Reported component name

    MX ASSET CONFIG

  • Reported component ID

    5724R4500

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-06-26

  • Closed date

    2012-06-28

  • Last modified date

    2012-06-28

  • 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

    MX ASSET CONFIG

  • Fixed component ID

    5724R4500

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKSJ","label":"Maximo Asset Configuration Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
21 August 2024