New And Required Fields After CCB Upgrade (Doc ID 1321435.1)

Last updated on SEPTEMBER 14, 2022

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.3.1 and later
Information in this document applies to any platform.

Goal

**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

There are many new fields etc in the CCB V2.3.1 upgrade and some are marked as required.
Before upgrading it would be good to have a full analysis of these fields to determine what need to be done with them.

For example flag fields (Y,N) do not appear to populated and are blank but the programs appear to cope with this situation and when you access the field in the GUI the program may set it to N by default.

Questions:
1. The new fields will affect current business logic?
2. Is there needed to examine the new fields to populate a default value?

During the upgrade evaluation there has not been populated any defaults on new fields and there were not seen any issues.

Is there a general statement that explains the implications of new fields on current logic and is there a need to analyze the new fields to populate default values especially for required fields?

Solution

	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

Goal

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.

New And Required Fields After CCB Upgrade (Doc ID 1321435.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!