Oracle Utilities Customer Care and Billing

Release Notes

Release 2.4.0 Service Pack 3

E37711-04

June 2015

Oracle Utilities Customer Care and Billing Release Notes

E37711-04

Copyright © 2015 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Preface

These release notes provide an overview of the enhancements, known issues, and other changes in this release.

Audience

Oracle Utilities Customer Care and Billing Release Notes is intended for anyone installing or using Oracle Utilities Customer Care and Billing.

Related Documents

For more information, refer to these Oracle documents:

Installation Guides and Release Notes

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Release Notes

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Quick Install Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Installation Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Database Administrator’s Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Optional Product Installation Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 License Information User Guide

Administration and Business Process Guides

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Administration Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Business Process Guide

•

Oracle Utilities Application Framework V4.2.0.3 Administration Guide

•

Oracle Utilities Application Framework V4.2.0.3 Business Process Guide

Supplemental Documents

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Batch Server Administration Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Server Administration Guide

•

Oracle Utilities Customer Care and Billing V2.4.0.3 Security Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Release Notes

This document provides general information about this release of Oracle Utilities Customer Care and Billing, including new functionality, known issues, and other important information.

Refer to the Quick Install Guide and the Installation Guide for information regarding supported platforms and installation steps.

This guide includes the following:

•

Release Overview

•

Database Changes

•

System Data Changes

•

New Functionality

•

Oracle Utilities Application Framework Enhancements

•

Known Issues

•

Deprecation Notices

•

Supported Integrations

•

Demo Data Information

Release Overview

This section contains general information about this release of Oracle Utilities Customer Care and Billing version 2.4.0.3, also referred to as version 2.4.0 Service Pack 3.

This release includes the following components:

•

Oracle Utilities Customer Care and Billing version 2.4.0.3

•

Oracle Utilities Application Framework version 4.2.0.3

