The system provides base background processes that are an important component of the system. Use the batch control page to view the detailed descriptions of each batch control. In addition, the list of background processes provided in the base product may be viewed in the application viewer's batch control viewer.
The base processes fall into one of the following categories:
Process What’s Ready. These are background processes that create and update records that are "ready for processing". The definition of "ready" differs for every process. For example,
The payment upload process creates payments for every record that is pending
The overdue event monitor activates pending overdue events that have reached their trigger date
Some processes of this type use a business date in their determination of what is ready. If the requester of the process does not supply a specific business date, the system assumes that the current system date should be used. If you need to use a date other than the current date, simply supply the desired date when you request the batch process.
Monitor Processes. This is a subset of the “process what’s ready” category. A periodic monitor batch process is provided for any maintenance object whose business object defines a lifecycle. In addition deferred monitor batch process is provided if a business object supplied in the base product required a deferred process for one of its states. Note that monitor processes can be an important part of your implementation. For example, processing forms requires executing the monitor processes for form batch header, form upload staging, tax form and registration form.
Extract Processes. These processes extract information that is interfaced out of the system. Processes of this type typically extract records marked with a given run number. If the requester of the process does not supply a specific run number, the system assumes that the latest run number should be extracted. If you need to re-extract an historical batch, you can. Simply supply the respective run number when you request the batch process.
Adhoc Processes. These are background processes that are run on an ad hoc basis based on business needs.
To Do Entry Processes. These are background processes whose main purpose is to generate To Do Entry records based on a certain condition. Refer to To Do Entries Created By Background Processes for the details.
Purge Processes. There are a small number of background processes provided to purge historical records from certain objects that generate a large number of entries and may become unwieldy over time.
Object Validation Processes. These background processes are used to validate the master data objects. These programs are typically only run as part of the conversion and upgrade processes.
Referential Integrity Validation Processes. These background processes check the validity of foreign keys on various objects. These programs are typically run as part of the conversion and upgrade processes.
Conversion Processes. There are a series of background processes provided for loading historical data into your production database.
Refer to Batch Process Dependencies for guidelines on setting up your production schedule for the base background processes.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]