My Oracle Support Banner

'start read is later than stop read' Error Sometimes Occurs When Meter Read Is Saved On SASP (Doc ID 1326349.1)

Last updated on MARCH 23, 2019

Applies to:

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

Symptoms

**Any examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

CCB/CC&B - Oracle Utilities Customer Care and Billing

SA - Service Agreement

SP - Service Point (CCB)

When attempting to save a 'Stop' Meter Read on a SA/SP when no 'Start' Meter Read is populated, an error similar to the following sometimes occurs.


SA (#########) SP (##########) start read (null) date time (2009-03-31-23.00.00.000000) is later than stop read (55716169890) date time (2009-03-31-14.00.00.000000).

Message number; 3, 31818
Call sequence: ;CIPCSAPR;CIPCSAPL;CIPCSVAP



This scenario can occur in the case where a Service Agreement has been created but before it has been activated it becomes necessary to stop it. In this case, the SA will have a Field activity for both start and stop activity, but the stop read will be populated first if the Field Activity for stop activity gets processed first. This scenario can be replicated by manually adding a Stop Meter Read to a SA/SP, where the SA/SP is not yet active, and no Start Meter Read exists.

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.