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

Loading the Oracle BRM Prepaid Data to Oracle Billing Insight

You use a dedicated ODI extract and load process to load prepaid data from Oracle BRM to the Oracle Billing Insight database.

You can schedule prepaid data loading in configurable time periods (the default is every 15 minutes). For details, see Scheduling Unbilled and Prepaid Data Loading.

Only one data load process is allowed at a time.

This task is a step in Process of Setting Up and Integrating Oracle BRM With Oracle Billing Insight.

To load Oracle BRM prepaid data to Oracle Billing Insight

1. Log in to the Oracle Data Integrator as the repository owner.
2. On the Designer tab, expand Load Plans and Scenarios, expand BRMProvider, and expand DATA_LOAD.
3. Right click LOADPREPAIDDATA Version 001 and click Run.
4. Select ODIAgent from the Logical Agent drop-down list.
5. Specify 'NULL' in the Value field for the following variables in the Variable Values dialog:
   • BRMPROVIDER.pStartDate. When set to 'NULL' (in single quotation marks), the FROM_DATE value of EDX_INTG_PROVIDER_LOAD_CTRL table is used. The date format is YYYYMMDDHHMISS.
   • BRMPROVIDER.pEndDate. When set to 'NULL' (in single quotation marks), the sysdate of the Oracle BRM database is used. The date format is YYYYMMDDHHMISS

     To change a value, uncheck the Latest Value check box, and enter the new value. Enclose all string values in single quotation marks.

     Prepaid data generated between the BRMPROVIDER.pStartDate variable (inclusive) and BRMPROVIDER.pEndDate variable (exclusive) load into Oracle Billing Insight.

6. If you want to automatically reject a prepaid load when an error occurs, set the global variable 06_Auto_Reject to 'Y' (in single quotation marks).

   If a load fails, automatic rejection clears the data from the pre-staging tables and the associated staging tables. The data load log will show the discrepancy between the number of records inserted in the staging table and production fact tables. If a failure occurs when using this option, then you will no longer be able to reference the data in the staging tables.

   If you specify N to suppress this feature, you can reference the staging table data if a failure occurs. After successfully determining the cause of the failure, you must manually reject the data load before processing the next file. No other prepaid data can be loaded until the current run data is either published or rejected.