Overview of Oracle Loyalty Transactions

Setting up loyalty transactions can be done only by a Loyalty Program Administrator or a Loyalty Program Manager. Transactions are any actions that accrue (earn) or debit (burn) points for a member. This chapter describes how to create different types of transactions.

Let's look at the three types of transactions you can use.

Transaction Type

Description

Accrual Transaction

This transaction occurs when the member performs some activity that earns points.

Points are accrued by purchasing products from the host organization, from partners, or when an administrator credits points manually. Some examples are, accruing points for flying between specified cities, staying in a hotel chain, or purchasing certain products. Accrual transactions are also used for other activities, such as giving members enrollment bonuses and referral bonuses.

You, or a member, can also manually create an accrual dispute transaction. There are two types of Accrual dispute transactions: an Incorrect Accrual for a processed transaction, or a Missing Accrual for a missing transaction.

Redemption Transaction

This transaction occurs when the member redeems or exchanges points with the host partner for a reward.

Points are debited from the member's account when they're exchanged for a product, service, upgrade, or when an administrator debits points manually. If you use the Redemption REST API to set up member self-service, points are renewed through self-service.

Point Transfer Transaction

This transaction occurs when the member transfers points to, or receives points from, another member within the same loyalty program.

You can only enter Point Transfer transactions using the Member page, and not the Transactions page.

Integrated point-of-sales systems automatically create transactions. However, you can also manually create transactions directly within Oracle Loyalty. Batch jobs handle transactions by using their own criteria to search for all appropriate transactions with Queued status. These transactions are then processed one by one.

Note:

If you need to expedite an individual transaction, you can do this by manually changing its status to Queued in the UI. But, you can only do this for transactions with In Progress status. The batch engine then picks up and processes these Queued transactions according to its next scheduled run and load setup. For details, see Expedite a Transaction.