Administration Guide for Oracle Billing Insight > Loading Billing Data Into Oracle Billing Insight >

Process of Loading Billing Data

The process of loading billing data into Oracle Billing Insight using the Oracle Data Integrator (ODI) processes lets you automate your billing load to the degree that works for you. You can automatically publish the data into production or use a manual publish option.

There are separate processes for loading postpay, unbilled, and prepay billing data. Processes for rejecting and completing a load provide additional data management tools.

To load billing data into Oracle Billing Insight, perform the following tasks:

1. Load the provisioning data (changes to the company, account, service agreement, and hierarchy-related objects identified in the billing file) in real-time using Web services. For details, see Methods for Loading Provisioning Data. Provisioning data must be in place before bills for this data can successfully load into Oracle Billing Insight.
2. Run the ODI processes necessary for your billing system requirements:
   • If you are loading a postpay file, load the referenced master file first. For details, see Loading Master Files. (Failure to load the master data referenced in the billing load file will result in checksum errors when loading the billing file.)
   • To load individual postpay billing files, see Loading Postpay Billing Files.
   • To load a file for prepay billing data, see Loading Prepay Billing Files.
   • To load a file for unbilled data, see Loading Unbilled Files.
3. To override a global variable at run time, uncheck the Latest Value check box, and enter the new value. Enter string values enclosed in single quotation marks.
4. To view a list of the processes used in the execution of a file, click the Operations tab, and then expand All Executions.

   Successful processes appear with a green check, and failures appear with red check.

5. To reject a previously loaded billing data, see one of the following:
   • Rejecting Billing Files
   • Rejecting Statements
6. To complete the process of publishing a billing file that was loaded using the manual publishing option, see Publishing a Data Load Manually.
7. The data load and rejection scenarios generate email notifications to report on the success or failure of the task.
8. To review for checksum errors (postpay, unbilled, and prepay files only), see Resolving Checksum Errors.