IBM Support

IV98821: PM'S THAT HAVE A NESTED JOB PLAN ARE CREATING ORPHAN CHILD WO'S.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • STEPS TO REPRODUCE
    1. Search the work order application for work orders with
    DESCRIPTION LIKE DUPTEST and make sure there are none in the
    system
    2. Create 3 job plans
    2.1 The first job plan DUPJP1 has a single task and a single
    labor line. Make sure to prefix the description with DUPTEST
    and activate.
    2.2
    The second job plan DUPJP2 has a single task and single rotable
    material Activate RTO18 that specifies an item but not a
    storeroom.
    Make sure to prefix the description with DUPTEST and activate.
    2.3
    The third job plan DUPJP3 contains two tasks
    Task 10 that nests DUPJP1 and
    Task 20 that nests DUPJP2. Make sure to prefix the
    descriptions with DUPTEST and activate.
    3. Create a PM select any asset in ACTIVE status I activated
    12600
    and specify DUPJP3 as the Job Plan. Make sure the storeroom
    site has no value and activate.
    4.  Run the Generate Work Orders action and uncheck Use
    Frequency Critera and hit OK. You should get an error message.
    Select OK and Save the PM.
     5. If you go back and search the work orders with DESCRIPTION
    like DUPTEST you will see a record for DUPTEST JP1.
    6. If you open this record you will notice the parent work
    order number.
     If you try to jump to or search for this WO then you will see
    it is not in the system.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who uses pm to generate work orders.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Some child work orders were saved when there is a            *
    * problematic nested job plan in the job plan structure for    *
    * the PM during the PM WO Gen  process. . The child work       *
    * orders were created with the parent which was rolled         *
    * back(not saved)  when exception was caused by the            *
    * problematic nested job plan.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This is fixed in code.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.0.10 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV98821

  • 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

    2017-08-07

  • Closed date

    2017-12-08

  • Last modified date

    2017-12-08

  • 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

    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 #: IV98821

Modified date: 08 December 2017