IBM Support

IJ49684: ISSUES WITH ASSET DOWNTIME REPORTING FUNCTIONALITY WHEN REMOVING DOWNTIME FROM WORK ORDER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Problem:
    If Asset downtime is recorded through multiple Work orders with
    different downtime, and if we delete downtime from Work
    order->Manage Downtime History from any of the Work order, the
    total downtime of the Asset goes back to 0.
    
    Steps to Reproduce:
    1. Open the Work Order Tracking application
    2. Create a new record (1487)
    3. Populate the Asset field (1014)
    4. Under More Actions select 'Report Downtime' and input the
    start and end date fields.
    5. Select OK to close the window
    6. Create a second Work Order record (1489)
    7. Populate the Asset field with the same asset used in the
    first Work Order. (1014).
    8. Under More Actions select 'Report Downtime' and input the
    start and end date fields.
    9. Select OK to close the window.
    10. Move to the Asset application and select the Asset record
    used in the work order records (1014). Scroll to the Downtime
    section to ensure that the total downtime is populated.
    11. Move back to the Work Order Tracking application and search
    for one of the records previously created (1487)
    12. Under More Actions select 'Manage Downtime History'
    13. Delete the reported downtime line for the Asset.
    14. Select OK to close the window.
    15. Move to the Asset application and select the Asset being
    used (1014)
    16. Scroll down to the Downtime section to view the Total
    Downtime field.
    
    
    Results:
    Total Downtime field is set back to 0
    
    
    Expected Results:
    The downtime removed should be subtracted from the total Asset
    downtime reported
    
    Reported In Version:
    Tivoli's process automation engine 7.6.1.3
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If Asset downtime is recorded through multiple Work orders   *
    * with                                                         *
    * different downtime, and if we delete downtime from Work      *
    * order->Manage Downtime History from any of the Work order,   *
    * the                                                          *
    * total downtime of the Asset goes back to 0.                  *
    ****************************************************************
    

Problem conclusion

  • This will be fixed in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49684

  • 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

    2024-01-09

  • Closed date

    2024-02-26

  • Last modified date

    2024-02-26

  • 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:
26 February 2024