Duplicate SAs Created During Start Order When Premise Has Multiple SPs
(Doc ID 2783102.1)
Last updated on OCTOBER 03, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.7.0.3.0 to 2.8.0.0.0 [Release 2.7 to 2.8]Information in this document applies to any platform.
Symptoms
**Disclaimer:** This KM article may include the following abbreviations:
SA - Service Agreement
SP - Service Point
On : 2.7.0.3.0 version, ENV - Environment
Duplicate SAs created during Start Order When Premise has Multiple SPs
When an Order is used to start service at a premise that has an active SA and multiple SPs, duplicate SAs are created for the same SP. For example, if a premise has SP 1 and SP 2, an SA is created for SP 1 and a duplicate SA is created for SP 1. The logs show the correct SPs being associated with the SAs, but that does not seem to reflect in the SAs created.
This is causing customers to be double billed.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
SPs on-premise: XXXX1
SAs created by the service order.
In the logs, you’ll see that SA: XXXXSA1 contains different SP (which is the expected SP)
but if we will check on the created SAs it is showing that both electric SAs have the same SP.
SPs on-premise: XXXXX2
SAs created by the service order.
In the logs, you’ll see that SA: XXXXSA2 contains different SP (which is the expected SP)
but if we will check on the created SAs it is showing that both electric SAs have the same SP.
SPs on-premise: XXXXX3
SAs created by the service order.
In the logs, you’ll see that SA: XXXXSA3 contains different SP (which is the expected SP)
but if we will check on the created SAs it is showing that both electric SAs have the same SP.
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 |