CCB MDM Implementation Guide

Oracle Utilities Customer Care and Billing
Integration to Oracle Utilities Meter Data

Management
Implementation Guide
Oracle Utilities Meter Data Management v1.6.1
Oracle Utilities Customer Care and Billing v2.3.1
E18343-01
August 2010
Customer Care and Billing Integration to Oracle Utilities Meter Data Management
Copyright 2010, 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 software or related documentation is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S.
Government customers are commercial computer software or commercial technical data pursuant to
the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the
use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license
terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the
Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software
License (December 2007). Oracle America, Inc., 500Oracle Parkway, Redwood City, CA 94065.
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 which 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.
This software or hardware and documentation may provide access to or information on 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. Oracle
Corporation and its affiliates will not be responsible for any lost, costs, or damages incurred due to your
access to or use of third party content, products or services.
ii
Table of Contents
Chapter 1: Participating Applications Overview ........................................................................................ 5
Oracle Utilities Customer Care and Billing............................................................................................. 5
Oracle Utilities Meter Data Management ............................................................................................... 5
Terms ..................................................................................................................................................... 5
Prerequisites .......................................................................................................................................... 6
Chapter 2: Understanding the Integration ................................................................................................. 7
Business Process Overview .................................................................................................................. 7
Understanding the Integration Processes.............................................................................................. 9
Chapter 3: Configuration Guidelines ....................................................................................................... 22
Data Synchronization ........................................................................................................................... 22
Setting up Oracle Utilities Customer Care and Billing ......................................................................... 23
Setting Up Oracle Utilities Meter Data Management ........................................................................... 42
Setting up the Process Integration....................................................................................................... 45
Chapter 4: Monitoring, Error Handling and Troubleshooting................................................................... 63
Monitoring from Oracle Utilities Customer Care and Billing ................................................................ 63
Monitoring from Oracle Utilities Oracle Utilities Meter Data Management .......................................... 64
Monitoring from the Integration ............................................................................................................ 65
Chapter 5: Extensibility Options .............................................................................................................. 67
Pre Transformation Extension Point .................................................................................................... 67
Post Transformation Extension Point .................................................................................................. 67
Custom Transformations...................................................................................................................... 67
Appendix A: Data Mapping ...................................................................................................................... 71
SA Information Synchronization .......................................................................................................... 71
SP Information Synchronization .......................................................................................................... 75
Batch Bill Determinants Mapping ......................................................................................................... 78
Online Bill Determinants Mapping ....................................................................................................... 81
Replacement Reads Mapping ............................................................................................................. 85
Appendix B: Cross References ............................................................................................................... 87
iii
Chapter 1: Participating Applications

Overview
The Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data
Management integrates the following products:
Oracle Utilities Customer Care and Billing (CC&B)
Oracle Utilities Meter Data Management (MDM)
This chapter provides a general description of each of these applications.

Oracle Utilities Customer Care and Billing (CC&B) helps customers manage all aspects of the
utility customer lifecycle including service connection, complex billing, payment processing and
debt collection.
Oracle Utilities Meter Data Management

Oracle Utilities Meter Data Management (MDM) supports the loading, validation, editing, and
estimation (VEE) of meter data - from meter configuration, to meter read and usage validation, to
bill determinant calculations.
Terms
The following terms and acronyms are used throughout this guide.
Integration Terms
DVM
Domain Value Map
JMS
Java Message Service (JMS)
SOA
Service-Oriented Architecture Software modules that are provided as services can be integrated or used by
several applications using SOA, even if their respective architectures are substantially different. Rather than
defining an API, SOA defines the interface in terms of protocols and functionality.
JMS Queue
A staging area that contains messages those have been sent and are waiting to be read. The JMS Queues are
available on the Weblogic Application Server
Application Names
CC&B
MDM
Oracle Utilities Meter Data Management
Other General terms to be aware of include:

Edge applications
The applications that are involved in the integration - CC&B and MDM.
Participating
Application
One of the three applications involved in the 3-way integration - CC&B or MDM.
SOAP
Simple Object Access Protocol is a protocol specification for exchanging structured information in the
implementation of Web Services in computer networks.
SA
CC&B Service Agreement
SP
CC&B Service Point
XML
Extensible Markup Language
XSD
XML schema definition file.
UOM
Unit of measure
TOU
Time of use
SQI
Service Quantity Identifier
BDI
Billing Determinant Identifier
BD
Billing Determinants
VEE
Validation, Estimation and Editing
References
For more information on some of the terms and entities related to the integration, see Appendix
B: Cross References.
Prerequisites
All participating applications: Oracle Utilities Customer Care and Billing, Oracle Utilities Meter
Data Management and Oracle SOA Suite must be installed, set up and working properly.
Chapter 2: Understanding the Integration

This chapter provides an overview of the integration and outlines the applicable business
processes and integration points in the following sections:
Business Process Overview
Terms
Prerequisites
Understanding the Integration Processes
Business Process Overview

In this integration, Oracle Utilities Customer Care and Billing manages customers (persons),
accounts/service agreements (SAs) and service points (SPs) while Oracle Utilities Meter Data
Management serves as the database of record for meters and usage.
Oracle Utilities Customer Care and Billing requests bill determinant calculations from Oracle
Utilities Meter Data Management in order to generate bills for the customer. Replacement read
notifications are sent by Oracle Utilities Meter Data Management whenever corrections are made
to read information. This could prompt a cancel-rebill scenario in Oracle Utilities Customer Care
and Billing that would result in new request(s) for bill determinants.
During the billing cycle, Oracle Utilities Customer Care and Billing requests usage data from
Oracle Utilities Meter Data Management for all service agreements which are part of the billing.
The relationship between SPs and meters is maintained in Oracle Utilities Meter Data
Management. Minimal SA/SP data from Oracle Utilities Customer Care and Billing is
synchronized to Oracle Utilities Meter Data Management for VEE and Oracle Utilities Meter Data
Management operations.
The integration includes CC&B-MDM portal to access Oracle Utilities Meter Data Management
related data, such as meter configuration and usage, online.
The business processes are as follows:
SP synchronization
SA synchronization
Batch billing determinants request and response
Online billing determinants request and response
Replacement reads request and response
Except for replacement reads notification, all other flows are Oracle Utilities Customer Care and
Billing initiated.
The following diagram provides a visual representation of this processing:
CCB
Service Point
Information
Service Agreement
Information
Batch Bill
Determinants
Request
Online Bill
Determinants
Request
Off Cycle Bill

Generator
MDM
CCB Request
MDM Response
Service Point
Information
CCB Request
MDM Response
Account Information
CCB Request
MDM Response
CCB Request
MDM Response
MDM Request
CCB Response
Replacement Reads
Notification
CCB MDM - Integration Points

1. CC&B sends service point (SP) and service agreement (SA) data to MDM.
2. MDM calculates the billing determinants for each account.
3. CC&B then sends online or batch billing determinants requests to MDM.
4. MDM responds by sending back the billing determinants.
5. If there is any change to the billing determinants in MDM for a meter for which billing
determinants have already been sent to CC&B, then MDM sends a replacement read
notification to CC&B. CC&B then creates an off cycle bill generation to inform the user.
Understanding the Integration Processes

This section outlines the overall Technical overview, business process and specific integration
points handled by this integration.
Technical Overview
This is a direct integration between Oracle Utilities Customer Care and Billing and
Oracle Utilities Meter Data Management.
All the end to end integration flows are a-synchronous.
The integration receives messages from JMS Queues and sends messages to JMS
Queues. Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data
Management have the ability to read messages from JMS Queues and write
processed messages to JMS Queues.
Weblogic JMS is used as a queuing mechanism in the integration layer. For each
integration flow there are 8 JMS Queues:
Queue
Description
1.
Source application request queue
Source application adds messages to this queue which is then

picked up by the integration layer for transformation.
2.
Source application response

queue
Business errors in the integration and success or failure

acknowledgements from the target application are transformed by
the integration and written to this queue.
3.
Source application request error

queue
Technical errors in the integration request flow are written to this

queue.
4.
Source application response

error queue
Technical errors when the source application reads the messages

from the source response queue are written to this queue.
5.
Target application request queue
Integration reads messages from source application request

queue, transforms them and writes them to this queue.
6.
Target application response

queue
Success or failure acknowledgements from the target application

are written to this queue and are read by the integration.
7.
Target application request error

queue
Technical errors written when the target application tries to read

the message from the target request queue are written to this
queue.
8.
Target application response error

queue
Technical errors in the integration response flow are written to this

queue.
Two BPEL processes manage each integration flow: one for the request processing
and one for the response processing.
The Request BPEL process includes the following:

o
JMS Consumer to read from source request queue
JMS Producer to write to the target request queue
10
Transformations to convert messages from source format to target format.

DVMs are used for the transformation.
Error handling and error notification
The Response BPEL process includes the following

o
JMS Producer to read from the target response queue
JMS Producer to write to the source response queue
Acknowledgement transformations to convert messages from the target

format to the source format. DVMs are used for the transformation.
Error handling and error notification
The JMS consumer and BPEL process is configured to participate in a global

transaction so that BPEL process can issue rollback and commits on the queue.
The BPEL process issues rollbacks on the queue in the scenario where it is not able
to reach the target queue and the message is moved to the corresponding error
queue.
All technical errors in the integration layer are moved to the error queue of the
queue from which the message has been consumed.
The following diagram provides a graphical representation of this processing:

Weblogic Application Server
SOA Suite
Request BPEL Process
Source
Request
Queue
Source
Request XSD
Source
Request XSD
JMS Adapter
Consumer
Request
Transformation
Error ?
Yes
Custom Request
Transformation
Source
Request
Error Queue
Target
Request XSD
Target
Request
Queue
JMS Adapter
Producer
No
Error
Notification
Target
Request
Error Queue
Target
Request XSD
Business or
Technical Error?
Technical Error
Domain Value
Maps
Business Error
Error
Transformation
Error
Transformation
Source
Response XSD
Business
Error
Business or
Technical Error?
Response BPEL Process

Request BPEL Process
Target
Response XSD
Target
Responset XSD
Response
Transformation
JMS Adapter
Consumer
Yes
Error
Notification
Source
Response
Queue
JMS Adapter
Producer
Source
Response
Error Queue
No
Error ?
Target
Response
Queue
Target
Response
Error Queue
Technical Error
Source
Response XSD
Custom
Response
Transformation
Source
Response XSD
Domain Value
Maps
CCB MDM Integration - Technical Flow Diagram
11
Integration Points
The following Integration points are available in Oracle Utilities Customer Care and Billing
Integration to Oracle Utilities Meter Data.
SP Information Sync Integration Flow

Business Details
SP Sync synchronizes minimal SP and Premise details required by Oracle Utilities Meter Data
Management from Oracle Utilities Customer Care and Billing.
The following process diagram shows a graphical representation of this processing:
Business Flow Diagram

For more information refer to the business flow diagram titled 050601 Maintain Customer
Information (Reusable Subprocess).pdf included with the documentation package.
Technical Details
Oracle Utilities Customer Care and Billing sends the SP information in form of xml messages.
These messages are transformed by the integration layer then sent to Oracle Utilities Meter Data
Management SP Sync is triggered before SA Sync so that SPs required by the SAs are in Oracle
Utilities Meter Data Management before SA sync is carried out. Oracle Utilities Meter Data
12
Management sends an acknowledgement to the integration so that it can be transformed and

sent to Oracle Utilities Customer Care and Billing.
The integration artifacts for SP Sync are as follows:
Composites
Composite Name
Description
OUCCBOUMDMSPSyncReqEBF
SP Sync Request BPEL Process
OUMDMOUCCBSPSyncRespEBF
SP Sync Response BPEL Process
JMS Queues
Queue Name
OUCCBSPSyncRequest
Description
CCB SP Sync Request
Used by the integration layer to read incoming SP Sync messages from CCB.
OUCCBSPSyncRequestError
CCB SP Sync Request Error

Error Queue for CCB SP Sync Request
OUCCBSPSyncResponse
CCB SP Sync Response

Used by the integration layer to add transformed SP Sync response messages
from MDM. Also any integration business errors are sent to this queue.
OUCCBSPSyncResponseError
CCB SP Sync Response Error

Error Queue for CCB SP Sync Response
OUMDMSPSyncRequest
MDM SP Sync Request

Used by the integration layer to add transformed SP Sync request messages.
OUMDMSPSyncRequestError
MDM SP Sync Request Error

Error Queue for MDM SP Sync Request Error
OUMDMSPSyncResponse
MDM SP Sync Response

Used by the integration layer to read incoming SP Sync response messages from
MDM.
OUMDMSPSyncResponseError
MDM SP Sync Response Error

Error Queue for MDM SP Sync Response Error
13
SA Information Sync Integration Flow

Business Details
SA Sync synchronizes minimal SA, Account, SA-SP relationship and Person details required by
Oracle Utilities Meter Data Management from Oracle Utilities Customer Care and Billing.

For more information refer to the business flow diagram: 050601 Maintain Customer Information
(Reusable Subprocess).pdf included with the documentation package.
Technical Details
Oracle Utilities Customer Care and Billing sends the SA information in the form of xml messages
which are transformed by the integration layer and sent to Oracle Utilities Meter Data
Management. Oracle Utilities Meter Data Management sends an acknowledgement which is
transformed in the integration layer and sent to Oracle Utilities Customer Care and Billing.
The integration artifacts for SA Sync are as follows:
14
Composites
Composite Name
Description
OUCCBOUMDMSASyncReqEBF
SA Sync Request BPEL Process
OUMDMOUCCBSASyncRespEBF
SA Sync Response BPEL Process
JMS Queues
Queue Name
OUCCBSASyncRequest
Description
CCB SA Sync Request
Used by the integration layer to read incoming SA Sync messages from CCB.
OUCCBSASyncRequestError
CCB SA Sync Request Error

Error Queue for CCB SA Sync Request
OUCCBSASyncResponse
CCB SA Sync Response

Used by the integration layer to add transformed SA Sync response messages
OUCCBSASyncResponseError
CCB SA Sync Response Error

Error Queue for CCB SA Sync Response
OUMDMSASyncRequest
MDM SA Sync Request

Used by the integration layer to add transformed SA Sync request messages.
OUMDMSASyncRequestError
MDM SA Sync Request Error

Error Queue for MDM SA Sync Request Error
OUMDMSASyncResponse
MDM SA Sync Response

Used by the integration layer to read incoming SA Sync response messages from
MDM.
OUMDMSASyncResponseError
MDM SA Sync Response Error

Error Queue for MDM SA Sync Response Error
15
Batch Bill Determinants Integration Flow

Business Details
Batch bill determinant requests sent from Oracle Utilities Customer Care and Billing contain the
bill segment period, as well as all applicable rate version break periods. Oracle Utilities Meter
Data Management calculates bill determinants based on the consumption and the rates setup.
These Bill determinants are returned to Oracle Utilities Customer Care and Billing and used for
billing. Billing Determinants do not replace billing. Instead they calculate the determinants and
provide usage information needed to calculate and generate a bill.

