Configuring Oracle Utilities Customer Care and Billing
To configure the Oracle Utilities Customer Care and Billing portion of the integration you must define settings for all three integration points:
Refer to your user documentation for instructions regarding specific steps in Oracle Utilities Customer Care and Billing.
GL Integration Point
To enable this integration point, you must configure the following information in Oracle Utilities Customer Care and Billing:
Configuring GL Division
If you decide to integrate the financial transactions for a specific GL Division in Oracle Utilities Customer Care and Billing to E-Business Suite, identify the GL Division. This must match the GL Division specified in Integration_Lookup_table.
Configuring Distribution Codes
You must map your distribution codes in Oracle Utilities Customer Care and Billing to the appropriate GL Accounts in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL. First configure the distribution codes and then assign them to various entities within Oracle Utilities Customer Care and Billing.
The following table shows a sample configuration of one distribution code. Only fields relevant to the integration are included in this table:
Field Label
Value
Comment
Distribution Code
Example: R-ELERES
The distribution code to be used for financial transactions of a certain type.
Description
Example: Electric residential revenue
A description of how the distribution code is used.
GL Account Algorithm
GLCNST-DFLT
The standard product, or customer modified, algorithm you use for determining the GL Account String from the distribution code.
GL Account Details
1 of 1
Create at least one set of account details as needed by your chosen algorithm above. Only one is used based on status and effective date.
Effective Date
01-01-1900
The date you wish the following GL Account string to become active and used by the system, and therefore the integration software.
Status
Active
Only active status accounts are used by the product and therefore the integration.
GL Account
01.520.5250.0000.000
Input the GL Account String as explained below.
The distribution code links the GL Account to activities. As in the example above, a bill payment receives the code R-ELERES so that this revenue for electric residential service is applied to the account 01.520.5250.0000.000.The Algorithm, GLCNST-DFLT provides the hook which allows the integration to get the GL Account from the distribution code and recognize it in Oracle E-Business Suite to the correct GL Journal entry.
GL Account String
Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL accounts are structured using account segments. These are set up in your existing Oracle E-Business Suite Financials for General Ledger and Accounts Payable system according to your business practices.
Oracle Utilities Customer Care and Billing GL Account positions must be configured to mirror the segments and values in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. The segment positions are fixed in Oracle Utilities Customer Care and Billing so that the first segment is Company, the second segment is Department ID, and so on, as shown in the following table.
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Account Column name
Oracle Utilities Customer Care and Billing Distribution (GL_ACCT ) segment position
Company
Position 1
Department
Position 2
Account
Position 3
Sub-Account
Position 4
Product
Position 5
As you configure the segments, separate each with a dot (.).
Example:
A sample GL Account string is 01.520.5250.0000.000.
When interpreted by the standard mapping in the product, this GL Account String in the sub ledger equates to the following in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL:
• Company - 01
• Department - 520
• Account - 5250
• Sub-Account - 0000
• Product -000
Refer to the data mapping table for details on how the segments must be mapped.
Configuring GLASSIGN, and GLS for Oracle Utilities Customer Care and Billing Extract
To successfully execute extracts from Oracle Utilities Customer Care and Billing, two processes must be configured with the appropriate batch parameters and set to run on a scheduled basis. These processes can be scheduled using the Oracle Utilities Customer Care and Billing scheduling tool or an enterprise scheduler that meets the open architecture standards used by Oracle Utilities Customer Care and Billing.
Configuring the General Ledger ID Characteristic Type
For each CIS Division used in Oracle Utilities Customer Care and Billing, you must configure a Characteristic Value to have the General Ledger ID to be used in Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL.
1. Navigate to Admin menu > C > Characteristic Type to create a Characteristic Type.
The value for this characteristic type stores the value of the Ledger ID for Release 12.0 in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
2. Set up the details on the Characteristic Type as follows:
Field Label
Value
Comment
Characteristic Type
GLEDGER
The code associated with your characteristic type.
Description
General Ledger ID
A description of the use for this characteristic type.
Type of Char Value
Predefined Value
No freeform text is allowed, only a predefined set of values.
Allow Search by Char Val
Allowed
Allow Searches
Characteristic Value
xxx
 
3. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the CIS Division:
Field Label
Value
Comment
Characteristic Entity
CIS Division
This characteristic type can be inserted on a CIS Division.
4. Attach the Characteristic Type (created in step 1) to any CIS Divisions that are used. Navigate to Admin menu > C > CIS Division.
Field Label
Value
Comment
CIS Division
Example: CA
The CIS Division to be used.
Description
Example: California
A description of how the CIS Division is used.
Characteristic Tab
 
 
Effective Date
Example: 01-01-1900
The date you wish the characteristic type and value to become active and used by the system, and therefore the integration software.
Characteristic Type
GLEDGER
The characteristic type you created above.
Characteristic Value
xxx
The characteristic value created above.
AP Request Integration Point
This includes the following:
Language to Fetch the Adjustment Description
The language to be used to fetch the Adjustment Description will be obtained from the Account's Main Person's Language Preference.
Configuring the AP Operating Unit Characteristic Type
For each CIS Division used in Oracle Utilities Customer Care and Billing, you must configure a Characteristic Value to have the AP Operating Unit to be used in Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL.
Complete the following configuration in Oracle Utilities Customer Care and Billing to reference the AP Operating Unit corresponding to the CIS Division.
1. Create a Characteristic Type. Navigate to Admin menu > C > Characteristic Type.
The value for this characteristic type stores the value of the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID. In this example, it is EBSORGID. Add the Org Id of Oracle E-Business Suite Financials for General Ledger and Accounts Payable as a Characteristic value.
2. Set up the details on the Characteristic Type.
Field Label
Value
Comments
Characteristic Type
EBSORGID
The code associated with your characteristic type. This will be used in future steps.
Description
EBS Org ID
A description of the use for this characteristic type.
Type of Char Value
Predefined Value
No freeform text is allowed, only a predefined set of values.
Allow Search by Char Val
Allowed
Allow Searches
Characteristic Value
204
The name of the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID to be used.
Description
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Operating Unit
 
3. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the CIS Division.
Field Label
Value
Comments
Characteristic Entity
CIS Division
This characteristic type can be inserted on a CIS Division.
4. Attach the Characteristic Type (created in step 1) to any CIS Divisions that are used for AP Request Adjustments. In sample data an example is provided as the CA - CIS Division. Navigate to Admin menu > C > CIS Division.
Field Label
Value
Comments
CIS Division
Example: CA
The CIS Division to be used.
Description
Example: California
A description of how the CIS Division is used.
Characteristic Tab
 
 
Effective Date
Example: 01-01-1900
The date you wish the characteristic type and value to become active and used by the system, and therefore the integration software.
Characteristic Type
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID
The characteristic type you created above.
Characteristic Value
Example: 204
The value you gave to the characteristic type created above.
Configuring the Payment Terms ID Characteristic Type
For each CIS Division used in Oracle Utilities Customer Care and Billing, you must configure a Characteristic Value to have the Payment Terms ID to be used in Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL.
1. Create a Characteristic Type. Admin menu > C > Characteristic Type.
The value for this characteristic type stores the value of the Payment Terms ID in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
2. Set up the details on the Characteristic Type.
Field Label
Value
Comments
Characteristic Type
TERMS_ID
The code associated with your characteristic type.
Description
Payment Terms ID
A description of the use for this characteristic type.
Type of Char Value
Predefined Value
No freeform text is allowed, only a predefined set of values.
Allow Search by Char Val
Allowed
Allow Searches
Characteristic Value
xxx
Payment Terms ID in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
3. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the CIS Division.
4. Attach the Characteristic Type (created in step 1) to any CIS Divisions used for AP Request Adjustments. Navigate to Admin menu > C > CIS Division.
Field Label
Value
Comments
CIS Division
Example: CA
The CIS Division to be used.
Description
Example: California
A description of how the CIS Division is used.
Characteristic Tab
 
 
Effective Date
Example: 01-01-1900
The date you wish the characteristic type and value to become active and used by the system, and therefore the integration software.
Characteristic Type
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID
The characteristic type you created above.
Characteristic Value
Example: 204
The value you gave to the characteristic type created above.
Note: Only fields relevant to the integration are included in this table.
AP Data Integration Point
AP payment data is extracted from Oracle E-Business Suite Financials for General Ledger and Accounts Payable when an AP Request invoice is paid. This data is then translated by EBSToCCBAPDataBPELProcess and inserted into the Oracle Utilities Customer Care and Billing AP Request that originally initiated the invoice.
The CCBCancellationWebService invokes the Oracle Utilities Customer Care and Billing service, C1AdjustmentMaintenance, when a payment is canceled and the liability is closed in Oracle E-Business Suite Financials for General Ledger and Accounts Payable . The service uses the cancel reason specified in the integration lookup table when canceling the adjustment associated with an AP Request. The sample data cancel reason comes pre-configured as APVC (Accounts Payable Void Check) in Oracle Utilities Customer Care and Billing version 2.2.0.2 and later.
Verify that the following are configured correctly in Oracle Utilities Customer Care and Billing.
Adjustment Cancel Reason
Create the Adjustment Cancel Reason to be used when canceling an adjustment.
1. Navigate to the Adjustment Cancel Reason portal on the Admin menu.
2. Provide the Cancel Reason and Description.
Cancel Adjustment Service (C1AdjustmentMaintenance)
1. Navigate to the Inbound Service portal on the Admin menu.
2. Verify the XAI Inbound Service details.
Field Label
Value
Comments
XAI Inbound Service Name
Adjustment Maintenance
This service is used to change data associated with adjustment transactions.
Description
Adjustment Maintenance for AP Cancel
 
Long Description
Adjustment Maintenance for AP Cancel
 
Active
Checked
Active checkbox checked.
Request Schema
C1AdjustmentMaintenance.xsd
Used by BPEL to call this service.
Response Schema
C1AdjustmentMaintenance.xsd
Used by BPEL to receive the response from this service.
Transaction Type
Update
Service used to update an existing adjustment transaction.
In Oracle Utilities Customer Care and Billing v2.5.0.x, there is an option to use C1AdjustmentMaintenance IWS (Inbound WebService).
1. Navigate to the Inbound Web Service Deployment portal on the Admin menu.
2. Verify that the Inbound Web Service C1AdjustmentMaintenance is deployed.
3. Click the WSDL link to view C1AdjustmentMaintenance IWS WSDL.