Integration Configuration Checklist
Extensive configuration is required to implement the integration between Oracle Customer Care and Billing and Oracle E-Business Suite. This section provides a list of configuration tasks, including:
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Configuration
The following table provides details for configuring in Oracle E-Business Suite Financials:
Step
Information
Comments
A1
Accounting Flexfield
Identify and document the Accounting Flexfield to be used with the integrated data. You must decide this at the start of the integrations so all the journals are accounted and posted to these accounts.
A2
Ledger ID / Set of Books ID
Document the ledger(s) to which all the accounting entries are to be created and posted. In E-Business Suite Release12, the Ledger ID is used.
A3
Journal Source
Specify the Source of the journal from which it is created.
A4
Journal Category
Specify the Category to which all the journals belong.
A5
Organization ID
Document the AP Operating Unit(s) to be used with the integrated data.
 
Example: ‘Vision Operations’. Derive the Organization ID with respect to the Operating Unit.
 
Example: ‘204’.This is used in checklist step B3.
A6
Payment Terms Code
Create or document the payment terms code(s) to be used for paying AP vouchers coming from Customer Care and Billing.
 
Example: Net07 (CCBREFUND).
A7
Invoice Source
Create the invoice source to be used in Payables Import program.
 
Example: ’CCB’ to group all invoices coming from Oracle Utilities Customer Care and Billing.
A8
Lookup for Multi-Org setup
Populate values in INT_CCB_EBS_MORG_SETUPS lookup for Multi-Org setup.
A9
Country and State Codes
Define/Identify the Country and State codes for addresses. These should match the codes in Customer Care and Billing.
A10
Currency Codes
Currency Codes should match with the currency codes in Customer Care and Billing.
Oracle Utilities Customer Care and Billing Configuration
The following table provides details for configuring in Oracle Utilities Customer Care and Billing:
Step
Information
Comments
B1
GL Division
Configure the GL Division(s) to be used in the integration. Example: US1. This must match the GL Division specified in Integration_Lookup_table.
B2
Distribution Codes
Configure your distribution codes.
 
Example: 01.520.5250.0000.000 with ‘01’ corresponding to Company, ‘520’ corresponding to Department and so on. Refer to details of all mapping segments later in this document. This needs to be set up in sync with the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Flexfield.
B3
Operating Unit Characteristic Type
Configure a characteristic type to hold the value of the Operating Unit to be used. Example characteristic type: EBSORGID.
The value you create in this characteristic (Example: 204) must match what you documented in step A5.
B4
Create Cancel Reason Code
Create a Cancel Reason code.
B5
Link the characteristic type created in step B3 with the CIS Division
The CIS Division you are using (Example: CA) now has a characteristic type linked to it (Example: EBSORGID) that holds the name of the Org ID to use (Example: 204).
B6
General Ledger Characteristic Type
Configure a characteristic type to hold the value of the General Ledger ID for E-Business Suite Release 12. Example characteristic type: GLEDGER.
The value you create in this characteristic (Example: 1) must match what you documented in step A2.
B7
Link the characteristic type created in step B6 with the CIS Division
Add the characteristic type (Example: GLEDGER) to all CIS Divisions and specify the Ledger/Set of Books value to be used (Example: 1).
B8
Payment Terms Characteristic Type
Configure a characteristic type to hold the value of the Payment Terms ID to be used when creating Invoices in E-Business Suite.
 
The value you create in this characteristic must match what you documented in step A6.
B9
Link the characteristic type created in step B8 with the CIS Division
Add the characteristic type (Example: TERMS) to all CIS Divisions and specify the Payment Terms ID value to be used.
Integration Product Configuration
This section provides details on configuration settings for the integration product.
Task
Description
Setting Configuration Properties
Set configurations properties that are used by integration processes. Configuration is done in the INTEGRATION_LOOKUP_TABLE and INTEGRATION_PROCESS_ACTIVATION tables.
Setting BPEL Preference GL_AccountTransformationRequired
This configuration is used by the AP Request Integration Process to determine the delimiter of the GL Account string passed to Oracle E-Business Suite Financials for General Ledger and Accounts Payable AP Invoice Interface tables. By default, GL_AccountTransformationRequired is set to Y which translate the delimiter to a hypen. If this is the delimiter that your implementation needs then nothing needs to be done. If the GL Account obtained from Oracle Utilities Customer Care and Billing needs to be pass as is, then set it to N.
Setting Domain Value Maps
Set domain value maps (DVMs) to map codes and other static values across applications.
Setting Error Handling for the integration
Set up error notification.