IJ28221: MISSING SAMEAS SETTINGS FOR WORKORDER.REMARKDESC

APAR status

• Closed as program error.

Error description

• Problem
  
  When doing failure reporting in a tickets-related or
  workorder-related application, the value entered in the
  non-persistent Remarks field writes to the persistent
  FAILUREREMARK.DESCRIPTION attribute. The tickets-related objects
   correctly have a sameas relation to FAILUREREMARK.DESCRIPTION.
  The workorder-related objects have a sameas relation to
  WORKORDER.REMARKDESC. This is not correct.
  
  
  
  
  All non-persistent REMARKDESC attributes should have a sameas
  relation to the persistent FAILUREREMARK.DESCRIPTION to insure
  that changes to the configuration of this database attribute can
  accommodate values from ticket AND workorder applications.
  Otherwise, for example, WORKORDER.REMARKDESC can be increased to
  200 leading to a failure on save due to the non-persistent work
  order failure reporting Remark (WORKORDER.REMARKDESC) value
  being too large for the FAILUREREMARK.DESCRIPTION field.
  
  
  
  
  The following SQL shows the discrepancy:
  
  
  
  
  ?select
  objectname,attributename,sameasobject,sameasattribute,length,mus
  tbe,maxtype,persistent from maxattribute where
  (attributename='REMARKDESC' or sameasattribute='REMARKDESC') or
  (objectname='FAILUREREMARK' AND attributename='DESCRIPTION')
  order by sameasobject;
  
  
  Results
  
  The query above shows the missing and incorrect same as object
  and same as attributes on the work order-related objects.
  
  
  Expected Results
  
  The same as objects and same attributes for work order-related
  objects should be consistent with the ticket-related objects and
   refer to FAILUREREMARK.DESCRIPTION.
  
  
  Reported Version
  Maximo7.6.1.2
  

Local fix

• no work around
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * INCORRECT SAMEAS SETTINGS FOR WORKORDER-RELATED REMARKDESC   *
  * ATTRIBUTES                                                   *
  ****************************************************************
  When doing failure reporting in a tickets-related or
   workorder-related application, the value entered in the
   non-persistent Remarks field writes to the persistent
   FAILUREREMARK.DESCRIPTION attribute. The tickets-related
  objects
   correctly have a sameas relation to FAILUREREMARK.DESCRIPTION.
   The workorder-related objects have a sameas relation to
   WORKORDER.REMARKDESC. This is not correct.
   All non-persistent REMARKDESC attributes should have a sameas
   relation to the persistent FAILUREREMARK.DESCRIPTION to insure
   that changes to the configuration of this database attribute
  can
   accommodate values from ticket AND workorder applications.
   Otherwise, for example, WORKORDER.REMARKDESC can be increased
  to
   200 leading to a failure on save due to the non-persistent
  work
   order failure reporting Remark (WORKORDER.REMARKDESC) value
   being too large for the FAILUREREMARK.DESCRIPTION field.
   The following SQL shows the discrepancy:
   select
  
  objectname,attributename,sameasobject,sameasattribute,length,mus
   tbe,maxtype,persistent from maxattribute where
   (attributename='REMARKDESC' or sameasattribute='REMARKDESC')
  or
   (objectname='FAILUREREMARK' AND attributename='DESCRIPTION')
   order by sameasobject;
   Results
   The query above shows the missing and incorrect same as object
   and same as attributes on the work order-related objects.
   Expected Results
   The same as objects and same attributes for work order-related
   objects should be consistent with the ticket-related objects
  and
   refer to FAILUREREMARK.DESCRIPTION.
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  Release 7.6.1.3 of Base Services
  

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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels