Overview of Batch Processing

Let's look at what batch jobs process which objects in Oracle Loyalty.

Object	Batch Job	Description
Transactions	Loyalty Batch Engine Main Job	To process transactions with Queued status, including transactions set to Queued status by either the Oracle Loyalty application (automatically or manually) or the API.
Tiers	Loyalty Batch Engine Main Job	To check tier setups for the tier end (expiration) dates. Once a tier reaches its end date (as compared to the system date), the Oracle Loyalty batch engine performs a tier downgrade or tier requalify for all members in that tier. Note: Tier upgrades occur in real time, and aren't part of batch processing.
Both Tiers and Transactions	Loyalty Batch Engine Main Job	To process both transactions and tier records in the same job.
Points	Batch Engine Point Expiry Main Job	To check program members for point expiration dates. Once points reach their end dates, Oracle Loyalty expires any unused points, reducing the member's point balance. The expiration basis is set when the point type is defined in the loyalty program. Note: Qualifying points don't expire.
Events	Loyalty Event-Driven Rewards Main Job	To generate event transactions.
Point Blocks for Prepaid Partners	Loyalty Partner Debit Main Job	To debit point blocks when members accrue points from transactions with prepaid partners.
Members and Transactions	Delete Loyalty Members and Transactions Main Job	To delete members and related transactional data.

To split the load impact, you can define and schedule multiple jobs to process individual objects. You can schedule processes to run immediately, at a scheduled time, or on a regular basis at a set time.