Start Service Request Process Flow Errors Out Due To An Existing Pending Start (Doc ID 2964275.1)

Last updated on AUGUST 16, 2023

Applies to:

Symptoms

On: 2.8.0.0.0 version, CI - Customer Information

Start Service Request Process Flow errors out due to an existing pending start

When trying to start a service (through the Start Service Process Flow) for a premise that has an existing pending start SA, an error is thrown saying that the existing SA could not be stopped.
In the old Start/Stop page, this was allowed provided that the start dates do not overlap (i.e. the new SA's start date is later than the existing pending start SA's start date). What happens in the old start/stop page is that the new SA's start date is used as the existing SA's end date.

ERROR
-----------------------
SA with CIS Division CA and SA Type E-RES encountered the following error: SA-California / Electric residential, ERES2, Pending Start,
12-31-2021 - 11-17-2022, Electric heat option, 8876598330 could not be stopped...

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Premise 3006071884 has a pending start SA for 12-31-2021
2. Start a new service on the premise
3. Start Date is set to 11-17-2022 which is past the start date of the existing pending start SA so
there is no overlap
4. Error is encountered when finishing the process flow:

SA with CIS Division CA and SA Type E-RES encountered the following error: SA-California / Electric residential, ERES2, Pending Start,
12-31-2021 - 11-17-2022, Electric heat option, 8876598330 could not be stopped..

Changes

Cause

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