Siebel Loyalty Administration Guide > Working with Siebel Loyalty Program Members > About Working with Loyalty Members Using the Siebel Application Interface >

Entering Loyalty Members' Transactions


A Transaction is any action that accrues ("earns") or debits ("burns") points for a member. There are the following types of transactions:

  • Accrual Transactions. The member performs some activity that earns points. Members can accrue points on purchasing products from the host organization or from partners. Some examples are flying between specified cities, staying in a hotel, spending money on a purchase, or selling products.
  • Redemption Transactions. The member redeems points for a reward, such as a product, a service, or an upgrade, and the points are debited from the member's account. The member redeems points for a reward with host, the partner or using the eLoyalty Member Portal.
  • Service Transactions. The member purchases some service, such as enrollment, lounge purchase, membership renewal, or voucher reissue, and the points are debited from the member's account.
  • Custom Transactions. You can also create custom transactions to suit your business model.

These transactions are also listed in the Transactions view of the Loyalty Members screen, so member service representatives can use this view to look at a complete list of member transactions.

When redeeming points for a reward, the member can choose to pay for the transaction entirely with points, or with a combination of points and other values such as cash or a credit card charge.

NOTE:  As an alternative to the Members screen, transactions can also be entered in the Transactions screen. If you require additional fields, then you can add them to the Transactions screen by extending the Transaction business component using Siebel Tools. For more information about Siebel Tools, see Using Siebel Tools.

To enter a transaction

  1. Navigate to the Loyalty Members screen.
  2. In the Members list, click the Member Number (#) field of the member.
  3. Click the Transactions view tab.
  4. Add a new record to the Transactions list, and complete the necessary fields. Some fields are described in the following table.
    Field
    Description

    Transaction Date

    Displays the date when the transaction occurred. This date is used as the date when the customer earns the points.

    NOTE:  To decide whether a promotion applies to a transaction, the Siebel Loyalty Engine evaluates whether the transaction's Transaction Date (not its Processed On Date) is within the promotion's start and end dates, inclusive.

    Type

    Select whether the transaction is Accrual, Redemption, Service, or Custom.

    Sub Type

    Select the Subtype for the transaction:

    • Accrual transactions. The subtypes are: Action Based Bonus, Cancellation, Gift, Loan, Product, Incorrect Accrual, Manual Credit, and Missing Accrual.
    • Redemption transactions. The subtypes are: Availment, Cancellation, Loan Repayment, Manual Debit, Product, and Transfer.
    • Service transactions. The subtypes are: Membership Renewal, Voucher Reissue, Enrollment, Points Purchase, Points Transfer, Membership Cancellation, and Lounge Purchase.
    • Custom transactions. The subtypes depend on the subtypes you define.

    Status

    Select the status of the transaction from these options:

    • In Progress. Default status when a transaction is first created manually.
    • Submitted. The MSR selects this value if manager approval is required for this transaction.
    • Cancelled. The MSR can click the Cancel button to set the value of the status to Cancelled. This status is used to recall a transaction that it has been submitted for approval. After submitting a transaction, the MSR cannot change it without recalling it.
    • Rejected - Manager. The manager selects this value to reject the transaction.
    • Approved. The MSR or manager selects this value to approve the transaction.
    • Acceptable. If the status is Acceptable, then the user can process the transaction in real time by clicking the Process button. The engine does not process transactions with this status; the user must click the Process button. For information about when transactions are created with the status Acceptable, see Allowing Manual Processing of Queued Transactions.
    • Queued. If the status is Queued, then the engine component that is invoked by clicking the Process button does not process this transaction. It is only processed by the batch engine.
    • Partner Pending. Indicates that an action from a partner is required before the transaction can be processed. The possible actions by a partner are Partner Approved and Partner Rejected.

    The field can also display the following values, generated by Siebel Loyalty:

    • Rejected - Engine: Insufficient Points. Siebel Loyalty sets the field to this value if the member does not have enough points for the redemption transaction.
    • Rejected - Engine: Missing Member Data. Siebel Loyalty sets the field to this value if required data about the member is missing.

    Corporate Reference

    Displays the Member ID of an Account Member if the current individual member is on a Corporate flight. The points accrued is controlled by the attributes defined at the Individual Member level (to validate whether he is actually affiliated with a particular corporation) and the Account Member level (to validate accrual type).

    Product Name

    If the subtype is Product, then select the name of the product.

    Base Points

    Displays the minimum number of points a member would receive (if this transaction is an accrual) or use (if this transaction is a redemption). All promotion calculations (such as a 50% bonus) are based on this value.

    Point Type

    Select the base point's type. For more information about point types, see Creating Point Types for Loyalty Programs.

    Qualifying Points

    Displays whether the base points are qualifying or nonqualifying (bonus) points.

    Submit To

    Displays the user ID of the person who must approve the transaction. Defaults to the MSR's manager. The MSR can choose a different value to submit this transaction to someone else for approval. To process the transaction without manager approval, leave this field empty and follow the instructions in Step 6.

    For information about setting up the manager's approval limit, see Adding Employees as Loyalty Users.

  5. You can view more information about a transaction by clicking the hyperlink in the Transaction Id field. Click the Points Items view and look at the Accrual Items list, if this transaction is an accrual transaction, or at the Redemption Items list, if this was a redemption transaction. The Accrual Items list shows all of the points that a member earned for this single transaction. The Redemption Items List shows the original accruals that were used to pay for the redemption. Both these lists are read-only.
  6. If you want to process this transaction without manager approval, then:
    1. Click the hyperlink in the Transaction Id field.
    2. In the More Info form, select the External check box.
    3. In the Transaction form, in the Status field, select Acceptable.
Siebel Loyalty Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.