For more information, refer to the business flow diagram: 100106 Provide Consumption Data to
Billing.pdf included with the documentation package.
Technical Details
The batch billing process in Oracle Utilities Customer Care and Billing is running, requesting bill
determinant calculations from Oracle Utilities Meter Data Management for multiple accounts.
Oracle Utilities Customer Care and Billing initiates the Batch Bill request and Oracle Utilities
Meter Data Management returns Bill determinants to Oracle Utilities Customer Care and Billing
per account.
The integration artifacts for Batch Bill Determinants Integration Flow are as follows:
16
Composites
Composite Name
Description
OUCCBOUMDMBatchBDReqEBF
Batch BD Request BPEL Process
OUMDMOUCCBBatchBDRespEBF
Batch BD Response BPEL Process
JMS Queues
Queue Name
OUCCBBatchBDRequest
Description
CCB Batch BD Request
Used by the integration layer to read incoming Batch BD messages from CCB.
OUCCBBatchBDRequestError
CCB Batch BD Request Error

Error Queue for CCB Batch BD Request
OUCCBBatchBDResponse
CCB Batch BD Response

Used by the integration layer to add transformed Batch BD response messages
OUCCBBatchBDResponseError
CCB Batch BD Response Error

Error Queue for CCB Batch BD Response
OUMDMBatchBDRequest
MDM Batch BD Request

Used by the integration layer to add transformed Batch BD request messages.
OUMDMBatchBDRequestError
MDM Batch BD Request Error

Error Queue for MDM Batch BD Request Error
OUMDMBatchBDResponse
MDM Batch BD Response

Used by the integration layer to read incoming Batch BD response messages from
MDM.
OUMDMBatchBDResponseError
MDM Batch BD Response Error

Error Queue for MDM Batch BD Response Error
17
Online Bill Determinants Integration Flow

Business Details
Online bill determinant requests sent from Oracle Utilities Customer Care and Billing contain the
bill segment period, as well as all applicable rate version break periods. Oracle Utilities Meter
Data Management calculates bill determinants based on the consumption and the rates setup.
These bill determinants are returned to Oracle Utilities Customer Care and Billing and used for
billing. Billing determinants do not replace billing. Instead they calculate the determinants and
provide usage information needed to calculate and generate a bill.

For more information, refer to the business flow diagram: 100106 Provide Consumption Data to
Billing.pdf included with the documentation package.
Technical Details
If a user is requesting an ad-hoc bill determinant calculation in Oracle Utilities Customer Care and
Billing for a specific account Oracle Utilities Customer Care and Billing initiates the Online Bill
request for a specific account and Oracle Utilities Meter Data Management returns Bill
determinants for the account. Oracle Utilities Meter Data Management sends out success or
failure acknowledgement to the integration layer so that it can be transformed and sent to Oracle
Utilities Customer Care and Billing.
The integration artifacts for Online Bill Determinants Integration Flow are as follows:
18
Composites
Composite Name
Description
OUCCBOUMDMOnlineBDReqEBF
Online BD Request BPEL Process
OUMDMOUCCBOnlineBDRespEBF
Online BD Response BPEL Process
JMS Queues
Queue Name
OUCCBOnlineBDRequest
Description
CCB Online BD Request
Used by the integration layer to read incoming Online BD messages from CCB.
OUCCBOnlineBDRequestError
CCB Online BD Request Error

Error Queue for CCB Online BD Request
OUCCBOnlineBDResponse
CCB Online BD Response

Used by the integration layer to add transformed Online BD response messages
OUCCBOnlineBDResponseError
CCB Online BD Response Error

Error Queue for CCB Online BD Response
OUMDMOnlineBDRequest
MDM Online BD Request

Used by the integration layer to add transformed Online BD request messages.
OUMDMOnlineBDRequestError
MDM Online BD Request Error

Error Queue for MDM Online BD Request Error
OUMDMOnlineBDResponse
MDM Online BD Response

Used by the integration layer to read incoming Online BD response messages
from MDM.
OUMDMOnlineBDResponseError
MDM Online BD Response Error

Error Queue for MDM Online BD Response Error
19
Replacement Reads Integration Flow

Business Details
As meter reads are received in Oracle Utilities Meter Data Management from the field, they must
be interrogated to determine if they are replacement reads for existing reads marked as used
during billing. If so, and this meter has been configured to allow replacement reads, a request to
Oracle Utilities Customer Care and Billing is generated to indicate that the replacement usage
was received. Oracle Utilities Customer Care and Billing creates an Offcycle Bill Generator object
and either an automatic rebill or manual rebill can be configured in Oracle Utilities Customer Care
and Billing.

For more information on the replacement reads flow refer to the business flow diagram in 100106
Provide Consumption Data to Billing.pdf included with the documentation package.
Technical Details
Replacement meter reads are created in Oracle Utilities Meter Data Management and notification
is sent to Oracle Utilities Customer Care and Billing. Oracle Utilities Customer Care and Billing
creates off cycle bill generator based on the Oracle Utilities Meter Data Management request.
Oracle Utilities Customer Care and Billing sends only failure acknowledgements to Oracle Utilities
Meter Data Management.
The integration artifacts for SP Sync are as follows:
20
Composites
Composite Name
Description
OUMDMOUCCBReplReadReqEBF
Replacement Read Request BPEL Process
OUCCBOUMWMReplReadRespEBF
Replacement Read Response BPEL Process
JMS Queues
Queue Name
Description
OUMDMReplReadRequest
CCB Replacement Read Request - Used by the integration layer to read incoming
Replacement Read messages from MDM.
OUMDMReplReadRequestError
MDM Replacement Read Request Error - Error Queue for MDM Replacement Read
Request
OUMDMReplReadResponse
MDM Replacement Read Response - Used by the integration layer to add transformed
Replacement Read response messages from MDM. Also any integration business errors
are sent to this queue.
OUMDMReplReadResponseError
MDM Replacement Read Response Error - Error Queue for MDM Replacement Read
Response
OUCCBReplReadRequest
CCB Replacement Read Request - Used by the integration layer to add transformed
Replacement Read request messages.
OUCCBReplReadRequestError
CCB Replacement Read Request Error - Error Queue for CCB Replacement Read
Request Error
OUCCBReplReadResponse
CCB Replacement Read Response - Used by the integration layer to read incoming
Replacement Read response messages from CCB.
OUCCBReplReadResponseError
CCB Replacement Read Response Error - Error Queue for CCB Replacement Read
Response Error
21
Chapter 3: Configuration Guidelines

This chapter provides detail into the required configuration settings for the integration, and
discusses details related to:
Data Synchronization
Setting up Oracle Utilities Customer Care and Billing.
Setting up Oracle Utilities Meter Data Management
Setting up the integration layer
Data Synchronization
Oracle Utilities Meter Data Management serves as the database of record for meters and usage
while Oracle Utilities Customer Care and Billing manages customers (persons), accounts (service
agreements) and service points. The SA and SP Sync integration point adds relevant SP/SA
data from Oracle Utilities Customer Care and Billing in Oracle Utilities Meter Data Management.
The data synchronization for the following is not completed by the integration product.
a. Meter to SP Association
b. Rates Setup in Oracle Utilities Meter Data Management and Oracle Utilities Customer
Care and Billing
Meter to Service Point Association

The service point to meter relationship is not covered by the synchronization process. Only
service point information is passed from Oracle Utilities Customer Care and Billing to Oracle
Utilities Meter Data Management.
Please refer to Oracle Utilities Meter Data Management Product Documentation for configuration
options available to associate meter information with service points.
Rates Setup in Oracle Utilities Meter Data Management and

Rate setup information is not covered by the synchronization process.
Please refer to Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data
Management product documentation for configuring rates.
22
Setting up Oracle Utilities Customer Care and

Billing
Setting up Oracle Utilities Meter Data Management for the integration requires configuration of
the following:
Admin Tables
Batch Code
BO Algorithms
MO Algorithms
Maintenance Objects
Business Objects
For more information on configuring and working with Oracle Utilities Customer Care and
Billing, see the Oracle Utilities Customer Care and Billing standard documentation.
The following sections provide details into how to configure these items.
Some configurations described may be required for general functionality and do not necessarily
relate directly to the integration; however these are called out as particularly significant
configuration items. The inclusion of such items does not mean that other general items that are
not mentioned do not need to be configured.
Configure Admin Tables

This section describes unique setup issues specifically related to configuring your system for the
integration.
For more information about configuring Oracle Utilities Customer Care and Billing, see the
Oracle Utilities Customer Care and Billing User Guide
Country
Create a country code in Oracle Utilities Customer Care and Billing.
The Main page is used to customize the fields and field descriptions that are displayed where
addresses are used in the system. This ensures that the all addresses conform to the customary
address format and conventions of the particular country you have defined.
Navigation
Admin Menu > Country
Guideline
Create the required country entities
Corresponding DVM
OUCCB_OUMDM_Country
23
CIS Division
A CIS division is associated with a jurisdiction. The definition of a jurisdiction is a geographicoriented entity with unique business rules. For example, if you conduct business in California and
Nevada, and each state has different collection rules, you need a separate jurisdiction for each
state. Set up a CIS division for each jurisdiction in which you conduct business.
The codes defined here must exactly match values in the DVM indicated.
Navigation
Admin Menu > CIS Division
Guideline
Corresponding DVM
Create the divisions required by your business and populate the

necessary information if these records are not created yet.
OUCCB_OUMDM_CISDivision
SA Type
Create the required SA Types. The codes defined here must exactly match values in the DVM
indicated.
Navigation
Admin Menu > SA Type
Guideline
Create SA Types
Corresponding DVM
OUCCB_OUMDM_SAType
SA Status
Create SA Statuses to be sent to Oracle Utilities Meter Data Management. The codes defined
here must exactly match values in the DVM indicated.
Navigation
Admin Menu > Look Up
Guideline
Corresponding DVM
Add SA Status values to the lookup field SA_STATUS_FLG
OUCCB_OUMDM_SAStatus
SIC Code
A service agreement for non-residential service should reference a standard industry code (SIC).
This code is used to categorize service agreements for reporting purposes. The codes defined
Navigation
Admin Menu > SIC Code
Guideline
Corresponding DVM
Add applicable values
OUCCB_OUMDM_SIC
Rate Schedule
Start the rate definition process then enter general information about the rate. The codes defined
Navigation
Main Menu > Rates > Rate Schedule
24
Guideline
Add applicable values
Corresponding DVM
OUCCB_OUMDM_RateInfo
Unit of Measure
Define the Unit of Measure codes. The codes defined here must exactly match values in the DVM
indicated.
Navigation
Guideline
Admin Menu > Unit of Measure
Define unit of measurement codes.
Corresponding DVM
OUMDM_OUCCB_UOM
Time of Use
Define the Time of Use codes. The codes defined here must exactly match values in the DVM
indicated.
Navigation
Admin Menu > Time of Use
Guideline
Define time of use codes
Corresponding
DVM
OUMDM_OUCCB_TOU
Service Quantity Identifier

Define the SQI codes. The codes defined here must exactly match values in the DVM indicated.
Navigation
Guideline
Admin Menu > Service Quantity Identifier
Define service quantity identifiers
Corresponding DVM
OUMDM_OUCCB_BDI
Usage Type Code

Define the Usage Type codes. The codes defined here must exactly match values in the DVM
indicated.
Navigation
Admin Menu > Look Up
Guideline
Corresponding DVM
Define Usage Type codes by adding values to the

C1_USAGE_TYPE_FLG field.
OUMDM_OUCCB_UsageType
Batch Code
This is the batch process to run the sync request. It is a generic batch process that is used for
different sync processes. It has a couple of parameters that can be used to control which sync
request BOs to process.
Batch Code
F1-SYNRQ
Description
Sync Request Monitor Process. This is the batch process to run the sync request. It is a generic
batch process that is used for different sync processes. It has a couple of parameters that can be
used to control which sync request BOs to process.
25
Batch Parameters
Parameter Description
maintenanceObject
Sync Request maintenance object.
Value
F1-SYNC REQ
(This is the defaulted value.)
isRestrictedByBatchCode
The value of true restricts processing to

sync requests whose current state is linked
to this batch code.
restrictToBusinessObject
Enter a business object code here to limit

the process to sync requests linked to this
business object.
C1-NMSSPSyncRequest
Enter a status code here to limit the

process to sync requests in this state.
PENDING
restrictToBOStatus
Batch Code
(To run only the NMS customer sync

request, populate this value)_
(To only process sync request, in Pending

status, populate this value)_
Description
C1-MDMIL
Sync Request Initial Load for MDM - This process starts a corresponding sync request BO for each SA and SP
in the system to setup initial data in MDM. Once this is done, only the next job needs to run on a regular basis.
C1-USGDF
Usage Scheduled Monitor Process (Deferred) - This batch process invokes monitoring rules associated with
the current state of usage records. This batch needs to be executed twice for the Business Object C1UsageRequestCyclicalBilling, once for Pending state and then for Billing Determinants Received state
BILLING
Create bills using bill cycle - The bill cycle process creates bills for accounts with an "open" bill cycle.
BO Algorithms
Algorithm Type
C1-CAPMDMSAI and
C1-CAPMDMSPI
26
Description
Configure the pre-processing algorithms that create the initial snapshot. For the SA Sync, use
algorithm type C1-CAPMDMSAI. For the SP Sync, use C1-CAPMDMSPI. See the algorithm
descriptions for details on how to specify the parameters below.
1.
Define the read BOs each of the algorithms use to build the initial/final snapshot. For the
SA Sync, the base product provides C1-MDMPerson, C1-MDMAccount, C1-MDMSA for
this purpose. For the SP Sync, use C1-MDMPremise and C1-MDMSP. If additional
elements are needed in the sync request, your implementation may create a child of any of
these BOs and add the element under a group called <customElements>. This ensures
that they are included in the sync request message at the proper group nodes so that any
custom translation your implementation may decide to do at the integration layer can be
done.
2.
Define the data area that holds the elements needed in the snapshot. For the SA Sync,
the base product provides C1-MDM1SABasedSnapshot; the SP Sync uses C1MDM1SPBasedSnapshot. Your implementation should not have to create a custom data
area as this already provides <customElements> nodes throughout its schema to allow for
the addition of any elements not included in the base solution.
3.
It is possible to filter qualifying SA Types or SP types for each of the syncs. If this is so,
define these values in the algorithm so that only changes to these SA or SP types are
communicated across to MDM.
4.
It is possible to specify custom read BOs by SA or SP Type. To do so, simply define your
custom BO along with the SA or SP Type you wish to use it with. The algorithm uses this
value instead of those defined in 1.
Algorithm Type
Description
C1-MDM-TMOT
This monitor algorithm sets a timeout limit on the receipt of a response from the external system.
Define the number of hours your implementation wishes to wait for a response from MDM before
transitioning the sync request into the Error state.
F1-TD-CREATE
This enter algorithm creates a To Do entry. At a minimum, your implementation must define the To
Do Type to use in creating the To Do entry and the Characteristic Type For Log Entry to be used in
linking the to do entry to the sync request via its logs. The base product provides F1-SYNRQ and F1TODO, respectively, for this purpose. For details on the other parameters used by this algorithm, see
the algorithm type description.
MO Algorithms
Configure the MO Audit algorithms. MO Audit algorithms contain the logic to instantiate a sync
request (as long as one does not already exist in the initial state for the MO-Primary Keys
combination). A generic algorithm F1-GCHG-CDCP comes with the base product and is plugged
in on MOs that need to instantiate sync requests for the same MO. This algorithm instantiates
the BOs defined in the Sync Request BO MO Option (see Maintenance Objects below). For MOs
that need a sync request instantiated for a different MO unique algorithms that contain this logic
are used. (For example, changes to the Person or Account MO need to be communicated via an
SA sync request; or changes to the Premise MO need to be communicated via an SP sync)
Algorithm Type
Description
C1-PERCDCSA
This algorithm instantiates an SA-based sync request whenever a change to the

