My Oracle Support Banner

MUP1 Creates A Severity Severe Error When READ_DTTM Is 01/01/0001 In CCB V260 But Not In CCB V231 (Doc ID 2724248.1)

Last updated on NOVEMBER 01, 2020

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.6.0.1.0 to 2.6.0.1.0 [Release 2.6]
Information in this document applies to any platform.

Symptoms

On :CCB 2.6.0.1.0 version, MR - Meter Read

ACTUAL BEHAVIOR:
-------------------------------
MUP1 creates a severity severe error when READ_DTTM is 01/01/0001 in CCB V260 but not in CCB V231. This prevents the rest of the data being processed. In CCB V231, records with READ_DTTM = 01/01/0001 gets processed by MUP1 and eventually creates a valid Meter Read Upload exception. The behavior in CCB V26010 is different i.e. it creates a severity severe exception which prevents the rest of the records to be processed. LADWP has to change the row in Meter Read Upload Staging table to "E" (error) for the MUP1 to continue. The reason for this is the JAVA program did not parse the 01/01/0001 correctly.

EXPECTED BEHAVIOUR:
--------------------------------------
CCB V26010 should parse the date correctly so the job can log the appropriate meter read upload exception and thus no data correction has to take place. It should behave the same as V231.

ERROR
-----------------------
Caused by: com.splwg.base.api.datatypes.DateFormatParseException: Error parsing a DateTime from string '1-01-01-00.00.00.00' using format yyyy-MM-dd-HH.mm.ss at index -1
at com.splwg.base.api.datatypes.DateFormat.parseCalendar(DateFormat.java:238) ~[spl-base-4.3.0.5.0.jar:?]
at com.splwg.base.api.datatypes.DateFormat.parseDateTime(DateFormat.java:139) ~[spl-base-4.3.0.5.0.jar:?]
at com.splwg.base.api.datatypes.DateTime.fromString(DateTime.java:630) ~[spl-base-4.3.0.5.0.jar:?]
at com.splwg.base.api.datatypes.DateTime.parseIso(DateTime.java:568) ~[spl-base-4.3.0.5.0.jar:?]
at com.splwg.base.support.program.types.StringFieldImpl.bindInto(StringFieldImpl.java:234) ~[spl-base-4.3.0.5.0.jar:?]


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. The meter upload staging table is getting populated by the client, which is typical, via an interface.



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.