IV79849: APPLICATION ALLOWS DUPLICATE ENTRIES IN WOANCESTOR TABLE AT SAME HIERARCHY LEVEL

APAR status

• Closed as program error.

Error description

• There is an issue with the work order ancestor table, whereby
  there
  are duplicate "ancestor" entries created for the same "hierarchy
  levels" for certain work orders.
  .
  Steps to replicate in core Work Order Tracking:
  Go to an exisitng work order, 1001, that has no child work order
  associated with it.
  Query DB for that work order no. in WOANCESTOR.
  There exists one record for the wo referencing itself with
  Hierarchy=0
  Go to Plans tab and using New Row button add a child work order
  to 1001
  and save
  Query WOANCESTOR for child work order, there are two rows one
  for the
  child work order itself at Hierarchy=0 and one record for the
  parent
  work order at Hierarchy=1
  Now recall the child work order no and with the child work order
  as the
  header or top work order record in WOT
  GO to the Parent WO field on the Plans tab, highlight the value
  in the
  field and ctrl+x then tab out to remove the value
  DON'T SAVE
  Immediately, click the detail menu button and choose the Select
  Value
  menu option
  Pick any work order and click the save toolbar button
  Query the child work order in the WOANCESTOR table again and now
  there
  are three record the second row for the original wo Hierarchy=1
  remained, in addition to a third row that was created with the
  second
  assigned parent wo Hierarchy =1
  Thus there are TWO Hierarchy  =1 records which is INCORRECT.
  The original woancestor record should
  have been
  deleted.  If you simply replaced the parent with a new
  parent(without
  the CTL-X and tab out step), the woancestor records are created
  correctly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users who use the work order Tracking application.    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Old woancestor records were not deleted when the child wo is *
  * changing a new parent work order.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * User can directly change the new parent.  This happened only *
  * when user cleared the parent field, tabbing out, and entered *
  * a new parent work order.                                     *
  ****************************************************************
  

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.5.0.10 Product
  

Temporary fix

Comments

APAR Information

• 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

• R750 PSY

     UP