Batch Categories

A batch process may be categorized for documentation purposes. The base values provided are as follows:

  • Ad Hoc. Processes of this type are run on an ad hoc basis, only when needed. For example, if there is a process to do a mass cancel / correction of data, it would only be run when a situation occurs requiring this.

  • Extract. Extract 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 simply supply the respective run number when you request the batch process.

  • ILM. Information Lifecycle Management jobs are crawler background processes that are associated with the ILM based storage solution.

  • Monitor. Processes of this type are processes related to business objects with a lifecycle state that defines monitor algorithms. The monitor process selects records in a given state and executes its algorithms, which may cause the record to transition to another state or may trigger some other logic to occur. Using configuration, the monitor process may target only specific records. Refer to Monitoring Batch Processes for more information. Note that these types of background processes can be considered a subset of Process What’s Ready

  • Process What’s Ready. Processes of this type create and update records that are “ready” for processing. The definition of “ready” differs for every process. For example, a payment upload process creates payments for every record that is pending. An overdue event monitor activates pending overdue events that have reached their trigger date.

  • Purge. Processes of this type are used to purge historical records from certain objects that generate a large number of entries and may become unwieldy over time.

  • To Do Entry. Processes of this type are used to detect a given situation and create or complete a To Do Entry. Refer to To Do Entries Created by Background Processes for more information.

  • Upgrade. Processes of this type are typically run only one time and are used to populate data in a table based on information that can be determined elsewhere in the system. These are processes that could have been done through an upgrade script, but perhaps due to data volume or timing, the upgrade logic warranted a separate stand-alone process.

  • Upload. Processes of this type are used to upload data from a file into the system.

  • The following categories are related to the data conversion / migration processes:

    • Conversion. Processes of this type are dedicated to converting or migrating data from external applications into the product.

    • Object Validation. Processes of this type are dedicated to validate data within objects for conversion or migration purposes.

    • Referential Integrity. Processes of this type are dedicated to validate referential integrity within objects for conversion or migration purposes.

Note: Additional categories may be introduced by your specific product.