IBM Support

IV96029: 'INHERIT STATUS CHANGE' FLAG IS CHECKED ON SAVE IN WORK ORDER APPLICATION EVEN AFTER DISABLING IT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Here are the steps followed when recreating the issue in the
    Maximo
    environment. We found this in the 'Work Order Tracking' Core
    application.
    1 - Create a  workorder or choose an existing Maximo  work
    order.
    Ensure the 'Inherit Status Changes?' flag is checked.
    2 - Create another work order and choose the work order in step
    1 as a
    parent work order.
    3 - By default the 'Inherit Status Changes' flag is checked
    before
    save. Disable the flag and save the child work order
    Notice that the 'Inherit Status Changes' flag is again reset
    to checked.
    This behavior can be observed when disabling the flag and trying
    to
    save the work order multiple times. Each time, the flag will be
    enabled/set to 1.
    .
    Additional Comments
    
    found that setting the default to 0 (in the database
    configuration)
    does not prevent the system from enabling the flag on save. Each
    time we
    save the work order, the PARENTCHGSSTATUS flag (Inherit Status
    Changes?) is enabled.
    
    IMPORTANT TO NOTE (Please Read)
    This issue is unique to the Maximo deployment used below.
    (Maximo
    ACM + Maximo (Tr) + Maximo HSE+ Maximo Linear)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users that use Maximo for Nuclear 7.5.1.0 or high.       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * 'INHERIT STATUS CHANGE' FLAG IS CHECKED ON SAVE IN WORK      *
    * ORDERAPPLICATION EVEN AFTER DISABLING IT                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Database change.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV96029

  • Reported component name

    MX ASSET CONFIG

  • Reported component ID

    5724R4500

  • Reported release

    764

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-12

  • Closed date

    2017-05-17

  • Last modified date

    2024-10-29

  • 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

    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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"764","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
31 October 2024