Purpose: This screen includes the following system control values for integration with Oracle Retail Customer Engagement:
• ORCE Customer Integration (L37)
• MICROS Integration Item ID (L38)
• Item for Non-Merchandise Amounts (L39)
• Cross Channel Orders to Exclude in Sales Feed (L35)
• Return Disposition Code to Exclude in ORCE Sales Feed (M22)
• Merchandise Only in Sales Feed (L36)
• ORCE Organization Descriptor (L50)
• Send Profile Data to ORCE (L51)
• Default Location for ORCE Integration (K69)
• Prompt to Join Loyalty (M07)
• ORCE Loyalty Card Prefix (M08)
• ORCE Loyalty Card Series Sequence Number (M09)
• ORCE Loyalty Registration Notification Email Program (M10)
Each is described below.
ORCE Customer Integration (L37)
Purpose: Defines how Order Management System communicates customer information with Oracle Retail Customer Engagement.
Code field: Set this field to:
• SALES: Order Management System populates the Oracle Retail Customer Engagement Customer file with a Customer Engagement Add or Update Customer Message based on customer activity when you run the Oracle Retail Customer Engagement Sales Feed. In this situation, the file includes only sold to customers that are associated with the invoices in the Customer Engagement Post POSlog Transaction Message. Use this setting if Order Management System is the system of record for customer information. Note: You cannot set this field to SALES if the Use ORCE Loyalty (M06) system control value is selected.
• INTERACT: Order Management System communicates interactively with Oracle Retail Customer Engagement when you create or update a customer, and also populates the Oracle Retail Customer Engagement Customer file with a Customer Engagement Add or Update Customer Message based on customer activity when you run the Oracle Retail Customer Engagement Sales Feed. When you search for a customer in customer maintenance, order entry, when creating catalog requests, or when creating customer memberships, Order Management System looks first to Oracle Retail Customer Engagement, rather than the Order Management System Customer Sold To table, and you use the Customer Scan Screen. Use this setting if Oracle Retail Customer Engagement is the system of record for customer information.
• blank: Order Management System does not communicate customer information to Oracle Retail Customer Engagement, or search the Oracle Retail Customer Engagement database for customers.
For more information: See the Customer Engagement Batch Customer and Sales Integration and the Customer Engagement Customer Integration.
MICROS Integration Item ID (L38)
Purpose: Defines how Order Management System identifies items/SKUs for integrations with other systems.
ITEM |
Order Management System uses the Item code and SKU code to identify items/SKUs for integrations with other systems. |
XREF |
Order Management System uses the Retail reference number to identify items/SKUs for integrations with other systems. If you use retail reference number, make sure you define a unique reference number for each of your items/SKUs. • You can define a retail reference number for a non-SKUed item on the Create or Change Item (Base Information) screen. • You can define a retail reference number for a SKUed item on the Create or Change SKU - 1 of 2 (With Overrides) screen. Note: You do not need to define a Retail reference number for the item defined in the Item for Non-Merchandise Amounts (L39) system control value; the system sends the item code defined in this system control value to Oracle Retail Customer Engagement, regardless of how the MICROS Integration Item ID system control value is set. |
Oracle Retail Customer Engagement Item Feed Process: If you leave this system control value blank, the system writes an error in the Application Log when you submit the Oracle Retail Customer Engagement Item Feed Process: ORCE Item Feed not run because SCV L38 MICROS Integration Item ID was not set up.
Oracle Retail Customer Engagement Sales Feed Process: If you leave this system control value blank, the system writes an error in the Application Log when you submit the Oracle Retail Customer Engagement Sales Feed Process: ORCE Sales Feed not run because SCV L38 MICROS Integration Item ID was not set up.
For more information: See:
• Customer Engagement Batch Customer and Sales Integration
• Customer Engagement Customer Wish List Integration
• Customer Engagement Purchase History Integration
Item for Non-Merchandise Amounts (L39)
Purpose: Defines the item code to include in the Customer Engagement Post POSlog Transaction Message to represent all non-merchandise amounts for an invoice, such as freight, additional freight, handling and additional charges.
Integration with the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service: This system control value is also used as part of the Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service.
Enter an item code in this field if the Merchandise Only in Sales Feed (L36) system control value is unselected.
Note: The item code cannot be greater than 10 positions. Create the item as a non-SKUed, non-inventory item.
For more information: See Customer Engagement Batch Customer and Sales Integration or the Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service for background.
Cross Channel Orders to Exclude in Sales Feed (L35)
Purpose: Defines the types of orders Order Management System excludes from the Oracle Retail Customer Engagement Sales Feed. You might want to exclude certain order types from the feed if another external system is already sending these orders to Oracle Retail Customer Engagement, so sending the orders again could create duplicates.
Note: This system control value is used to exclude sale (debit) invoices from the Oracle Retail Customer Engagement Sales feed; the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value can be used to exclude return (credit) invoices from the Oracle Retail Customer Engagement Sales feed.
Code field:
R |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is R (Retail Pickup Order) from the Oracle Retail Customer Engagement Sales Feed. |
D |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is D (Delivery Order) from the Oracle Retail Customer Engagement Sales Feed. |
S |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
P |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
RD |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is R (Retail Pickup Order) or D (Delivery Order) from the Oracle Retail Customer Engagement Sales Feed. |
RS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is R (Retail Pickup Order) or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
DS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is D (Delivery Order) or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
PR |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup) or R (Retail Pickup Order) from the Oracle Retail Customer Engagement Sales Feed. |
PD |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup) or D (Delivery Order) from the Oracle Retail Customer Engagement Sales Feed. |
PS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup) or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
RDS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is R (Retail Pickup Order), D (Delivery Order) or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
PRD |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup), R (Retail Pickup Order), or D (Delivery Order) from the Oracle Retail Customer Engagement Sales Feed. |
PRS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup), R (Retail Pickup Order), or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
PDS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup), D (Delivery Order) or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
PRDS |
Exclude sale (debit) invoices whose OST OBR Delivery Type in the Order Ship To table is P (Store Pickup), R (Retail Pickup Order), D (Delivery Order) or S (Ship for Pickup) from the Oracle Retail Customer Engagement Sales Feed. |
blank |
Do not exclude any sale (debit) invoices from the Oracle Retail Customer Engagement Sales feed, regardless of the setting of the OST OBR Delivery Type in the Order Ship To table. |
For more information: See Customer Engagement Batch Customer and Sales Integration.
Return Disposition Code to Exclude in ORCE Sales Feed (M22)
Purpose: Defines the return disposition code assigned to return (credit) invoices that Order Management System excludes from the Oracle Retail Customer Engagement Sales Feed when the Suppress refund field in the Order Payment Method table is Y. In addition, Order Management System does not generate a return confirmation for these returns.
You might want to exclude certain returns from the Oracle Retail Customer Engagement Sales feed if another external system is already sending these returns to Oracle Retail Customer Engagement, so sending the returns again could create duplicates.
Note: This system control value is used to exclude return (credit) invoices from the Oracle Retail Customer Engagement Sales feed; the Cross Channel Orders to Exclude in Sales Feed (L35) system control value can be used to exclude sales (debit) invoices from the Oracle Retail Customer Engagement Sales feed.
Code field: Enter the return disposition code assigned to return (credit) invoices that Order Management System excludes from the Oracle Retail Customer Engagement Sales Feed when the Suppress refund field in the Order Payment Method table is Y. In this situation, Order Management System does not generate a return confirmation for these returns.
Return disposition codes are defined in and validated against the Return Disposition table; see Establishing Return Disposition Values (WRDV).
Retail pickup and delivery orders: In the case of retail pickup and delivery orders, the system deactivates the pay type once the order is shipped. In order to process a return against a retail pickup or delivery order, the Suppress Returns for Retail Pickup/Delivery (L88) system control value must be unselected and a user must add a new pay type to the order. The system adds the new pay type to the order with the Suppress refund field set to blank, allowing the refund to be processed and included in the Oracle Retail Customer Engagement Sales Feed.
Summary: The table below explains when the system excludes a return (credit) invoice from the Oracle Retail Customer Engagement Sales Feed and suppresses its return confirmation from generating.
SCV M22 Return Disposition |
Return Disposition for Return |
Suppress Refunds? |
Results |
1 |
2 |
N or blank |
Because the return disposition on the return does not match the return disposition defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value, the system includes the return (credit) invoice in the Oracle Retail Customer Engagement Sales feed and generates a return confirmation for the return. |
1 |
2 |
Y |
Because the return disposition on the return does not match the return disposition defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value, the system includes the return (credit) invoice in the Oracle Retail Customer Engagement Sales feed and generates a return confirmation for the return. |
1 |
1 |
N or blank |
Because the Suppress refunds setting for the order payment method is N or blank, the system includes the return (credit) invoice in the Oracle Retail Customer Engagement Sales feed and generates a return confirmation for the return. |
1 |
1 |
Y |
Because the return disposition on the return matches the return disposition defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value AND the Suppress refunds setting for the order payment method is Y, the system excludes the return (credit) invoice from the Oracle Retail Customer Engagement Sales feed and does not generate a return confirmation for the return. |
Suppress refund flag: You can suppress refund processing:
• For orders you receive through the Generic Order Interface (Order API). In this situation, the refund is generated in an N (cancel pending) status and the Suppress refund field in the Order Payment Method table is Y. See Suppressing Deposits and Refunds for an overview.
• For orders associated with a return you receive through the Inbound Return API. In this situation, the refund is generated in a N (cancel pending) status and the Suppress refund field in the Order Payment Method table is Y. See Suppressing Refunds for an overview.
You can review the setting of the Suppress refund field at the Display Order Pay Type Screen (1 of 2).
Multi-line returns: When processing multiple returns against an order, the last return processed updates the Suppress refund field in the Order Payment Method table. If you do not run the Oracle Retail Customer Engagement Sales feed until all returns have been processed, the setting of the Suppress refund field for the last return will determine whether all of the return (credit) invoices are included or excluded from the Oracle Retail Customer Engagement Sales feed.
Example 1: In this example, the return disposition defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value is 1.
Return Line |
Return Disposition |
Suppress Refunds? |
1 |
1 |
N |
2 |
1 |
Y |
Example 1 results: If you ran the Oracle Retail Customer Engagement Sales feed after each return, the system would include return line 1 in the Oracle Retail Customer Engagement Sales feed and generate a return confirmation for the return and exclude return line 2 from the Oracle Retail Customer Engagement Sales feed and suppress the return confirmation for this return. However, if you ran the Oracle Retail Customer Engagement Sales feed after processing both returns, the system would exclude both returns from the Oracle Retail Customer Engagement Sales feed and suppress the return confirmation for each return because the Suppress refunds field in the Order Payment Method table is set to Y.
Example 2: In this example, the return disposition defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value is 1.
Return Line |
Return Disposition |
Suppress Refunds? |
1 |
1 |
N |
2 |
1 |
Y |
3 |
1 |
N |
Example 2 results: If you ran the Oracle Retail Customer Engagement Sales feed after each return, the system would include return lines 1 and 3 in the Oracle Retail Customer Engagement Sales feed and generate a return confirmation for these returns and exclude return line 2 from the Oracle Retail Customer Engagement Sales feed and suppress the return confirmation for this return. However, if you ran the Oracle Retail Customer Engagement Sales feed after processing all returns, the system would include all of the returns in the Oracle Retail Customer Engagement Sales feed and generate a return confirmation for each return because the Suppress refunds field in the Order Payment Method table is set to N.
Example 3: In this example, the return disposition defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value is 1.
Return Line |
Return Disposition |
Suppress Refunds? |
1 |
1 |
Y |
2 |
1 |
N |
3 |
2 |
Y |
Example 3 results: If you ran the Oracle Retail Customer Engagement Sales feed after each return, the system would include return lines 2 and 3 in the Oracle Retail Customer Engagement Sales feed and generate a return confirmation for these returns and exclude return line 1 from the Oracle Retail Customer Engagement Sales feed and suppress the return confirmation for this return. However, if you ran the Oracle Retail Customer Engagement Sales feed after processing all returns, the system would include only return line 3 in the Oracle Retail Customer Engagement Sales feed and generate a return confirmation for this return because the Suppress refunds field in the Order Payment Method table is set to Y. Return line 3 is include in the Oracle Retail Customer Engagement Sales feed because its return disposition code does not match the return disposition code defined in the Return Disposition Code to Exclude in ORCE Sales Feed (M22) system control value.
Leave this field blank if you do not want to exclude return (credit) invoices from the Oracle Retail Customer Engagement Sales Feed based on the assigned return disposition code. In this situation:
• the system includes return (credit) invoices in the Oracle Retail Customer Engagement Sales feed regardless of the assigned return disposition code and Suppress refund setting in the Order Payment Method table.
• the system generates a return confirmation regardless of the assigned return disposition code and Suppress refund setting in the Order Payment Method table.
For more information: See Customer Engagement Batch Customer and Sales Integration.
Merchandise Only in Sales Feed (L36)
Purpose: Defines whether Order Management System includes full invoice totals or only merchandise and tax amounts in the Customer Engagement Post POSlog Transaction Message.
Yes/No field:
• Select this field to include merchandise and tax amounts only in the Oracle Retail Customer Engagement Sales file.
• Unselect this field to include full invoice totals, including merchandise, freight, and additional charges, in the Oracle Retail Customer Engagement Sales file. Use the Item for Non-Merchandise Amounts (L39) system control value to define the item code to include in the Customer Engagement Post POSlog Transaction Message to represent all non-merchandise amounts for an item, such as freight, additional freight, handling and additional charges.
For more information: See Customer Engagement Batch Customer and Sales Integration.
ORCE Organization Descriptor (L50)
Purpose: Use this field to specify the code that identifies the Oracle Retail Customer Engagement organization that maps to your Order Management System company.
Code field: Enter the three-position code that matches the Organization descriptor specified through the Oracle Retail Customer Engagement Conflate option if you use Customer Engagement 15.x or earlier, or the Organization ID Descriptor property if you use Customer Engagement 16.x or 17.x.
The system uses the value in this field during web service calls to Oracle Retail Customer Engagement.
This entry should typically be entered in lower case.
Note: This system control value is also defined under the Stored Value Card Processing Values (I71) umbrella system control value.
Send Profile Data to ORCE (L51)
Purpose: Use this field to control whether to send customer profile data through the interactive customer integration with Oracle Retail Customer Engagement.
Yes/No field: Select this field to include customer profile data in the interactive customer integration with Oracle Retail Customer Engagement; otherwise, leave this field unselected if the data should not be sent to Oracle Retail Customer Engagement.
Note: This system control value affects the interactive Customer Engagement Customer Integration only; it does not affect sending customers to Oracle Retail Customer Engagement through the Customer Engagement Batch Customer and Sales Integration, as described under Customer Engagement Add or Update Customer Message.
For more information: See:
• Customer Engagement Customer Integration for an overview and background on the integration.
• Order Management System Customer Profile > Oracle Retail Customer Engagement Attribute Definition for more information on the setup required in Oracle Retail Customer Engagement in order to map customer profile data.
• Setting Up Customer Profiles (WPFL) for background on setting up and using customer demographic profiles.
Default Location for ORCE Integration (K69)
Purpose: Use this field to define the location Order Management System sends to an external system, such as Oracle Retail Customer Engagement. You can also use this number as part of your unique POSLog integration.
Code field: Enter the store number you have set up through Work with Store Cross Reference (WSCR).
When you specify a location in this system control value, the following cross-reference fields are available for review or entry:
• Store tender field on the Create Pay Type Screen provides a cross-reference to the corresponding tender code in a point-of-sale system. This code is passed in the POSLog integration to Customer Engagement, where it can be used as a loyalty qualifier.
• Store tax code field on the Create Postal Code Screen and Create SCF Screen provides a cross-reference to the corresponding tax code in a point-of-sale system.
Leave this field blank if you do not have an integration with a point-of-sale system.
Oracle Retail Customer Engagement integration: The system includes the location you define here:
• in the name of the XML batch file that is sent to Oracle Retail Customer Engagement. See Customer Engagement Batch Customer and Sales Integration for more information on sending customer, item, sales and return information from Order Management System to Oracle Retail Customer Engagement.
• in the stored value card transactions sent to Oracle Retail Customer Engagement. See Customer Engagement Stored Value Card Integration.
Note: For the Oracle Retail Customer Engagement integration, the location cannot be greater than 8 positions.
Custom POSLog Integration: POSLog is a text file of the day’s sales transactions. A daily process generates the file based on the invoices for that day. You can use a periodic function, typically named POSLOG, to extract data from invoices and generate the POSLog file to support your unique POSLog integration. For information on setting up the POSLOG periodic function, contact your Order Management System representative.
POSLog property settings: Use the following properties to define the information required to transmit the POSLog file from Order Management System via FTP for integration with a point-of-sale system. You use a periodic function to extract transaction information to a file name Store#123.POL, where 123 is the store number assigned in the Default Location for Sales Download (K69) system control value.
If you use a unique POSLog integration, define the following properties:
CW_POS_LOG_FILE_NAME: Specifies the name of the POSLog file, with the pound sign (#) indicating where to insert the three-position Default Location for Sales Download (K69). For example, if you set this property to Store #.POL, the file is named Store #123.POL, where 123 is the Default Location for Sales Download (K69).
CW_FTP_POS_LOG_FILE: If set to Y, indicates to FTP the POSLog file using the poslog_ftp_commands.script, described below.
CW_DELETE_POS_LOG_FILE_AFTER_FTP: If set to Y, indicates to delete the POSLog file after sending it by FTP.
FTP script: The FTP script for POSLog integration is defined in the poslog_ftp_commands.script file. This file is located in the CWDIRECTCP_FTP_FOLDER property. The script consists of:
open | server | userID | passwd
put | /poslog/FTP_REMOTE_FILE_NAME
where:
• server = the name of the destination server
• userID = a valid user ID for the destination system
• passwd = the user ID’s password
Note: You should not modify the second line of the command file.
Purpose: Use this field to define whether you use the Customer Engagement Customer Wish List Integration.
Yes/No field: Select this field if you want to use the Oracle Retail Customer Engagement Customer Wish List integration.
Important: If you select this field, the ORCE Customer Integration (L37) system control value must be set to INTERACT, indicating you communicate with Oracle Retail Customer Engagement interactively.
Leave this field unselected if you do not want to use the Oracle Retail Customer Engagement Customer Wish List integration.
For more information: See Customer Engagement Customer Wish List Integration for processing details and the required setup.
Purpose: Use this field to define whether you use the Customer Engagement Loyalty Integration.
Yes/No field: Select this field if you want to use the Oracle Retail Customer Engagement Loyalty integration.
Important: If you select this field:
• The ORCE Customer Integration (L37) system control value must be set to INTERACT, indicating you communicate with Oracle Retail Customer Engagement interactively.
• You must define a card prefix in the ORCE Loyalty Card Prefix (M08) system control value.
• You must define a card series sequence number in the ORCE Loyalty Card Series Sequence Number (M09) system control value.
Leave this field unselected if you do not want to use the Oracle Retail Customer Engagement Loyalty integration.
For more information: See Customer Engagement Loyalty Integration for processing details and the required setup.
Purpose: Use this field to define whether the system automatically displays the Customer Loyalty Registration Window during Order Entry and Work with Customers (WCST) when Oracle Retail Customer Engagement does not find a loyalty card for the customer.
Yes/No field: Select this field to automatically display the Customer Loyalty Registration window when you:
• Select a sold to customer on the Customer Selection Screen if Oracle Retail Customer Engagement does not find a loyalty card for the customer and the customer’s ORCE_LOYALTY_PROMPT_ATTRIBUTE setting in Oracle Retail Customer Engagement is TRUE or blank.
• Change a sold to customer in Creating and Updating Sold-to Customers (WCST) if Oracle Retail Customer Engagement does not find a loyalty card for the customer and the customer’s ORCE_LOYALTY_PROMPT_ATTRIBUTE setting in Oracle Retail Customer Engagement is TRUE or blank.
• Create a sold to customer in Creating and Updating Sold-to Customers (WCST) or Order Entry (OEOM) after the customer is created in Oracle Retail Customer Engagement.
- In Work with Customers, this window automatically displays after the final Accept to create the customer.
- In Order Entry, this window automatically displays after the system validates the customer information and source code on the order and you click Accept.
• Create an order in Order Entry (OEOM) if you do not use the CTI Customer Selection Screen and Oracle Retail Customer Engagement does not find a loyalty card for the customer and the customer’s ORCE_LOYALTY_PROMPT_ATTRIBUTE setting in Oracle Retail Customer Engagement is TRUE or blank. This window automatically displays after the system validates the customer information and source code on the order and you click Accept.
Leave this field unselected if you do not want the Customer Loyalty Registration window to automatically display. Regardless of the setting of this system control value, this window displays when you:
• Select Loyalty from the Action drop-down menu on the Customer Scan Screen in Work with Customers (WCST) or Order Entry (OEOM).
• Select Loyalty on the Customer Selection Screen after selecting a sold to customer.
• Select Loyalty Account on the Display More Options Screen.
• Select Loyalty Account on the More Customer Sold To Options Screen.
• Select Loyalty on the Third Streamlined Order Inquiry Screen (Order Summary) in Streamlined Order Inquiry (DORI).
When you select the Loyalty option, the system retrieves the sold to customer’s information from Oracle Retail Customer Engagement. If Oracle Retail Customer Engagement does not find a loyalty card for the customer, the system advances you to the Customer Loyalty Registration Window, where you can select to enroll the customer in the Oracle Retail Customer Engagement Loyalty program.
Note:
• If Oracle Retail Customer Engagement finds a loyalty card assigned to the customer, the system advances you to the Display Loyalty Account Screen. If Oracle Retail Customer Engagement finds more than one loyalty card assigned to the customer, the loyalty account information for the first card displays on the screen.
• If a Relate ID is not defined for the customer in the Customer Sold To table, the system displays an error message similar to the following: This customer does not have a Relate ID. Note: If a Relate ID is not defined for the sold to customer, the Loyalty option does not display on the Third Streamlined Order Inquiry Screen (Order Summary) in Streamlined Order Inquiry (DORI).
• If a connection could not be made to Oracle Retail Customer Engagement, the system displays an error message similar to the following: Unable to connect to ORCE.
Note: In order to display the Customer Loyalty Registration window, the Use ORCE Loyalty (M06) system control value must be selected and the ORCE Customer Integration (L37) system control value must be set to INTERACT.
ORCE Loyalty Card Prefix (M08)
Purpose: Use this field to define the 5 digit prefix assigned to the Loyalty Card Definition in Oracle Retail Customer Engagement that is used to assign new loyalty cards to sold to customers that join the loyalty program.
Code field: Enter the 5 digit prefix assigned to the Loyalty Card Definition in Oracle Retail Customer Engagement that is used to assign new loyalty cards to customers.
Note:
• You must define a loyalty card prefix if the Use ORCE Loyalty (M06) system control is selected.
• The 5 digit card prefix you enter here must match the 5 digit card prefix in Oracle Retail Customer Engagement; for example, if the card prefix in Oracle Retail Customer Engagement is 00905, you must enter 00905 in this field.
• A different card prefix is used for the Customer Engagement Stored Value Card Integration.
For more information: See Customer Engagement Loyalty Integration.
ORCE Loyalty Card Series Sequence Number (M09)
Purpose: Use this field to define the 2 digit card series number assigned to the Loyalty Card Definition in Oracle Retail Customer Engagement that is used to assign new loyalty cards to sold to customers that join the loyalty program.
Code field: Enter the 2 digit card series sequence number assigned to the Loyalty Card Definition in Oracle Retail Customer Engagement that is used to assign new loyalty cards to customers.
Note:
• You must define a loyalty card series sequence number if the Use ORCE Loyalty (M06) system control is selected.
• The 2 digit card number you enter here must match the 2 digit card number in Oracle Retail Customer Engagement; for example, if the card series sequence number in Oracle Retail Customer Engagement is 02, you must enter 02 in this field.
• A different card series sequence number is used for the Customer Engagement Stored Value Card Integration.
For more information: See Customer Engagement Loyalty Integration.
ORCE Loyalty Registration Notification Email Program (M10)
Purpose: Use this field to define the program used to generate a Oracle Retail Customer Engagement Loyalty Registration Notifications email when a sold to customer joins the loyalty program and is assigned a loyalty card in Oracle Retail Customer Engagement. This email contains the loyalty card number assigned to the customer during the loyalty registration process; see Oracle Retail Customer Engagement Loyalty Registration Notification Sample and Contents for a sample email.
System name field: Enter the program used to generate a Loyalty Registration Notification email. The base program name is LoyRegNotf.
Leave this field blank if you do not want to generate a Oracle Retail Customer Engagement Loyalty Registration Notification email when a sold to customer joins the loyalty program and is assigned a loyalty card in Oracle Retail Customer Engagement.
For more information: See Customer Engagement Loyalty Integration.
