6Import Data for Other Object Types
This chapter contains the following:
Import Your Program Data
Use this topic to import program data into Oracle Loyalty Cloud. You can use the import functionality to create, update, or delete program records.
To import program records, perform the following tasks:
-
Map your source data to Oracle Loyalty Cloud object attributes.
-
Create the source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import activity.
How to Map Your Source Data to Target Object Attributes
To import your program data into Oracle Loyalty Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Loyalty Cloud.
You need to do the following before creating the CSV file for data import:
-
Identify how your source data attributes map to the target object attributes in Oracle Loyalty Cloud.
-
Ensure that the prerequisite steps, such as understanding what attributes are required for importing your objects, are complete.
-
Understand your options for uniquely identifying the records.
-
Ensure parent records exist before importing child records.
-
Identify the target object attributes that are required in the CSV file for a successful import.
Before You Start
There are no prerequisite tasks for importing program data.
Select a Unique Identifier for Your Records
To import data into Oracle Loyalty Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Loyalty Cloud.
The preferred options to uniquely identify an object record are as follows:
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Loyalty Program object, the attribute is ProgramNumber.
-
Internal ID: If you're identifying a record that already exists in Oracle Loyalty Cloud, then you can use the internal ID of the record. An Internal ID is typically a system-generated unique identifier attribute with "id" in the attribute name. You can determine the internal ID of a record by exporting Oracle Loyalty Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Loyalty Program object, this attribute is LoyProgramId.
Required Attributes and Validations
To import data successfully into Oracle Loyalty Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes.
The following table lists the required attributes for importing new program records, required attributes for updating these program records, prerequisite setup tasks for the attributes, and specific validations, if any, for a program import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Loyalty Program record | Updating an Existing Loyalty Program record |
---|---|---|---|---|---|---|
LoyProgramId |
The unique ID for the Loyalty Program record. |
Number |
18 |
None |
Not required |
Conditionally required. A value is required if ProgramNumber is empty. |
ProgramNumber |
The program number. |
Text |
30 |
Not required Oracle Loyalty Cloud generates a program number if one isn't provided in the import file. |
Required |
Conditionally required. A value is required if LoyProgramId is empty. |
Name |
The name of the loyalty program. |
Text |
30 |
None |
Required |
Not required |
ProgramOwner |
The owner of the loyalty program. |
Text |
30 |
None |
Required |
Not required |
You can view the Loyalty Program object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.
Create the Source CSV File
The CSV file is provided as input to the data import process. You must populate the CSV file with the data you want to import into Oracle Loyalty Cloud.
You can either create a CSV file on your own or use templates available in pre-existing mappings. To download a template, do the following:
-
Open Tools, and click Import Management.
-
Click the Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. In the following sample source file, the import CSV file inserts a new program with Name and ProgramOwner attributes.
Name | ProgramOwner |
---|---|
Program Name 1 |
Owner 1 |
Program Name 2 |
Owner 2 |
In the following sample source file, the user enters ProgramNumber or LoyProgramId to identify the record, updating the name of the program in Oracle Loyalty Cloud.
ProgramNumber | Name |
---|---|
PRG0000000041 |
Program Name replaced |
In the following sample source file, the user enters the ProgramNumber or LoyProgramId to identify the program, deleting the program in Oracle Loyalty Cloud by the given ProgramNumber or LoyProgramId.
ProgramNumber | |
---|---|
PRG0000000041 |
|
Create the Import Activity
To import data into Oracle Loyalty Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Loyalty Program from the Object drop-down list.
-
In File Name, browse and upload the required CSV file, and click Next.
-
In the Create Import Activity: Map Fields page, edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Promotion Data
Use this topic to import promotion data into Oracle Loyalty Cloud. You can use the import functionality to create, update, or delete promotion records.
To import promotion records, perform the following tasks:
-
Map your source data to Oracle Loyalty Cloud object attributes.
-
Create the source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import activity.
How to Map Your Source Data to Target Object Attributes
To import your promotion data into Oracle Loyalty Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Loyalty Cloud.
You need to do the following before creating the CSV file for data import:
-
Identify how your source data attributes map to the target object attributes in Oracle Loyalty Cloud.
-
Ensure that the prerequisite steps, such as understanding what attributes are required for importing your objects, are complete.
-
Understand your options for uniquely identifying the records.
-
Ensure parent records exist before importing child records.
-
Identify the target object attributes that are required in the CSV file for a successful import.
Before You Start
You need to set certain options for some attributes in the application before you can populate them. For example, you need to set up a program because promotion data contains references to programs. Also, when importing a child record, ensure that its parent record exists in the database.
Select a Unique Identifier for Your Records
To import data into Oracle Loyalty Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Loyalty Cloud.
The preferred options to uniquely identify an object record are as follows:
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Loyalty Promotion object, the attribute is PromotionNumber.
-
Internal ID: If you're identifying a record that already exists in Oracle Loyalty Cloud, then you can use the internal ID of the record. An Internal ID is typically a system-generated unique identifier attribute with "id" in the attribute name. You can determine the internal ID of a record by exporting Oracle Loyalty Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Loyalty Promotion object, these attributes are as follows:
-
LoyPromoId
-
LoyProgId
-
PartnerId
-
Required Attributes and Validations
To import data successfully into Oracle Loyalty Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes.
The following table lists the required attributes for importing new promotion records, required attributes for updating these promotion records, prerequisite setup tasks for the attributes, and specific validations, if any, for a promotion import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Loyalty Promotion record | Updating an Existing Loyalty Promotion record |
---|---|---|---|---|---|---|
LoyPromoId |
The unique ID for the promotion record. |
Number |
18 |
None |
Not required |
Conditionally required. A value is required if PromotionNumber is empty. |
PromotionNumber |
The PUID of the promotion from which the promotion record can be uniquely identified. |
Text |
30 |
None |
Not required |
Conditionally required. A value is required if LoyPromoId is empty. |
Name |
The name of the promotion. |
Text |
50 |
If providing a value, then the value must be unique. |
Required |
Not required |
ProgramNumber |
The unique ID for the program. |
Text |
30 |
The program must exist. |
Required |
Not required |
TypeCode |
The promotion type code name. The accepted values are ORA_TXN_ACC, ORA_TXN_RED, and so on. |
Text |
30 |
If providing a value, then the value must be a valid, enabled lookup code for lookup type ORA_LOY_TXN_TYPE. |
Required |
Not required |
SubTypeCode |
The promotion subtype name. This attribute is dependent on the TypeCodeName attribute. The accepted values are: A. If Accrual - ORA_ACC_MCR, ORA_ACC_PROD, and so on. B. If Redemption - ORA_RED_PROD, ORA_RED_MDT, and so on. |
Text |
30 |
If providing a value, then the value must be a valid, enabled lookup code for lookup type ORA_LOY_ACCRL_TXN_SUB_TYPE or ORA_LOY_REDEM_TXN_SUB_TYPE. |
Required |
Not required |
You can view the Loyalty Promotion object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.
Create the Source CSV File
The CSV file is provided as input to the data import process. You must populate the CSV file with the data you want to import into Oracle Loyalty Cloud.
You can either create a CSV file on your own or use templates available in pre-existing mappings. To download a template, do the following:
-
Open Tools, and click Import Management.
-
Click the Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. In the following sample source file, the import CSV file uses Name (promotion name) and ProgramNumber information from a legacy system to identify the promotion and program. A value is provided for TypeCode and SubTypeCode to identify the type of promotion being created.
Name | ProgramNumber | TypeCode | SubTypeCode |
---|---|---|---|
SLPromoImport1 |
PRG0000033020 |
ORA_TXN_ACC |
ORA_ACC_PROD |
SLPromoImport2 |
PRG0000033020 |
ORA_TXN_RED |
ORA_RED_PROD |
In the following sample source file, the user enters PromotionNumber to identify the promotion record, updating the name of the promotion in Oracle Loyalty Cloud.
PromotionNumber | Name |
---|---|
PROM0000003001 |
LDemo_Create_Update1 |
PROM0000003002 |
LDemo_Create_Update2 |
In the following sample source file, the user enters the PromotionNumber to identify the promotion, deleting the promotion in Oracle Loyalty Cloud by the given PromotionNumber.
-
You can only delete a promotion if the promotion is in Inactive status.
-
Deletion of tier promotions isn't allowed from an import.
PromotionNumber | |
---|---|
PROM0000003001 |
|
PROM0000003002 |
Create the Import Activity
To import data into Oracle Loyalty Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Loyalty Promotion from the Object drop-down list.
-
In File Name, browse and upload the required CSV file, and click Next.
-
In the Create Import Activity: Map Fields page, edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Promotion Incentive Choice Data
Use this topic to import promotion incentive choice data into Oracle Loyalty Cloud. You can use the import functionality to create, update, or delete promotion incentive choice records.
To import promotion incentive choice records, perform the following tasks:
-
Map your source data to Oracle Loyalty Cloud object attributes.
-
Create the source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import activity.
How to Map Your Source Data to Target Object Attributes
To import your promotion incentive choice data into Oracle Loyalty Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Loyalty Cloud.
You need to do the following before creating the CSV file for data import:
-
Identify how your source data attributes map to the target object attributes in Oracle Loyalty Cloud.
-
Ensure that the prerequisite steps, such as understanding what attributes are required for importing your objects, are complete.
-
Understand your options for uniquely identifying the records.
-
Ensure parent records exist before importing child records.
-
Identify the target object attributes that are required in the CSV file for a successful import.
Before You Start
You need to set certain options for some attributes in the application before you can populate them. For example, you need to set up a promotion because a promotion incentive choice is a child of a promotion. Also, when importing a child record, ensure that its parent record exists in the database.
Select a Unique Identifier for Your Records
To import data into Oracle Loyalty Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Loyalty Cloud.
The preferred options to uniquely identify an object record are as follows:
-
Internal ID: If you're identifying a record that already exists in Oracle Loyalty Cloud, then you can use the internal ID of the record. An Internal ID is typically a system-generated unique identifier attribute with "id" in the attribute name. You can determine the internal ID of a record by exporting Oracle Loyalty Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Loyalty Promotion Incentive Choice object, these attributes are as follows:
-
LoyIncentiveChoiceId
-
PromotionId
-
Required Attributes and Validations
To import data successfully into Oracle Loyalty Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes.
The following table lists the required attributes for importing new promotion incentive choice records, required attributes for updating these promotion incentive choice records, prerequisite setup tasks for the attributes, and specific validations, if any, for a promotion incentive choice import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Loyalty Incentive Choice record | Updating an Existing Loyalty Incentive Choice record |
---|---|---|---|---|---|---|
LoyIncentiveChoiceId |
The unique ID for the incentive choice record. |
Number |
18 |
None |
Not required |
Required |
PromotionNumber |
The promotion for which the incentive choice is created. |
String |
30 |
The promotion must exist and be available for enrollment. |
Required |
Not required |
IncentiveChoice |
The name of the incentive choice. |
String |
50 |
The incentive choice value must be unique. |
Required |
Not required |
DefaultFlag |
The default indicator. |
String |
1 |
If the incentive choice being created is the first incentive choice record for the promotion, then set the default indicator to 'Y'. |
Not required |
Not required |
You can view the Loyalty Promotion object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.
Create the Source CSV File
The CSV file is provided as input to the data import process. You must populate the CSV file with the data you want to import into Oracle Loyalty Cloud.
You can either create a CSV file on your own or use templates available in pre-existing mappings. To download a template, do the following:
-
Open Tools, and click Import Management.
-
Click the Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. In the following sample source file, the import CSV file uses PromotionNumber information from legacy system to identify the Loyalty Promotion for which an incentive choice will be created. A value is provided for IncentiveChoice to uniquely identify the Promotion Incentive Choice record.
PromotionNumber | IncentiveChoice | DescriptionText |
---|---|---|
PROM0000003001 |
ICTest1 |
My first IC record |
PROM0000003001 |
ICTest2 |
My second IC record |
PROM0000003001 |
Text1 |
My text |
In the following sample source file, the user enters LoyIncentiveChoiceId to identify the Promotion Incentive Choice, updating the default value of the promotion incentive choice in Oracle Loyalty Cloud.
LoyIncentiveChoiceId | DescriptionText |
---|---|
300100180801400 |
First IC record |
300100180801401 |
Second IC record |
In the following sample source file, the user enters the LoyIncentiveChoiceId to identify the promotion incentive choice, deleting the promotion incentive choice in Oracle Loyalty Cloud by the given LoyIncentiveChoiceId.
LoyIncentiveChoiceId | |
---|---|
300100180801400 |
|
300100180801401 |
Create the Import Activity
To import data into Oracle Loyalty Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Loyalty Promotion Specific Attribute from the Object drop-down list.
-
In File Name, browse and upload the required CSV file, and click Next.
-
In the Create Import Activity: Map Fields page, edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Promotion Specific Attribute Data
Use this topic to import promotion specific attribute data into Oracle Loyalty Cloud. You can use the import functionality to create, update, or delete promotion specific attribute records.
To import promotion specific attribute records, perform the following tasks:
-
Map your source data to Oracle Loyalty Cloud object attributes.
-
Create the source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import activity.
How to Map Your Source Data to Target Object Attributes
To import your promotion specific attribute data into Oracle Loyalty Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Loyalty Cloud.
You need to do the following before creating the CSV file for data import:
-
Identify how your source data attributes map to the target object attributes in Oracle Loyalty Cloud.
-
Ensure that the prerequisite steps, such as understanding what attributes are required for importing your objects, are complete.
-
Understand your options for uniquely identifying the records.
-
Ensure parent records exist before importing child records.
-
Identify the target object attributes that are required in the CSV file for a successful import.
Before You Start
You need to set certain options for some attributes in the application before you can populate them. For example, you need to set up a promotion because a promotion specific attribute is a child of a promotion object. Also, when importing a child record, ensure that its parent record exists in the database.
Select a Unique Identifier for Your Records
To import data into Oracle Loyalty Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Loyalty Cloud.
The preferred options to uniquely identify an object record are as follows:
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Loyalty Promotion Specific Attribute object, the attribute is Name.
-
Internal ID: If you're identifying a record that already exists in Oracle Loyalty Cloud, then you can use the internal ID of the record. An Internal ID is typically a system-generated unique identifier attribute with "id" in the attribute name. You can determine the internal ID of a record by exporting Oracle Loyalty Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Loyalty Promotion Specific Attribute object, these attributes are as follows:
-
LoyAttrdefnBId
-
PromotionId
-
Required Attributes and Validations
To import data successfully into Oracle Loyalty Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes.
The following table lists the required attributes for importing new promotion specific attribute records, required attributes for updating these promotion specific attribute records, prerequisite setup tasks for the attributes, and specific validations, if any, for a promotion specific attribute import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Loyalty Promotion Specific Attribute record | Updating an Existing Loyalty Promotion Specific Attribute record |
---|---|---|---|---|---|---|
LoyAttrdefnBId |
The unique ID for the Loyalty Promotion Specific Attribute record. |
Number |
18 |
None |
Not required |
Required |
InternalName |
The internal name of the promotion attribute. |
Text |
75 |
The internal name value entered should be unique. Possible values for the internal name attribute are:
|
Required |
Not required |
DisplayName |
The name of the promotion specific attribute. |
Text |
30 |
The display name entered must be unique. |
Required |
Not required |
PromotionNumber |
The unique ID for the promotion. |
Text |
30 |
The promotion must exist. |
Required |
Not required |
DefaultValue |
The default value of the promotion specific attribute. |
Text |
75 |
The default value, if provided, is dependent on the InternalName attribute. |
Not required |
Not required |
You can view the Loyalty Promotion Specific Attribute objects in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.
Create the Source CSV File
The CSV file is provided as input to the data import process. You must populate the CSV file with the data you want to import into Oracle Loyalty Cloud.
You can either create a CSV file on your own or use templates available in pre-existing mappings. To download a template, do the following:
-
Open Tools, and click Import Management.
-
Click the Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. In the following sample source file, the import CSV file uses PromotionNumber information from a legacy system to identify the promotion.
PromotionNunber | InternalName | DisplayName | DefaultValue |
---|---|---|---|
PROM0000003001 |
Number1 |
N1 |
1234 |
PROM0000003001 |
Date1 |
DT2 |
30-07-2019 04:25:55 AM |
PROM0000003001 |
Text1 |
TXT1 |
TestRecord |
In the following sample source file, the user enters LoyAttrdefnBId to identify the promotion specific attribute record, updating the default value of the promotion specific attribute in Oracle Loyalty Cloud.
LoyAttrdefnBId | DefaultValue |
---|---|
300100178776416 |
23456 |
300100179259521 |
Test Record 1 |
In the following sample source file, the user enters the LoyAttrdefnBId to identify the promotion specific attribute, deleting the promotion specific attribute in Oracle Loyalty Cloud by the given LoyAttrdefnBId.
LoyAttrdefnBId | |
---|---|
300100178776416 |
|
300100179259521 |
Create the Import Activity
To import data into Oracle Loyalty Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Loyalty Promotion Specific Attribute from the Object drop-down list.
-
In File Name, browse and upload the required CSV file, and click Next.
-
In the Create Import Activity: Map Fields page, edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity.
The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Promotion Rules Data
Use this topic to import promotion rules data into Oracle Loyalty Cloud or export them from Oracle Loyalty Cloud.
General Prerequisites for Exporting or Importing Promotion Rules
Before you begin exporting or importing promotion rules, make sure that all the setup data required for creating a promotion rule is available and activated. The following is the list of objects used in the rules criteria and action:
-
Promotion objects:
-
Promotion header object
-
Promotion specific attributes
-
Incentive choices
-
-
Program objects:
-
Program level attributes:
-
Member dynamic attributes
-
Member field attributes
-
Transaction attributes
-
Calendar attributes
-
Point total attributes
-
Point type attributes
-
Member tier attributes
-
-
Point types
-
Point subtypes
-
Tiers
-
Event driven rewards
-
-
Other objects:
-
Members (individual and company)
-
Vouchers
-
-
External objects:
-
Products
-
Static Lists (FND_LOOKUP)
-
Partners
-
Prerequisites for Exporting Promotion Rules
When a promotion satisfies the following criteria, you can export the defined rules can be exported to a downloadable file by clicking the Rules Export menu item regardless of whether the promotion is active or not:
-
The promotion must have a minimum of one rule.
-
The promotion rules must be complete, in other words, both the IF and DO blocks must be defined.
-
The promotion rules must be valid at the time of the export. If there are any errors or warnings for any of the rules, then the rules of a promotion can't be exported. You can verify the validity of the rules in the Rules At a Glance tab or by looking into rules through the Manage Rules functionality.
Export the Promotion Rules
To export your promotion rules, complete the following steps:
-
Sign in as a setup user.
-
Open Promotions, and then the desired promotion.
The Edit Promotion window opens.
-
Click the Actions menu, and then Rules Export.
After clicking Rules Export menu item, a downloadable file is available for you to save. This file contains the necessary contents, such as attributes, object mapping information, and serialized promotion rules dictionary, to import rules into another promotion.
The default file name is <Promotion Name>, and type of file is XML. If there are any errors or warnings for the rules, an appropriate error message is displayed.
-
Save the file.
Note: Ensure users don't modify this file. -
If you receive Rules Export errors, the following is sample corrective action to fix certain errors:
-
Sample Error Message: The promotion rules for the promotion {PROMO_NAME} couldn't be exported due to errors. Fix them and try exporting the rules again.
Make sure there are no warnings or errors in the rules. You can view them by clicking Navigator, Promotion, PromotionEdit, Promotion Rules at a Glance tab, and then the Manage Rules view.
-
Sample Error Message: There are no rules defined for this promotion.
This error appears when the promotion doesn't have any rules defined. At least one complete valid rule is required to export rules. User must define a rule.
-
Prerequisites for Importing Promotion Rules
An import of promotion rules imports all the rules in the case of a successful import, but imports none if any import validations fail.
For newly created promotions, the rules import adds all rules to the promotions.
For existing promotions with rules, the rules import overwrites the existing rules with the imported rules.
The following are the prerequisites for promotion rules import:
-
The uploaded import XML file containing promotion rules must be valid.
-
The promotion must be in Inactive status. If the promotion is active, the Rules Import menu item is disabled.
-
All setup data used in the exported promotion must be available and active as needed in this promotion as well, where the rules are being imported.
-
For attributes, Name, data-type and category (Transaction, Point Total, Calendar, and so on) used in the source promotion rule must match with that of the target promotion.
-
For objects like Point type, Point subtype, Tiers, and so on, the promotion name must match between the source and target promotion.
-
-
The type and subtype of the two promotions must match.
-
The kind of promotion must match, for example, Enrollment Required Promotion, Tier Promotion, Base Promotion and Normal Promotion.
Import the Promotion Rules
To import your promotion rules, complete the following steps:
-
Sign in as a setup user.
-
Open Promotions, and then the desired promotion.
The Edit Promotion window opens.
-
Click the Actions menu, and then Rules Import.
-
In the file browser dialog that opens, browse and select the XML file containing the rules, and click OK to upload the file.
-
After uploading exported file, click OK to import the rules.
If all validations are successful, all the rules are imported and the following message is displayed:
You have imported all rules to the promotion.
-
If you receive a Rules Import error message, click the Download link in the message and download the <PromotionName>Import.xml file.
This file contains all the errors for the import process. You can find these errors inside the RulesImportErrorSummary tag of the file. After fixing the errors listed in the downloaded file, you can attempt to import rules again. See the following topic on actions to correct sample errors.
Corrective Actions to Fix Rule Import Errors
The following are actions to take for sample error messages:
Sample Error Message | Corrective Actions |
---|---|
The member dynamic attribute with name Member Preferred Program is either inactive or undefined. |
Check whether an attribute named Member Preferred Program is available and in active status by navigating to Program, Program Level Attributes, and then Member Dynamic Attributes.
|
The member field attribute with the point type name Regular is either inactive or undefined. |
|
The promotion type and subtype don't match the uploaded file's promotion type and subtype. |
|
You must change the data type of point totals attribute YearTotals to data type String. This type must match the promotion rules you're importing. |
|
You can't import enrollment required rules to the promotion with name HighMiles. This isn't an enrollment required promotion. You can only use the enrollment attribute {ENROLL_ATTR_NAME} in an enrollment required promotion. |
This error message appears if you attempt to import rules of an enrollment required promotion into a normal promotion. If possible, you must prevent doing such an import. The kind of promotion between the source and target promotion must match. If you pursue this type of import, then change the promotion to an enrollment required promotion by checking the Enrollment Required check box by navigating to Loyalty, Promotion, and then Promotion Edit. |
The rules can't be imported because the promotion with name {PROMO_NAME} isn't a base promotion. |
You're attempting to import base promotion rules into an unsupported promotion (Tier, Enrollment Required, Normal). Base promotion rules can be imported only to another base promotion. |
The point type with name Regular wasn't found. |
During an import, objects are mapped internally between a source promotion or program to the target promotion or program. They're mapped using the unique identifier, Name. For example, if a point type named Regular is used in the Assign Points action when importing rules into another promotion, a point type named Regular must exist in the target promotion. Otherwise, the import throws this sample error. A similar error can be found for the objects which are mapped as part of the import flow. The following objects are mapped as part of an import (you can navigate to these objects by clicking Navigator, Loyalty, Program, Program Edit, and then the object type):
The following objects aren't mapped as part of an import:
If these unmapped objects are used in the exported rules, then they wouldn't be validated and mapped in the target promotion during import flow. After the import, a warning is displayed for these objects usage in the Rules UI (Manage Rules, Promotion Rules at a Glance) and you must fix them manually before activating them. For static lists, ensure they're available in both the source and target environments, or else fix the rule manually. |
You must provide a valid action for this promotion. The promotion action with name {ACTION_NAME} is invalid. |
Ensure that the type and subtype of the source and target promotions are one and the same. This error message appears if you attempt to import rules which have an action that isn't appropriate for target promotion type and subtype combinations. For example, a Cancel Voucher action isn't applicable for a promotion type of Accrual and subtype of Product. Cancel actions are applicable only for the Cancellation promotion subtype. |
Import Your Member Association Data
Use this topic to import member association data into Oracle Loyalty Cloud. You can use the import functionality to create and update member association records.
To import member association records, perform the following tasks:
-
Map your source data to Oracle Loyalty Cloud object attributes.
-
Create the source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import activity.
How to Map Your Source Data to Target Object Attributes
To import your member association data into Oracle Loyalty Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Loyalty Cloud.
You need to do the following before creating the CSV file for data import:
-
Identify how your source data attributes map to the target object attributes in Oracle Loyalty Cloud.
-
Ensure that the prerequisite steps, such as understanding what attributes are required for importing your objects, are complete.
-
Understand your options for uniquely identifying the records.
-
Ensure parent records exist before importing child records.
-
Identify the target object attributes that are required in the CSV file for a successful import.
Before You Start
You need to set certain options for some attributes in the application before you can populate them. For example, you need to set up a loyalty program and import member data first before you import member association data, because member association data references loyalty programs and members. Also, when importing a child record, ensure that its parent record exists in the database.
Select a Unique Identifier for Your Records
To import data into Oracle Loyalty Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Loyalty Cloud.
The preferred options to uniquely identify an object record are as follows:
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Loyalty Member Association object, the attribute is MemberAssociationPUID.
-
Internal ID: If you're identifying a record that already exists in Oracle Loyalty Cloud, then you can use the internal ID of the record. An Internal ID is typically a system-generated unique identifier attribute with "id" in the attribute name. You can determine the internal ID of a record by exporting Oracle Loyalty Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Loyalty Member Association object, these attributes are as follows:
-
GroupMemberId
-
MemberId
-
Required Attributes and Validations
To import data successfully into Oracle Loyalty Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes.
The following table lists the required attributes for importing new member association records, required attributes for updating these member association records, prerequisite setup tasks for the attributes, and specific validations, if any, for a member association import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Loyalty Member Association record | Updating an Existing Loyalty Member Association record |
---|---|---|---|---|---|---|
AssociationEndDate |
The date when the association between the company or host member and the individual member ends. |
TIMESTAMP |
Not applicable |
None |
Optional |
Optional |
AssociationStartDate |
The date when the association between the company member and individual member begins. |
TIMESTAMP |
Not applicable |
Start date must not duplicate the end date. |
Required |
Required |
GroupMemberNumber |
The PUID of the group (company or household) member. |
Text |
30 |
The company or household member must exist. |
Required |
Required |
MemberAssociationId |
Primary key |
Text |
30 |
None |
Not required |
Required |
MemberAssociationPUID |
The PUID of the member association. |
Text |
30 |
None |
Not required. Oracle Loyalty Cloud will generate the PUID if it isn't provided in the import file. |
Not required |
MemberAssociationType |
The value is from the group member type code, which represents the association type. |
Text |
30 |
None |
Not required |
Not required |
MemberNumber |
The PUID of the individual member. |
Text |
30 |
The individual member must exist. |
Required |
Required |
You can view the Loyalty Member Association object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.
Create the Source CSV File
The CSV file is provided as input to the data import process. You must populate the CSV file with the data you want to import into Oracle Loyalty Cloud.
You can either create a CSV file on your own or use templates available in pre-existing mappings. To download a template, do the following:
-
Open Tools, and click Import Management.
-
Click the Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. In the following sample source file, the import CSV file uses MemberNumber information from a legacy system to identify the member.
AssociationEndDate | MemberName | AssociationStartDate | GroupMemberNumber |
---|---|---|---|
9/1/2021 |
MEM0000040001 |
3/1/2019 |
MEM0000040002 |
9/1/2030 |
MEM0000040001 |
4/1/2019 |
MEM0000040002 |
In the following sample source file, the user enters MemberAssociationId to identify the member association record, updating the value of the AssociationEndDate or AssociationStartDate attribute of the member association in Oracle Loyalty Cloud.
AssociationEndDate | MemberName | AssociationStartDate | GroupMemberNumber |
---|---|---|---|
9/1/2031 |
MEM0000040001 |
3/1/2019 |
MEM0000040002 |
9/1/2030 |
MEM0000040001 |
14/1/2019 |
MEM0000040002 |
Create the Import Activity
To import data into Oracle Loyalty Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Loyalty Member Association from the Object drop-down list.
-
In File Name, browse and upload the required CSV file, and click Next.
-
In the Create Import Activity: Map Fields page, edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do the following:
-
Sign in as a setup user.
-
Open Tools, and click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity.
The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.