IJ36119: WHEN MXE.APP.WORKORDER.INSPECTIONBATCHRECORD PROPERTY VALUE IS MISSING or TRUE,MORE THAN 1 WO RECORD US CREATED FOR SAME WO

APAR status

• Closed as new function.

Error description

• When mxe.app.workorder.InspectionBatchRecord property's value is
  missing or true,more than one WORKORDER record is created for
  the same WO
  
  STEPS TO REPRODUCE:
  1. Go To Manage Inspection Forms.
  2. Create a new form setting the Name to "Test
  mxe.app.workorder.InspectionBatchRecord" and the Type to
  "Inspection".
  3. Click "Save". For purposes of this test, it is not necessary
  to add any questions.
  4. On the "Revision History" screen, take note of the
  InspFormNum that appears under the Name.
  It will be entered in the "Inspection Form" field in the various
  test scenarios.
  5. Click on the Status to change it from "Draft" to "Active".
  6. Open Oracle SQLDeveloper or another SQL tool.
  
  Condition 1: System Property Is Missing
  1. Go To System Properties.
  2. Search for Property Name =
  "mxe.app.workorder.InspectionBatchRecord".
  3. If found, delete it and restart JVM.  It should not be found
  unless it was previously added manually
  
  Condition 2: System  Property  Is  1/true:
  1. Go To System Properties.
  Click "Add Row", enter "mxe.app.workorder.InspectionBatchRecord"
  for Property Name, enter
  "Test" for Description, enter "1" for Global Value, and click
  "Save".
  3. Click the checkbox to the left of the row, click "Live
  Refresh", and then click "OK" on the
  resulting dialog.
  
  Checking Results:
  After each test do the following:
  1. Go To Conduct an Inspection.
  2. Find the newly created tiles.
  3. If a Batch tile (top-right corner folded) was added, click on
  it.
  4. In the SQL tool, run the following:
  SELECT IsBatch, ReferenceObject, ReferenceObjectID, Parent, IR.*
  FROM InspectionResult IR
  ORDER BY IR.InspectionResultID DESC ;
  
  Test: Top-Level WO with Inspection on WO and a MultiAssetLocCI
  record:
  1. Go To Work Order Tracking.
  2. Create a new WO.
  3. Enter "Case TS######### - Scenario X.B - WO" in Description.
  (Substitute "I", "II", or "III" for
  "X".)
  4. Enter a unique Location (AIR101).
  5. Click "New Row" in the "Multiple Assets, Locations, and CIs"
  table and enter a unique Location
  (AIR102).
  6. (Optional) Save. Run test first without this step. If
  "Database error number 1" error occurs, repeat
  test including this step and capture both results adding a ".2"
  to the scenario ID.
  7. Enter the InspFormNum in the Inspection Form field on the WO
  and on the row in the "Multiple
  Assets, Locations, and CIs" table.
  8. Save.
  
  RESULTS:
  - After Step 8, a System Message appeared saying "BMXAA4211E -
  Database error number 1 has occurred when operating on WORKVIEW
  : Record=1297 Class=WORKORDER Site=BEDFORD. Report the error to
  the owner of the deployment."
  - In spite of the error, four InspectionResult records were
  inserted into the database. One is a PARENTWO record, one is a
  MULTIASSETLOCCI record, and two are WORKORDER records. The two
  WORKORDER records have the same ReferenceObjectID and neither
  have the Parent column populated. (The WO and related records
  were also written to the database.)
  - If you close the dialog, add a "." to the end of the
  Description (to enable the Save button), remove the ".", and
  Save again, you get the same error.
  - If you close the dialog and create a new WO to repeat the
  Steps including the optional Save at Step 6, you get the same
  error after Step 6. It is the exact error meaning it is still
  referencing the previous WO. In this case, the error appears to
  be keeping the new WO from being saved.
  - To clear the error, you need to exit and re-launch Work Order
  Tracking
  (edited)
  
  REPORTED IN VERSION:
  Maximo Asset Management 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When adding a MULTIASSETLOCI record, a duplicated record was *
  * created on INSPECTIORESULT                                   *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained on the ifix package for
  Release 7612
  

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