Integration Guide for Oracle Billing Insight > Integrating Oracle Billing Insight With Oracle BRM > Loading Oracle BRM Data (Postpay, Unbilled, and Prepay) to Oracle Billing Insight >

Loading Oracle BRM Postpay Data to Oracle Billing Insight

You use a dedicated extract and load process to load Oracle BRM postpay data directly to Oracle Billing Insight or to load into billing data files, depending on the output type you chose when installing BRM Provider (TABLE or FILE). This process lets you load postpay billing data in bulk when performing the initial integration of Oracle BRM and Oracle Billing Insight.

You can configure BRM Provider to trigger the postpay load process using BRM AQAdapter when the bill when the bill utility is run in Oracle BRM. For details, see Configuring BRM Provider.

If BRM AQAdapter and the ODI agent are deployed on different hosts, make sure that the ODI Agent listens on the hostname instead of the localhost.

Only one data load process is allowed at a time. You must load master data and provision account data before loading postpay billing data.

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

To load Oracle BRM postpay 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 LOADPOSTPAIDDATA 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. To change a value, uncheck the Latest Value check box, and enter the new value. Enclose all string values in single quotation marks.
   • 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.

     Bills generated between the BRMPROVIDER.pStartDate variable (inclusive) and BRMPROVIDER.pEndDate variable (exclusive) will be included in the output, generated in the format specified in your BRM Provider configuration:

   • To a Table. When the output type configured in BRM Provider is TABLE, postpay billing data loads directly into a Oracle Billing Insight DIM table.
   • To a File. When the output type configured in BRM Provider is FILE, postpay billing data is generated to a text file in the location you specify in the BRMPROV_BILLFILE_LOCATION parameter. You must upload this file to the Oracle Billing Insight database server where the Oracle Service Cloud hosting team will use the standard Oracle Billing Insight ODI processes to load the 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. If you want to automatically reject a 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 production 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 are generating Oracle BRM output to files, automatic rejection removes files from the BRMPROV_BILLFILE_LOCATION and BRMPROV_TMPFILE_LOCATION directories if files exist.

   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 billing data can be loaded from Oracle BRM until the current run data is either published or rejected.