Oracle Revenue Management And Billing Implementation
Oracle Revenue Management and BillingIntegration to PeopleSoft Enterprise Financials forGeneral Ledger and Accounts PayableImplementation GuideRevision 1.0E37134-01September, 2012.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationE37134-01Copyright 2012, Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respectiveowners.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure, and areprotected 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, orby any means. Reverse engineering, disassembly, or de-compilation of this software, unless required by law for interoperability, isprohibited.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 RIGHTSPrograms, software, databases, related documentation and technical data delivered to U.S. Government customers are "commercialcomputer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to restrictions andlicense 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 USA, Inc., 500Oracle Parkway, Redwood City, CA 94065.This software is developed for general use in a variety of information management applications. It is not developed or intended for usein any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software indangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures toensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware in dangerous applications.This software and documentation may provide access to or information on content, products and services from third parties. OracleCorporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third partycontent, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurreddue to your access to or use of third party content, products or services.
Table of Contents1.Glossary .12.Solution Overview.22.1Summary .22.2Business Process Task Flow .22.3Best Practices .102.3.12.4One-Time Configuration Settings . 10Solution Flow .152.4.12.4.22.4.32.4.42.4.52.4.62.4.7Integration Prerequisites . 15ODI Process Flow . 15Solution Diagram for Integration using ODI . 15Database Details for Integration . 17Logic Used in the Integration Points . 19Process Scheduling . 22Trouble Shooting . 233.Physical Data Model .244.Configuration .254.1.15.Verifying the Integration.425.1.15.1.25.1.36.GL Extension Point . 45AP Request Extension Point . 45AP Data Extension Point . 46Appendix: A .478.1.19.GL Request . 44AP Request . 44AP data Request . 44Available Extension Points in ODI .457.1.17.1.27.1.38.GL Integration Point . 42A/P Request Integration Point . 42A/P Data Integration Point . 42Running ODI process flows .446.1.16.1.26.1.37.Configuring the Integration . 25PeopleSoft Data Mapping . 47ODI Process Flow .729.1.19.1.29.1.31GL Flow: . 72AP Request Flow . 74APDATA Flow . 77Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB Integration1. GlossaryTermDefinitionRMBGLDLGLAPLKMIKMCKMOracle Revenue Management and Billing SystemGeneral Ledger Download Flat FileGeneral LedgerAccounts PayableLoad Knowledge ModuleIntegration Knowledge ModuleCheck Knowledge Module1Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB Integration2. Solution Overview2.1 SummaryThis document provides information on the integration between Revenue Management and Billing (RMB) and Oracle PeopleSoftEnterprise Financial Management for General Ledger and Accounts Payable using Oracle Data Integrator tool. The sections belowprovide an overview of the participating applications and information regarding the business processes addressed by this integration.2.2 Business Process Task FlowThis integration of products incorporates three areas of key functionality to facilitate the transfer of information between twoapplications. Data is sent from Oracle Revenue Management and Billing to Oracle PeopleSoft Enterprise Financial Management forGeneral Ledger and Accounts Payable and vice versa to support the following transactions and actions:RMBPeopleSoftA bill is created/ cancelledThe general ledger is updated with the journalA payment is created/ cancelledinformation.An adjustment is created / cancelledAn adjustment whose type indicates A/P RequestAn accounts payable Invoice is created and associatedis createdwith a single payment vendorPeopleSoftRMBA payment is created for an invoice related to anPayment information is sent from PeopleSoft to RMB.RMB A/P request.The A/P Request is updated with the paymentA check related to an invoice linked to an A/Pinformation.request is re-issued.A check related to an invoice linked to an A/PThe A/P request and its associated adjustment arerequest is voided and the liability is closed.cancelled.2Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationThe flow of data between the two systems is illustrated below:2.2.1.1 General Ledger ProcessFor general ledger transactions, RMB is considered the sub-ledger and Oracle PeopleSoft Enterprise Financials for GeneralLedger and Accounts Payable is considered the general ledger General Ledger transactions are written in one direction; from RMB to Oracle PeopleSoft Enterprise Financials forGeneral Ledger and Accounts Payable. Financial transactions are moved from the sub-ledger to the general ledger when two consecutive RMB batch processes,GLASSIGN and GLS, are run according to a set schedule. These are standard processes released with RMB. The GLASSIGN and GLS processes group all the financial transactions in RMB that must be included in a batch. TheGL Integration Point looks for batches of financial transactions that are ready to be sent, extracts and summarizes thedata, translates the data from a sub-ledger format to the format required by the general ledger, and writes it to the OraclePeopleSoft Generic Accounting Entry Table PS JGEN ACCNT ENTRY. Once the entries are created in Oracle PeopleSoft Enterprise Financial Management, the standard journal generationprocess must be executed to create the necessary journal entries within the General Ledger.This can be accomplished by scheduling the standard Oracle PeopleSoft Enterprise Financials for General Ledger andAccounts Payable journal generator process or by manually running this process through the standard user interface providedwithin the Oracle PeopleSoft Enterprise Financials for General Ledger and Accounts Payable product. You must set up a3Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB Integrationjournal generator template to facilitate the Journal Generator’s upload of data from the Oracle PeopleSoft EnterpriseFinancials for General Ledger and Accounts Payable staging tables.Figure 1GL Process Flow DiagramThese are the steps for the GL Process flow:1. Run GLASSIGN batch program in RMB which simply calls each GL’s details distribution code’s GL assignmentalgorithm and updates the GL detail with the GL account number. (Ref: Steps 1 & 2 in flow diagram)4Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB Integration2. Run GLS batch program in RMB which creates FT download staging records for all FTs that are ready to be posted to theGL. (Ref: Steps 3 & 4 in flow diagram)3. ODI extracts this FT information from RMB to be interfaced with PeopleSoft. (Ref: Steps 5 , 6 & 7 in flow diagram)4. ODI updates the Next Batch Nbr for GLDL in CI Batch Ctrl table in RMB. (Ref: Step 8 in flow diagram)5. ODI transforms and inserts the data into PeopleSoft Generic Accounting Entry table PS JGEN ACCNT ENTRY(Ref: Steps 9 to 15 in flow diagram)6. ODI updates the Last Update DateTime in CI Batch Ctrl table in RMB. (Ref: Steps 16 in flow diagram)7. Run Journal Import process in PeopleSoft to import FTs. (Ref: Steps 17 in flow diagram)8. Any errors in interface tables must be corrected in PeopleSoft and Journal Import process must be re-run. (Ref: Steps 18 &19 in flow diagram)2.2.1.2 Account Payable Request Process AP Request transactions are written in one direction from RMB to Oracle PeopleSoft Enterprise Financial Management.Customer, customer account, and AP Request information is extracted from RMB and exported to PeopleSoft EnterpriseFinancial Management as single payment voucher information. Once the customer and refund request data is loaded into Oracle PeopleSoft Enterprise Financial Management, by theintegration product, the standard voucher build process must be executed. This can be accomplished using a scheduledprocess or by manually running the process through the standard user interface provided within the Oracle PeopleSoftEnterprise Financial Management product. You must have set up a single payment vendor to represent the RMB refund customers. It is also necessary to pre-configure an accounting entry template in Oracle PeopleSoft Enterprise Financial Management toindicate the accounts that accompany the refund. The integration extracts AP Requests from RMB where the status of the AP Request is ‘N’ indicating the AP Request is ‘NotSelected for Payment’. Once the data has been integrated the integration software updates the AP Request status in RMB to‘R’ indicating it has been ‘Requested for Payment’.5Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationFigure 2 AP Process Flow DiagramThese are the steps in AP Request flow:1. Create and Freeze an Adjustment in RMB and run GLASSIGN batch program. (Ref: Steps 1 & 2 in flow diagram)2. ODI extracts AP Refund Request information from RMB. (Ref: Steps 3 , 4 & 5 in flow diagram)3. ODI updates the Next Batch Nbr for APDL in CI Batch Ctrl table in RMB (Ref: Steps 6 in flow diagram)6Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB Integration4. ODI process transforms and inserts the data into PS AP Voucher Build Interface tables. (Ref: Steps 8 to 13 in flowdiagram)5. ODI updates the status of A/P Request in RMB (Ref: Steps 14 & 15 in flow diagram)6. In case of an error, ODI decrements the Next Batch Nbr for APDL in CI Batch Ctrl table in RMB (Ref: Steps 14)7. Run AP Voucher Build Process in PeopleSoft to import Invoices. Any errors in Interface tables must be corrected inOracle PeopleSoft Enterprise Financial Management. (Ref: Steps 18 & 19 in flow diagram)2.2.1.3 Account Payable Data ProcessAP Data transactions are written in one direction from PeopleSoft to RMB. Payment information for system-generated checks is created and processed in PeopleSoft, then exported to RMB. This Payment information corresponds to the AP Refund Requests originally generated in RMB and exported to PeopleSoftfor payment processing. The AP Data Integration Point updates the original AP Request in RMB with the details of the payment including the checknumber and date. Once a payment has been created in PeopleSoft and the information is integrated to RMB, the AP Request status in RMB isupdated to ‘P’ indicating that the AP Request has been paid. Additional statuses that can occur include ‘C’ – Closed or onHold and ‘X’ – Cancelled.Please refer to the table below to review how canceled payments are handled.PeopleSoftPayment is completedPayment stopped and placed on holdPayment is re-issuedPayment is cancelled and the liability isclosedRMB AP Request Resulting ActionPayment information updated and statuschanges to “P” for PaidPayment status changes to “C” for ClosedPayment information updated and statuschanges to “P” for PaidPayment status changes to “X” forCancelledRMB Adjustment ResultingActionNo changeNo changeNo changeAdjustment is cancelledPayment Cancellation ProcessWhen a payment is cancelled in Oracle PeopleSoft Enterprise Financial Management, the following options are available:Re-Open/ Re-IssueIf a check is cancelled for any reason in Oracle PeopleSoft Enterprise Financials for General Ledger and Accounts Payable,the new information is updated on the AP Request in RMB and the AP Request status is set to ’C’ indicating that the APRequest has been closed.7Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationThe AP Request in RMB only holds the most recent check information sent (no history of checks re-issued).A new payment schedule is created for the voucher and is picked up for payment processing by the pay cycle. When thepayment is re-issued, the new payment information is sent to RMB and the AP Request status in RMB is set to ‘P’ indicatingthat the AP Request has been paid. A payment cannot be re-issued if the corresponding voucher is posted.Re-Open/HoldIf a payment is stopped or voided to be re-opened and put on hold, the cancellation information is sent to RMB as updatesto the AP Request. The AP Request payment status flag in the RMB is set to ‘C’ indicating a ‘Closed’ status. This affects onlythe AP Request, the adjustment in RMB is not impacted.Do not Re-Issue/Close LiabilityIf the payment is voided or stopped and all liability is closed, the integration cancels the AP Request and then calls a servicein RMB to cancel the adjustment related to the request. The AP Request payment status flag in RMB is set to ‘X’ indicating a‘Cancelled’ status. The adjustment transaction is also cancelled using the standard adjustment maintenance object within theRMB application software.An RMB adjustment cancellation algorithm, named CI ADCA-CRTD – ‘Adjustment Cancellation – Create To Do Entry’,can be configured to create a To Do List entry to notify the users about the cancellation of the adjustment and AP Requestwithin RMB. If this algorithm is configured to the adjustment type you are using for AP Refunds, the RMB system creates aTo Do Entry when an adjustment of this type is cancelled.The adjustment cancellation algorithm is shipped and documented as part of standard RMB application software.8Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationFigure 3 AP Data Process Flow DiagramThese are the steps in AP Data process flow when a payment is made in PeopleSoft1. Payment is made in PeopleSoft for Invoices originated from RMB. (Ref: Step 1 in flow diagram)2. ODI transforms and updates the Payment information in RMB and reports any errors in transformation(Ref: Steps 2 to 8 in flow diagram)3. ODI updates the Last Run Date of AP Data Process in Integration Schema. (Ref: Step 9 in flow diagram)9Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationFigure 4 AP Cancellation Data Process Flow DiagramThese are the steps in the AP Data process flow when a payment is cancelled in PeopleSoft1. Payment is cancelled in PeopleSoft for invoices originated from RMB (Ref: Step 1 in flow diagram)2. ODI updates the Cancellation information in RMB. (Ref: Steps 2 to 9 in flow diagram) and reports any errors intransformation. Note that C1AdjustmentMaintenance Service is invoked to cancel an adjustment in RMB.4. ODI updates the Last Run Date of AP Data process in Integration schema. (Ref: Step 10 in flow diagram)2.3 Best PracticesThe following sections provide business information that helps achieve accurate and error-free movement of data between RMB andPeopleSoft.Information on how to configure settings that are specific to the integration is provided in the section titled Configuring theIntegration. Refer to product specific documentation for information on how to complete product specific configuration tasks.2.3.1 One-Time Configuration SettingsSome one-time configuration settings must be coordinated manually to ensure proper results from the movement of data between thetwo applications.10Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationGeneral Ledger ConfigurationOracle PeopleSoft Enterprise Financial Management General Ledger is the source of truth for all General Ledger information. OracleRevenue Management and Billing is considered to be the sub-ledger. It is assumed that the General Ledger has already beenconfigured to accommodate you business needs.Distribution CodesRMB uses distribution codes to map sub-ledger transactions to the General Ledger Accounts. As part of your RMB setup, it isassumed that you have properly mapped your distribution codes to the General Ledger chart of accounts.General Ledger Divisions for Non-Integrated TransactionsIf some of the transactions created in RMB must not be integrated to your General Ledger you must configure a separate GeneralLedger Division for these transactions. You must then configure the integration product to distinguish which General Ledger Divisionmust be integrated with the General Ledger (it ignores all others).2.3.1.1 General Ledger IntegrationOracle PeopleSoft Enterprise Financial Management General Ledger accounts is structured using account segments. These are set upin your existing PeopleSoft Enterprise Financial Management configuration according to your business practices. RMB distributioncodes must be configured to mirror the segments in PeopleSoft. The segment positions are separated by dots '.' in RMB so that thefirst segment is Account, the second segment is Department ID, and so on.Create your chart of accounts in the PeopleSoft Enterprise Financial Management General Ledger then set up your RMB distributioncodes to map to the General Ledger account structure using dot separators.Do not become confused by the dual use of the word account, for the PeopleSoft Enterprise Financial Management general ledgeraccounts and the RMB customer billing accounts. A customer billing account is simply information associated with a customer that isused in the RMB payment and billing process, and does not relate to the PeopleSoft Enterprise Financial Management accountingdefinition of account (General Ledger Account). The RMB distribution code translates to the PeopleSoft Enterprise FinancialManagement general ledger account.2.3.1.1.1 Oracle PeopleSoft Enterprise Financial Management General Ledger SettingsConfigure General Ledger settings in Oracle PeopleSoft Enterprise Financial Management General Ledger according to the followingguidelines, keeping in mind that Oracle PeopleSoft Enterprise Financial Management General Ledger is the source of truth for thegeneral ledger. Journal Generator Process: Schedule the Journal Generator process to create journal vouchers from RMB informationinserted into interface tables by the integration software. When you configure PeopleSoft Enterprise Financial Managementto run this process automatically at a preset time please ensure you have matched this timing with the timing of other actionscompleted by RMB and the integration product. Alternatively you may use the standard user interface within PeopleSoftEnterprise Financial Management to run the Journal Generator process manually.11Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB Integration Accounting Entry Definition: If not already configured, pre-configure an accounting entry definition in PeopleSoftEnterprise Financial Management to indicate the staging table where incoming accounting entries should be stored, and themapping from staging table fields to active chart fields. Ensure that all mandatory fields on the staging tables are mapped. Journal Generator Template: If not already configured, pre-configure a Journal Generator Template in PeopleSoftEnterprise Financial Management to set the journal processing defaults for incoming RMB data. The integration software relies on other PeopleSoft Enterprise Financial Management configuration information including:Business Unit, Calendars, Ledger groups and Ledger. These are normally already configured as part of your implementation.If these do not already exist please configure them for the Integration software to run correctly.2.3.1.1.2 Oracle Revenue Management and Billing General Ledger SettingsConfigure General Ledger settings in Oracle Revenue Management and Billing according to the following guidelines, keeping in mindthat Oracle PeopleSoft Enterprise Financial Management General Ledger is the overriding source for the general ledger. Schedule the GLASSIGN and GLS batch processes to run at an appropriate time of day. These processes get sub ledgerinformation in Oracle Revenue Management and Billing and all information that has not been posted to the General Ledger,making them ready to extract, transform and load to the General Ledger. When you configure Oracle Revenue Managementand Billing to run this process automatically at a preset time, ensure you have coordinated this timing with the timing of otheractions done by PeopleSoft and the integration product. (Alternatively you may use the standard user interface within OracleRevenue Management and Billing to run these batch processes manually). Ensure that Distribution Codes are configured in Oracle Revenue Management and Billing to properly reflect the GeneralLedger accounts that must be debited and credited for each type of financial transaction created.2.3.1.1.3 Integration Software General Ledger SettingsAs part of the technical configuration you must configure the following information: E-mail address of the person who must be notified if the integration software detects and logs an error while performing theintegration The Ledger ID, Ledger Source and Ledger Category to use for journal voucher lines in Oracle PeopleSoft EnterpriseFinancial Management that came from Oracle Revenue Management and Billing through the integration. If you enter an Oracle Revenue Management and Billing GL Division name in the configuration table then only financialtransactions associated with this GL Division are extracted for integration to Oracle PeopleSoft Enterprise FinancialManagement GL. If you want all Oracle Revenue Management and Billing financial transactions to be integrated to OraclePeopleSoft Enterprise Financial Management GL maintain this parameter as “ALL”2.3.1.1.4 AccountingThe following shows the basic accounting debits and credits that can be achieved through the setup indicated above:Oracle Revenue ManagementDebit AccountCredit Accountand Billing EventCharges generated by billing12Accounts ReceivableRevenueCopyright 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Revenue Management and Billing Implementation Guide for PeopleSoft RMB IntegrationCustomer making paymentCashAccounts ReceivableA/P Request adjustmentAccounts ReceivableAccounts Payable Clearing2.3.1.2 Accounts Payable (A/P) Request and A/P Data Integrations2.3.1.2.1 Oracle PeopleSoft Enterprise Financial Management General Ledger A/P SettingsThe PeopleSoft Enterprise Financial Management AP Voucher Build Application Engine Process (AP VCHRBLD) is run asscheduled to read the data from the AP Voucher Build Interface tables and create single payment vouchers corresponding to the RMBAP Requests.PeopleSoft Enterprise Financial Management single payment vendors are used to identify standard customer related information usedfor all AP Requests coming from RMB. These must be setup in PeopleSoft Enterprise Financial Management for the integration toprocess these transactions correctly.Configuration needed for AP Request and AP Payment integrations includes: PeopleSoft Enterprise Financial Management AP Voucher Build Application Engine Process: Schedule this processto create AP Vouchers from Oracle Revenue Management and Billing information inserted into interface tables by theintegration product software. When you configure PeopleSoft Enterprise Financial Management to run this processautomati
An accounts payable Invoice is created and associated with a single payment vendor PeopleSoft RMB A payment is created for an invoice related to an RMB A/P request. Payment information is sent from PeopleSoft to RMB. The A/P Request is updated with the payment A check related to an invoice
Oracle e-Commerce Gateway, Oracle Business Intelligence System, Oracle Financial Analyzer, Oracle Reports, Oracle Strategic Enterprise Management, Oracle Financials, Oracle Internet Procurement, Oracle Supply Chain, Oracle Call Center, Oracle e-Commerce, Oracle Integration Products & Technologies, Oracle Marketing, Oracle Service,
Oracle is a registered trademark and Designer/2000, Developer/2000, Oracle7, Oracle8, Oracle Application Object Library, Oracle Applications, Oracle Alert, Oracle Financials, Oracle Workflow, SQL*Forms, SQL*Plus, SQL*Report, Oracle Data Browser, Oracle Forms, Oracle General Ledger, Oracle Human Resources, Oracle Manufacturing, Oracle Reports,
7 Messaging Server Oracle Oracle Communications suite Oracle 8 Mail Server Oracle Oracle Communications suite Oracle 9 IDAM Oracle Oracle Access Management Suite Plus / Oracle Identity Manager Connectors Pack / Oracle Identity Governance Suite Oracle 10 Business Intelligence
Advanced Replication Option, Database Server, Enabling the Information Age, Oracle Call Interface, Oracle EDI Gateway, Oracle Enterprise Manager, Oracle Expert, Oracle Expert Option, Oracle Forms, Oracle Parallel Server [or, Oracle7 Parallel Server], Oracle Procedural Gateway, Oracle Replication Services, Oracle Reports, Oracle
Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Implementation Guide Preface Audience This document is intended for anyone implementing the Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management. Documentation and Resources
Oracle Database using Oracle Real Application Clusters (Oracle RAC) and Oracle Resource Management provided the first consolidation platform optimized for Oracle Database and is the MAA best practice for Oracle Database 11g. Oracle RAC enables multiple Oracle databases to be easily consolidated onto a single Oracle RAC cluster.
Oracle Utilities Customer Care and Billing Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Implementation Guide Preface This document is intended for anyone implementing the Oracle Utilities Customer Care and Billing Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
Oracle Field Service for the mobile worker to perform the activity. The field activity completion information is sent from Oracle Field Service to Oracle Utilities Customer Care and Billing where it is processed by Oracle Utilities Customer Care and Billing. In addition, the integration supports item/device verification, an ability to send interim
