IBM Support

IJ06018: IN WORK ORDER TRACKING APPLICATION, FAILURE CLASS FIELD DOES NOT GET POPULATED IN TASK WORK ORDERS

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

  • STEPS TO REPLICATE:
    
    1) Go to Locations application
    
    2) Create a new Operating Location associated to any valid
    Failure Class, as for example, PRINTER, and save the record
    
    3) Go to Work Order Tracking application
    
    4) Create a new WO against the Location created above and save
    the record
    
    Note that, as expected, system automatically populates the WO
    Failure Class field with the Location Failure Class.
    
    5) Go to Plans tab and add a new Task to the WO and save the
    record
    
    6) Navigate to the Reference WO field, copy its number and bring
    up the Reference WO record to the screen
    
    RESULTS:
    Even though creating the Task WO against the same Location as
    the Parent WO, in the Task WO the Failure Class field is empty.
    This is the issue.
    
    EXPECTED RESULTS:
    In the Task WO, the Failure Class field should be the same as
    the Failure Class from both Parent WO and Location.
    
    PRODUCT VERSION:
    Maximo 7.6.0.9
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Failure code not set on a new work order task.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    STEPS TO REPLICATE:
    1) Go to Locations application
    2) Create a new Operating Location associated to any valid
    Failure Class, as for example, PRINTER, and save the record
    3) Go to Work Order Tracking application
    4) Create a new WO against the Location created above and save
    the record
    Note that, as expected, system automatically populates the WO
    Failure Class field with the Location Failure Class.
    
    5) Go to Plans tab and add a new Task to the WO and save the
    record
    6) Navigate to the Reference WO field, copy its number and bring
    up the Reference WO record to the screen
    
    RESULTS:
    Even though creating the Task WO against the same Location as
    the Parent WO, in the Task WO the Failure Class field is empty.
    This is the issue.
    
    EXPECTED RESULTS:
    In the Task WO, the Failure Class field should be the same as
    the Failure Class from both Parent WO and Location.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	| release\fix pack\interim fix for Release 7.6.1.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ06018

  • Reported component name

    WORK ORDERS

  • Reported component ID

    5724R46WO

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-27

  • Closed date

    2018-05-16

  • Last modified date

    2018-05-16

  • 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

    WORK ORDERS

  • Fixed component ID

    5724R46WO

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Work Order Tracking

Software version: 760

Reference #: IJ06018

Modified date: 16 May 2018