Person MO is detected. Define the sync request BO to be instantiated in the
algorithms parameters.
C1-ACCTCDCSA
This algorithm instantiates an SA-based sync request whenever a change to the

Account MO is detected. Define the sync request BO to be instantiated in the
C1-PREMCDCSP
This algorithm instantiates an SP-based sync request whenever a change to the

Premise MO is detected. Define the sync request BO to be instantiated in the
Maintenance Object
Maintenance Object
Description
PERSON
Specify the MO Audit algorithm configured in the previous section.
ACCOUNT
SA
Specify the generic MO Audit algorithm F1-GCHG-CDCP. Also specify the C1MDMSASyncRequest BO in the Sync Request BO MO Option.
SP
Specify the generic MO Audit algorithm F1-GCHG-CDCP. Also specify the C1MDMSPSyncRequest BO in the Sync Request BO MO Option.
PREMISE
27
Business Object
Business Object
C1-MDMSASyncRequest and C1MDMSPSyncRequest
Description
These business objects define the behavior of the outbound sync requests for MDM.
It contains the schema elements monitored and synchronized to MDM.
The following BO Options must be configured to create the outbound sync request:
- Outbound Message Type: This contains a reference to the outbound message BO
to use. The base package includes BO C1-NMSSPSyncReqOutMsg for the NMS SP
Sync. Refer to Defining Outbound Message Types in the user documentation for
more information.
External System: This contains the reference to the outbound message type and its
corresponding configuration for communicating with the external system. The base
package includes the message XSL C1-CCBJMSQAddNamespace.xsl. Please refer
to user documentation referencing External Systems for more information.
Specify the pre-processing algorithm configured in the previous section.
Specify the time out algorithm as a monitor algorithm on the Awaiting
Acknowledgement state for this BO.
Specify the To Do creation algorithm on the Error state for this BO.
Depending on the technology used to communicate the sync request to the external
system, you may need to create your own enter algorithm and plug it into the Send
Request state. The base package comes with an algorithm that creates a message
and drops it into a JMS Queue. If your implementation uses this algorithm (C1-CROUTMSG), you must define the BO Options for External System and Outbound
Message Type.
28
Business Object
C1-UsageRequest
Description
This business object defines the behavior of a usage request.
To configure your system for usage requests using this business object:
- Create a bill segment type for service agreements that require bill determinants. This
bill segment type should reference the following base product algorithms:
- Create Algorithm: Create bill segment using a usage request
- Get Consumption Algorithm: Get bill segment consumption using a usage request
- Set up SA types for service agreements that require bill determinants. These SA
types SA types should have a special role flag of Bill Determinants Required and
should reference the bill segment type above
- A cancellation reason is required when a usage request is cancelled. Your
implementation must define valid cancel reasons. Navigate to the lookup page and
define valid values for the lookup field C1_USG_CANCEL_RSN_FLG
- Create a 'Check for Response Timeout' algorithm (see above) and specify your
timeout criteria. Update the Awaiting Bill Determinants state on the usage request BO
to reference the timeout algorithm
In addition to the standard BO options, the following BO options are relevant to usage
request business objects:
- External System: An external system is required to communicate usage requests to
the external system
- Outbound Message Type: An outbound message type is required for the usage
request outbound message
C1-UsageRequestNonCyclical
This business object defines the behavior of a usage request created from noncyclical or online bill generation.
the external system
- Outbound Message Type: An outbound message type is required for the noncyclical billing usage request outbound message. This outbound message type must
reference the base MDM Non-Cyclical Billing Usage Request Outbound Message
C1-UsageRequestCyclicalBilling
This business object defines the behavior of a usage request created from the cyclical
or batch billing process.
the external system
- Outbound Message Type: An outbound message type is required for the cyclical
billing usage request outbound message. This outbound message type must
reference the base MDM Cyclical Billing Usage Request Outbound Message business
object.
29
For more information about the sync request process, the business objects, maintenance
objects and other components use for this process, see the Oracle Utilities Framework User
Guide section titled Data Synchronization.
JMS Configuration
This section describes the JMS configuration to be done in the Oracle Utilities Customer Care
and Billing weblogic server and in the Oracle Utilities Customer Care and Billing deployment xml
files. The configuration in this section is used for receiving JMS messages from the integration
layer.
Weblogic Server JMS Configuration

For the JMS configuration in the Oracle Utilities Customer Care and Billing Weblogic server login
to the console using the URL http://<server_name>:<port_number>/console
For example: http://ccbserver:7001/console
JMS Module
Create a new JMS Module in the weblogic console.
To create a JMS Module to be used for remote queue configuration:

1. Enter the weblogic console and create a new JMS module.
2.
Enter a meaningful name for the JMS module. This JMS Module is used to create configurations which
consume messages from remote weblogic queues. Example: MDMInegrationModule
Foreign Server
Create a new Foreign Server under the JMS Module in the weblogic console.
To create the Foreign Server to be used for remote queue configuration:

1. Enter the weblogic console and select the JMS module created for the integration.
2.
Create a Foreign server under the JMS Module.

Add the following for the Foreign Server
30
Name Name for the Foreign Server For example: CCBMDMForeignServer
JNDI Initial Context Factory weblogic.jndi.WLInitialContextFactory
JNDI Connection URL Add the URL for the Integration SOA Server
For example: t3://soserver.com:8002
JNDI Properties Credential Password for the SOA Server user
JNDI Properties - java.naming.security.principal=<SOA Server user>

Example: weblogic
3. Under the Foreign server create a Foreign Destination for each remote queue.
Name Name of foreign destination
Local JNDI Name Add a local JNDI name for the Integration Queue. Local JNDI name
is later added manually as part of configuration in the weblogic-ejb-jar.xml <weblogicenterprise-bean> <message-driven-descriptor> <destination-jndi-name>
Remote JNDI Name JNDI name of the queue on the Integration SOA Server
Examples:
For each Integration point, one destination is created.
SP Sync
Destination Name
Local JNDI Name
OUCCBSPSyncResponse
jms/LocalOUCCBSPSyncResponse
Remote JNDI Name

jms/OUCCBSPSyncResponse
SA Sync
Destination Name
Local JNDI Name
OUCCBSASyncResponse
jms/LocalOUCCBSASyncResponse
Remote JNDI Name

jms/OUCCBSASyncResponse
Batch BD
Destination Name
Local JNDI Name
OUCCBBatchBDResponse
jms/LocalOUCCBBatchBDResponse
Remote JNDI Name

jms/OUCCBBatchBDResponse
Online BD
Destination Name
Local JNDI Name
Remote JNDI Name
OUCCBOnlineBDResponse
jms/LocalOUCCBOnlineBDResponse
jms/OUCCBOnlineBDResponse
Replacement Reads
Destination Name
Local JNDI Name
OUCCBReplReadRequest
jms/LocalOUCCBReplReadRequest
Remote JNDI Name

jms/OUCCBReplReadRequest
4. Under the Foreign server create a Remote Connection Factory.

31
Name Name of remote connection factory
Local JNDI Name Add a local JNDI name for the Integration Connection Factory. This
JNDI name is added manually later as part of configuration in the weblogic-ejb-jar.xml
<weblogic-enterprise-bean> <message-driven-descriptor> <connection-factory-jndiname>
Remote JNDI Name JNDI name of the JMS Connection factory on the Integration SOA
Server
For example:
Connection Factory Name
Local JNDI Name
Remote JNDI Name
OUCCBOUMDMConnectionFactory
jms/LocalOUCCBOUMDMConnectionFactory
jms/OUCCBOUMDMConnectionFactory
Configuration File Changes

Configure Message Driven Beans (MDB)
It is recommended that you use the Oracle Utilities Customer Care and Billing template and CM
(Customer Modification) feature to make changes to these configuration files. This ensures that
your modifications cannot be overwritten by future application patches.
Modify files: ejb-jar.xml and ejb-weblogic-jar.xml
Location: Oracle Utilities Customer Care and Billing Enterprise Archive (EAR) file
32
The Oracle Utilities Customer Care and Billing configuration files, ejb-jar.xml and ejbweblogic-jar.xml, must be modified to configure Message Driven Beans (MDB). MDBs
which receive messages from the integration queues. These files are part of the Oracle
Utilities Customer Care and Billing Enterprise Archive (EAR) file.
The Oracle Utilities Customer Care and Billing application needs to be redeployed after
these changes are made.
Managing Configuration Files: Configuration files such as config.xml, ejb-jar.xml and

ejb-weblogic-jar.xml are managed through template configuration files which reside in
the environment's etc directory. When the initialSetup.sh script is executed,
environment specific information is combined with the template to create the target file
which is then deployed to the correct location. When the environment is started up
(spl.sh start) the changes are automatically deployed to WebLogic.
Override the existing template: It is possible to override the existing template by

providing another template file in the same location, with the same name but prefixed
with ".cm". For example, if etc/cm.ejb-jar.xml.template is found when initialSetup is run,
the cm.ejb-jar.xml.template is used to generate the target ejb-jar.xml file.
Enabling changes for the integration: To enable your changes for integration with
Oracle Utilities Meter Data Management it is recommended that you first make a "CM"
copy of the existing template and make your changes to the CM version. If there are
any problems with starting the application it is a simple process to delete the CM
versions of the files and rerun initialSetup to regenerate and redeploy the original
versions.
If you make CM versions of the template files and later install a patch which updates the
base template, the CM version will not be updated.
Working example configuration files are available for download from My Oracle Support in Patch
number 9974118 - CCB - MDM/NMS INTEGRATION CONFIGURATION EXAMPLES. Before
installing the examples please read the Product Fix Design document included in the patch for
more information.
To create MDB to receive messages from the CCB Inbound queue:

Create a new MDB to receive messages from each integration inbound queue. For simplicity, we
refer to the names of the target configuration files in the following examples, however but you
should make your changes in the etc/cm.<target file>.template version of the file and then
execute initalSetup.sh (Unix) or initalSetup.cmd (Windows) to deploy the generated file.
1. Create an MDB for each CCB inbound queue to receive messages and invoke CCB service.
2. Modify the ejb-jar.xml and weblogic-ejb-jar.xml to configure the MDBs.
3. Add the <message-driven> and <container-transaction> tag for each inbound queue in the ejb-jar.xml.
Add a security role with role cisusers in the ejb-jar.xml e.g
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar>
<display-name>ServiceBean</display-name>
<enterprise-beans>


<message-driven>
<description>MDB for OUCCBSPSyncResponse</description>
<display-name>OUCCBSPSyncResponse</display-name>
<ejb-name>OUCCBSPSyncResponse</ejb-name>
<ejb-class>com.splwg.ejb.mdb.MessageProcessor</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<message-destination-type>javax.jms.Queue</messagedestination-type>
</message-driven>


<message-driven>
<description>MDB for OUCCBSASyncResponse</description>
<display-name>OUCCBSASyncResponse</display-name>
<ejb-name>OUCCBSASyncResponse</ejb-name>
</message-driven>


33
<message-driven>
<description>MDB for OUCCBBatchBDResponse</description>
<display-name>OUCCBBatchBDResponse</display-name>
<ejb-name>OUCCBBatchBDResponse</ejb-name>
</message-driven>


<message-driven>
<description>MDB for OUCCBOnlineBDResponse</description>
<display-name>OUCCBOnlineBDResponse</display-name>
<ejb-name>OUCCBOnlineBDResponse</ejb-name>
</message-driven>


<message-driven>
<description>MDB for OUCCBReplReadRequest</description>
<display-name>OUCCBReplReadRequest</display-name>
<ejb-name>OUCCBReplReadRequest</ejb-name>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<security-role>
<role-name>cisusers</role-name>
</security-role>


<container-transaction>
<method>
<method-name>onMessage</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>


<method>
</method>

<method>
</method>
34
<method>
</method>

<method>
</method>
</assembly-descriptor>
</ejb-jar>
4. Modify the weblogic-ejb-jar.xml. Add the <weblogic-enterprise-bean> tag for each inbound queue.
Add a security role with role cisusers.
5. The following are references in the <weblogic-enterprise-bean> tag.
a. <ejb-name> - MDB Name given in ejb-jar.xml
b. <destination-jndi-name> - JNDI name provided in JMS Module Foreign
Server Foreign Destination Local JNDI Name
c. <connection-factory-jndi-name> - JNDI name provided in JMS Module Foreign

ServerRemote Connection FactoryLocal JNDI Name
E.g
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>SPLServiceBean</ejb-name>
<jndi-name>spl/servicebean</jndi-name>
</weblogic-enterprise-bean>


<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>5</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-freepool>
</pool>
<destination-jndiname>jms/LocalOUCCBSPSyncResponse</destination-jndi-name>
<connection-factory-jndiname>jms/LocalOUCCBOUMDMConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>


<pool>
35
</pool>
<destination-jndiname>jms/LocalOUCCBSASyncResponse</destination-jndi-name>

<pool>
</pool>
<destination-jndiname>jms/LocalOUCCBBatchBDResponse</destination-jndi-name>

<pool>
</pool>
<destination-jndiname>jms/LocalOUCCBOnlineBDResponse</destination-jndi-name>

<pool>
</pool>
<destination-jndiname>jms/LocalOUCCBReplReadRequest</destination-jndi-name>
<security-role-assignment>
<role-name>cisusers</role-name>
<principal-name>cisusers</principal-name>
</security-role-assignment>
</weblogic-ejb-jar>
36
Outbound Configuration
XAI JNDI Server
Create a new XAI JNDI Server which points to the Integration SOA server.
To create XAI JNDI Server configured to communicate with integration layer:

