Administration Guide for Oracle Self-Service E-Billing > Running the ETL Jobs Using Oracle Workflow Manager >

Loading Billed Data

You must load your billing data into Oracle Self-Service E-Billing, using the EBILL_DATALOAD ETL loader process. The EBILL_DATALOAD job loads the ETL data into the OLAP database, then by default automatically publishes the data load into the OLAP production tables and proceeds to update the OLTP database using the LOAD_PRODUCTION process.

You run the EBILL_DATALOAD process from the Design Center in Oracle Workflow Builder. Oracle Warehouse Builder is a single, comprehensive tool for all aspects of data management. It provides data quality, data auditing, fully integrated relational and dimensional modeling, and full life cycle management of data and metadata.

You can optionally run the EBILL_DATALOAD job using the manual publish option. The manual option keeps the data in the OLAP work-in-process (WIP) tables and does not publish the data to production. If you use the manual option, then you must verify the data and run either the Reject_Group_Bill_File or Reject_Master_Bill_File job to reject the data, or run the LOAD_PRODUCTION file to accept the data and complete the ETL publishing process.

CAUTION:  If you are running a catch-up load, then you must load past bill files sequentially and check log files to verify that each load is successful before proceeding to the next period. Also check that multiple files in the same billing period have loaded successfully. If a bill file does not load successfully, then that billing period data might not appear on analytic reports because the Hierarchy Node table might not load correctly.

You also have the option to perform a validation on the billing file to be loaded. This option validates the company-to-group key or account-to-group key for the file. By default, the job does not perform a validation.

CAUTION:  If you run the EBILL_DATALOAD job using the validation option, then you might experience a degradation in performance.

If you load unbilled data into Oracle Self-Service E-Billing, then the EBILL_DATALOAD job also removes unbilled data records. For more information about unbilled data, see Loading Unbilled Data.

To run the EBILL_DATALOAD process

1. Log in to the Oracle Workflow Builder Design Center as the repository owner.
2. Launch the Control Center from the Tools menu.
3. Expand the EBILLING_ETL_LOCATION, ETL_PF_MODULE, and ETL_SUP nodes.
4. Right click the EBILL_DATALOAD node and click Start.
5. Specify the following input parameters.

   Parameter	Description
   IN_01_FILE_NAME_PATTERN	The file name pattern for identifying input file names.
   IN_02_INPUT_PATH	The full directory path where the billing data input file to be loaded to Oracle Self-Service E-Billing is located.
   IN_03_OUTPUT_PATH	The full directory path where you want Oracle Self-Service E-Billing to place the input file for processing.
   IN_04_REJECT_PATH	The full directory path where you want Oracle Self-Service E-Billing to place an input file that the EBILL_DATALOAD job rejects.
   IN_05_PUBLISH	Specify whether the file will be automatically published to production. To automatically publish the load to production, specify A, which is the default. To use the manual publish option, specify M.
   IN_06_REGULAR_LOAD	Specify whether the ETL-Bill file load is for the regular, or current, billing period. If the load is for the regular, or current, billing period, then specify True. The default is True. If this is a catch-up load for a past billing period, then specify False. Catch-up loads are used in the Business Edition of Oracle Self-Service E-Billing only.
   IN_07_DATA_AUDIT_FLAG	Specify whether to run data auditing. To audit the data, specify True. To bypass data auditing, specify False. The default is False.
   IN_08_FROM_ADDRESS	The email address of the address to appear in the from field on email notifications sent by the job.
   IN_09_TO_ADDRESS	The email address to send any notifications sent by the job, such as admin@example.com.
   IN_10_CC_ADDRESS	An email address to copy on any notifications sent by the job, such as admin2@example.com.
   IN_11_SMTP_PORT	The number of the SMTP port to use for sending email notifications.
   IN_12_SMTP_SERVER	The name of the SMTP server to use for sending email notifications.
   IN_13_VALIDATE_PARTN_KEY	Specify whether you want to validate the associations between the company or account data and group keys. To perform key validation, specify Y. To bypass key validation, specify N. The default is N.
   IN_14_AUTO_REJECT	Specify whether to automatically reject the current bill if the EBILL_DATALOAD fails and clear the data from the associated staging tables. If the load fails, then the ETL 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. To automatically reject the load, specify Y. If you specify N to suppress this feature, then if a failure occurs you can reference the staging table data. After successfully determining the cause of the failure, you must manually reject the ETL_Bill file before processing your next ETL_Bill file.
   IN_15_PROVISIONING_INUSE	Specifies whether the application is using provisioning, or loading company, account, and service data using Web Services. If the value is Y, the EBILL_DATALOAD job skips the processes that load data into company, account, and service dimension tables. If you specify N, the EBILL_DATALOAD job loads the company, account, and service data from the billing load file. The default is N.

6. A dialog box might appear stating that the object must be deployed before execution. If this dialog appears, then click OK.