IJ44686: WHILE ADDING A NEW LOCATION RECORD, THE SYSTEM WRONGLY LOOKS FOR RELATED WORK ORDERS.

APAR status

• Closed as program error.

Error description

• Problem Description:
  There is no need to look for related WO sets when a Location
  record is to be added since none exists. This consumes good
  amount of time.
  
  The log displays:
  select * from workorder where status in (select value from
  synonymdomain where domainid = 'WOSTATUS' and maxvalue not in (
  'CLOSE' , 'COMP' , 'CAN' )) and worktype in (select worktype
  from worktype a where type = 'CAL' and a.orgid = orgid) and
  location = 'LOCATION1' and siteid = 'BEDFORD' and targstartdate
  = (select min(targstartdate) from workorder where targstartdate
  is not null and status in(select value from synonymdomain where
  domainid = 'WOSTATUS' and maxvalue not in ( 'CLOSE' , 'COMP' ,
  'CAN' )) and worktype in (select worktype from worktype a where
  type = 'CAL' and a.orgid = orgid) and location = 'LOCATION1' and
  siteid = 'BEDFORD' ) for read only
  
  REPORTED IN VERSION:
  IBM Maximo Asset Management 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * WHILE ADDING A NEW LOCATION RECORD, THE SYSTEM WRONGLY LOOKS *
  * FOR RELATED WORK ORDERS                                      *
  ****************************************************************
  

Problem conclusion

• A fix for this APAR will be included in a future release.
  

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:

Fix information

• Fixed component name

  ASSETS

• Fixed component ID

  5724R46AS

Applicable component levels