ASSET INSPECTION DETAILS NOT PLANT SPECIFIC - FRM-40600 ERROR PRODUCED

(Doc ID 753391.1)

Last updated on OCTOBER 16, 2016

Applies to:

Oracle Utilities Work and Asset Management - Version 1.7.15.3.2 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

When trying to Save an Asset Inspection Data Observation, a "FRM-40600:Record has already been
inserted." error is produced. This test requires that Steps 1 to 7 be performed in two different
Plants such that when the User clicks on Save in Step 7 for the second Plant, the SEQUENCE_NUMBER
being created is the same one that was just created in the other Plant. This can be accomplished
by setting the Sequence Numbers value to the same number for the SA_ASSET_INSPECTION_DETAIL table
in both Plants. If the error is not produced, you will have to look in TOAD or SQL Developer to
ensure that the above was happening.

### Steps to Reproduce ###
1. Navigate to the Asset Class Module. Select an Asset Class. (I missed the "Class" word in my
screenshots document, but the screenshot is of teh Asset Class module.)
2. Navigate to the Condition Assessment View and detail an Assessment Name, Description and Basis
3. Navigate to the Inspection Criteria View and detail Categories, Weights and Criteria. Set the
Asset Class to Active
3. Navigate to the Inspection Criteria View and detail Categories, Weights and Criteria. Set the
Condition Assessment and Asset Class to Active
4. Navigate to the Asset module and assign the Asset Class from Step 1 to that Asset
5. Navigate to the Asset Inspection Data module, click on New and create an Inspection
6. Navigate to the Observations View. Enter/Select a Category and Failed Criteria
7. Click on Save. Note error produced
8. Navigate to the Sequence Numbers module and enter the SA_ASSET_INSPECTION_DETAIL table
9. Open TOAD or SQL Developer. Navigate to the Data view of the SA_ASSET_INSPECTION_DETAIL table.
I’m not sure why I am seeing a LOT of records with the same SEQUENCE_NUMBER. I do not on my
laptop. That is not the issue though. The issue appears to be that the SEQUENCE_NUMBER being
assigned by the system is not PLANT specific. The application is trying to create a
SEQUENCE_NUMBER of “18”, but I already have a row with the SEQUENCE_NUMBER = “18”, but
it’s for PLANT = “01”, not “35”, which is the PLANT I was logged in to
10. For a temporary work around and to prove my theory, sort on ASC for the SEQUENCE_NUMBER field
to determine the highest number on the table, regardless of the PLANT
11. Navigate back to the Sequence Numbers module and set the SA_ASSET_INSPECTION_DETAIL table for a number higher than the highest one from above
12. Navigate back to the Observations View from Step 6 for the Plant you received the error in and
click on Save. The record is saved successfully.






Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms