My Oracle Support Banner

Outbound Communication Response Error - Via FCS Meter Reads Upload Process (Doc ID 2912075.1)

Last updated on JANUARY 26, 2023

Applies to:

Oracle Utilities Meter Data Management - Version 2.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Outbound Communication Response Error - Via FCS Meter Reads Upload Process

IMDs w/ Reader Remarks and a No Read condition code, such that a Measurement will not get created when the IMD is finalized, still update Most Recent Msrmt Date/Time even without a Measurement. This results in a future search in Activity looking for measurement at that same time and then failing when it doesn't find one.

This results in a problem and has downstream effects. In the customer's case, the Device Event when processed will trigger a Service Investigation which results in a Field Activity being created. The Field Activity is one that uses script D1-RetReaDtl which calls D2-RetReaDtl to retrieve the most recent measurement. The script fails because it tries to find a measurement that matches the Most Recent Measurement Date/Time but that measurement does not exist.

EXPECTED BEHAVIOR
The measurement date times on the Measuring Component should only be updated if a Measurement was created at that time.


STEPS

(details are for support environment)
MC id 900028207869
Note at the beginning of the test there are measurements through standard time 06/09/2022 11:00 PM for this MC

1) Upload to upload a Reader Remark on an IMD and no reading.
Specifically this means <deviceEventTypes> section is populated with at least one Reader Remark and the IMD enQty is 0 and the ccondion is code 100500 which is a No Read Condition "No Read - Field"

Sample IMD upload:
<deviceList>
<device>
<initialMeasurementDataList>
<initialMeasurementData>
<serviceProvider>GENIUS</serviceProvider>
<preVEE>
<dvcIdN>EDE-007</dvcIdN>
<mcId>900028207869</mcId>
<uom>KWH</uom>
<enDt>2022-06-20-00.00.00</enDt>
<enQty>0</enQty>
<inShift>D1SH</inShift>
<ccond>100500</ccond>
</preVEE>
<processData>
<deviceEventTypes>
<deviceEventTypesList>
<deviceEventType>BROKENMETER</deviceEventType>
</deviceEventTypesList>
</deviceEventTypes>
</processData>
</initialMeasurementData>
</initialMeasurementDataList>
</device>
</deviceList>

Using D1-InitialLoadIMDScalar.
2) Finalize the above IMD:
-IMD was finalized as expected.
-No Measurement was created due to the "No Read - Field" condition code used.

-Device Event was created for the Reader Remark

3) Checking Most Recent Measurement Date/Time:
Query: select most_recent_msrmt_dttm from D1_MEASR_COMP where MEASR_COMP_ID = '900028207869';
Result: 06/19/2022 11:00 PM

Changes

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.