IBM Support

IV34527: PM STATUS: POPULATE STOP DATE ON INACTIVE OPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PM Status: Populate Stop Date on INACTIVE Option
    
    Environment
    Maximo 7.5.0.1 for windows 2008
    
    
    Description:
    
    PM Status: Populate Stop Date on INACTIVE Option  is not
    working.
    
    PMChangestatus
    
    Problem
    
    PM Status: Populate Stop Date on INACTIVE Option  is not
    working.
    
    Test case
    
    Step 1. Creating a pm in overdue (PM: 1106).
    
    
    The BDI will not create a workorder because the "Active Date
    Reviewed"  is not checked. Is Ok.
    
    Step 2. Change pm Status to "INACTIVE"
    Preventive Maintenance Application ' Change Status.
    
    
    Checkbox "Populate Stop Date on INACTIVE" is checked. This
    assumes that the field PM.
    
    PLUSASTOPDATE is filled with the sysdate so the BDI should
    not "re-activates" the pm.
    
    Click "OK" and save the PM.
    
    After running  a query  on the pm the it appeared that the PM is
    set to  "INACTIVE" but the PLUSASTOPDATE is null
    
    
    Query:
    
    "select pmnum, description,status,PLUSASTOPDATE
    from pm where pmnum = '1106';"
    
    
    Result:
    
    
    Step 3: Running the BDI
    Asset ' View ' Maintenance Plan PM "1106" is not visible because
    it is set to "INACTIVE".
    
    
    When running the BDI a Workorder is created and the PM is listed
    again on the "Maintenance Plan" tab.
    This should not happen. The PM needs to stay inactive.
    
    eds to stay inactive.
    
    
    
    Cause
    
    The "Database Configuration" application shows the class:
    "psdi.app.pm.virtual.PMChangeStatusSet" on the "PMCHANGESTATUS"
    object.
    
    Also a field class is set on "STATUS".
    
    "psdi.app.pm.virtual.FldPMChangeStatus"
    
    
    "PLUSA" Classes
    
    In Eclipse it appeared that there is a class
    
    "psdi.plusa.app.pm.virtual.PlusAPMChangeStatusSet" class which
    extends "psdi.app.pm.virtual.PMChangeStatusSet".
    
    
    The same for field "STATUS".
    
    "psdi.plusa.app.pm.virtual.PlusAFldPMChangeStatus" extends
    "psdi.app.pm.virtual.FldPMChangeStatus".
    
    
    Step 4. Changing the classes on object "PMCHANGESTATUS"
    
    Original classes:
    
    psdi.app.pm.virtual.PMChangeStatusSet
    psdi.app.pm.virtual.FldPMChangeStatus
    
    Replaced by:
    
    psdi.plusa.app.pm.virtual.PlusAPMChangeStatusSet
    psdi.plusa.app.pm.virtual.PlusAFldPMChangeStatus
    
    Step 5. Test Again
    After a same test  the PM.PLUSASTOPDATE is now filled with
    sysdate when the pm status  is changed "INACTIVE".
    
    When running the BDI no workorder is generated and the pm is not
    "re-activated". Now it is working as aspected.
    
    Solution
    Changing the classes on object "PMCHANGESTATUS" as described at
    step 4.
    
    ACM Dev instructed for APAR creation:
    
    ACM DEV have identified that there is some missing information
    from the ACM product xml file which is the root of the reported
    problem.
    
    
    
    Raisinge this APAR so that ACM Dev can add the missing
    information and provide as a hotfix.
    

Local fix

  • Dev to fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Maximo ACM Preventive Maintenance application.      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the status of a PM is changed to INACTIVE and the       *
    * option "Populate Stop Date on INACTIVE" is checked then the  *
    * system fails to populate the Stop Date.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Install the hotfix to rectify this problem.                  *
    ****************************************************************
    Missing lines from the ACM product xml file caused the class
    extensions which implement this functionality to be lost when
    updatedb is run.
    

Problem conclusion

  • Missing class extensions added to aviation.xml to resolve this
    isssue.
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 750 Maximo ACM
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV34527

  • Reported component name

    PREVENTIVE MAIN

  • Reported component ID

    5724R46PM

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-01-11

  • Closed date

    2013-01-31

  • Last modified date

    2013-01-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

    PREVENTIVE MAIN

  • Fixed component ID

    5724R46PM

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPN7","label":"Prev Maint"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
31 January 2013