Bug 23754881: Not Able To Create NBB With Covered SA Having Only Stopped SA ID(s)
(Doc ID 2307950.1)
Last updated on OCTOBER 06, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.5.0.2.0 to 2.6.0.0.0 [Release 2.5 to 2.6]Information in this document applies to any platform.
Symptoms
On : 2.5.0.2.0 version, IP - Installation Upgrade Proc
ACTUAL BEHAVIOR
---------------
Bug 23754881 : Not able to create NBB with Covered SA having only Stopped SA ID(s)
One observed that NBB creation is failing when adding only stopped SA as covered SA under NBB as part of Bug fix 23754881.
C1CI_OPT_TYP_FLG (base) is not configured properly.
As per bug pfd, it says it should 'Allow stopped SA on NBB SA Char type'. But lookup has been configured with option type of pre-defined values (Y/N).
So, one needs to create SA char type (predefined) with value Y/N and to define the same under Feature Configuration for option type 'C1NB'
Also as per pfd, it should allow stopped SA under NBB which is currently not working when adding only stopped SA.
EXPECTED BEHAVIOR
-----------------------
One should be able to create NBB SA only by adding a STOPPED SA also.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Utility SA Eligible for NBB.
2. Stop the Utility SA.
3. Try to create the NBB SA only by adding a STOPPED SA as covered SA.
4. The base does not allow to create the NBB SA. It shows NBB cannot be activated because it does not cover any SA.
BUSINESS IMPACT
-----------------------
Due to this issue, users cannot create NBB for Stopped Utility SAs.
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 |