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

Loading Prepaid Data

You can optionally load prepaid billing data into Oracle Self-Service E-Billing, using the EBILL_PPDATALOAD ETL process in Oracle Workflow Builder.

Before loading a prepaid data file, the prepaid account and service agreement numbers must exist in Oracle Self-Service E-Billing. For information on how to provision the required data using Web Services, see Web Services Reference for Oracle Self-Service E-Billing.

The EBILL_PPDATALOAD job loads the prepaid ETL data into the OLAP staging tables, then automatically publishes the data load into the OLAP prepaid fact table.

The EBILL_PPDATALOAD process performs a checksum error evaluation and logs missing or incorrect data.

You use the IN_11_AUTO_REJECT parameter to specify whether to automatically or manually reject a prepaid data file that fails to load correctly:

• Automatic rejection of an unbilled file. Using automatic rejection directs the EBILL_PPDATALOAD job to automatically clear the data and staging tables for an unbilled file that fails to load properly.
• Manual rejection of an unbilled file. Using manual rejection requires that you manually run a rejection process for the failed prepaid file. For details on manually rejecting a prepaid file that failed to load properly, see Rejecting an Unbilled or Prepaid Data File.

It is recommended that you keep not more than three months of prepaid data, as this could result in less efficient reporting analysis on the data. For details on how to purge prepaid data, see Purging Unbilled or Prepaid Data Records.

To run the EBILL_PPDATALOAD process

1. Verify that the required account and service agreement data for the prepay data file has been provisioned in Oracle Self-Service E-Billing.
2. Log in to the Oracle Workflow Builder Design Center as the repository owner.
3. Launch the Control Center from the Tools menu.
4. Expand the EBILLING_ETL_LOCATION, ETL_PF_MODULE, and ETL_SUP nodes.
5. Right click the EBILL_PPDATALOAD node and click Start.
6. Specify the following input parameters.

   Parameter	Description
   IN_01_FILE_NAME_PATTERN	The file name pattern for identifying prepay input file names.
   IN_02_INPUT_PATH	The full directory path where the 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_PPDATALOAD job rejects.
   IN_05_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_06_TO_ADDRESS	The email address to send any notifications sent by the job, such as admin@example.com.
   IN_07_CC_ADDRESS	An email address to copy on any notifications sent by the job, such as admin2@example.com.
   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_SMTP_PORT	The number of the SMTP port to use for sending email notifications.
   IN_10_SMTP_SERVER	The name of the SMTP server to use for sending email notifications.
   IN_11_AUTO_REJECT	Specify whether to automatically reject the current unbilled data if the EBILL_PPDATALOAD fails and clear the data from the associated staging tables. If you specify N to suppress this feature, then if a failure occurs you can reference the staging table data and use the EDX_ETL_CHECKSUM_TROUBLESHOOT process. The ETL log will show the discrepancy between the number of records inserted in the staging table and production fact tables. After successfully determining the cause of the failure, you must manually reject the file before processing your next file. If you specify Y to use the auto reject feature, you will not be able to reference the data that was in the staging tables.

7. A dialog box might appear stating that the object must be deployed before execution. If this dialog appears, then click OK.
8. Review the checksum result in the ETL log table, EDX_RPT_ETL_LOG.

   For more information about resolving checksum errors, see Resolving Checksum Errors.