Integration Guide for Oracle Billing Insight > Integrating Oracle Billing Insight With Oracle BRM >

Process of Loading Data from Oracle BRM in a Live Production Environment

Once you have completed the initial process of integrating Oracle BRM with Oracle Billing Insight, you perform the following tasks as needed to continuously load and synchronize data from Oracle BRM to Oracle Billing Insight in a live production environment:

1. If there are changes to the Oracle BRM bill item configuration, then you must reconfigure the mapping tables in the pre-staging schema to reflect the changes. For details, see Configuring Mapping Tables.
2. If there are changes to master data in Oracle BRM, then you must load the new data using the master data load ODI process. Master data includes payment types, adjustment types, charge type and sub charge type, product and sub-product information, tariff information, unit type and currency type. For details, see Loading Oracle BRM Master Data to Oracle Billing Insight.

   If you output Oracle BRM master data to a flat file (you set the OUTPUT_TYPE property in the BRMProvider.properties file to FILE when configuring BRM Provider), then also copy the generated master text files to the appropriate load input directory on your Oracle Billing Insight installation, where the Oracle Cloud Service hosting team will load the master data files using the standard ODI load processes described in Administration Guide for Oracle Billing Insight.

3. Run the HierarchyCopy job at beginning of the each new billing period. For details, see Administration Guide for Oracle Billing Insight.
4. Synchronize new or updated Oracle BRM account data in real-time using RESTful Web services with BRM AQAdapter. You can provision account contact information and payment transactions in real-time using RESTful Web services. For more information, see Provisioning Oracle BRM Account Data in Real-Time to Oracle Billing Insight Using BRM AQAdapter.
5. Schedule BRM Provider to initiate loading postpay data from Oracle BRM to Oracle Billing Insight whenever the bill utility is run in Oracle BRM. Once configured, the pin_bill_day utility triggers the custom billRun event, and BRM AQAdapter processes the loading of postpay billing data from Oracle BRM to Oracle Billing Insight. (You can schedule BRM Provider to automatically initiate the postpay data load while configuring BRM Provider. For details, see Configuring BRM Provider.)

   If you output Oracle BRM postpay data to a flat file (you set the OUTPUT_TYPE property in the BRMProvider.properties file to FILE when configuring BRM Provider), then also copy the generated postpay billing files to the appropriate load input directory on your Oracle Billing Insight installation, where the Oracle Service Cloud hosting team will use the standard Oracle Billing Insight ODI processes to load the postpay billing text file into the Oracle Billing Insight database production tables. For details about the standard Oracle Billing Insight ODI processes, see Administration Guide for Oracle Billing Insight.

6. Schedule unbilled (CDR) and prepay data (including last top up, current balance, expiry data, CDR data, and so on) to be loaded by BRM Provider in configurable time periods. The default time interval is every 15 minutes. For details, see Scheduling Unbilled and Prepay Data Loading.

   If you chose to output Oracle BRM data to a flat file (you set the OUTPUT_TYPE property in the BRMProvider.properties file to FILE when configuring BRM Provider), then also copy the generated billing files to the appropriate load input directory on your Oracle Billing Insight installation, where the Oracle Service Cloud hosting team will use the standard Oracle Billing Insight ODI processes to load the unbilled and prepay billing text files into the Oracle Billing Insight database production tables.