1. Navigate to Admin Menu, XAI JNDI Server.
2. Enter XAI JNDI Server name. For example: CI_MDM_JNDI
3. Enter XAI JNDI Server description E.g CCB-MDM Integration server
4. Populate the Provider URL in the format t3//<SOA Server>: <SOA Port>
For example: t3://soaserver.us.oracle.com:8002
XAI JMS Queue

Create a new XAI JMS Queue for each Integration Queue where Oracle Utilities Customer Care
and Billing sends messages.
To create XAI JMS Queue

1. Navigate to Admin Menu, XAI JMS Queue.
2. Enter the following
XAI JMS Queue Queue name in Oracle Utilities Customer Care and Billing
Description Queue description
Queue Name JNDI name of the queue on the Integration server For example:
jms/OUCCBSPSyncRequest
Target Client Flag JMS
XAI JNDI Server Select the XAI JNDI Server created for the integration.
Examples:
SP Sync Integration Point

XAI JMS Queue
CI_MDM1SPSyn
Description
Queue Name
SP Sync Request
jms/OUCCBSPSyncRequest
Target Client Flag
XAI JNDI Server
JMS
CI_MDM_JNDI
Target Client Flag
XAI JNDI Server
JMS
CI_MDM_JNDI
SA Sync Integration Point

XAI JMS Queue
CI_MDM1SASyn
Description
Queue Name
SA Sync Request
jms/OUCCBSASyncRequest
37
Batch BD Integration Point

XAI JMS
Queue
CI_MDM1_BBD
Description
Batch Bill Determinant
Request
Queue Name
jms/OUCCBBatchBDRequest
Target Client
Flag
JMS
XAI JNDI
Server
CI_MDM_JNDI
Online BD Integration Point

XAI JMS
Queue
CI_MDM1_OBD
Description
Online Bill Determinant
Request
Queue Name
jms/OUCCBOnlineBDRequest
Target Client
Flag
JMS
XAI JNDI
Server
CI_MDM_JNDI
Replacement Reads Integration Point

XAI JMS
Queue
CI_MDM1_CRD
Description
Online Corrected Read
Response
Queue Name
jms/OUCCBReplReadResponse
Target
Client Flag
JMS
XAI JNDI
Server
CI_MDM_JNDI
XAI JMS Connection

Create a new XAI JMS Connection to be used to connect to the integration queues.
To create XAI JMS Connection

1. Navigate to Admin Menu, XAI JMS Connection.
2. Enter the following
XAI JMS Connection Connection name in Oracle Utilities Customer Care and Billing
Description Connection description
XAI JNDI Server Select XAI JNDI Server created for this integration as described in
the XAI JNDI Server section
JNDI ConnectionFactory JNDI name of the Connection factory on the Integration

server.
For example: jms/OUCCOUMDMConnectionFactory

XAI JMS Connection
CI_MDM_CF
38
Description
CCB MDM Integration
Connection
XAI JNDI Server

CI_MDM_JNDI
JNDI Connection Factory

jms/OUCCBOUMDMConnectionFactory
XAI Sender
Create a new XAI Sender for each Oracle Utilities Customer Care and Billing Outbound
Integration Queue.
To create a Realtime XAI sender configured to communicate with integration layer:

1. Navigate to Admin Menu, XAI Sender.
2. Enter a unique XAI Sender and Description.
3. Populate values as follow:
XAI Sender Sender name in Oracle Utilities Customer Care and Billing
Description Sender description
Invocation Type Real-time
XAI Class RTJMSQSNDR (Realtime JMS Queue Sender)
Active - Select the checkbox
MSG Encoding UTF-8 message encoding
XAI JMS Connection XAI JMS connection created for the integration
XAI JMS Queue XAI JMS Queue created for the Oracle Utilities Customer Care and
Billing Outbound Queue.
4. Select the Context tab and set values for the following Context Types:
JMS Message Type (Bytes(Y)/Text(N)) N
JMS User Name user for the SOA server to be accessed
JMS User Password Password for the SOA server to be accessed.

Examples:

XAI Sender
Description
CI_MDM_SPSYN
MDM SP Sync Request Sender
XAI JMS Connection

CI_MDM_CF
XAI JMS Queue

CI_MDM1SPSyn

XAI Sender
Description
CI_MDM_SASYN
MDM SA Sync Request Sender
XAI JMS Connection

CI_MDM_CF
XAI JMS Queue

CI_MDM1SASyn
39

XAI Sender
Description
CI_MDM_BBD
MDM Batch Bill Determinant JMS Queue Sender
XAI JMS Connection
XAI JMS Queue
CI_MDM_CF
CI_MDM1_BBD

XAI Sender
Description
CI_MDM_OBD
MDM Online Bill Determinant JMS Queue Sender
XAI JMS Connection
XAI JMS Queue
CI_MDM_CF
CI_MDM1_OBD

XAI Sender
Description
XAI JMS Connection
CI_MDM_CRD
MDM Corrected Read JMS Queue Sender
CI_MDM_CF
XAI JMS Queue

CI_MDM1_CRD
Outbound Message Type

To create a Outbound Message Type for each Oracle Utilities Customer Care and Billing Outbound
queue:
Create a new Outbound Message type for each Oracle Utilities Customer Care and Billing
Outbound Integration Queue.
1. Navigate to Admin Menu, Outbound Message Type.

2. Enter an Outbound Message Type, Description and Detailed Description.
3. Select the Outbound Message Business object created for the specific outbound queue.
Examples:
CI_MDM1SPSYN
Description
Business Object
MDM1 SP Sync Request Outbound Message
C1-MDM1SPSyncReqOutMsg
Description
Business Object
MDM1 SA Sync Request Outbound Message
C1-MDM1SASyncReqOutMsg

CI_MDM1SASYN

CI_MDM_BBD
40
Description
Business Object
MDM Batch Bill Determinants Outbound Message
C1-CyclicalUsgReqOutMsg

CI_MDM_OBD
Description
Business Object
MDM Online Bill Determinants Outbound Message
C1-NonCyclicalUsgReqOutMsg

CI-CORRREADM
Description
Business Object
Corrected Read CCB Response
CI-CorrectedReadOutMsg
External System
To create a Outbound Message Type for each Oracle Utilities Customer Care and Billing Outbound
queue:
Create a new External System for Oracle Utilities Customer Care and Billing Integration to Oracle
Utilities Meter Data.
1. To define an External System, open Admin Menu, External System.

2. Enter a unique External System and Description.
For example: Name = CI_MDM1, Description = Oracle Utilities Meter Data Management
3.
Set Our Name in Their System to Customer Care and Billing
4. Associate the Outbound message types created to the External System. For each Outbound message
type set the following
Outbound Message Type Set the outbound message type created for Oracle Utilities
Customer Care and Billing outbound queue
Processing Method Real-time
XAI Sender Set the XAI Sender created for the queue.
Message XSL - C1-CCBJMSQAddNamespace.xsl

For example: External System CI_MDM1
Outbound
Message Type
Processing
Method
XAI Sender
Message XSL
CI_MDM1SPSYN
Real-time
CI_MDM_SPSYN
C1-CCBJMSQAddNamespace.xsl
CI_MDM1SASYN
Real-time
CI_MDM_SASYN
CI_MDM_BBD
Real-time
CI_MDM_BBD
CI_MDM_OBD
Real-time
CI_MDM_OBD
CI-CORRREADM
Real-time
CI_MDM_CRD
41
For more information about configuration guidelines see the Oracle Utilities Customer Care and
Billing documentation.
Setting Up Oracle Utilities Meter Data

Management
Setting up Oracle Utilities Meter Data Management for the integration involves the following
configurations:
Configure synchronization adapter services
Configure bill determinant request adapter services
Configure replacement reading adapter services
Set up the weblogic environment.
The following sections provide a general overview of these steps, however you should refer to the
Oracle Utilities Meter Data Management Installation and Configuration Guide for detailed steps.
For more information on configuring and working with Oracle Utilities Oracle Utilities Meter Data
Management, please refer to Oracle Utilities Meter Data Management Installation and
Configuration Guide for Release 1.6.1.0.
Standard Oracle Utilities Meter Data Management configuration such as setting up usage
validation rules and setting up services to poll for usage data is covered in the standard Oracle
Utilities Meter Data Management configuration guides.
Configuring Synchronization Adapter Services

The adapter services used to update service point and account data are pre-defined in the Oracle
Utilities Data Repository, but must be properly configured before data synchronization can be
performed.
CCB_SP_TO_MDM_SERVICE
When service point sync requests are sent from Oracle Utilities Customer Care and Billing, they
are sent to a JMS queue monitored by the CCB_SP_TO_MDM_SERVICE service. When a
record is added or changed, the CCB_SP_TO_MDM_SERVICE business rule updates the
service point related data based on the details in the sync request. Configuring the
CCB_SP_TO_MDM_SERVICE service involves the following:
42
Specifying the JMS Queue
Enabling the service
Creating multiple CCB_SP_TO_MDM_SERVICE services

Adding additional elements to the Rules Description Language Configuration for

CCB_SP_TO_MDM_RDL
CCB_SA_TO_MDM_SERVICE
When service account (account data) sync requests are sent from Oracle Utilities Customer Care
and Billing, they are sent to a JMS queue monitored by the CCB_SA_TO_MDM_SERVICE
service. When a record is added or changed, the CCB_SA_TO_MDM_SERVICE business rule
updates the service point-related data based on the details in the sync request. Configuring the
CCB_SA_TO_MDM_SERVICE service involves the following:
Creating multiple CCB_SA_TO_MDM_SERVICE services
Adding additional elements to the Rules Description Language Configuration for

CCB_SA_TO_MDM_RDL (optional)
Configuring Bill Determinant Request Adapter Services

The Adapter services used to process bill determinant calculation requests are pre-defined in the
Oracle Utilities Data Repository, but must be properly configured before processing can be
performed.
CCB_INTEGRATOR_JMS_TRIGGER_SERVICE
When bill determinant calculations are requested from Oracle Utilities Customer Care and Billing,
a record is created in the JMS Queue The CCB_INTEGRATOR_JMS_TRIGGER_SERVICE
service monitors this queue, and when a record is detected, the
CCB_INTEGRATOR_TRIGGER_RULE business rule triggers the Account Selector to create a
record in the BD Request table and record in the BD Queue / BD Queue Archive table for the
account. Configuring the CCB_INTEGRATOR_JMS_TRIGGER_SERVICE service involves the
following:
Creating multiple CCB_INTEGRATOR_JMS_TRIGGER_SERVICE services
BD_QUEUEPOLLER
The BD_QUEUEPOLLER service monitors the BD Queue table and when a record is detected,
triggers the Calculator Engine for each record.
When configuring this service and Calculator Engine to process external calculation requests,
include the following parameter in the LODESTAR.CFG configuration file on all application
servers that run the calculator engine:
43
BD_QUEUEPUBLISHER
The BD_QUEUEPUBLISHER service monitors the BD Queue table and when a record is
detected, triggers the Bill Determinant Publisher for each record. Configuring the
BD_QUEUEPUBLISHER service involves the following:
Creating multiple BD_QUEUEPUBLISHER services
Adjusting the Runtime Service properties
Configuring Replacement Reading Adapter Services

The Adapter services used to process replacement readings are pre-defined in the Oracle Utilities
Data Repository, but must be properly configured before processing can be performed.
CCB_REPL_READ
When replacement usage is detected for an account for which bill determinants have previously
been calculated, a record is created in the Payload Extension table with a Payload Type of
BDRECALC.. The CCB_REPL_READ service monitors this table, and when a record is
detected, the CCB_REPL_READ service sends a message to an outbound queue containing
details of the replacement reading (Account ID, Service Point ID, Start Time, Stop Time, and
Meter ID). Configuring the CCB_REPL_READ service involves the following:
Creating multiple CCB_REPL_READ services
CCB_REPL_ERROR
If there is an error when sending a notification of a replacement reading to Oracle Utilities
Customer Care and Billing, a record is created in a JMS queue The CCB_REPL_ERROR service
monitors this queue, and when a record is detected, the CCB_REPL_ERROR business rule
triggers the Account Selector to create a work queue item noting the failure to send the message.
Configuring the CCB_REPL_ERROR service involves the following:
Creating multiple CCB_REPL_READ services
Setting up the Weblogic Environment

The following describes additional set up needed for the Oracle Utilities Oracle Utilities Meter
Data Management Application Server to communicate with a Weblogic sever.
44
Provide Application Server with Weblogic client JAR file

Weblogic provides a client JAR file that is needed on the application sever machine. Reference
the Weblogic documentation on how to generate the client jar file. After creating this file place
this JAR on the Application server machine. We recommend placing this file under its own
directory like c:\weblogic\lib directory.
Update LTMH.CFG.XML file

