New And Required Fields After CCB Upgrade
Last updated on OCTOBER 18, 2016
Applies to:Oracle Utilities Customer Care and Billing - Version: 2.3.1
Information in this document applies to any platform.
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.
1. The new fields will affect current business logic?
2. Do we need to examine the new fields to populate a default value?
During the upgrade evaluation we have not populate any defaults on new fields and we have not seen any issues.
Is there a general statement that explains the implications of new fields on current logic and do we need to analyse the new fields to populate default values especially for required fields?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms