2Implement Oracle Loyalty
This chapter contains the following:
Overview of Oracle Loyalty Implementation
Let's look at what you need to start an implementation of Oracle Loyalty.
First, you need a user with the Application Implementation Consultant role (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB). Here's why it's important. In Oracle Loyalty, the Application Implementation Consultant is responsible for opting into the offerings applicable to your business requirements. This person manages enterprise-wide implementations. Also, this role collaborates with specific application administrators to implement consistent enterprise application setup. This includes architecture, information, rules, and access to all setup tasks across all products.
For more information on this role, see Securing Applications.
Next, before you implement Oracle Loyalty members and transactions, you must set up and configure loyalty programs, partners, and promotions.
For more information on setting up Oracle Loyalty, specifically managing the opt-in and setting up your offerings, see Oracle CX Using Functional Setup Manager.
Oracle Loyalty Offering
You use the Oracle Loyalty offering to create dynamic, cross-industry loyalty programs that drive customer initiatives with promotions and rewards. Examples of these are:
-
Airlines' frequent-flyer programs
-
Retailers' frequent shopper programs
-
Hotels' frequent guest programs
It's a good idea to determine who your best customers are and how you want to affect their behavior. To do this, you must research and analyze your business requirements. For example, in Oracle Loyalty you design a loyalty program that encourages members to use a specific communication channel instead of more traditional channels. This could be persuading more customers to use social media, instead of them contacting your company call center.
Here are the main functional areas of the loyalty offering. For the full list of functional areas and features in this offering, use the Associated Features report.
For more information on the Associated Features report, the information in it, and how to access it, see Oracle CX Using Functional Setup Manager.
| Functional Area | Description |
|---|---|
|
Loyalty Members |
Here you can create, review, and define specific elements of your loyalty program in relation to your enrolled members. Let's say you want to change your program to limit the number of loyalty member groups, or maybe you want to increase the number of membership levels that are available. |
|
Loyalty Transactions |
Here you can create, review, and define specific elements of your loyalty program in relation to your enrolled members' transactions. You might want to use these actions to change your program to encourage members to use specific airports, or to buy specific air fares. |
Oracle Loyalty Public Unique IDs
What is a public unique ID (PUID)? When an application uses document sequencing, it generates a unique number (or ID) for each business object record when it's created in the database. Oracle Loyalty users can't easily read or use unique IDs because of their length and complexity. As an administrator, you can configure the format of the unique ID that's generated, to make it more user-friendly and readable. This user-friendly value is called the public unique ID (PUID). The default format of a PUID is the default object name, followed by a 10-digit number.
A specific number of Oracle Loyalty objects support PUIDs for generating unique sequencing, using an advanced setup with PUID attributes. What does this advanced setup involve? The refers to generating the unique sequence of PUIDs for each business object, or more specifically, generating a specific prefix and radix configuration for each business object. PUID specification mandates that an object, let's say the Members object, must be searched by its PUID, MemberNumber. This table lists the business objects where the PUID attribute is exposed, as well as pickers by PUID attribute:
| Top-Level Object Name | Model Support (PUID Attribute Name) | Object PUID Generation | Global Search By PUID | PUID Exposed by Default in List Management |
|---|---|---|---|---|
|
Member |
MemberNumber |
Supported |
Unsupported |
Supported |
|
Program |
ProgramNumber |
Supported |
Unsupported |
Unsupported |
|
Transaction |
TransactionNumber |
Supported |
Unsupported |
Supported |
|
Promotion |
PromotionNumber |
Supported |
Unsupported |
Unsupported |
This table shows the child objects where the PUID attribute is exposed, as well as pickers by PUID attribute:
| Top-Level Object Name | Model Support (PUID Attribute Name) | Object PUID Generation | Global Search By PUID | PUID Exposed by Default in List Management |
|---|---|---|---|---|
|
MembershipCard |
CardNumber |
Supported |
Unsupported |
Supported |
|
Voucher |
VoucherNumber |
Supported |
Unsupported |
Supported |
|
Bucket |
BucketUid |
Supported |
Unsupported |
Unsupported |
|
RedemptionItem |
ItemNum |
Supported |
Unsupported |
Unsupported |
|
MemberTier |
MemTierNum |
Supported |
Unsupported |
Unsupported |
|
AccrualItem |
AccrualItemNumber |
Supported |
Unsupported |
Unsupported |
|
CompanyMembership |
MemberCorpNumber |
Supported |
Unsupported |
Unsupported |
|
MemberPromotionsEnrolled |
PromoMemNumber |
Supported |
Unsupported |
Unsupported |
Use one these options for setup:
-
Default setup, where you require no implementation steps.
-
Basic setup, which you can configure to a certain degree. If you use this setup, the default setup isn't used.
-
Advanced setup, which is more complex and configurable. This setup is on a per-object basis, whereas the default and basic setups apply to all objects.
Here is more information on the default, basic, and advanced setups, and where to find more information.
| Setup Option | Description | Where to Find More Information |
|---|---|---|
|
Default Setup |
You need no implementation steps for this setup. Oracle Loyalty automatically generates a unique 10-digit numeric ID with a default object prefix for each record. The document sequencing begins with a 1. |
No additional documentation, other than this introduction. |
|
Basic Setup |
In this setup, you set two profile options where you configure the radix (or base numbers and characters) and prefix to use. The application generates an alphanumeric public unique ID instead of the default numeric public unique ID for each record. |
See the Public Unique ID Basic Setup section in Oracle CX Sales Implementing Sales. |
|
Advanced Setup |
In this setup, you define a radix and prefix for each object. It isn't required for the radix and prefix to be different for each object. You can perform an advanced setup for the following extensible Oracle Loyalty objects: Member, Program, Transaction, Member Tier, Card, and Voucher. |
See the Public Unique ID Advanced Setup section in Oracle CX Sales Implementing Sales. |
Public Unique ID Advanced Setup
When you do an advanced setup, you can define a different prefix and numbering radix for each business object. For Oracle Loyalty, the objects are Member and Transaction. If you decide to migrate from an external application using an import, then you can specify PUIDs for Oracle Loyalty objects. If you decide not to specify PUIDs during import, then the Oracle Loyalty application generates PUIDs automatically.
Consider these points:
-
If you enter a prefix value, you must set a radix value. You can't use the prefix setting by itself. The length of a prefix value is 5.
-
If you require a delimiter, then include it as part of the prefix.
-
The concatenated public unique ID and prefix can't exceed the defined field length, which is usually 30 characters.
Here's how you configure the radix and optionally, the prefix, in an advanced setup.
-
Open Setup and Maintenance and then select Sales from the Setup menu.
-
In the Functional Areas list, click Sales Foundation.
-
In the Sales Foundation pane, select All Tasks from the Show menu, and then click the Manage Public Unique Identifier Sequence Generation.
This opens the Manage Public Unique Identifier Sequence Generation page.
-
If you're configuring these values for the first time, select Add Row from the Actions menu to add a row to the table.
-
In the Object Name menu, select the object for which you're configuring the public unique ID.
-
In the Prefix box, enter the prefix you want to use for the object and unique ID.
-
Enter a maximum of five characters.
-
The allowed characters are: 0-9, A-Z, a-z, and these special characters: period, hyphen, comma, and underscore.
-
-
In the Radix menu, select the base numbering to use.
-
Repeat for other objects.
-
Click Save and Close.
This table lists options for RADIX in the Manage Public Unique Identifier Sequence Generation task. For example, this is what the sequence looks like if a Member Number is in the format of "MemberNumber":
-
"MEM0000000001" if the Advance Setup for Member object isn't setup.
-
If the Advance Setup for Member object is setup, then the MemberNumber is created in the form of "MemberNumber" = "MEMBER_106065",
-
PREFIX is MEMBER_ and RADIX is "106065" which is in the format of "No Alphanumeric Conversion".
-
RADIX is in the format of "Letters A-Z, Upper Case". "MemberNumber": "MEMBER_GAXM",
| Prefix | Radix |
|---|---|
|
NULL |
NULL |
|
NULL |
Numbers 0-9, letters A-F |
|
NULL |
Numbers 0-9, letters A-F |
|
A- |
Numbers 0-9, letters A-F |
|
A- |
Numbers 0-9, letters A-F |
|
Null |
No alphanumeric conversion |
|
A- |
Numbers 0-9, letters A-Z, letters a-z |
|
A- |
Numbers 0-9, letters A-Z upper case |
|
A- |
Numbers 0-9, letters ABCDEFGHJKLMNPQRTUWXY |
|
A- |
Numbers 2-9, letters BCDFGHJKLMNPQRSTVWXYZ |
|
A- |
Letters A-Z, Upper Case |
|
A- |
Numbers 0-9, letters A-F |