Please visit My Oracle Support (http://support.oracle.com) and Oracle Software Delivery Cloud (http://edelivery.oracle.com/) for the most recent service packs and patches for Oracle Utilities Customer Care and Billing V2.4.0 to ensure you have the most current version of this product.

Supported Platforms

See the Supported Platforms section of the Oracle Utilities Customer Care and Billing Quick Install Guide included in this release for an updated list of supported platforms.

Simple Upgrades

This version of Oracle Utilities Customer Care and Billing supports the following simple upgrade paths:

•

Upgrade from Oracle Utilities Customer Care and Billing 2.2.0 Service Pack 10 to 2.4.0 Service Pack 3

•

Upgrade from Oracle Utilities Customer Care and Billing 2.3.1 Service Pack 10 to 2.4.0 Service Pack 3

•

Upgrade from Oracle Utilities Customer Care and Billing 2.4.0 Service Pack 1 to 2.4.0 Service Pack 3

•

Upgrade from Oracle Utilities Customer Care and Billing 2.4.0 Service Pack 2 to 2.4.0 Service Pack 3.

Note that if you are upgrading from a version not on the list above, a multiple step upgrade of the database would be necessary to get to one of the versions listed above. All prior upgrades have been supplied in the database package.

Prerequisite Software Notices

This release of Oracle Utilities Customer Care and Billing requires Micro Focus 5.1 WrapPack 7 or 8 or 9 or 10.

Database Changes

Version 2.4.0.3 includes database enhancements. For more information about database changes see the Oracle Utilities Customer Care and Billing Database Administrator’s Guide. These changes include:

•

Service Cycle (SVC_CYC_CD) and Service Route (SVC_RTE_CD) have been increased from 8 to 16 bytes. The change is reflected in CI_SP_RTE and CI_SVC_RTE_STG_DWN tables.

•

Created new XC339S1 index on the CI_SPR table, NT_XID_CD field. (Bug number 18054823)

•

Created new XT094S7 index on the CI_FA table, FA_EXT_ID. (Bug number 18054823)

•

Created new XT064S1 index on the CI_BAL_CTL_GRP table, BALANCING_STAT_FLG, BAL_CTL_GRP_ID fields. (Bug number 18681476)

•

Created new XT027S1 index on the CI_NT_DWN_CTXT table, CTXT_VAL, NT_DWN_CTXT_FLG fields. (Framework Bug number 18056717)

•

Lookup field: C1_NF_SSTASK_TYPE_FLG, Values: ‘C1FI’, ‘C1MP’ are set to ‘CM’. A pre-blueprint script will change the owner flag to ‘CM’.

•

Email ID field length increased from 70 to 254 characters (Bug 20659806)

•

Improve TD-CEVT run for reference (Bug 19274344)

System Data Changes

•

Application Service C1-LEADEVENTBOAS (Lead Event BO) is modified in this release

•

The following Application Services are new for this release:

Application Service

Description

C1-EXECENRLINTVCRI

Execute Enrollment Initiative Criteria

C1THDPR

Third Party Representative Portal

C1THDPRQ

Third Party Representative Query Portal

C1-NOTFTYPEBOAS

Notification Type BO

C1-NTFPRTASKBOAS

Notification Communication Preference BO

C1-NTFTYPE

Notification Type MO

C1-NTFYPREF

Communication Preference Maintenance

C1-PERCONTTYPE

Person Contact Type

C1-PERCONTTYPEBOAS

Person Contact Type BO

C1NTFTYP

Notification Type Portal

C1PCNTTY

Person Contact Type Portal

New Functionality

This section describes new and enhanced features in this release of Oracle Utilities Customer Care and Billing, including:

•

Person Contacts

•

Notification Preferences

•

Bill Segment Auto Cancel

•

Customer Program Management Enhancements

•

DataConnect Extracts

Person Contacts

Person Contact is a new child of Person. Person Contact provides a place to consolidate all contact information such as phone number, e-mail addresses, and any other contact information contacts in one place. ‘Do not disturb’ information can be captured for each contact. A batch process, C1-INPUS (Create Person Contact from Person Phone/Email) is provided to create person contacts from person phone and e-mail.

Notification Preferences

Notification Preferences adds new functionality to send notifications to customers and maintain customer preferences for receiving or not receiving notifications. Notification Types are highly configurable and define the message, allowable channels, who can receive the notification, if a subscription is required or if the notification can be sent without a subscription, and more. Opting out is also supported.

Communication preferences are maintained in the Account portal. Additionally, communication preferences can be used to define preferences for e-mailing or faxing bills and quotes, including sending to multiple destinations.

Notification Changes

In previous releases, notifications were only supported through Customer Self-Service and Notification Center. A lookup, C1_NF_SSTASK_TYPE_FLG was used to define notification types. In this release, notification types are defined in a new object. The existing lookup was renamed to "Notification Type (Legacy)".

Upgrade note: For existing implementations, an upgrade script sets the owner to ‘CM’ on lookup values C1FI and C1MP. If your implementation is not using self-service integration and notification center, the two lookup values can be deleted.

Bill Segment Auto Cancel

A new algorithm C1-BSAXMINGR (Auto-Cancel Old Bill Segments Until Minimum Good Read) allows previous bill segments not meeting a minimum good read type to be canceled even when an excessive read situation is not encountered.

Customer Program Management Enhancements

The Customer Program Management module has been enhanced to cater for additional market segmentation capabilities and enabling third party program management interaction.

Third Party Representatives are typically external parties that are equipped or skilled to undertake a specific set of tasks or work (for example: perform a site visit, energy audit, equipment installation etc). The Customer Program Management module has been enhanced to:

•

capture third party representative information

•

assign leads to third party representatives

•

support notifying third party representatives of tasks or work to be carried out for a particular lead

•

support receiving and capturing updates on the progress of the tasks or work associated with a lead.

Additional information may also be captured such as miscellaneous notes on leads and lead events, the communication channel used to communicate with a customer, and the channel used by the customer when they respond to sign up for an initiative (or program).

DataConnect Extracts

The DataConnect Extracts capability allows critical information to be extracted from Oracle Utilities Customer Care and Billing. These extracts can be used to integrate Oracle Utilities Customer Care and Billing with other utility applications or provide data to third party vendors.

In Oracle Utilities Customer Care and Billing, there are two types of DataConnect extracts:

•

Master Data: Customer account related data from service agreements and account /person-related records; related service point and premise information; and related service point /meter history information.

•

Billing Data: Billing related information. Both historical and current information may be extracted.

Oracle Utilities Application Framework Enhancements

This section describes new and enhanced features in this release of Oracle Utilities Application Framework v4.2.0.3, including:

•

User Enhancement

•

Configuration Migration Assistant Enhancements

•

Status Reason Enhancements

•

External Message Enhancements

•

Sync Request Enhancements

•

Request Enhancements

•

Miscellaneous Enhancements

User Enhancement

Email Address Increased

In this release, the user's email address has been increased from 70 bytes to 254 bytes. Besides the user table, this change is reflected in Batch Submission and Batch Control.

Configuration Migration Assistant Enhancements

The following items describe enhancements to Configuration Migration Assistant (CMA) functionality.

Changes to the Import, Compare and Apply to Improve Performance

Known Issues : Refer to the Known Issues section for a description of bug 20504847 related to this functionality.

In previous releases, all steps related to importing a data set, including comparing the imported data to the target region's data and applying the data, were performed at the data set level. This meant that for a data set with a large amount of data, the processes could be very slow.

In this release, various changes were made to the import process to take advantage of multi-threading. The following are a summary of the changes made to the overall import process:

•

The steps to import the data and compare the imported data to the data in the target environment were previously done in a single step for the whole data set. In this release, the logic has been separated into several steps. The import of the data is still performed as a single step for each data set. This step creates migration transactions and migration objects based on the input file. For the compare step, the bulk of the logic is performed at the migration object level. This step may be performed multi-threaded. There are also two additional minor steps at the migration transaction and data set levels to update status values.

•

No changes have been made to the approval step. As with previous releases, the user may set default states for objects being added or changed (to Approved, Needs Review, or Rejected). A user must verify when the data set is ready to transition to the Apply step using a state transition.

•

The step to apply the data was previously a single step for the whole data set. In this release the logic has been separated into multiple steps to improve performance and to improve error handling. The apply steps take into account that fact that there may be dependencies between records. The steps can be summarized as follows:

•

First, a batch process at the migration object level tries to apply objects. All objects that do not have a dependency on any other object can be processed successfully at this step. This step is iterative to cater for simple dependencies between objects, where timing may result in an object with a dependency being processed prior to the object it is dependent on. It will keep trying to apply objects up to a maximum retry count. Objects that have circular references to each other will not successfully be processed in this step and will result in an error.

•

The next step is a batch process at the migration transaction level. If all objects are applied after the first step, the transaction step is merely a status update. But if any of the objects are in error after the first step, the transaction level process will try to apply objects grouped in the same transaction as a single step.

The lifecycle of the data set supports retrying the Apply at the object level or at the transaction level to allow for users to resolve errors in this step.

In addition, changes have been made to the cancellation process for an import data set and its related migration transactions and migration objects. In previous releases, a user could cancel a pending data set or an approved data set, but then undo the cancel. In this release, cancelling a data set is a final state and a user cannot undo this decision. This follows more closely the standard followed for other business objects in the product that support a canceled state.

To support the above changes, several changes have been made to the lifecycle of the base business object for migration data set import, migration transaction and migration object business objects.

•

Migration Data Set Import lifecycle changes (Business Object F1-MigrDataSetImport):

•

The Cancel Apply and Applied with Errors states have been removed.

•

All non-final states may go to the Canceled state. This state has been configured to support a Status Reason.

•

The status Ready to Compare has been changed from a transitory status to a non-transitory status. This status now has a deferred batch control defined. This state is now waiting for its migration transactions to be moved to a Ready to Apply state.

•

The Ready to Apply state is now called Apply Objects. This state waits for its related migration objects to move out of the Approved state.

•

The Applying state is now called Apply Transactions. This state waits for its related migration transactions to move out of the Ready to Apply state.

•

Two new transitory states have been added to support error retry functionality: Retry Objects and Retry Transactions.

•

Migration Transaction lifecycle changes (Business Object F1-MigrTransactionImport):

•

The Applying state has been removed.

•

The Canceled state has been added. All non-final states may transition to this state. A record will automatically transition to this state if the system detects that its data set is canceled.

•

The Pending state now has a deferred batch control. This is to support then new Compare step functionality. This state monitors that all related migration objects have processed their comparison step.

•

The Ready to Apply state now has a deferred batch control. Records in this state are picked up to perform the Apply step at the transaction level.

•

The Error Applying state now has a deferred batch control. Records in this state are picked up when a user has initiated a retry of the apply step at the transaction level.

•

Migration Object lifecycle changes (Business Object F1-MigrObjectImport):

•

The Pending state now has a deferred batch control. Records are picked up in this status and transition to a new Comparing state, which is transitory. Algorithms on the comparing state determine the appropriate next state for the migration object based on the comparison.

•

The Error Comparing state has been added. This is used to mark problems with imported objects that prevent further processing.

•

The Canceled state has been added. All non-final states may transition to this state. A record will automatically transition to this state if the system detects that its data set is canceled.

•

The Approved state now has a deferred batch control. Records in this state are picked up to perform the Apply step at the object level.

•

The Error Applying state now has a deferred batch control. Records in this state are picked up when a user has initiated a retry of the apply step at the object level.

In addition, several new batch controls have been introduced to support the various steps in the import, compare and apply steps at the various record levels. This includes a new Data Set Import monitor batch control that is separated from the Data Set Export monitor batch control.

More Information : Refer to the Summary tab of the business object page for the above business objects for a view of the lifecycles. In addition, the Configuration Migration Assistant chapter in the user documentation includes extensive detail about the various steps covering the import of a data set.

Upgrade Comment: The "Cancel Apply" and "Applied with Errors" states on the Migration Data Set Import lifecycle have being removed. It used to be possible to transition a data set into this status and then to "un-cancel" it and move it back to an apply-able status. Now, if a data set is moved into Canceled status, it will not be possible to undo this. If there are any data sets you think you might like to un-cancel, you should do that before installing this fix.

User Interface Enhancements

The following items describe enhancements to various user interface portals related to CMA.

Migration Data Set Export Query Portal Enhancements

In this release, the existing Migration Data Set Export Search option has been enhanced to allow a user to filter by the data set status.

Migration Data Set Import Query Portal Enhancements

In this release, the existing Migration Data Set Import Search option has been enhanced to allow a user to filter by the data set status.

In addition, a new search option, Migration Data Sets In Error, has been added. Using this search option, a user can find data sets that one or more migration objects in the Error Applying state or one or more transactions in the Error Applying state.

Migration Data Set Import Portal Enhancements

The maintenance portal for migration data set import has several changes to support the enhancements described above and to aid in error handling:

•

The main section now displays the number of migration objects in the data set that still need to be applied.

•

The main section includes an indication of the number of migration objects in the largest migration transaction.

•

The Migration Data Set Transactions zone now includes a column that indicates the number of unapplied migration objects for the transaction.

•

The Migration Data Set Impacted Object Summary zone now includes a new filter adjacent to the status drop down, allowing the user to indicate that all records in a final status should be ignored.

•

The portal includes a new zone Migration Objects in Error. This is only visible if there are objects in error. It lists all the errors, allowing a user to see if there are related issues, and allowing a user to review individual problems.

•

The portal includes a new zone Migration Transactions in Error. This is only visible if there are transactions in error.

Migration Transaction Portal Enhancements

The maintenance portal for migration transaction has been enhanced to display the number of related migration objects that are not yet processed.

Status Reason Enhancements

The following items describe enhancements to Status Reason functionality.

New Optional Usage Flag

In this release, an optional Usage flag has been added to BO Status Reason business object. This usage flag is configured as a pre-defined characteristic type that allows custom values to be defined. The usage flag allows an implementation to mark a given status reason for a given business object/status with a business usage. Only one status reason for a given BO/Status may be assigned a given usage.

This allows for an appropriate status reason to be chosen for a state transition that occurs via a system action. An algorithm can find the correct reason to use for the record's BO and status using the usage flag, providing the ability to reuse algorithms across business objects.

In addition, the system supplies a business service that retrieves the status reason for a given BO, Status, and usage value.

Note : This was fixed in 4.2.0.2.0 as a hot fix related to Bug 19697312.

External Message Enhancements

The following items describe enhancements related to exchanging messages with an external system.

WebSphere Support for Inbound Web Service

In this release, inbound web service functionality is now supported on WebSphere.

Note : This enhancement was added in 4.2.0.2.0 as a hot fix related to Bug 18072916.

External Message - Suppress Standard Time Adjustment

In previous releases, when no time zone information is received for a date/time element on an incoming message, it is assumed to be in "legal time" (example summer time) of the installation time zone. The system then converts the time to "standard time" for the installation time zone within the integration layer if the target date/time field is configured as storing date/times in "standard time".

In this release, a new notation was added to indicate to the system that no adjustments should be made to the time of an input date/time field to shift for "legal time" to "standard time". This allows the decision of whether to treat the incoming date/time as being in "legal time" or "standard time" to be deferred to the business logic (where the correct time zone associated with the incoming data may be known).

A new flag value ignoreStandardTime has been added to dateTimeTagFormat for date and time elements on incoming messages to indicate that no standard time adjustment should be done when mapping to business schema elements. It is advisable to only use this option when the requesting system will send a mixture of date/times in "legal time" and "standard time" and it is unable to provide the appropriate UTC offset to unambiguously identify them as such.

For example, imagine a request is submitted as follows and the target schema element indicates stdTime="true" (and we are currently in summer time):

<request dateTimeTagFormat="xsd:ignoreStandardTime">

<availableOnStd>2009-07-15T13:11:00</availableOnStd>

</request>

When converted to the target business object, it will be:

<availableOnStd>2009-07-15-14.13.00</availableOnStd>

If ignoreStandardTime is not set, the system would have adjusted the time by an hour to shift from "legal time" to "standard time" of the installation time zone.

It should be noted that this new functionality only applies to incoming date/times in the XSD:dateTime format; OUAF formatted date/times will continue to always be assumed as "legal time" of the installation time zone when no time zone indication has been provided.

Sync Request Enhancements

The following items describe enhancements to Sync Request functionality.

Correct Status Reason Configuration

In a previous release some of the configuration of status reason on the Sync Request and BI Sync Request business objects were incorrect and have been corrected.

•

F1-SyncRequest - Sync Request. This business object had introduced the state SYNC_WITH_ER and had marked it as optionally allowing a status reason. However, status reason is not supported by the business object. That setting has been removed.

•

F1-GenericBISyncRequest - Generic BI Sync Request. This business object supports status reason. However, no state was configured to mark status reason as optional or required. In this release, the state DISCARDED has been configured to allow status reason as Optional and CANCELED has been configured with status reason as Required.

Note : When upgrading, an implementation that uses the Generic BI Sync Request functionality and allows manual Cancellation must define appropriate status reason fields. Alternatively, if you wish to not require status reasons for cancelling records that reference this business object, update the configuration to change the setting of status reason from required to the desired option.

The base status reason F1NR - Synchronization Not Required - for BO F1-GenericBISyncRequest/Status DISCARDED had previously been released. However, it was not visible on the status reason page because the Discarded state on the Generic BI Sync Request BO had not been configured to indicate status reason is optional. In this release, the base status reason is now visible. Note that it has been changed to be "Not Selectable".

Assigning Discarded Reason Based on Usage

As mentioned in New Optional Usage Flag , the status reason BO has been updated to allow for the definition of a usage for a given reason. Specifically to support the BI Sync Request BO, the usage characteristic type includes the characteristic value of F1NC - "No Changes Detected".

The base status reason F1NR - Synchronization Not Required - for BO F1-GenericBISyncRequest/Status DISCARDED has been updated to define the usage of F1NC.

In addition, the following algorithms have been changed to determine the Status Reason for the current BO, the DISCARDED state and the usage of F1NC when transitioning the record to Discarded. This allows other Sync Request BOs that have the same lifecycle as F1-GenericBISyncRequest to reuse these algorithms, if applicable:

•

Compare Initial and Final Snapshot, with Status Reason ( F1-CMPSNAPSR)

•

Take Final Snapshot ( F1-FINALSNAP)

Request Enhancements

The following items describe enhancements to Request functionality.

New Characteristic Collection

The Request maintenance object is provided by the product to enable an implementation to design an ad-hoc batch process using the configuration tools.

In this release a characteristic collection has been added to the maintenance object.

Note : This enhancement was added in 4.2.0.2.0 as a hot fix related to Bug 19977490.

Miscellaneous Enhancements

New Business Service Converts XML to Delimited Format

In this release, a new business service has been provided that can receive an XML document along with the related schema that defines the XML document and return the data formatted using a supplied delimiter.

Note : This enhancement was added in 4.2.0.2.0 as a hot fix related to Bug 19971152.

Passing Context From Favorites

In version 2.2 of the framework, clicking a link in the Favorite Links zone in the dashboard populated context in the target transaction, even if the context was not configured in the navigation option that defines the link. In version 4.0.0 and higher, this behavior was changed to only populate context if defined in the navigation option (consistent with other navigation methods).

For implementations upgrading from version 2.2 to version 4.x, retaining the 2.2 behavior is desirable in the case where business processes expect this behavior. To support this, a new Feature Configuration option has been defined for the General System Configuration feature type: Pass Context in Favorites Zone (true/false). Setting this to true will retain the 2.2 behavior. Setting it to false (or not defining the option at all) will apply the 4.x behavior.

Upgrade Note : When upgrading, the system will attempt to detect if the implementation is upgrading from 2.2; if so, it will automatically insert a feature option to set this configuration to true.

Extract for DataRaker

In this release, the batch process that is used to create flat files for Business Intelligence-oriented extracts has been enhanced to support the following new parameters:

•

filePath . Indicates the file path where the flat files will be extracted. If the value is not populated, the file path from the General BI Master Configuration is used (as per previous releases). If this parameter is populated, the charEncoding parameter must also be supplied.

•

charEncoding . Defines the character encoding used for flat file extraction, for example UTF-8. If the value is not populated, the character encoding setting from the General BI Master Configuration is used (as per previous releases). If this parameter is populated, the filePath parameter must also be supplied.

•

includeRunDateTimeFlatFileName . This is a Boolean that accepts Y or N as values. Setting the value to "Y" indicates that the system date/time should be appended to the file name. A value of "N" (the default) does not add any information to the file name.

Note : this enhancement was added in 4.2.0.2.0 as a hot fix related to Bug 19976768.

Known Issues

There are no known issues in Oracle Utilities Customer Care and Billing version 2.4.0.3 at the time of release.

The following table lists known issues in Oracle Utilities Application Framework version 4.2.0.3 at the time of release.

Bug Number

Description

21235468

Unable to complete import in target environment (Error on F1-MGOAP). The import process for CMA (configuration migration import) is not working correctly and should not be used. [20504847]

21242058

Worklist - Navigation from Lead Events does not work.

Bug Fixes Not Included in This Release

This section lists bug fixes released for previous versions of the product that have not been included in this release. These fixes are planned for a future date for the current release using the bug numbers listed in the tables below:

Oracle Utilities Customer Care and Billing

2.4.0.2.0 Fix

Description

2.4.0.3.0 Fix

20981673

LL REV ALGORITHM COPIES ALL TENANT'S RATES INCLUDING NO LONGER EFFECTIVE

21227656

21024755

INCORRECT NAVIGATION OF PENDING FIELD ACTIVITY ON START/STOP PAGE

21227672

21039604

BATCH BILLING DOES NOT CREATE A BILL IF SERVICE AGREEMENT STARTS AT THE END OF THE MONTH

21227706

21157205

PAYMENT EVENT TRANSFER OVERRIDES MATCH VALUE WITH THE OLD MATCH VALUE.

21227712

Oracle Utilities Application Framework

Original version

Original Bug

Description

4.2.0.3.0 Hot Fix

4.2.0.1.0

18111283

Problem handling optional varchar prime key fields

20960645

4.2.0.1.0

18201137

Primary key 1 missing when displaying migration transaction objects

20925067

4.2.0.1.0

18387829

Home link does not navigate to the correct home page

20794181

4.2.0.1.0

19232235

Scroll bars always hide one menu item even when there is enough space

20925175

Deprecation Notices

This section describes items that are deprecated in this release or planned for deprecation in a future release, including:

•

Deprecated Functionality in This Release

•

Deprecation Notices for Application Framework 4.2.0.3

•

Metadata Planned for Deprecation

Deprecated Functionality in This Release

None.

Deprecation Notices for Application Framework 4.2.0.3

•

Embedded Help Portal. This portal was provided to help in defining inline or embedded help for UI maps. The tool is not widely used. It will be deprecated in a future release.

•

The table usage flag (TBL_USAGE_FLG) on MD Table (CI_MD_TBL) and the field usage flag (FLD_USAGE_FLG) on MD Table Field (CI_MD_TBL_FLD) will be deprecated in a future release. The fields are not used by the product.

•

ConfigLab and Archiving and Purging. In a future release the configuration lab and archiving and purging processes that are built using DB processes will be deprecated.

•

Environment Reference . This administrative maintenance object was related to ConfigLab and Archiving, which are no longer supported. In a future release, the following will be removed:

•

Migration Plan F1-EnvironmentRef. Note that no base migration request references this plan. Implementations should ensure that no custom migration request references this plan.

•

Business Object F1-EnvironmentRefPhysicalBO.

•

Maintenance Object ENV REF.

•

The To Do Type F1-SYNRQ (Sync Request Error) is not in use and will be deleted in a future release. Errors for the Sync Request Monitor (that also has the name F1-SYNRQ) are reported using the To Do Type F1-SYNTD (Sync Request Monitor Errors).

•

The service program EMAILSERVICE (Email Service) is invalid and will be deleted in a future release. The service program F1-EMAILSERVICE is the valid one provided for real-time email service functionality.

Metadata Planned for Deprecation

As part of an enhancement to Fieldwork PIP (Bug 18362634 - fieldwork PIP- MPL replacement), we moved some XSL files from CCB to SOA server.

Going forward, Fieldwork PIP is going to use XSLs located in the integration; Oracle Utilities Customer Care and Billing XSLs created for MPL processing will not be used.

This does not apply to XSL files used for Appointments flow in this integration and other XSLs defined on Outbound Message Type for other integrations.

These are the CCB transformation files to be deprecated in the next release:

•

C1FAIntExtOrderCreate.xsl

•

C1FAIntExtOrderUpdate.xsl

•

C1FAIntExtOrderCancel.xsl

•

C1FAIntExtOrderCreateUpdateCancel.xsl

•

C1FieldServiceIntFormatHelp.xsl

•

C1FieldWorkExtensionTemplate.xsl

•

SPLEAMPlantSelection.xsl

•

C1FieldServiceIntOrderCreate.xsl

•

C1FieldServiceIntOrderUpdate.xsl

•

C1FieldServiceIntOrderCancel.xsl

•

C1FieldWorkIntOrderCreateUpdateCancel.xsl

Supported Integrations

The following integrations are supported in this version of Oracle Utilities Customer Care and Billing (CCB):

Oracle Application Integrations

•

CCB 2.4.0.3 to E-Business Suite (Revenue Accounting) R12.1.1

•

CCB 2.4.0.3 to PeopleSoft (Financials) 9.0

•

CCB 2.4.0.3 to JD Edwards (Enterprise One) 9.1

Oracle Utilities Product Integrations

•

CCB 2.4.0.3 / Oracle Utilities Analytics 2.4.0

•

Oracle Integration Pack for Oracle Utilities Field Work 11.2, 12.1.0.1

•

CCB 2.4.0.3 to Oracle Utilities Meter Data Management 2.1.0.3

•

CCB 2.4.0.3 to Oracle Utilities Network Management System 1.12.0.2

•

CCB 2.4.0.3 to Oracle Utilities Service Order Management 2.1.0.3

Additional Integrations

•

Oracle Documaker 12.1 and 12.2

•

BI Publisher 11.1.1.7.0

•

Oracle Utilities Customer Self Service 2.1.0.2

•

CCB 2.4.0.3 to Siebel 8.1.1.9

Demo Data Information

The application delivers a demo database based on the application versions provided with the release, including Oracle Utilities Application Framework. Demo data provides sample configuration and data for key application features.

Demo data is included in the package and includes its own installation instructions. Please refer to the Installation Guide for more information or contact Oracle Support.