2Manage Optimized Import
This chapter contains the following:
Known Issue for Optimized Import
Optimized imports use the same CSV template file as standard imports.
However, before running specific optimized imports, for example, importing member data and transaction data, you must remove the attributes in the CSV file that only support standard import, and replace those attributes with the replacement attributes as suggested as listed in the following topics.
Suggested Member Data Attributes for Optimized Import
You can use the optimized import functionality to create, update, or delete your member data.
Before you import member data using optimized import, you must remove the attributes in the CSV file that only support standard import, and replace those attributes with the replacement attributes as suggested as listed in the following table.
Attributes That Only Support Standard Import Mode | Suggested Attributes to Use for Both Standard and Optimized Modes |
---|---|
Status |
StatusCode |
PartyName |
PartyNumber |
ProgramNumber |
LoyProgramName |
AccountTypeCode |
AccntId |
RealTimeBonusFlag |
Not required. |
ReferredByNam |
ReferredByNumber |
RelType |
RelationshipId |
MemberEmailAddress |
Not required. |
EnrollFlag |
Not required. |
AccrualToHouseholdFlag |
Not required. |
CreationSource |
Not required. |
LoyHouseholdName |
Not available |
LoyAccountName |
AccntId |
URL |
Not required. |
HouseholdMemberNumber |
Not available |
Note: For the following attributes, you must first import
your contact data as a prerequisite. Use PartyNumber as the mapping
attribute after importing your contact data.
|
|
PersonName |
PartyNumber |
ContactName |
PartyNumber |
DateOfBirth |
PartyNumber |
WorkPhoneNumer |
PartyNumber |
MobileNumber |
PartyNumber |
AddressLineOne |
PartyNumber |
AddressLineTwo |
PartyNumber |
AddressLineThree |
PartyNumber |
City |
PartyNumber |
Country |
PartyNumber |
County |
PartyNumber |
PostalCode |
PartyNumber |
Province |
PartyNumber |
State |
PartyNumber |
JobTitle |
PartyNumber |
ContactFirstName |
PartyNumber |
ContactLastName |
PartyNumber |
Suggested Transaction Data Attributes for Optimized Import
You can use the optimized import functionality to create, update, or delete your transaction data.
Before you import transaction data using optimized import, you must remove the attributes in the CSV file that only support standard import, and replace those attributes with the replacement attributes as suggested as listed in the following table.
Attributes That Only Support Standard Import Mode | Suggested Attributes to Use for Both Standard and Optimized Modes |
---|---|
ProgramNumber |
ProgramName |
InvOrgId |
OrganizationCode |
Description |
ProductNumber |
TransferPoints |
Not required |
EventName |
Not required. |
BackupInvOrgId |
Not required |
BackupProductNumber |
Not required |
CorpRefName |
CorporateReferenceNumber |
CorpRefMemberId |
CorporateReferenceNumber |
VoucherNumber |
VoucherId |
Suggested Membership Card Data Attributes for Optimized Import
You can use the optimized import functionality to create, update, or delete your membership card data.
Before you import membership card data using optimized import, you must remove the attributes in the CSV file that only support standard import, and replace those attributes with the replacement attributes as suggested as listed in the following table.
Attributes That Only Support Standard Import Mode | Suggested Attributes to Use for Both Standard and Optimized Modes |
---|---|
LoyCardId |
CardNumber |
CardType |
Not required |
CardStatus |
StatusCode |
Add the Required Role and Data Security Policy
Before using optimized mode to import contacts, accounts, and households in a member card data import, you must complete the following procedure to add the required role and data security policy:
-
Log in to the application as the Security Manager user.
-
Open Tools, and then click Security Console.
-
In the Security Console, click Users.
-
Enter "All" and "LOYALTY_PROGRAM_ADMINISTRATOR" in the search fields, and click Search.
-
In the Display Name column, select LOYALTY_PROGRAM_ADMINISTRATOR.
-
Click Roles and enter the "Master Data Management Application Administrator" role in the search field for job roles, and click Search.
-
Click on the search results, and in the Action Menu, select Edit Role and complete the following fields:
-
Name. Master Data Management Application Administrator
-
Code. ORA_ZCH_MASTER_DATA_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB
-
Description. Administers the installation and maintenance of customer data management application and foundation model.
-
-
Click Next.
-
Navigate to step 3, Data Security Policy.
-
Select +Create Data Security Policy.
-
Complete the following fields to create the policy:
-
Policy Name. Grant PII to Social Security Number
-
Database Resource. Search for "Trading Community Party"
-
Data set. all values
-
Actions. Manage Trading Community Person Social Security
-
-
Click OK.
-
From the Data Security Policies edit screen for the role, click Next three times, and then click Save and Close.
-
Assign the new role to the user who's performing the optimized import.