While the system uses a third-party party scheduler to secure and execute its background processes, there are additional issues that you should be familiar with:
Note:
All batch controls are delivered with the
system.
- Batch control records are used for the following purposes:
-
- For processes that extract information, the batch control record defines the next batch number to be assigned to new records that are eligible for extraction. For example, the batch control record associated with the process that extracts bill print information defines the next batch number to be assigned to recently completed bill routings. When this bill print extract process next runs, it extracts all bill routings marked with the current batch number (and increments the next batch number).
- The batch control record for each background process organizes audit information about the historical execution of the background process. The system uses this information to control the restart of failed processes. You can use this information to view error messages associated with failed runs.
- Many processes have been designed to run in parallel in order to speed execution. For example, the process that produces bills in Oracle Utilities Customer Care and Billing can be executed so that bills are produced in multiple "threads" (and multiple threads can execute at the same time). Batch control records associated with this type of process organize audit information about each thread in every execution. The system uses this information to control the restart of failed threads. Refer to Parallel Background Processes for more information.
- Some processes define extra parameters. These parameters are defined with the batch control and will be used when the background process is submitted on-line.
The following diagram illustrates the relationships that exist for batch control records.
Results of each batch run can be viewed using the Batch Run Tree page.