IBM Support

IZ07546: READING ENTERED IN WORK ORDER VIA THE TASK LINE ON THE ACTUALS TAB IN WORK ORDER TRACKING NOT UPDATING ASSET.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Reading entered in Work Order via the task line on the Actuals
    tab in Work Order Tracking not updating Asset.
    
    Maximo - 6.2.1 Build 156 DB build V600-530
    
    Windows 2003
    
    Weblogic 8.1.4.0.
    
    Measurement information entered in the Work Order application on
    the
    Plans/Actuals tab, on a task line item, updates the reading for
    the
    Measurement Point in Condition Monitroing application, however,
    in the Assets
    application if you recall the asset and select Manage Meter
    Readings
    History there is no reference to the reading which was entered
    from the
    Work Order application.
    
    Steps to replicate:
    
    Create Asset (11430TEST)
    
    Create a Job Plan with this asset (JP11430TST)
    
    Create a Meter O-PressureTST with the Type - Gauge, Unit - PSI
    
    Create a Condition Monitoring Point, Assign Asset (11430),
    Assign
    Meter (O-PressureTST).
    
    Upper Warning Limit - 4500
    
    Upper Action - 5000
    
    Lower Warning Limit - 3500
    
    Lower Action Limit - 3200
    
    Upper Limit Job Plan, Lower Limit Job Plan (JP11430TST)
    
    Upper Priority 2, Lower Priority 2
    
    
    
    Open a new work order, assign Asset, 11430TEST, Assign job plan
    JP11430TST
    
    
    Approve the work order, then enter on Actuals tab, for
    one of your tasks a Gauge Meter value (4000) for Measurement
    Information
    
    Save
    
    Go back to your Condition Monitoring application and recall the
    point you created for the Asset 11430TEST, value will be
    recorded (4000)
    
    Go to your Asset (11430TEST), Select Actions Drop Down Menu,
    select
    "Manage Meters History"- Characteristics and Gauge Meter
    Readings is not updated with the gauge meter reading that was
    entered on the Work Order.
    
    Tested and confirmed the behavior. The question is:
    
    Should the reading recorded on the Actuals tab be relevant and
    update to
    the Asset, as it is recorded against a condition monitoring
    point? I think it
    should. Further testing indicated that placing a value in the
    Measurement Value field
    without a Measurement Point Value on the Actuals tab in the WOT
    app also
    does not show up in the Manage Meter Readings History in the
    Asset application. It does not show up if a Measurement Point is
    not entered, either in the aforementioned option
    or in the Condition Monitoring application as expected. If the
    Enter
    Meter Readings option is used in the Work Order Tracking app
    then the
    value entered does show up in the Manage Meter Reading History
    option in
    the Assets app.
    
    Tested the client's scenario in Maximo 5.2 and while the
    functionality
    is different, ultimately the reading, entered on the task line
    on the
    Actuals tab, was updated on the Measurement tab (which in 6.2.1
    is
    replaced by the Select Actions option Manage Meter Readings
    History) for
    the equipment in the Equipment application. It also updated the
    measurement reading for the point in the Condition Monitoring
    application. In testing in 5.2 I also noticed that there is no
    Enter
    Meter readings option in the Select Actions menu of the WO
    Tracking
    application, just another way 5.2 differs from 6.2.1.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Maximo users                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Fields: assetnum, location, inspector,  *
    *                      metername, assetid  were not saved in   *
    *                      the measurement table                   *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    READING ENTERED IN WORK ORDER VIA THE TASK LINE ON THE ACTUALS
    TAB IN WORK ORDER TRACKING NOT
    

Problem conclusion

  • Fixed in the FldWOMeasuremtnValue.java, FldWOMeasureData.java
    and FldWOPointNum.java
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ07546

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    621

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-10-29

  • Closed date

    2007-12-03

  • Last modified date

    2007-12-03

  • 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

    ASSETS

  • Fixed component ID

    5724R46AS

Applicable component levels

  • R621 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":"621","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
09 April 2023