Siebel Loyalty Administration Guide > Getting Started with Siebel Loyalty > Configuring Siebel Loyalty >

Setting Up Custom Transaction Types for Siebel Loyalty


Custom transactions give you the ability to create new types of transactions, as subtypes of the Custom type, that are not available as standard transaction types of Siebel Loyalty.

This feature enables you to create new transaction subtypes of the transaction type Custom for services that are not available as standard Siebel Loyalty transaction types or subtypes, such as duplicate card issue, baggage loss, walk-in fee, and other services for which you can charge members monetary fees, monetary fees and points, or points alone. You can define promotions exclusively for each of these custom transaction subtypes so that the Loyalty engine evaluates only these promotions.

NOTE:  The functionality described in this topic requires that you install Siebel CRM Release 8.1.1.10 or later. For information, see the applicable Siebel Maintenance Release Guide on My Oracle Support.

When member service representatives create a custom transaction, they use the following fields:

  • Transaction Type. The user selects Custom Transaction in the Transaction Type field.
  • Transaction Sub Type. You can create custom values for the Transaction Sub Type field for the user to select when the type is Custom Transaction. You cannot create custom subtypes for other transaction types.

For more information about how member service representatives create transactions, see Entering Loyalty Members' Transactions.

Custom promotions cannot be part of a promotion design. The Assign Points, Update Attribute and Redeem Points actions are supported for Custom promotions.

To set up custom transactions, the Loyalty Administrator must do the following:

  • Define the product used by the custom transaction in a similar way that you would define an accrual or redemption product. You can define a single product for all custom transactions or different products for different varieties of custom transactions. The transaction type field in the Points tab for the product must be Custom. A partner product offering is not required for custom transactions. For more information about defining products, see Defining Loyalty Products, Price Lists, and Catalogs.
  • Create a transaction subtype to be selected by the member service representative. This is created in the Administration - Data screen, List of Values view by adding records with the Type LOY_TXN_SUB_TYPE_CD, as described in the procedure below.
  • Create a promotion to perform the actions needed for this custom transaction. In the Apply To field in the Promotion list, select Custom. Create rules with the criteria that check the value in the Transaction Sub Type field of the transaction and that execute the actions for this custom transaction if it is the appropriate subtype; in the Apply to field of the rules, select Transaction. For more information about creating promotions, see Setting Up Siebel Loyalty Promotions.

Defining Custom Transaction Subtypes

Use this procedure to define custom transaction subtypes.

NOTE:  The transaction type LOY_TXN_TYPE_CD and the promotion subtype LOY_PROMOTION_SUB_TYPE with the value Custom are included in the seed data.

To define custom transaction subtypes

  1. Navigate to the Administration - Data screen, List of Values view.
  2. Add new records of this type and complete the necessary fields. There must be one record for each of the display values that you want for subtypes. Some fields are described in the following table.
    Field
    Description

    Type

    Enter LOY_TXN_SUB_TYPE_CD.

    Display Value

    Enter a value to be displayed in the subtypes picklist when the transaction is created.

    Parent LIC

    Select CUSTOM.

  3. Click Clear Cache.

    NOTE:  New values do not go into effect unless you click Clear Cache.

Example of Creating a Custom Transaction

This topic gives one example of creating custom transactions. You might use this feature differently, depending on your business model.

The Loyalty administrator wants to create a custom transaction type for duplicate card issue, which gives members discounts based on their tier. Bronze members are not eligible for any discount, silver members are eligible for a 25% discount, gold members are eligible for 50% discount, and platinum members get the service at no cost.

To do this:

  • The Loyalty administrator uses the Administration Product screen to add a product, and select Custom as the product type in the Points view for that product. The product might be named Custom Services if it is a generic product to be used by all custom transactions, or it might be named Duplicate Card if it is a product to be used specifically for this custom service.
  • The Loyalty administrator creates a new custom transaction subtype by adding a record in the Administration - Data screen, List of Values view with the values shown in the following table.
    Field
    Value

    Type

    LOY_TXN_SUB_TYPE_CD

    Display Value

    Duplicate Card Issue

    Parent LIC

    CUSTOM

  • The Loyalty administrator writes a promotion with Custom selected in the Apply To field. This promotion has rules that check the value in the transaction's subtype field to see that it is Duplicate Card Issue, calculate the fee with the appropriate discount for the tier that the member is in, and charge the member the appropriate fee for issuing a duplicate card.
  • After this setup is complete, member service representatives can create transactions and selects Custom in the Type field and Duplicate Card Issue in the Sub type field, and the promotion charges the member the appropriate fee.

    For example, a silver member telephones the call center and asks for a duplicate card. The member service representative creates a transaction, selects Custom in the Type field and selects Duplicate Card Issue in the Sub Type field. The promotion is executed and charges the member a fee that is discounted 25% from the full price of getting a duplicate card.

Siebel Loyalty Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.