IV93823: ADDING OBSERVATION VIA MIF ON WORKORDER CREATES REFETCH ERROR

APAR status

• Closed as program error.

Error description

• Reproduced on 7.5.0.4 and 7.6.0.6
  
  1) Go to Integration=> Object Structures. Create a new Object
  Structure.
  Fill in all fields as below:
  Object Structure: MXWOACTIVITY
  Consumed by: Integration
  In the Source Object section: Object: WOACTIVITY
  
  2) Go to Integration=>Enterprise Services. Create a new
  Enterprise
  Service.
  Fill in all fields as below:
  Enterprise Service: MXWOACTIVITYInterface
  Object Structure: MXWOACTIVITY
  
  3) Go to Integration => External Systems. Search for EXTSYS1.
  Check Enabled.
  Click on the Enterprise Services tab.
  Click on New Row button. Fill in teh fields as below:
  Enterprise service: MXWOACTIVITYInterface
  Check Enabled.
  
  4) Create a new ALNDOMAIN with the name MRNMETER and the
  values: GOOD,
  BAD, UGLY
  
  5) Create a new meter. Fill in the fields as below:
  Meter: MRNOBS1
  Meter Type: CHARACTERISTIC
  Domain: MRNMETER
  
  6) Create a new ASSET. Fill in the fields as below:
  Asset: MRNL1
  Check Linear.
  In the section Linear Referencing Details:
  Direction: NORTH
  LRM: KILOMETERS
  Start Measure: 1
  End Measure: 3
  Save.
  Change the Status to ACTIVE.
  
  7)Create a new Condition Monitoring. Fill in the fields as
  below:
  Point: MRNCM1
  Asset: MRNL1
  Meter: MRNOBS1
  Save.
  
  8)Go back to Asset application. Search for the asset MRNL1.
  Click on Meters tab. In the Meters section fill in the field
  Start
  Measure with 1 and End Measure with 2.
  Save.
  
  9) Create a new Work Order. Fill in the fields as below:
  Work Order: 3107
  Click on Plans tab.
  Click on New Row in the Tasks for Work Order section.Fill in
  the fields
  as below:
  Asset: MRNL1
  Save.
  Take a note the value of the field Reference WO in the task.
  
  10)Navigate to External Systems-> Select EXTSYS1 from Step 3.
  Select MXWOACTIVITYInterface from Enterprise Services Tab.
  Save the XML below:
  
  <?xml version="1.0" encoding="UTF-8"?>
     <SyncMXWOACTIVITY xmlns="http://www.ibm.com/maximo"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  creationDateTime="2014-04-01T15:21:51-04:00" transLanguage="EN"
  baseLanguage="EN" messageID="1396380111249131188"
  maximoVersion="7 5
  20130129-2023 V7504-38">
         <MXWOACTIVITYSet>
             <WOACTIVITY  action="AddChange">
                 <WONUM>REPLACE HERE THE VALUE OF REFERENCE
  WO</WONUM>
                 <POINTNUM>MRNCM1</POINTNUM>
                 <OBSERVATION>GOOD</OBSERVATION>
                 <SITEID>BEDFORD</SITEID>
                <ORGID>EAGLENA</ORGID>
             </WOACTIVITY>
         </MXWOACTIVITYSet>
     </SyncMXWOACTIVITY>
  
  Click on Data Import button.
  Check Import Preview.
  Search for the XML created in this step.
  Click OK.
  
  Stack of the error:
  [2/6/17 13:10:12:307 EST] 00000101 SystemOut     O 06 Feb 2017
  13:10:12:307 [ERROR] [MXServer] [] Error processing SOAP
  message:nested
  exception is: psdi.util.MXRowUpdateException: BMXAA8229W -
  Record
  ASSETMETER :  Asset=MRNL1 Meter=MRNOBS1 Site=BEDFORD Linear
  Specification Id=27 has been updated by another user. Your
  changes have
  not been saved. Refresh the record and try again.
  javax.ejb.EJBException: nested exception is:
  psdi.util.MXRowUpdateException: BMXAA8229W - Record ASSETMETER :
  Asset=MRNL1 Meter=MRNOBS1 Site=BEDFORD Linear Specification
  Id=27 has
  been updated by another user. Your changes have not been saved.
  Refresh
  the record and try again.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * users who use MIF to import observation to WO activity.      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * User encountered the "Re-fetch error" on ASSETMETER when     *
  * importing the observation/characteristic type of meter       *
  * reading to a work activity.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * none                                                         *
  ****************************************************************
  

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.8 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

  ASSETS

• Fixed component ID

  5724R46AS

Applicable component levels

• R760 PSY

     UP