Include the statements below in the LTMH configuration file on the application server. This file is
normally found in the c:\lodestar\cfg directory.
<LTMH JMSENABLED="true">
<JNDI>
<CONTEXTFACTORY>
weblogic.jndi.WLInitialContextFactory</CONTEXTFACTORY>
<PROVIDERURL> t3://weblogic ip : port </PROVIDERURL>
</JNDI>
</LTMH>
Note: The <PROVIDERURL> element must be updated with the location of the Weblogic
Server. (Example: <PROVIDERURL>t3://10.149.183.43:7021</PROVIDERURL>)
To specify the JMS Sever class path

Add the location to the Weblogic client JAR file to the classpath field on the JMS Server record.
1.
Select Tools and Utilities-Adapter Components-JMS Servers.

The JMS Server screen opens.
2.
Enter weblogic.jms.ConnectionFactory in the Name field and click Search.

The weblogic.jms.ConnectionFactory record appears on the JMS Server screen.
3.
Under the Child section click on the "System Properties".

The System Properties screen appears.
4.
Edit the Classpath field, add the Weblogic client path directory to the end of the data string and click
Save.
Example Classpath= "\portal.jar;.\ltmh.jar;.\lsice.jar;c:\weblogic\wlfullclient.jar"
Setting up the Process Integration

The following sections describe how to configure the integration pack to meet the requirements
for the 2-way integration. Configuration steps include setting:
45
Configuration properties
System properties
Domain value maps
Error handling
Setting Configuration Properties

The ConfigurationProperties.xml contains properties which can be defaulted in the integration.
Also it contains flags to enable extension points within the integration.
ConfigurationProperties.xml is located in MDS under the directory apps/CCBMDM/AIAMetaData/config.
Note. Whenever the ConfigurationProperties.xml file is updated, the file must be reloaded for
updates to be reflected in the applications or services that use the updated properties. You can
perform the reload by rebooting the soa server.
Settings for System Properties

There are two sets of configuration properties described in this section:
Module Configurations are the properties that are shared by multiple integration flows
within this Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter
Data.
Service Configurations are the properties that are used by a specific BPEL process.
Module Configurations
DVM flags signal whether an error is triggered when the DVM lookup value is not found for a
DVM. If the value is set to true the integration layer triggers a DVM exception to the initiating
application. If the value is set to false the integration does not trigger any exception and it passes
the source application value as the default value to the target application.
Module Name
Default / Shipped
Value
Description
CCB.Generic.MessageCategory
11114
This is the message category that the integration layer uses for CCB
error messages.
CCB.GenericBusinessException.Messag
eNumber
11001
This is the message number that the integration layer uses for generic
CCB errors.
CCB.GenericDVMException.MessageNu
mber
11401
This is the message number that the integration layer uses for DVM
errors.
SOA-INFRA.AuditLevel
ON
This property needs to be set to OFF if the Audit Level is set to OFF
for the BPEL processes. If the setting is OFF then error handling does
not use the composite and component instance IDs to log the error
message.
46
Module Name
Default / Shipped
Value
ErrorHandling.GenericEmailID
Description
This property is used to set the administrator email ID for the
errorhandling process to send out an email in case of a critical failure
where even the Errorhandling process fails.
DVM.OUCCB_OUMDM_Country.Throw
Exception
false
This is the flag for the OUCCB_OUMDM_Country DVM.
DVM.OUCCB_OUMDM_CISDivision.Thr
owException
false
This is flag for the OUCCB_OUMDM_CISDivision DVM.
DVM.OUCCB_OUMDM_SAType.Throw
Exception
false
This is flag for the OUCCB_OUMDM_SAType DVM.
DVM.OUCCB_OUMDM_SAStatus.Thro
wException
false
This is flag for the OUCCB_OUMDM_SAStatus DVM.
DVM.OUCCB_OUMDM_SIC.ThrowExce
ption
false
This is flag for the OUCCB_OUMDM_SIC DVM.
DVM.OUCCB_OUMDM_RateInfo.Throw
Exception
false
This is flag for the OUCCB_OUMDM_RateInfo DVM.
DVM.OUMDM_OUCCB_BDI.ThrowExce
ption
false
This is flag for the OUMDM_OUCCB_BDI DVM.
DVM.OUMDM_OUCCB_TOU.ThrowExc
eption
false
This is flag for the OUMDM_OUCCB_TOU DVM.
DVM.OUMDM_OUCCB_UOM.ThrowExc
eption
false
This is flag for the OUMDM_OUCCB_UOM DVM.
DVM.OUMDM_OUCCB_UsageType.Thr
owException
false
This is flag for the OUMDM_OUCCB_UsageType DVM.
Service Configurations
Service Name
OUCCBOUMDMSPSyncR
eqEBF
OUMDMOUCCBSPSyncR
espEBF
Property Name
Default / Shipped
Value
Description
Default.SystemID
OU_CCB_01
Initiating system ID.
Extension.PreXformCCBto
MDM
false
If set to true the pre transformation extension

service is invoked.
Extension.PreInvokeEnQue
ueToMDM
false
If set to true the Pre Enqueue extension service is

invoked.
BusinessError.NotificationFl
ag
false
If set to true Business error notification is sent via

email.
TechnicalError.NotificationF
lag
false
If set to true Technical error notification is sent via

email.
Default.SystemID
OU_MDM_01
Extension.PreXformMDMto
CCB
false
If set to true the Pre transformation extension

service is invoked.
47
Service Name
OUCCBOUMDMSASyncR
eqEBF
OUMDMOUCCBSASyncR
espEBF
OUCCBOUMDMBatchBDR
eqEBF
OUMDMOUCCBBatchBDR
espEBF
48
Property Name
Default / Shipped
Value
Description
ueToCCB
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_CCB_01
MDM
false

service is invoked.
ueToMDM
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_MDM_01
CCB
false

service is invoked.
Extension.PreEnqueuetoC
CB
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_CCB_01
MDM
false

service is invoked.
Extension.PreEnqueuetoM
DM
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_MDM_01
CCB
false

service is invoked.
CB
false

invoked.
Service Name
OUCCBOUMDMOnlineBD
ReqEBF
OUMDMOUCCBOnlineBD
RespEBF
OUMDMOUCCBReplRead
ReqEBF
OUCCBOUMDMReplRead
RespEBF
Property Name
Default / Shipped
Value
Description
ag
false

email.
lag
false

email.
Default.SystemID
OU_CCB_01
MDM
false

service is invoked.
Extension.PreEnqueuetoM
DM
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_MDM_01
CCB
false

service is invoked.
CB
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_MDM_01
CCB
false

service is invoked.
ueToCCB
false

invoked.
ag
false

email.
lag
false

email.
Default.SystemID
OU_CCB_01
MDM
false

service is invoked.
ueToMDM
false

invoked.
ag
false

email.
49
Service Name
Property Name
lag
Default / Shipped
Value
false
Description
email.
Domain Value Maps

Domain value maps (DVMs) are a standard feature of the Oracle SOA Suite which maps codes
and other static values across applications. For example, US and USA.
DVMs are static in nature, though administrators can add additional maps as needed.
Transactional business processes never update DVMsthey only read from them. They are
stored in XML files and cached in memory at runtime.
To maintain the information within the domain value maps:

1. Open a browser and access the SOA Composer application for your installation
2. On the SOA composer click on the Open dropdown and select Open DVM. This displays a list of all
the DVM files in the MDS.
3. Select the relevant DVM you wish to maintain.
4. The Edit button in the top navigation bar enables editing the DVM.
5. Once the DVM has been edited click on the Save button in the top navigation bar. This saves the
DVM data for that session.
6. Click on Commit after updating each DVM. This saves the DVM data in the MDS.
These are the DVMs for the Oracle Utilities Customer Care and Billing Integration to Oracle
Utilities Meter Data:
DVM
Integration Points
Description
OUCCB_OUMDM_ErrorCode
All
Mapping between CCB message number and MDM

Error code
OUCCB_OUMDM_Country
SP Sync
Mapping between CCB country code and MDM

Country code and address format
SA Sync
Mapping between CCB and MDM CIS Division
OUCCB_OUMDM_SAType
SA Sync
Mapping between CCB and MDM SA Type
SA Sync
Mapping between CCB and MDM SA Status
OUCCB_OUMDM_SIC
SA Sync
Mapping between CCB and MDM Standard Industrial

Code
50
DVM
Integration Points
Description
SA Sync
Mapping between CCB Rate Schedule to MDM Rate

schedule, Rate Code, Rate Form code and
Jurisdiction
OUMDM_OUCCB_UOM
Batch and Online BD
Mapping between CCB and MDM UOM
OUMDM_OUCCB_TOU
Batch and Online BD
Mapping between CCB and MDM TOU
OUMDM_OUCCB_BDI
Batch and Online BD
Mapping between MDM BDI to CCB SQI, UOM and

TOU
Batch and Online BD
Mapping between CCB and MDM Usage Type
For more information refer the chapters Working with Domain Value Maps and Using SOA
Composer with Domain Value Maps in the Oracle Fusion Middleware Developer's Guide
for Oracle SOA Suite for more information about Domain Value Maps
This DVM is used by the integration code to transform the Oracle Utilities Meter Data
Management error code to Oracle Utilities Customer Care and Billing message number. This help
the implementation layer to map specific message numbers to specific error codes and thus
provide more user friendly error messages in Oracle Utilities Customer Care and Billing.
OUCCB_ErrorCode
OUMDM_ErrorCode
This is the CCB Message Number
This is the MDM Error code
OUCCB_OUMDM_Country
This DVM is used by the integration layer to map the Oracle Utilities Customer Care and Billing
country code to corresponding Oracle Utilities Meter Data Management Country code and Oracle
Utilities Meter Data Management Address format.
OUCCB_CountryCode
This is a valid country code defined in CCB
OUMDM_Country Code
This is a valid country code defined
in MDM
OUMDM_AddressFormat
This is the address format defined in MDM
which corresponds to the country code
CIS Division to corresponding Oracle Utilities Meter Data Management CIS Division.
OUCCB_CISDivision
This is a valid CIS Division defined in CCB
OUMDM_CISDivision
This is a valid CIS Division defined in MDM
OUCCB_OUMDM_SAType
SA Type to corresponding Oracle Utilities Meter Data Management SA Type.
51
OUCCB_SAType
This is a valid SA Type defined in CCB
OUMDM_SAType
This is a valid SA Type defined in MDM
SA status to corresponding Oracle Utilities Meter Data Management SA status.
OUCCB_SAStatus
This is a valid SA Status defined in CCB
OUMDM_SAStatus
This is a valid SA Status defined in MDM
OUCCB_OUMDM_SIC
standard industrial code (SIC) to corresponding Oracle Utilities Meter Data Management standard
industrial code.
OUCCB_SIC
This is a valid SIC defined in CCB
OUMDM_SIC
This is a valid SIC defined in MDM
Rate schedule to the corresponding Oracle Utilities Meter Data Management Rate schedule, rate
code, rate form code and jurisdiction.
OUCCB_RateSche
dule
OUMDM_RateSc
hedule
OUMDM_RateCod
e
OUMDM_RateF
ormCode
OUMDM_Jurisdictio
n
This is a valid rate

schedule defined in
CCB

schedule defined in
MDM
This is a valid rate code

defined in MDM

form code defined in
MDM
This is a valid jurisdiction

code defined in MDM
OUMDM_OUCCB_UOM
This DVM is used by the integration layer to map the Oracle Utilities Meter Data Management
UOM to corresponding Oracle Utilities Customer Care and Billing UOM.
OUMDM_UOM
This is a valid UOM defined in MDM
OUCCB_UOM
This is a valid UOM defined in CCB
OUMDM_OUCCB_TOU
TOU to corresponding Oracle Utilities Customer Care and Billing TOU.
OUMDM_TOU
This is a valid TOU defined in MDM
52
OUCCB_TOU
This is a valid TOU defined in CCB
OUMDM_OUCCB_BDI
BDI to Oracle Utilities Customer Care and Billing SQI, UOM and TOU. If the service quantity list
sent by Oracle Utilities Meter Data Management contains BDI then the OUMDM_OUCCB_UOM
and OUMDM_OUCCB_TOU are not used for that list. Instead the values picked up from this
DVM are used even for UOM and TOU mapping.
OUMDM_BDI
OUCCB_SQI
OUCCB_UOM
This is a valid BDI defined in

MDM
This is a valid SQI defined in

CCB
This is a valid UOM defined in

CCB
OUCCB_TOU
This is a valid TOU defined in
CCB
usage type to corresponding Oracle Utilities Customer Care and Billing usage type.
OUMDM_UsageType
This is a valid Usage type defined in MDM
OUCCB_UsageType
This is a valid Usage type defined in CCB
53
Error Handling
Integration Layer
Request Processing BPEL
Source Request
Queue
Business
Error ?
Source Request
Error Queue
Technical
Error ?
No
Target Request
Queue
No
Target Request
Error Queue
Yes
Yes
Error
Notification
Response Processing BPEL
Source Response
Queue
No
Technical
Error ?
Business
Error ?
No
Yes
Source Request
Error Queue
Yes
Target Response
Queue
Target Response
Error Queue
Error
Notification
CCB MDM Integration Error Handling
The integration includes two types of errors:
S. No
A1
54
Business Errors triggered when the DVM lookup values are not found or there is a
transformation error in the integration layer.
Business errors are sent back to the source application and can be re-tried from
there.
Technical Errors trigger when there are connectivity issues between queues.
Technical errors are sent to the error queue and can be re-tried from integration
layer.
Integration Flow
SP Information Sync
CCB originated request
processing
Type of error
Business error
Action
Notification
Type
Message sent to CCB

SP Response Queue
Email (optional) and

CCB ToDo
Retry
Data Correction in
CCB
S. No
Integration Flow
A2
A3
SP Information Sync
MDM originated
response processing
A4
B1
SA Information Sync
CCB originated request
processing
B2
B3
SA Information Sync
MDM originated
response processing
B4
C1
Batch BD CCB
originated request
processing
C2
C3
Batch BD MDM
originated response
processing
Type of error
Action
Notification
Type
Retry
Technical error
Message rolled back

to CCB SP Request
Error Queue
Email (optional)
Administrator has to
move the messages
to the CCB SP
Request Queue
from Weblogic
Admin Console
Business error
Message sent to CCB

SP Response Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to MDM SP
Response Error
Queue
Email (optional)
move the messages
to the MDM SP
Response Queue
from Weblogic
Admin Console
Business error
Message sent to CCB

SA Response Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to CCB SA Request
Error Queue
Email (optional)
move the messages
to the CCB SA
Request Queue
from Weblogic
Admin Console
Business error
Message sent to CCB

SA Response Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to MDM SA
Response Error
Queue
Email (optional)
move the messages
to the MDM SA
Response Queue
from Weblogic
Admin Console
Business error
Message sent to CCB

Batch BD Response
Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to CCB Batch BD
Request Error Queue
Email (optional)
move the messages
to the CCB Batch
BD Request Queue
from Weblogic
Admin Console
Business error
Message sent to CCB

Batch BD Response
Queue

CCB ToDo
Data Correction in
CCB
55
S. No
Integration Flow
C4
D1
Online BD CCB
originated request
processing
D2
D3
Online BD MDM
originated response
processing
D4
E1
Replacement Read
MDM originated request
processing
E2
E3
E4
56
Replacement Read
CCB originated
response processing
Type of error
Action
Notification
Type
Retry
Technical error
Message rolled back

to MDM Batch BD
Response Error
Queue
Email (optional)
move the messages
to the MDM Batch
BD Response
Queue from
Weblogic Admin
Console
Business error
Message sent to CCB

Online BD Response
Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to CCB Online BD
Request Error Queue
Email (optional)
move the messages
to the CCB Online
BD Request Queue
from Weblogic
Admin Console
Business error
Message sent to CCB

Online BD Response
Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to MDM Online BD
Response Error
Queue
Email (optional)
move the messages
to the MDM Online
BD Response
Queue from
Weblogic Admin
Console
Business error
Message sent to
MDM Replacement
Read Response
Queue
Email (optional)
Data Correction in
MDM
Technical error
Message rolled back

to MDM Replacement
Read Request Error
Queue
Email (optional)
move the messages
to the MDM
Replacement Read
Request Queue
from Weblogic
Admin Console
Business error
Message sent to
MDM Replacement
Read Response
Queue

CCB ToDo
Data Correction in
CCB
Technical error
Message rolled back

to CCB Replacement
Read Response Error
Queue
Email (optional)
move the messages
to the CCB
Replacement Read
Response Queue
from Weblogic
Admin Console
To retry the Technical error failure messages:

1. Open a browser and access the Weblogic console for your installation
2. Navigate to Services-> Messaging -> JMS Modules.
3. Select the CCB-MDM Integration JMS Module to show all the queues related to this integration.
4. Select the appropriate error queue and click on the Monitoring tab.
5. This tab shows the details about the messages in the queue in a table.
6. Select the checkbox in the details table and click on the Show Messages button. This displays all the
messages in the error queue.
7. Click on the Move button and select the Move All option.
8. Select the CCB-MDM JMS Server to move the messages and click on the Next button.
9. Now select the correct parent queue for the error queue from the dropdown and click on the Finish
button.
10. This action moves all the messages to the source queue so that the integration layer can process all
the messages again.
Error Notification Setup

Steps to enable EMAIL notification for CCB-MDM Error Handling module.
1. Log in to the enterprise manager console.
2. Click on 1> Expand SOA right click on soa-infra SOA Administration Workflow Notification
Properties
3. On this screen select EMAIL from the drop down.
4. Provide the email IDs for From address.
INTEGRATION_ERR_STORE
The INTEGRATION_ERR_STORE table is used to store all the error details for each message
failure The table is populated for each integration point based on the
BusinessError.NotificationFlag and TechnicalError.NotificationFlag properties for each service in
the ConfigurationProperties.xml.
INTEGRATION_ERR_LOOKUP
Error handling module configuration is governed by the Integration_err_lookup table. This table
contains processing instructions for each composite. The Error_Processing_Parent composite
picks data for one composite and calls error_Processing_Detail for processing. The configuration
in this table is used to process the error records stored in the INTEGRATION_ERR_STORE
table.
57
S. No.
Column Name
Description
Default / Suggested values
LookUp_ID
Sequence ID of entry in this table. This is

auto generated.
Auto generated
IP_Name
The name of the composite that is

processed.
This column is pre populated with

the individual enterprise business
flow name.
Example
OUMDMOUCCBReplReadReqEBF
3
Processing_Status
Current status of processing it has to be

one of the following.
Do not modify: Modifying this value

will break the code.
NOT REQUIRED
HALTED (waiting for manual intervention),

NOT REQUIRED
ALIVE
4
Run_Flag
Processing flag status, Y or N. Unread

value = N, read value =Y
Next_Runtime
Next runtime when the error record should

be processed for this composite.
SYSDATE+200
Halt_For_Error
Allowed values Y or N.
When set to Y manual intervention is

required after one successful error record
processing.
When set to N processing continues
without halting.
7
RunTime_Interval
Runtime in minutes after which the next

error processing should be done.
Default : P10Y0M0DT0H0M0S
Example : P10Y0M0DT0H0M0S
Next processing is done after
10 years 0 months 0 days 0 hours 0
minutes and 0 seconds
This value must be updated based on the
business requirement. Setting fewer
intervals may have impact on performance.
8
Email_ID
Email-ID where error notifications are sent.
Default : email@email.com
This value can be different or same for all

the composites.
58
9
Email_Content_Type
GENERIC One email is sent for all

errors. No detail information is included.
Default : GENERIC
SINGLE One email is sent for all errors

with all details included in the attachment.
MULTIPLE Multiple emails are sent &
each email has information equal to the
value specified in the
Error_Count_Per_Notification column.
Values are case sensitive and must always
be given in upper case.
10
Email_XSL
XSL to be applied for creating email

Content which includes subject/body and
attachment. Look and feel can be modified
here.
Default file is provided for all the

composites and present under the
xsl folder of composite.
Example:
xsl/Transformation_Create_Email.xs
l
Copy this to the mds folder and
enter the mds path in this column
for additional configuration.
11
Error_Count_Per_Processing
A notification is sent after the number of

records set here is processed.
Default : 100
For example: If this is set to 50 then an

email notification containing 50 reocrds is
sent after 50 records are created in the
error store.
12
Email_Attachment_Location
Location where the email attachment is

created on the server.
This value should point to the location /
folder where the attachment should be
stored.
This is used to create the attachment file in
the following format.
INTEGRATION_ERR_LOOKUP.Email_Att
achment_Location + IP_Name + Date (in
YYYYMMDDHH24MMSS)
13
Email_Attachment_Flag
Y Send email with attachment. In this

case it is not mandatory to have
Email_Attachment_Location specified.
N Send email without attachment but

send the attachment location. In this case
Email_Attachment_Location has to be
specified.
ServerName
+INTEGRATION_ERR_LOOKUP.Email_At
tachment_Location +
IntegrationPoint_Name + Date in
YYYYMMDDHH24MMSS
59
14
Publish_Human_Task_Flag
Y Publish human task
N Dont publish human task

If Halt_For_Error value is set to Y and
Publish_Human_Task_Flag is also Y then
human task is published and the user can
take action from worklist application.
15
ID_Human_Task
User/Group ID to which human task should

be published in case Halt_For_Error is set
to Y
weblogic
This ID must be present in the weblogic

realm pointed by fusion middleware.
16
Last_Updated_Date
Last updated date time
SYSDATE
17
Purge_Error_Store_Flag
Y Purge data
Default : N
N No purge require
The process PurgeIntegrationErrorStore is
deployed when the flag,
purge.process.deploy=true, in the
deploy.properties file is set to true during
installation.
If flag.purge.process = false then value of
this column Purge_Error_Store_Flag will
always be N.
18
Purge_Processing_Status_Flag
Y Purge Processing in process
Default : N
N Purge processing not happening

The process PurgeIntegrationErrorStore is
only deployed when the flag,
purge.process.deploy=true, in the
deploy.properties file is set to true during
installation.
If flag.purge.process = false then value of
this column Purge_Error_Store_Flag will
always be N.
60
19
Purge_Frequency
No of days after which data should be

purged. This will be in picture format
Default : P10Y0M0DT0H0M0S
Example : P10Y0M0DT0H0M0S
Next processing will be done after
10 years 0 months 0 days 0 hours 0
minutes and 0 seconds
This value has to be updated based on the
business requirement. Setting fewer
intervals may have impact on performance.
Need to set this value appropriately.
Applicable only when flag.purge.process =
true in deploy.properties file during
installation and the process
PurgeIntegrationErrorStore ID deployed.
20
Next_Purge_Date
Next purge date. Format: Next_Purge_date

+ Purge_Frequency
SYSDATE+100

21
Purge_File_Name
Directory Name where purge file should be

stored.
'location on server where

purge record should be
persisted'
Primary Key - LookUp _ID, IP_Name
To customize error email notifications for individual integration points:

1. Use the composite: UpdateIntegrationErrorLookupTable .
2. Enter the following url into a browser to get the screen that will provide options of updating the contents
of the table.
http://<hostname>:<soa server port>/soa-infra/services/CCB-MDM/
UpdateIntegrationErrorLookupTable/updateintegrationerrorlookuptablebpel_client_ep?
3. Expand WS-Security and provide authentication information.
This username and password is going to be same as that used for login to weblogic enterprise manager
console.
61
4. Expand the paylod section.

This displays several editable text fields.
Only the ipName field is mandatory and should be entered as one of the values from
INTEGRATION_ERR_LOOKUP.IP_NAME field.
By default all the checkboxes appearing next to the text fields are checked.
5. Provide values in the text field.
If you do not want to have a particular value updated then uncheck the box.
62
Chapter 4: Monitoring, Error Handling and

Troubleshooting
This chapter provides detail into monitoring and troubleshooting, and discusses how to:
Monitor from Oracle Utilities Customer Care and Billing
Monitor from Oracle Utilities Meter Data Management
Monitor from the Integration Layer
Monitoring from Oracle Utilities Customer Care

and Billing
Oracle Utilities Customer Care and Billing Error Logs
Errors related to the online integration invocation from CCB are stored in the
CCB_ENVIRONMENT_NAME/system/logs folder.
For example: V231_CCB_PERF_BLD10_LIN_ORA_WLS/logs/system
Errors related to Batch integration invocation from CCB are stored in the $SPLOUTPUT/
CCB_ENVIRONMENT_NAME folder.
For example: /spl/sploutput/V231_CCB_PERF_BLD10_LIN_ORA_WLS
For more information about errors and notifications see the Oracle Utilities Customer Care and
Billing documentation.
Notifications
Errors in the Integration are communicated back to the Initiating application.
In Oracle Utilities Customer Care and Billing an XAI Inbound service is invoked to report back the
errors. If this service fails then a ToDo item is created in Oracle Utilities Customer Care and
Billing
Connection Errors
Information can be found in the log files in the folders described above.
63
Monitoring from Oracle Utilities Oracle Utilities

Meter Data Management
Oracle Utilities Energy Information Platform Adapter Logging
The Oracle Utilities Energy Information Platform Adapter (and Oracle Utilities Transaction
Management) can be configured to create log files that capture the activity of Adapter business
rules and services for diagnostic and troubleshooting purposes. This section provides an
overview of the log files produced by the Adapter, including:
Viewing Log Files

Adapter log files are created in the C:\LODESTAR\LTMH\Runtime\Log directory on the
application or web server on which the Adapter software is running. A separate log file is created
for each Runtime Service that is run on the application or web server.
The name of each log file is as follows:
<SERVICE_NAME>.log
where:
<SERVICE_NAME> is the name of the Runtime Service
Log files are appended to each time a service is executed.

All events and actions captured in each log file are time-stamped in the following format:
YYYY/MM/DD HH:MM:SS:mmm - <EVENT>
Example:
2007-05-24 13:48:16.523 - Import_CSV_Demo started.
Steps to follow from Oracle Utilities Oracle Utilities Meter Data

Management
Process Control Interface
The Process Control Interface screen displays the status of meter data management import
processes executed by the Energy Information Platform Adapter. This screen is helpful when
researching issues related to import of usage data into Oracle Utilities Meter Data Management.
This screen displays information based on the number of payloads and transactions processed. A
payload is an import file (or database record, or JMS queue message) used to import usage and
meter events. A transaction is a single usage or meter event record within a payload. For more
information see Oracle Utilities Meter Data Management Users Guide Chapter 5.
To View the Process Control Interface

Select Meter Data Management->Operations->Process Control Interface.
64
Viewing Billing Determinant Queue Records

Billing Determinant Queue (BD Queue) records are created for each account submitted as part of
a billing determinant calculation request. Active BD Queue records represent billing determinant
calculations (one for each account) that are currently being processed, and are stored in the BD
Queue table. Archive BD Queue records represent billing determinant calculations that have been
executed, and are stored in the BD Queue Archive table. You view these individual records on
the BD Queue (for active queue records) or BD Queue Archive (for archived queue records)
screen.
To view the BD Queue and BD Queue Archive

Select Data Menu then click on "BD Queue" or "BD Queue Archive" to view the data.
Notifications
Errors in the integration are communicated back to the initiating application. In Oracle Utilities
Meter Data Management the adapter service errors are reported by a HUBInbound exception or
Work Queue item creation.
Information can be found in the log file described above.
Connection Errors
Information can be found the log file described above.
Monitoring from the Integration

To monitor the integration flow using the Integration the following can be used
1. Monitoring the composite instances using Weblogic SOA Enterprise Manager

2. Monitoring the Weblogic logs
Steps to follow for Weblogic SOA Enterprise Manager

1. Login into the Weblogic SOA server Enterprise Manager
2. In the left menu navigate to SOA soa-infra CCB-MDM.
3. All the composite processes deployed for the integration are available under the partition CCB-MDM.
4. Select the appropriate process to list all the instances for the processes sorted by time of execution.
5. The instances also have the request ID as part of the display name.
6. Click the appropriate process instance and it will display the flow for the process.
65
7. The composite flow lists all the activities in the process instance.
Steps to follow for Weblogic logs

1. Login into the machine where the SOA Server is installed
2. The SOA logs are stored in: <Weblogic installation folder>/user_projects/domains/<SOA Domain
name>/servers/<SOA Server name>/logs
For example:
/slot/ems1234/oracle/Middleware/user_projects/domains/soa_domain/servers/soa_server1/lo
gs
Data Purge
The Oracle Fusion Middleware maintains state of the instances and the database needs to be
purged periodically. Refer to Note 815896.1 on Oracle Metalink for details about purging data
from Fusion Middleware database.
66
Chapter 5: Extensibility Options

The Integration Process allows extensibility of transaction messages using the following methods:
Pre Transformation Extension Point
Post Transformation Extension Point
Custom Transformations
Pre Transformation Extension Point

The pre transformation extension point is invoked before the main transformation is executed.
This transformation aids in transforming the source xml coming as an input to the integration
process.
The integration layer defines an external call from the pre transformation extension point. This
extension point accepts source xml as input and gives the source xml as output. The
implementation can choose to plug in an abstract wsdl from a concrete wsdl. This can assist the
implementation in invoking any external web service and transform the input xml.
Post Transformation Extension Point

The post transformation extension point is invoked after the main transformation is executed. This
transformation aids in transforming the target xml going as an input to the target queue.
The integration layer defines an external call from the post transformation extension point. This
extension point accepts the target xml as input and gives the target xml as output. The
implementation can choose to plug in an abstract wsdl from a concrete wsdl. This can assist the
implementation in invoking any external web service and transform the output xml.
Custom Transformations
The custom transformations are used to add data to custom elements in the incoming and
outgoing messages. The incoming and outgoing messages have custom elements defined in the
message. These custom elements refer to a Custom xml schema. The main transformation
invokes custom transformation.
Empty custom transformation and custom schemas are shipped with the product. The
implementation team can add additional fields in the custom schema and map them using the
custom transformations.
Using custom transformations allows the implementation to define and pass additional data from
the source system to the target system.
67
Steps to implement Extension Points

1. Each process in the integration has a pre and post transformation extension point which can be used to
invoke web services and transform the payload.
2. The desired extension point can be triggered from the process by enabling it using the
ConfigurationProperties.xml pre and post transformation extension flags as described in section Setting
Configuration Properties
3. Each process has its own Concrete wsdl which is used to read the endpoint location for the extension
service.
4. These concrete wsdl files are located in MDS under the directories /apps/CCBMDM/AIAMetaData/AIAComponents/ExtensionServiceLibrary/OUCCB and /apps/CCBMDM/AIAMetaData/AIAComponents/ExtensionServiceLibrary/OUMDM
5. The binding, port type and soap address for the extension service can be added in the concrete wsdl in
the installation home folder and the wsdl moved to MDS.
6. To move the wsdl to MDS update the appropriate wsdl in the product install home. The directories in
the product install home are CCB_MDM_INSTALL_HOME/MDSArtifacts/AIAMetaData/AIAComponents/ExtensionServiceLibrary/OUCCB and
CCB_MDM_INSTALL_HOME/MDSArtifacts/AIAMetaData/AIAComponents/ExtensionServiceLibrary/OUMDM.
7. The ConfigurationProperties.xml and the concrete wsdl need to be checked-in into MDS and the soa
server has to be restarted.
8. Refer to command for MDS update in the installation guide to update MDS.
9. Restart the SOA server. On restart the extension point invokes the web service in the concrete wsdl.
For example: To enable the extension points for OUCCBOUMDMSPSyncReqExtension add
the binding and service elements to the OUCCBOUMDMSPSyncReqExtensionConcrete.wsdl
<binding name="OUCCBOUMDMSPSyncReqV1ExtensionServiceSOAP11Binding"
type="ccbext:OUCCBOUMDMSPSyncReqV1ExtensionService">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="PreXformCCBtoMDM">
<soap:operation style="document"
soapAction="http://xmlns.oracle.com/OUCCBOUMDMSPSyncReqEBF/OUCCBOUMDMSPSyncR
eqExtension/V1/PreXformCCBtoMDM"/>
<input>
<soap:body use="literal" parts="CCBToMDM"/>
</input>
<output>
<soap:body use="literal" parts="CCBToMDM"/>
</output>
<fault name="fault">
<soap:fault name="fault" use="literal"/>
</fault>
</operation>
<operation name="PreInvokeMDMEnQueue">
<soap:operation style="document"
68
soapAction="http://xmlns.oracle.com/OUCCBOUMDMSPSyncReqEBF/OUCCBOUMDMSPSyncR
eqExtension/V1/PreInvokeMDMEnQueue"/>
<input>
<soap:body use="literal" parts="MDMEnqueue"/>
</input>
<output>
<soap:body use="literal" parts="MDMEnqueue"/>
</output>
<fault name="fault">
<soap:fault name="fault" use="literal"/>
</fault>
</operation>
</binding>
<service name="OUCCBOUMDMSPSyncReqV1ExtensionService">

<distributionMethod
xmlns="http://xmlns.oracle.com/OUMDM/RequestMessage">
<xsl:value-of
select="/tns1:sendDetails/tns1:syncRequestDetails/tns1:initialSnapshot/tns1:
saInfo/tns1:customElements/tns1:distMethod"/>
</distributionMethod>
</xsl:template>
70
Appendix A: Data Mapping

This section provides mapping details for each integration point.
SA Information Synchronization
SA Sync Request Mapping
CCB SA Sync Request Message
Element Name
Parent
Element
sendDetails
MDM SA Sync Request Message
Type
Element Name
OutermostTag
SyncRequest
syncRequestId
syncRequestId
sendDetails
Field
bo
sendDetails
Field
boStatus
sendDetails
Field
createDateTime
sendDetails
Field
statusDateTime
sendDetails
Field
version
sendDetails
Field
sourceSystem
sendDetails
Field
syncRequired
sendDetails
Field
forceSync
sendDetails
Field
initialLoad
sendDetails
Field
discardReason
sendDetails
Field
cancelReason
sendDetails
Field
mo
sendDetails
Field
pkValue1
sendDetails
Field
pkValue2
sendDetails
Field
pkValue3
sendDetails
Field
pkValue4
sendDetails
Field
pkValue5
sendDetails
Field
saBO
sendDetails
Field
accountBO
sendDetails
Field
personBO
sendDetails
Field
snapshotDA
sendDetails
Field
Parent
Element
Type
DVM Mapping
DVM
OutermostTag
SyncRequest
Field
71
DVM Mapping
postScript
sendDetails
Field
syncRequestDetails
sendDetails
Group
initialSnapshot
sendDetails
Group
initialSnapshot
SyncRequest
Group
personInfo
initialSnapshot
Group
personInfo
initialSnapshot
Group
personId
personInfo
Field
personId
personInfo
Field
name
personInfo
Field
name
personInfo
Field
customElements
personInfo
Group
customElements
personInfo
Group
accountInfo
initialSnapshot
Group
accountInfo
initialSnapshot
Group
accountId
accountInfo
Field
accountId
accountInfo
Field
billCycle
accountInfo
Field
mainPerson
accountInfo
Field
personId
accountInfo
Field
customElements
accountInfo
Group
customElements
accountInfo
Group
saInfo
initialSnapshot
Group
saInfo
initialSnapshot
Group
saId
saInfo
Field
saId
saInfo
Field
accountId
saInfo
Field
accountId
saInfo
Field
cisDivision
saInfo
Field
cisDivision
saInfo
Field
saType
saInfo
Field
saType
saInfo
Field
OUCCB_OUMDM_SAType
status
saInfo
Field
status
saInfo
Field
saStartDate
saInfo
Field
saStartDate
saInfo
Field
saStopDate
saInfo
Field
saStopDate
saInfo
Field
sic
saInfo
Field
sic
saInfo
Field
saRateHistory
saInfo
List
saRateHistory
saInfo
List
effectiveDate
saRateHistory
Field
effectiveDate
saRateHistory
Field
rateSchedule
saRateHistory
Field
rateSchedule
saRateHistory
Field
rateCode
saRateHistory
Field
rateFormCode
saRateHistory
Field
jurisCode
saRateHistory
Field
saSp
saInfo
List
saSp
saInfo
List
saSpId
saSp
Field
saSpId
saSp
Field
spId
saSp
Field
spId
saSp
Field
saSpStartDateTime
saSp
Field
saSpStartDateTime
saSp
Field
72
OUCCB_OUMDM_SIC
DVM Mapping
saSpStopDateTime
saSp
Field
saSpStopDateTime
saSp
Field
howToUse
saSp
Field
howToUse
saSp
Field
usePercent
saSp
Field
usePercent
saSp
Field
customElements
saInfo
Group
customElements
saInfo
Group
customElements
initialSnapshot
Group
customElements
initialSnapshot
Group
finalSnapshot
sendDetails
Group
finalSnapshot
SyncRequest
Group
personInfo
finalSnapshot
Group
personInfo
finalSnapshot
Group
personId
personInfo
Field
personId
personInfo
Field
name
personInfo
Field
name
personInfo
Field
customElements
personInfo
Group
customElements
personInfo
Group
accountInfo
finalSnapshot
Group
accountInfo
finalSnapshot
Group
accountId
accountInfo
Field
accountId
accountInfo
Field
billCycle
accountInfo
Field
mainPerson
accountInfo
Field
personId
accountInfo
Field
customElements
accountInfo
Group
customElements
accountInfo
Group
saInfo
finalSnapshot
Group
saInfo
finalSnapshot
Group
saId
saInfo
Field
saId
saInfo
Field
accountId
saInfo
Field
accountId
saInfo
Field
cisDivision
saInfo
Field
cisDivision
saInfo
Field
saType
saInfo
Field
saType
saInfo
Field
OUCCB_OUMDM_SAType
status
saInfo
Field
status
saInfo
Field
saStartDate
saInfo
Field
saStartDate
saInfo
Field
saStopDate
saInfo
Field
saStopDate
saInfo
Field
sic
saInfo
Field
sic
saInfo
Field
saRateHistory
saInfo
List
saRateHistory
saInfo
Group
effectiveDate
saRateHistory
Field
effectiveDate
saRateHistory
Field
rateSchedule
saRateHistory
Field
rateSchedule
saRateHistory
Field
rateCode
saRateHistory
Field
rateFormCode
saRateHistory
Field
jurisCode
saRateHistory
Field
saSp
saInfo
List
saSp
saInfo
List
OUCCB_OUMDM_SIC
73
saSpId
saSp
Field
saSpId
saSp
Field
spId
saSp
Field
spId
saSp
Field
saSpStartDateTime
saSp
Field
saSpStartDateTime
saSp
Field
saSpStopDateTime
saSp
Field
saSpStopDateTime
saSp
Field
howToUse
saSp
Field
howToUse
saSp
Field
usePercent
saSp
Field
usePercent
saSp
Field
customElements
saInfo
Group
customElements
saInfo
Group
customElements
finalSnapshot
Group
customElements
finalSnapshot
Group
DVM Mapping
SA Sync Response Mapping

MDM SA Sync Response Message
Element
Name
Parent Element
SyncReque
stResult
CCB SA Sync Response Message
Type
Element Name
OutermostTag
F1UpdateAndTransitionSyncR
equest
Parent Element
DVM
Mapping
Type
OutermostTag
syncReque
stId
SyncRequestRe
sult
Field
syncRequestId
F1UpdateAndTransitionSyncRequest
Field
Error
SyncRequestRe
sult
Group
exceptionInfo
Group
messageCategory
Field
messageNumber
Field
sequence
Field
comments
Field
messageParameters
exceptionInfo
List
parameterSequence
messageParameters
Field
messageParameterValue
messageParameters
Field
customElements
Group
ErrorCode
ErrorDesc
customEle
ments
Error
Error
SyncRequestRe
sult
74
Field
Field
Group
DVM
OUCCB_OUMD
M_ErrorCode
SP Information Synchronization
SP Sync Request Mapping
CCB SP Sync Request Message
Element Name
Parent Element
sendDetails
MDM SP Sync Request Message
Type
Element Name
Parent Element
Type
OutermostTa
g
SyncRequest
syncRequestId
SyncRequest
Field
DVM
OutermostTa
g
syncRequestId
sendDetails
Field
bo
sendDetails
Field
boStatus
sendDetails
Field
createDateTime
sendDetails
Field
statusDateTime
sendDetails
Field
version
sendDetails
Field
sourceSystem
sendDetails
Field
syncRequired
sendDetails
Field
forceSync
sendDetails
Field
initialLoad
sendDetails
Field
discardReason
sendDetails
Field
cancelReason
sendDetails
Field
mo
sendDetails
Field
pkValue1
sendDetails
Field
pkValue2
sendDetails
Field
pkValue3
sendDetails
Field
pkValue4
sendDetails
Field
pkValue5
sendDetails
Field
spBO
sendDetails
Field
premiseBO
sendDetails
Field
snapshotDA
sendDetails
Field
postScript
sendDetails
Field
syncRequestDetails
sendDetails
Group
initialSnapshot
syncRequestDetails
Group
initialSnapshot
SyncRequest
Group
spInfo
initialSnapshot
Group
spInfo
initialSnapshot
Group
spId
spInfo
Field
spId
spInfo
Field
premiseId
spInfo
Field
premiseId
spInfo
Field
spType
spInfo
Field
DVM Mapping
75
DVM Mapping
installDate
spInfo
Field
installDate
spInfo
Field
abolishDate
spInfo
Field
abolishDate
spInfo
Field
customElements
spInfo
Group
customElements
spInfo
Group
premiseInfo
initialSnapshot
Group
premiseInfo
initialSnapshot
Group
premiseId
premiseInfo
Field
premiseId
premiseInfo
Field
country
premiseInfo
Field
country
premiseInfo
Field
OUCCB_OUMDM_
Country
addressFormat
premiseInfo
Field
OUCCB_OUMDM_
Country
address1
premiseInfo
Field
address1
premiseInfo
Field
address2
premiseInfo
Field
address2
premiseInfo
Field
address3
premiseInfo
Field
address3
premiseInfo
Field
address4
premiseInfo
Field
address4
premiseInfo
Field
houseType
premiseInfo
Field
houseType
premiseInfo
Field
number1
premiseInfo
Field
number1
premiseInfo
Field
number2
premiseInfo
Field
number2
premiseInfo
Field
inCityLimit
premiseInfo
Field
inCityLimit
premiseInfo
Field
city
premiseInfo
Field
city
premiseInfo
Field
geographic
premiseInfo
Field
geographicCode
premiseInfo
Field
county
premiseInfo
Field
county
premiseInfo
Field
state
premiseInfo
Field
state
premiseInfo
Field
postal
premiseInfo
Field
postal
premiseInfo
Field
customElements
premiseInfo
Group
customElements
premiseInfo
Group
customElements
initialSnapshot
Group
customElements
initialSnapshot
Group
finalSnapshot
syncRequestDetails
Group
finalSnapshot
SyncRequest
Group
spInfo
finalSnapshot
Group
spInfo
finalSnapshot
Group
spId
spInfo
Field
spId
spInfo
Field
premiseId
spInfo
Field
premiseId
spInfo
Field
spType
spInfo
Field
installDate
spInfo
Field
installDate
spInfo
Field
abolishDate
spInfo
Field
abolishDate
spInfo
Field
customElements
spInfo
Group
customElements
spInfo
Group
premiseInfo
finalSnapshot
Group
premiseInfo
finalSnapshot
Group
premiseId
premiseInfo
Field
premiseId
premiseInfo
Field
country
premiseInfo
Field
country
premiseInfo
Field
76
OUCCB_OUMDM_
Country

addressFormat
premiseInfo
Field
address1
premiseInfo
Field
address1
premiseInfo
Field
address2
premiseInfo
Field
address2
premiseInfo
Field
address3
premiseInfo
Field
address3
premiseInfo
Field
address4
premiseInfo
Field
address4
premiseInfo
Field
houseType
premiseInfo
Field
houseType
premiseInfo
Field
number1
premiseInfo
Field
number1
premiseInfo
Field
number2
premiseInfo
Field
number2
premiseInfo
Field
inCityLimit
premiseInfo
Field
inCityLimit
premiseInfo
Field
city
premiseInfo
Field
city
premiseInfo
Field
geographic
premiseInfo
Field
geographicCode
premiseInfo
Field
county
premiseInfo
Field
county
premiseInfo
Field
state
premiseInfo
Field
state
premiseInfo
Field
postal
premiseInfo
Field
postal
premiseInfo
Field
customElements
premiseInfo
Group
customElements
premiseInfo
Group
customElements
finalSnapshot
Group
customElements
finalSnapshot
Group
DVM Mapping
OUCCB_OUMDM_
Country
SP Sync Response Mapping

MDM SP Sync Response Message
Element
Name
Parent Element
SyncReq
uestResu
lt
CCB SP Sync Response Message
Type
Element Name
OutermostT
ag
F1UpdateAndTransitionSync
Request
Parent Element
DVM Mapping
Type
Outermo
stTag
syncReq
uestId
SyncRequestResu
lt
Field
syncRequestId
Request
Field
Error
SyncRequestResu
lt
Group
exceptionInfo
Request
Group
messageCategory
Request
Field
messageNumber
Request
Field
sequence
Request
Field
ErrorCod
e
Error
Field
DVM
OUCCB_OUMDM_Error
Code
77
MDM SP Sync Response Message
ErrorDes
c
Error
Field
CCB SP Sync Response Message
DVM Mapping
comments
Request
Field
messageParameters
exceptionInfo
List
parameterSequence
messageParameters
Field
messageParameterValue
messageParameters
Field
Batch Bill Determinants Mapping

Batch Bill Determinants Request Mapping
CCB Batch BD Request Message
Element Name
Parent Element
sendDetails
MDM Batch BD Request Message
Type
Element Name
Parent Element
Type
OutermostTag
request
usageId
request
Field
createDateTime
request
Field
DVM
OutermostTag
usageId
sendDetails
Field
bo
sendDetails
Field
boStatus
sendDetails
Field
createDateTime
sendDetails
Field
statusDateTime
sendDetails
Field
intervalProcessing
sendDetails
Group
startDateTime
intervalProcessing
Field
startDateTime
request
Field
endDateTimeFrom
intervalProcessing
Field
endDateTime
request
Field
endDateTimeTo
intervalProcessing
Field
scalarProcessing
sendDetails
Group
billingOption
scalarProcessing
Field
startDateTime
scalarProcessing
Field
endDateTime
scalarProcessing
Field
minDaysOffset
scalarProcessing
Field
maxDaysOffset
scalarProcessing
Field
allowEstimate
scalarProcessing
Field
estimateDate
scalarProcessing
Field
isEstimate
scalarProcessing
Field
externalReferenceId
sendDetails
Field
externalReferenceId
request
Field
saId
sendDetails
Field
saId
request
Field
billSegmentId
sendDetails
Field
78
DVM
Mapping
CCB Batch BD Request Message
MDM Batch BD Request Message
version
sendDetails
Field
dateBreaks
sendDetails
List
dateBreaks
request
Group
breakDateTime
dateBreaks
Field
breakDateTime
dateBreaks
List
billCondition
sendDetails
Field
customElements
sendDetails
Group
customElements
request
Group
billCycle
sendDetails
Field
windowStartDate
sendDetails
Field
billModeInfo
sendDetails
Field
billMode
sendDetails
Field
billModeInfo
sendDetails
Field
DVM
Mapping
Batch Bill Determinants Response Mapping

MDM Batch BD Response Message
Element Name
Parent
Element
MDMResponse
CCB Batch BD Response Message
Type
Element Name
OutermostT
ag
C1UpdateUsageRequ
est
Parent Element
Type
DVM
OutermostT
ag
usageId
MDMRespon
se
Field
usageId
C1UpdateUsageRequ
est
Field
usagePeriod
MDMRespon
se
Group
usagePeriod
C1UpdateUsageRequ
est
Group
startDateTime
usagePeriod
Field
startDateTime
usagePeriod
Field
endDateTime
usagePeriod
Field
endDateTime
usagePeriod
Field
scalarProcessing
C1UpdateUsageRequ
est
Group
isEstimate
scalarProcessing
Field
spUsagePeriod
MDMRespon
se
List
spUsagePeriod
C1UpdateUsageRequ
est
List
startDateTime
spUsagePeri
od
Field
startDateTime
spUsagePeriod
Field
endDateTime
spUsagePeri
od
Field
endDateTime
spUsagePeriod
Field
serviceQty
spUsagePeri
od
List
serviceQty
spUsagePeriod
List
DVM Mapping
79
DVM Mapping
mdm_bdi
serviceQty
Field
sqi
serviceQty
Field
OUMDM_OUCCB_BDI
mdm_tou
serviceQty
Field
tou
serviceQty
Field
OUMDM_OUCCB_TOU
mdm_uom
serviceQty
Field
uom
serviceQty
Field
OUMDM_OUCCB_UOM
seq
serviceQty
Field
seq
serviceQty
Field
spId
serviceQty
Field
spId
serviceQty
Field
qty
serviceQty
Field
qty
serviceQty
Field
usagePeriods
MDMRespon
se
List
usagePeriods
C1UpdateUsageRequ
est
List
endDateTime
usagePeriods
Field
endDateTime
usagePeriods
Field
startDateTime
usagePeriods
Field
startDateTime
usagePeriods
Field
usageRequestTyp
e
usagePeriods
Field
usageRequestType
usagePeriods
Field
serviceQty
usagePeriods
List
serviceQty
usagePeriods
List
mdm_uom
serviceQty
Field
uom
serviceQty
Field
OUMDM_OUCCB_UOM
mdm_tou
serviceQty
Field
tou
serviceQty
Field
OUMDM_OUCCB_TOU
mdm_bdi
serviceQty
Field
sqi
serviceQty
Field
OUMDM_OUCCB_BDI
seq
serviceQty
Field
seq
serviceQty
Field
qty
serviceQty
Field
qty
serviceQty
Field
reads
C1UpdateUsageRequ
est
List
spId
reads
Field
readSeq
reads
Field
startReadDateTime
reads
Field
endReadDateTime
reads
Field
uom
reads
Field
tou
reads
Field
sqi
reads
Field
startReading
reads
Field
endReading
reads
Field
measuredQty
reads
Field
finalQty
reads
Field
finalUom
reads
Field
80
OUMDM_OUCCB_Usage
Type
Error
MDMRespon
se
ErrorCode
Error
ErrorDesc
Error
customElements
MDMRespon
se
List
Field

finalTou
reads
Field
finalSqi
reads
Field
sphowToUse
reads
Field
reghowToUse
reads
Field
constant
reads
Field
measuresPeakQuantit
y
reads
Field
usePercent
reads
Field
customElements
reads
Group
exceptionInfo
C1UpdateUsageRequ
est
List
messageCategory
exceptionInfo
Field
messageNumber
exceptionInfo
Field
sequence
exceptionInfo
Field
comments
exceptionInfo
Field
messageParameters
exceptionInfo
Group
parameterSequence
messageParameters
Field
messageParameterVa
lue
messageParameters
Field
customElements
C1UpdateUsageRequ
est
Group
Field
Group
DVM Mapping
OUCCB_OUMDM_ErrorC
ode
Online Bill Determinants Mapping

Online Bill Determinants Request Mapping
CCB Online BD Request Message
Element Name
Parent Element
sendDetails
MDM Online BD Request Message
Type
Element Name
OutermostTag
request
usageId
request
Field
createDateTime
request
Field
usageId
sendDetails
Field
bo
sendDetails
Field
boStatus
sendDetails
Field
createDateTime
sendDetails
Field
Parent Element
Type
DVM
Mapping
DVM
OutermostTag
81
CCB Online BD Request Message
MDM Online BD Request Message
statusDateTime
sendDetails
Field
intervalProcessing
sendDetails
Group
startDateTime
intervalProcessing
Field
startDateTime
request
Field
endDateTimeFrom
intervalProcessing
Field
endDateTime
request
Field
endDateTimeTo
intervalProcessing
Field
scalarProcessing
sendDetails
Group
billingOption
scalarProcessing
Field
startDateTime
scalarProcessing
Field
endDateTime
scalarProcessing
Field
minDaysOffset
scalarProcessing
Field
maxDaysOffset
scalarProcessing
Field
allowEstimate
scalarProcessing
Field
estimateDate
scalarProcessing
Field
isEstimate
scalarProcessing
Field
externalReferenceId
sendDetails
Field
externalReferenceId
request
Field
saId
sendDetails
Field
saId
request
Field
billSegmentId
sendDetails
Field
version
sendDetails
Field
dateBreaks
sendDetails
List
dateBreaks
request
Group
breakDateTime
dateBreaks
Field
breakDateTime
dateBreaks
List
billCondition
sendDetails
Field
customElements
sendDetails
Group
customElements
request
Group
userId
sendDetails
Field
billModeInfo
sendDetails
Field
billMode
sendDetails
Field
billModeInfo
sendDetails
Field
DVM
Mapping
Online Bill Determinants Response Mapping

MDM Online BD Response Message
Element Name
82
Parent
Element
Type
CCB Online BD Response Message

Element Name
Parent Element
Type
DVM Mapping
DVM
MDMResponse
OutermostTa
g
C1UpdateUsageReque
st
DVM Mapping
OutermostTa
g
usageId
MDMRespons
e
Field
usageId
C1UpdateUsageReque
st
Field
usagePeriod
MDMRespons
e
Group
usagePeriod
C1UpdateUsageReque
st
Group
startDateTime
usagePeriod
Field
startDateTime
usagePeriod
Field
endDateTime
usagePeriod
Field
endDateTime
usagePeriod
Field
scalarProcessing
C1UpdateUsageReque
st
Group
isEstimate
scalarProcessing
Field
spUsagePeriod
MDMRespons
e
List
spUsagePeriod
C1UpdateUsageReque
st
List
startDateTime
spUsagePerio
d
Field
startDateTime
spUsagePeriod
Field
endDateTime
spUsagePerio
d
Field
endDateTime
spUsagePeriod
Field
serviceQty
spUsagePerio
d
List
serviceQty
spUsagePeriod
List
mdm_bdi
serviceQty
Field
sqi
serviceQty
Field
OUMDM_OUCCB_B
DI
mdm_tou
serviceQty
Field
tou
serviceQty
Field
OUMDM_OUCCB_T
OU
mdm_uom
serviceQty
Field
uom
serviceQty
Field
OUMDM_OUCCB_U
OM
seq
serviceQty
Field
seq
serviceQty
Field
spId
serviceQty
Field
spId
serviceQty
Field
qty
serviceQty
Field
qty
serviceQty
Field
usagePeriods
MDMRespons
e
List
usagePeriods
C1UpdateUsageReque
st
List
endDateTime
usagePeriods
Field
endDateTime
usagePeriods
Field
startDateTime
usagePeriods
Field
startDateTime
usagePeriods
Field
usageRequestTyp
e
usagePeriods
Field
usageRequestType
usagePeriods
Field
serviceQty
usagePeriods
List
serviceQty
usagePeriods
List
mdm_uom
serviceQty
Field
uom
serviceQty
Field
OUMDM_OUCCB_Us
ageType
OUMDM_OUCCB_U
OM
83
mdm_tou
serviceQty
Field

tou
serviceQty
DVM Mapping
Field
OUMDM_OUCCB_T
OU
mdm_bdi
serviceQty
Field
sqi
serviceQty
Field
OUMDM_OUCCB_B
DI
seq
serviceQty
Field
seq
serviceQty
Field
qty
serviceQty
Field
qty
serviceQty
Field
reads
C1UpdateUsageReque
st
List
spId
reads
Field
readSeq
reads
Field
startReadDateTime
reads
Field
endReadDateTime
reads
Field
uom
reads
Field
tou
reads
Field
sqi
reads
Field
startReading
reads
Field
endReading
reads
Field
measuredQty
reads
Field
finalQty
reads
Field
finalUom
reads
Field
finalTou
reads
Field
finalSqi
reads
Field
sphowToUse
reads
Field
reghowToUse
reads
Field
constant
reads
Field
measuresPeakQuantity
reads
Field
usePercent
reads
Field
customElements
reads
Group
exceptionInfo
C1UpdateUsageReque
st
List
messageCategory
exceptionInfo
Field
messageNumber
exceptionInfo
Field
sequence
exceptionInfo
Field
comments
exceptionInfo
Field
Error
MDMRespons
e
ErrorCode
ErrorDesc
84
Error
Error
List
Field
Field
OUCCB_OUMDM_Er
rorCode
customElements
MDMRespons
e
Group

messageParameters
exceptionInfo
Group
parameterSequence
messageParameters
Field
messageParameterVal
ue
messageParameters
Field
customElements
C1UpdateUsageReque
st
Group
DVM Mapping
Replacement Reads Mapping

Replacement Reads Request Mapping
MDM Replacement Read Request Message
Element Name
Parent Element
ReplacementUsag
e
ID
ReplacementUsag
e
CCB Replacement Read Request Message
Type
Element Name
OutermostTa
g
C1DetAcctCreateCorrectedReadOCB
G
Field
Parent Element
Type
OutermostTag
replacementRead
C1DetAcctCreateCorrectedR
eadOCBG
Group
usageId
replacementRead
Field
externalReferenceId
replacementRead
Field
saList
replacementRead
List
saId
ReplacementUsag
e
List
saId
saList
Field
servicePoint
ReplacementUsag
e
Field
spId
replacementRead
Field
startTime
ReplacementUsag
e
Field
readStartDateTime
replacementRead
Field
stopTime
ReplacementUsag
e
Field
readEndDateTime
replacementRead
Field
meterId
ReplacementUsag
e
Field
customElements
ReplacementUsag
e
Field
customElements
replacementRead
Group
85
Replacement Reads Response Mapping

CCB Replacement Read Response Message
Element Name
Parent Element
sendDetails
MDM Replacement Read Response

Message
Type
Element Name
OutermostTa
g
ReplUsgErr
Parent
Element
Type
DVM
OutermostTa
g
externalReferenceId
sendDetails
Field
ID
ReplUsgEr
r
exceptionInfo
sendDetails
Group
Error
ReplUsgEr
r
Group
messageCategory
exceptionInfo
Field
messageNumber
exceptionInfo
Field
ErrorCode
Error
Field
comments
exceptionInfo
Field
ErrorDesc
Error
Field
messageParameters
exceptionInfo
Group
parameterSequence
messageParameter
s
Field
messageParameterValu
e
messageParameter
s
Field
customElements
sendDetails
Group
customElement
s
ReplUsgEr
r
Group
86
DVM Mapping
Appendix B: Cross References

The following sections provide references for where you can find more information on some of the
terms and entities related to this integration.
Domain Value Maps
Please refer to the chapters titled Working with Domain Value Maps and Using SOA Composer
with Domain Value Maps in the Oracle Fusion Middleware Developer's Guide for Oracle SOA
Suite.
JMS Adapter
Please refer to Oracle Fusion Middleware User's Guide for Technology Adapters for more
information.
Process Flow Diagrams
The following supplemental process flow diagrams are included with the documentation package.
050000 Customer Service.pdf
050600 Deliver Customer Care.pdf
050601 Maintain Customer Information CCB-MDM (Reusable Subprocess).pdf
050603 Fulfill Simple Request.pdf
100000 Billing and Revenue Management.pdf
100100 Manage Meter Data.pdf
100106 Provide Consumption Data to Billing.pdf
87

CCB MDM Implementation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCB MDM Implementation Guide

Uploaded by

Copyright:

Available Formats

Oracle Utilities Customer Care and Billing

Integration to Oracle Utilities Meter Data

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Chapter 1: Participating Applications

Oracle Utilities Customer Care and Billing (CC&B)

Oracle Utilities Meter Data Management (MDM)

This chapter provides a general description of each of these applications.

Oracle Utilities Customer Care and Billing

Oracle Utilities Meter Data Management

Domain Value Map

Java Message Service (JMS)

Oracle Utilities Customer Care and Billing

Oracle Utilities Meter Data Management

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Other General terms to be aware of include:

CC&B Service Agreement

CC&B Service Point

Extensible Markup Language

XML schema definition file.

Service Quantity Identifier

Billing Determinant Identifier

Validation, Estimation and Editing

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Chapter 2: Understanding the Integration

Business Process Overview

Understanding the Integration Processes

Business Process Overview

Batch billing determinants request and response

Online billing determinants request and response

Replacement reads request and response

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

The following diagram provides a visual representation of this processing:

Off Cycle Bill

CCB MDM - Integration Points

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Understanding the Integration Processes

All the end to end integration flows are a-synchronous.

Source application request queue

Source application adds messages to this queue which is then

Source application response

Business errors in the integration and success or failure

Source application request error

Technical errors in the integration request flow are written to this

Source application response

Technical errors when the source application reads the messages

Target application request queue

Integration reads messages from source application request

Target application response

Success or failure acknowledgements from the target application

Target application request error

Technical errors written when the target application tries to read

Target application response error

Technical errors in the integration response flow are written to this

The Request BPEL process includes the following:

JMS Consumer to read from source request queue

JMS Producer to write to the target request queue

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Transformations to convert messages from source format to target format.

Error handling and error notification

The Response BPEL process includes the following

JMS Producer to read from the target response queue

JMS Producer to write to the source response queue