This chapter describes the parameters, system configurations, and receipt components available for configuring the Oracle Retail Point-of-Service application.
This section describes the format of the tables used for describing the parameters, system configurations, and receipt components.
Table 3-1 describes the attributes shown for each parameter.
Table 3-1 Parameter Table Legend
Attribute | Description |
---|---|
Parameter |
The name of the parameter. |
Function |
A description of the effect the parameter has on application functionality. |
Allowed Values |
The possible values allowed for the parameter. |
Default Value |
The initial value assigned to the parameter. |
Entry Field Type |
The type of entry field used for modifying the parameter. The following types of entry fields are used:
|
When the Modification Takes Effect |
Indicates when a modification to a parameter will take effect in the application. The effect occurs immediately or at some time determined by the application functionality that uses the parameter. Note: When a parameter is edited on a Point-of-Service register and the modification takes effect immediately, the change takes place immediately on that register. Otherwise, the effect takes place as indicated for the parameter. When a parameter is edited in Back Office or Central Office, the parameter must be be distributed to Point-of-Service before it can take effect. |
Applications Affected by Modifications to the Parameter |
List of applications that are affected by modifications to the parameter. |
Applications Where the Parameter Can be Modified in the User Interface |
List of applications where the parameter can be modified through the application user interface. If None is listed for this attribute, the parameter cannot be modified through any application user interface but only by updating the XML file or database. |
Resides in XML or Database |
Indicates whether the parameter resides in an XML file, the database, or a properties file. Parameters that reside in the database are updated by using SQL statements to change the value in the database. Table, column, and row information that is needed for the SQL statement is listed for each parameter. |
XML Name |
The parameter name used in the XML file. This is also the name shown in the Central Office, Back Office, and Returns Management user interfaces. If None is listed for this attribute, the parameter is not included in an XML file and does not appear in any user interface. |
Table 3-2 describes the attributes shown for each system configuration.
Table 3-2 System Configuration Table Legend
Attribute | Description |
---|---|
System Configuration |
The name of the system configuration. |
Function |
A description of the effect the system configuration has on application functionality. |
Allowed Values |
The possible values allowed for the system configuration. |
Default Value |
The initial value assigned to the system configuration. |
Entry Field Type |
The type of entry field used for modifying the system configuration. The following types of entry fields are used:
|
When the Modification Takes Effect |
Indicates when a modification to a system configuration will take effect in the application. The effect occurs immediately or at some time determined by the application functionality that uses the system configuration. |
Applications Affected by Modifications to the System Configuration |
List of applications that are affected by modifications to the system configuration. |
Resides in XML, Database, or Properties File |
Indicates whether the system configuration resides in an XML file, the database, or a properties file. System configurations that reside in the database are updated by using SQL statements to change the value in the database. Table, column, and row information that is needed for the SQL statement is listed for each system configuration. For system configurations that reside in a properties files, the name of the file and the name of the category are listed. |
XML Name |
Information needed to change the system configuration based on where it resides. |
Table 3-3 describes the attributes shown for each receipt component.
Table 3-3 Point-of-Service Receipt Component Table Legend
Attribute | Description |
---|---|
Receipt Component |
The name of the receipt component. |
Function |
A description of the receipt information affected by this receipt component. |
Allowed Values |
The possible values allowed for the receipt component. |
Default Value |
The initial value assigned to the receipt component. |
Entry Field Type |
The type of entry field used for modifying the receipt component. The following types of entry fields are used:
|
When the Modification Takes Effect |
Indicates when a modification to a receipt component will take effect in the application. For all receipt components, the change takes effect when the blueprint file is distributed, if it is distributed, and read. |
Blueprint File Name |
Name of the blueprint file where the receipt component resides. |
This section describes the parameters for the Point-of-Service application. The parameters are itemized in tables by parameter group. For a description of the information in this table, see Table 3-1.
Table 3-4 describes the parameters in the Base parameter group.
Table 3-4 Point-of-Service Base Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the URL used to access the application that is launched when the Browser button is selected on the Point-of-Service main options screen. |
|
Allowed Values |
Valid URL address |
|
Default Value |
|
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
browserurl |
|
Function |
Text displayed as a message across the bottom of the dashboard. If the Enable Dashboard parameter is set to No, this parameter is ignored. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
Welcome to ORPOS 14.1. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
DashboardMessages |
|
Function |
List of reports that display within the dashboard when the dashboard is configured to display in the Main Options window. This parameter is only used when the Enable Dashboard parameter is set to Yes. |
|
Allowed Values |
Associate Productivity, Department Sales, Hourly Sales |
|
Default Value |
Associate Productivity, Department Sales, Hourly Sales |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
DashboardReports |
|
Function |
Sets the number of days of messages to retrieve for display. The number includes the current day and previous days. This parameter is only used when the Register Retrieve Notifications parameter is set to Yes. |
|
Allowed Values |
1 to 10 |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
DaysToRetrieveNotifications |
|
Function |
Text displayed on the customer facing monitor, when an environment is configured to include dual monitors. Carriage returns can be used to separate messages. If more than one message is defined, the messages cycle on the screen based on the time set in the Dual Display Messages Interval parameter. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
This is the Dual Display Marketing parameter message. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
DualDisplayMarketingMessages |
|
Function |
Time used to cycle through multiple marketing messages for Dual Display. This parameter is only used if more than one message is entered for the Dual Display Marketing Messages parameter value. The separate messages are defined by the user entering a carriage return between each message. |
|
Allowed Values |
500 to 1000000 |
|
Default Value |
10000 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
DualDisplayMessagesInterval |
|
Function |
Determines if a dashboard displays in the Main Options window. |
|
Allowed Values |
Yes, No If set to Yes, a dashboard displays in the Main Options window. The dashboard is configured with reports that are selected in the Dashboard Reports parameter. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
EnableDashboard |
|
Function |
Determines whether Point-of-Service can start on a register if offline data cannot be loaded at that time. |
|
Allowed Values |
Yes, No If set to Yes, Point-of-Service will start on a register even if offline data cannot be loaded. If set to No, Point-of-Service will not start when offline data cannot be loaded. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
IDDIOfflineSupportRequired |
|
Function |
Sets the number of minutes for the system to wait when there is no activity at the Main Options screen before checking for data updates for the register. |
|
Allowed Values |
1 to 60; -1 indicates infinity (the system never checks for updates) |
|
Default Value |
15 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
XML |
|
Resides in XML, Database, or Properties File |
IDDITimeoutInterval |
|
Function |
Sets the maximum number of messages to display. This parameter is only used when the Register Retrieve Notifications parameter is set to Yes. |
|
Allowed Values |
1 to 999 |
|
Default Value |
999 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
NotificationsMaximumResults |
|
Function |
Determines if the on screen keyboard is enabled. |
|
Allowed Values |
Yes, No If the parameter is set to Yes, the keyboard appears as a separate window and the Ctrl+K Keys button is enabled. If the parameter is set to No, the keyboard does not appear and the button is disabled. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
OnScreenKeyboardEnabled |
|
Function |
Enables and disables opening the cash register drawer when in training mode. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OpenDrawerInTrainingMode |
|
Function |
Determines the direction in which the list of recommended items moves when scrolling though the list. |
|
Allowed Values |
Yes, No If the parameter is set to Yes, the list moves in the same direction as the arrow button. If the parameter is set to No, the list moves in the opposite direction of the arrow button. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
RecommendedItemNaturalScrollDirection |
|
Function |
Determines if notification messages can be viewed at a register or mobile device. |
|
Allowed Values |
Yes, No If the parameter is set to Yes, the Messages button is enabled on the Main Options screen. If the parameter is set to No, the button is not enabled. |
|
Default Value |
Value set at installation time |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
RegisterRetrieveNotifications |
|
Function |
Sets the default country for all boxes used to select a country. |
|
Allowed Values |
USA, Canada, Japan, Germany, Great Britain, Mexico, France |
|
Default Value |
USA |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StoreCountry |
|
Function |
Sets the default state or province for all boxes used to select a state or province. |
|
Allowed Values |
Includes all the states or provinces for all the countries listed in the Store Country parameter |
|
Default Value |
Texas |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StoreStateProvince |
|
Function |
Sets the VAT number for the store. |
|
Allowed Values |
1 to 30 alphanumeric characters defined by the retailer |
|
Default Value |
572 8421 28 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StoresVATNumber |
|
Function |
Sets the number of minutes for the system to wait before automatically logging out the user due to inactivity while a transaction is in progress. Note: Automatic log out cancels the transaction in progress. |
|
Allowed Values |
1 to 15; -1 indicates infinity (the user will automatically be logged out after 15 minutes, which is the default) |
|
Default Value |
15 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TimeOutInactiveWithTransaction |
|
Function |
Sets the number of minutes for the system to wait before automatically logging out the user due to inactivity when a transaction is not in progress. |
|
Allowed Values |
1 to 15; -1 indicates infinity (the user will automatically be logged out after 15 minutes, which is the default) |
|
Default Value |
15 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TimeOutInactiveWithoutTransaction |
Table 3-5 describes the parameters in the Customer parameter group.
Table 3-5 Point-of-Service Customer Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Determines if the Pricing Group field is editable. |
|
Allowed Values |
Yes, No If set to Yes, the Pricing Group field is editable and defaults to None. If set to No, the field is display only. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSpecificPricing |
|
Function |
Determines if the Transaction Taxable field appears on the Agcy/Bus Name screen. |
|
Allowed Values |
Yes, No If set to Yes, the Transaction Taxable field is displayed. If set to No, the Transaction Taxable field is not displayed and the transaction is set to Tax Exempt status. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CaptureTransactionTaxStatus |
|
Function |
Defines the maximum number of matches to display after searching for a customer. |
|
Allowed Values |
1 to 999 |
|
Default Value |
20 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next customer search |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerMaximumMatches |
|
Function |
Determines whether the customer survey or reward option is available. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSurveyRewardAvailable |
|
Function |
Determines the start date for execution of the customer survey or reward. |
|
Allowed Values |
String in date format |
|
Default Value |
10/31/03 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSurveyRewardStart |
|
Function |
Determines the end date for execution of the customer survey or reward. |
|
Allowed Values |
String in date format |
|
Default Value |
2/14/04 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSurveyRewardEnd |
|
Function |
Determines the method in which a transaction is eligible for the customer survey or reward. |
|
Allowed Values |
Transaction Amount, Number of Transactions |
|
Default Value |
Transaction Amount |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSurveyRewardMethod |
|
Function |
Determines the number of transactions that must occur before a customer survey or reward is issued. |
|
Allowed Values |
1 to 9999 |
|
Default Value |
25 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSurveyReward_n_Transactions |
|
Function |
Determines the minimum amount that must be met before a customer survey or reward is issued. |
|
Allowed Values |
0.01 to 9999.99 |
|
Default Value |
100.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CustomerSurveyRewardTransactionAmount |
|
Function |
Sets the maximum number of transactions to search for to display as the customer's history. |
|
Allowed Values |
1 to 999 |
|
Default Value |
20 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next customer search |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumTransactionHistoryNumber |
|
Function |
Determines when customer information is captured. |
|
Allowed Values |
Yes, No If Yes, capture the information when the amount due is negative (refund). If No, capture the information when the amount due is positive or negative. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
NegativeAmtDue |
|
Function |
Determines if the system uses Oracle Customer functionality to link a transaction to a customer. |
|
Allowed Values |
Yes, No If set to Yes, the customer information is saved in a customer database. If set to No, none of the customer information is saved in a customer database. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OracleCustomer |
|
Function |
Determines whether the operator is prompted to capture Patriot Act (PAT) information. |
|
Allowed Values |
Yes, No If set to Yes, the operator is prompted to enter the information. If set to No, the operator is not prompted for the information. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PatCustomerInformation |
Table 3-6 describes the parameters in the Daily Operations parameter group.
Table 3-6 Point-of-Service Daily Operations Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Determines if the cashier is linked to sale transactions. This parameter is only used when the Identify Sales Associate Every Transaction parameter is set to No. |
|
Allowed Values |
Yes, No If this parameter set to Yes, the current operator is used as the sales associate linked to sale transactions. If set to No, no sales associate is linked to sales transactions. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
DefaultToCashier |
|
Function |
Determines if the cashier should be identified for every transaction. This parameter is only applicable when the Accountability parameter is set to Cashier. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
IdentifyCashierEveryTransaction |
|
Function |
Determines if the sales associate should be identified for every transaction. |
|
Allowed Values |
Yes, No If set to Yes, the operator is prompted to enter the Sales Associate ID for every transaction, the Associate Productivity Report is enabled and visible, and the sales associate function within item and transaction is enabled and visible. If it is set to No, the Default To Cashier parameter is called, the operator is not prompted to enter the sales associate for every transaction, and the Associate Productivity Report is disabled. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
IdentifySalesAssociateEveryTransaction |
|
Function |
Determines if the operator is prompted to enter customer information. |
|
Allowed Values |
None, Phone Number, Zip Code |
|
Default Value |
None |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PromptForCustomerInformation |
|
Function |
Determines if the employee ID is validated during a Payroll Pay Out transaction. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ValidatePayrollPayOutEmployeeID |
Table 3-7 describes the parameter in the Device Status parameter group.
Table 3-7 Point-of-Service Device Status Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
List of the devices to display on the Device Status screen. |
|
Allowed Values |
Authorization Service, Cash Drawer, Database, Fingerprint Reader, MICR, MSR, Printer, Scanner |
|
Default Value |
Authorization Service, Cash Drawer, Database, Fingerprint Reader, MICR, MSR, Printer, Scanner |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StatusDisplayList |
Table 3-8 describes the parameters in the Discount parameter group.
Table 3-8 Point-of-Service Discount Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Indicates whether the total value of the targets of a discount rule must be equal to or less than the value of the sources. |
|
Allowed Values |
True, False |
|
Default Value |
False |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
enableEqualOrLesserValue |
|
Function |
Sets the maximum percent allowed for a damage discount. |
|
Allowed Values |
0 to 100 A whole number greater than or equal to 0 and less than or equal to 100% of the selling price of the item. |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumDamageDiscountAmountPercent |
|
Function |
Sets the maximum percent allowed for an employee item discount. |
|
Allowed Values |
0 to 100 A whole number greater than or equal to 0 and less than or equal to 100% of the selling price of the item. |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumEmployeeDiscountAmountPercent |
|
Function |
Sets the maximum percent allowed for an employee transaction discount. |
|
Allowed Values |
0 to 100 A whole number greater than or equal to 0 and less than or equal to 100% of the selling price of the item. |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumEmployeeTransactionDiscountAmountPercent |
|
Function |
Sets the maximum amount allowed for an item discount. |
|
Allowed Values |
0 to 100 A whole number greater than or equal to 0 and less than or equal to 100% of the selling price of the item. |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumItemDiscountAmountPercent |
|
Function |
Sets the maximum percent allowed for an item markdown. |
|
Allowed Values |
0 to 100 A whole number greater than or equal to 0 and less than or equal to 100% of the selling price of the item. |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumItemMarkdownAmountPercent |
|
Function |
Sets the number of times an item can be discounted. |
|
Allowed Values |
One total discount allowed, One of each type of discount |
|
Default Value |
One of each type of discount |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaxDiscountsAllowed |
|
Function |
Sets the maximum percent allowed for a transaction discount. |
|
Allowed Values |
0 to 100 A whole number greater than or equal to 0 and less than or equal to 100% of the selling price of the item. |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumTransactionDiscountAmountPercent |
|
Function |
Determines how a discount amount is applied. |
|
Allowed Values |
Yes, No If set to Yes, the operator is allowed to prorate a discount amount across all selected items or discount each item. If set to No, the discount amount entered is applied to each item selected. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ProrateDiscountAmount |
Table 3-9 describes the parameters in the Email parameter group.
Note: Point-of-Service creates the automatic email messages and stores them in the database. It does not send the email messages to customers. The retailer is responsible for sending the email messages. For more information, see the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions. |
Table 3-9 Point-of-Service Email Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the footer text for automatic emails sent regarding filled orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Please do not respond to this email. For all inquiries regarding your order, contact Oracle Customer Service at 1-800-GO-ORACLE. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailFilledOrderFooter |
|
Function |
Sets the header text for automatic emails sent regarding filled orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Your order has been filled and is ready for pickup at the store. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailFilledOrderHeader |
|
Function |
Sets the footer text for automatic emails sent regarding canceled orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Please do not respond to this e-mail. For all inquiries regarding your order, contact Oracle Customer Service at 1-800-GO-ORACLE. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailCanceledOrderFooter |
|
Function |
Sets the header text for automatic emails sent regarding canceled orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Your order has been canceled. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailCanceledOrderHeader |
|
Function |
Sets the footer text for automatic emails sent regarding partial orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Please do not respond to this e-mail. For all inquiries regarding your order, contact Oracle Customer Service at 1-800-GO-ORACLE. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailPartialOrderFooter |
|
Function |
Sets the header text for automatic emails sent regarding partial orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Your order has been partially filled. Feel free to pick up the items that are ready. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailPartialOrderHeader |
|
Function |
Sets the footer text for automatic emails sent regarding picked up orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Please do not respond to this e-mail. For all inquiries regarding your order, contact Oracle Customer Service at 1-800-GO-ORACLE. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailPickedUpOrderFooter |
|
Function |
Sets the header text for automatic emails sent regarding completed orders. |
|
Allowed Values |
Text can be multiple lines |
|
Default Value |
Thank you for picking up your recent order. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEmailPickedUpOrderHeader |
Table 3-10 describes the parameter in the Employee parameter group.
Table 3-10 Point-of-Service Employee Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
The maximum number of employee matches to display after a search. |
|
Allowed Values |
1 to 999 |
|
Default Value |
20 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next employee search |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
EmployeeMaximumMatches |
Table 3-11 describes the parameters in the External Order parameter group.
Table 3-11 Point-of-Service External Order Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Defines the maximum number of matches to display after searching for an external order. |
|
Allowed Values |
1 to 999 |
|
Default Value |
50 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ExternalOrderMaximumMatches |
|
Function |
Determines if a signature capture is required when a transaction contains an external order. |
|
Allowed Values |
Yes, No If set to Yes, a signature is required. If set to No, the signature capture is not required. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ExternalOrderSigCapRequired |
|
Function |
Sets the legal description to display on the CPOI when a signature capture is required. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
By signing I agree to contract number <1234>. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
LegalExtOrderSigCap |
Table 3-12 describes the parameters in the House Account parameter group.
Table 3-12 Point-of-Service House Account Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the discount percent used as the default when applying a transaction discount when Instant Credit Card Enrollment is approved. |
|
Allowed Values |
0 to 100 |
|
Default Value |
10 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
DefaultInstantCreditDiscount |
|
Function |
If there is a paper credit application, this parameter enables franking information on the form. |
|
Allowed Values |
Yes, No If set to Yes, the system prompts for franking of the paper application. If set to No, the system does not prompt. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FrankInstantCreditApplication |
|
Function |
Enables and disables the House Account Payment feature. |
|
Allowed Values |
Yes, No If set to Yes, the Payment button is enabled on the House Account Options Menu. If set to No, the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
HouseAccountPayment |
|
Function |
Enables and disables the enrollment feature on the system. |
|
Allowed Values |
Yes, No If set to Yes, the Enrollment button is enabled on the House Account Options Menu. If set to No, the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
InstantCreditEnrollment |
|
Function |
Enables and disables the inquiry feature on the system. |
|
Allowed Values |
Yes, No If set to Yes, the Inquiry button is enabled on the House Account Options Menu. If set to No, the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
InstantCreditInquiry |
|
Function |
Sets the minimum age required for a customer to enroll for a house account. |
|
Allowed Values |
1 to 150 |
|
Default Value |
18 |
|
Entry Field Type |
Number |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinAgeForEnroll |
|
Function |
Enables and disables the feature to print a temporary shopping pass. |
|
Allowed Values |
Yes, No If set to Yes, the Temp. Pass. button is enabled on the House Account Options Menu. If set to No, the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PrintTemporaryShoppingPass |
|
Function |
Determines if a sales associate ID should be captured for the Instant Credit Card Enroll feature. The functionality is used to measure how many enrollments an employee performs, that is, the employee's productivity. |
|
Allowed Values |
Yes, No If set to Yes, the sales associate ID is captured. If set it No, it is not captured. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
Productivity |
|
Function |
Enables and disables the Reference Number Inquiry option to enter a reference number in order to complete a previously entered, but not completed, Instant Credit Card enrollment. |
|
Allowed Values |
Yes, No If set to Yes, the Ref. Num. Inq. button is enabled on the House Account Options Menu. If set to No, the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ReferenceNumberInquiry |
|
Function |
Determines if the retailer validates sales associate IDs. |
|
Allowed Values |
Yes, No If the user enters an invalid ID and this parameter is set to Yes, the system displays the Invalid Associate dialog message and prompts the user to enter the Sales Associate ID. If this parameter is set to No, the system does not display the Invalid Associate dialog message and accepts user's entry. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SalesAssociateValidation |
|
Function |
Sets the number of days a shopping pass is valid when the customer is approved through enrollment. |
|
Allowed Values |
1 to 365 |
|
Default Value |
14 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TempShoppingPassEnrollmentExp |
|
Function |
Sets the number of days a shopping pass is valid when the operator prints a temporary shopping pass for a customer. |
|
Allowed Values |
1 to 365 |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TempShoppingPassIssueExp |
Table 3-13 describes the parameters in the Item parameter group.
Table 3-13 Point-of-Service Item Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Allows the age prompt verification to be bypassed on the Date of Birth screen when an item added to a transaction has a Minimum Age for Purchase associated with it. |
|
Allowed Values |
Yes, No If set to Yes, the verification can be bypassed and the F2/Skip button is enabled. If set to No, the verification cannot be bypassed and the button is disabled. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AllowDateOfBirthPromptSkip |
|
Function |
Determines if the user is allowed to add an item that is not found in the database. |
|
Allowed Values |
Yes, No If set to Yes, the user can add the item which is not found in the database. If set to No, the user is not allowed to add the item. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AllowItemNotOnFile |
|
Function |
Determines whether the operator can enter quantity* and then scan or enter the item number. This provides a shortcut to input the multiple quantity for an item. |
|
Allowed Values |
Yes, No If set to Yes, the operator can use the shortcut to enter the multiple quantity for an item. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AllowMultipleQuantity |
|
Function |
Defines the maximum number of matches to display after searching for an item. |
|
Allowed Values |
1 to 999 |
|
Default Value |
100 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next item search |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ItemMaximumMatches |
|
Function |
Determines the search fields that are enabled when searching for an item in Point-of-Service. This parameter also determines whether the related fields are displayed on the Item Information and Advanced Inquiry screens in Point-of-Service. |
|
Allowed Values |
None, Department, ItemType, UnitOfMeasure, Style, Color, Size |
|
Default Value |
None |
|
Entry Field Type |
Create list |
|
When the Modification Takes Effect |
When the next item search occurs |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ItemSearchFields |
|
Function |
Determines whether the Planogram ID field is displayed on the Item Inquiry screens for item lookup and display. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PlanogramDisplay |
|
Function |
Determines if the user is prompted to place an order for an item that was found in the web store (not found locally). |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PromptToOrderItem |
|
Function |
Determines whether the operator can search for an item by manufacturer in Point-of-Service and Back Office. This parameter also determines whether or not the Manufacturer field is displayed on the Item Information and Advanced Inquiry screens in Point-of-Service, and the Item Maintenance and Item Inquiry screens in Back Office. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service, Back Office |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SearchforItembyManufacturer |
|
Function |
Determines whether the operator is prompted for the size of an item during an item inquiry. |
|
Allowed Values |
Yes, No If set to Yes, the operator is prompted to enter the size of the item. If set to No, the operator is not prompted. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SizeInputField |
|
Function |
Defines the maximum number of stores to return when searching for an item. |
|
Allowed Values |
1 to 999 |
|
Default Value |
100 |
|
Entry Field Type |
Next item inventory search |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StoreMaximumMatches |
Table 3-14 describes the parameters in the Layaway parameter group.
Table 3-14 Point-of-Service Layaway Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the fee that is withheld from the amount paid if the customer fails to complete the layaway. |
|
Allowed Values |
0.00 (USD) to 999.99 (USD) |
|
Default Value |
5.00 (USD) |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
When a layaway is created |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
DeletionFee |
|
Function |
Sets the number of days that the customer has to complete a layaway after the expiration date. |
|
Allowed Values |
1 to 365 |
|
Default Value |
5 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When a layaway is created |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ExpirationGracePeriod |
|
Function |
Sets the number of days the layaway is held until it is cancelled. |
|
Allowed Values |
1 to 365 |
|
Default Value |
30 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When a layaway is created. |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
LayawayDuration |
|
Function |
Sets the amount paid when a layaway is created. The fee is used in the calculation with the down payment amount and is not refunded if the layaway is deleted. |
|
Allowed Values |
0.00 (USD) to 9999.00 (USD) |
|
Default Value |
5.00 (USD) |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
When a layaway is created |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
LayawayFee |
|
Function |
The percent of the subtotal (the extended price of all items including item and transaction modifications, not including tax or fees) used in the down payment calculation. In a VAT environment, the extended price includes VAT. |
|
Allowed Values |
0 to 100 |
|
Default Value |
33 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When a layaway is created |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumDownPaymentPercent |
Table 3-15 describes the parameters in the Localization parameter group.
Table 3-15 Point-of-Service Localization Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
List of agencies that a retailer deals with. |
|
Allowed Values |
American Red Cross, Department of Welfare, Salvation Army, School, Other |
|
Default Value |
American Red Cross, Department of Welfare, Salvation Army, School, Other |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
Agencies |
Table 3-16 describes the parameters in the Operator ID parameter group.
Table 3-16 Point-of-Service Operator ID Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Determines if the employee ID or employee user ID is used for automatic entry. |
|
Allowed Values |
Employee, User If set to Employee, the employee ID is used for automatic entry. If set to User, the employee user ID is set for automatic entry. |
|
Default Value |
Employee |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEntryID |
|
Function |
Determines if, upon automatic entry of an ID, the system then requires a password. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutomaticEntryRequiresPassword |
|
Function |
Controls whether a fingerprint, using a biometric device, can be used for logins and manager override. |
|
Allowed Values |
NoFingerprint, OperatorAndFingerprint, FingerprintOnly If set to NoFingerprint, the login ID and password are used for login. If set to OperatorAndFingerprint, the login ID and fingerprint are used. If set to FingerprintOnly, the fingerprint is used for login. Note: For Mobile Point-of-Service, this parameter must be set to NoFingerprint. |
|
Default Value |
NoFingerprint |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
FingerprintLoginOptions |
|
Function |
Determines if the employee ID or employee user ID is used for manual entry. |
|
Allowed Values |
Employee, User If set to Employee, the employee ID is used for manual entry. If set to User, the employee user ID is set for manual entry. |
|
Default Value |
User |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ManualEntryID |
|
Function |
Determines if, upon manual entry of an ID, the system then requires a password. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ManualEntryRequiresPassword |
|
Maximum Number Fingerprints |
Function |
Sets the maximum number of fingerprints that can be registered for one employee record. |
Allowed Values |
1 to 10 |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumNumberFingerprints |
Table 3-17 describes the parameters in the Order parameter group.
Table 3-17 Point-of-Service Order Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the maximum number of matches to display when searching for an order. |
|
Allowed Values |
1 to 999 |
|
Default Value |
50 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OrderMaximumMatches |
|
Function |
Determines if the customer can pickup partial orders. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OrderPartialPickup |
|
Function |
Determines if repricing of items is allowed during order pickup. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OrderPartialPickup |
Table 3-18 describes the parameter in the Password Policy group. This parameter group is hidden.
Table 3-18 Point-of-Service Password Policy Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the length of the random temporary password generated by the system. |
|
Allowed Values |
7 to 12 |
|
Default Value |
12 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Back Office, Central Office |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TemporaryPasswordLength |
Table 3-19 describes the parameters in the Price Adjustment parameter group.
Table 3-19 Point-of-Service Price Adjustment Parameter Group
Table 3-20 describes the parameters in the Printing parameter group.
Table 3-20 Point-of-Service Printing Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Prints a customer copy receipt if the post void included a credit, debit, or e-check tender. If a customer copy prints, the number of receipts printed is controlled by the Void Receipt Print Control receipt component. |
|
Allowed Values |
Debit, Credit, E-Check |
|
Default Value |
Debit, Credit, E-Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutoPrintCustomerCopy |
|
Function |
Determines if a gift receipt is automatically printed for any gift registry item that is part of a sale transaction. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutoPrintGiftReceiptForGiftRegistry |
|
Function |
Enables and disables automatic printing of gift receipt when the transaction is a send transaction or contains send items. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AutoPrintGiftReceiptForSend |
|
Function |
Sets the message for the e-check that is franked when the e-check is approved. |
|
Allowed Values |
0 to 1000 alphanumeric characters 1 to 950 multibyte characters Text can be multiple lines |
|
Default Value |
VOID: This check has been |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ECheckFrankApproval |
|
Function |
Enables the reprinting of an original receipt. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
EnableReprintOriginalReceipt |
|
Function |
Determines whether the system prompts the user with the option to send a receipt via e-mail to the customer. |
|
Allowed Values |
Yes, No |
|
Default Value |
Value set at installation time |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
eReceiptFunctionality |
|
Function |
Defines the text for the subject line of an e-mail that contains an attached sales receipt. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
Your receipt from Oracle |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
eReceiptSubject |
|
Function |
Defines the text for the content of an e-mail that contains an attached sales receipt. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
Thank you for shopping at Oracle. |
|
Entry Field Type |
Multiple Line String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
eReceiptText |
|
Function |
Enables and disables franking for external orders. |
|
Allowed Values |
Yes, No If set to Yes, the system prompts for franking of the external order. If set to No, the system does not prompt. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FrankExternalOrder |
|
Function |
Determines whether an issued store gift certificate is franked. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FrankGiftCertificateIssued |
|
Function |
Enables and disables franking for non-cash tenders. |
|
Allowed Values |
None, Deposited Check, e-Check, Trav. Check(s), Mall Gift Cert, Gift Cert., Store Credit, Store Coupon, Money Order, P.O., Mail Bank Check |
|
Default Value |
Deposited Check, Trav. Check(s), MallCert, Gift Cert, Store Credit, Store Coupon, Money Order, P.O., E-check, Mail Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FrankingTenderList |
|
Function |
Determines if items with the same item ID and price are grouped together on a receipt. Note: This excludes serialized items and gift cards. If set to Yes, items are grouped on a receipt. If set to No, items print individually. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GroupLikeItemsOnReceipt |
|
Function |
Determines whether the system prints a receipt for cancelled transactions. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PrintCanceledTransactionReceipt |
|
Function |
Enables and disables credit signature slip printing for a credit card tender. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PrintCreditSignatureSlips |
|
Function |
Enables and disables debit slip printing for a debit tender. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PrintDebitSlip |
|
Function |
Enables and disables e-check signature slip for an e-check tender. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database or Database |
XML |
|
XML Name |
PrintECheckSignatureSlips |
|
Function |
Enables and disables receipt printing. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PrintReceipts |
|
Function |
Pixel height of the signature printed on the credit receipt. |
|
Allowed Values |
0 to 1000 |
|
Default Value |
200 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SignatureBitmapHeight |
|
Function |
Determines whether to skip the Receipt Options screen when e-receipt is enabled. |
|
Allowed Values |
Yes, No If e-receipt is enabled and this parameter is set to Yes, the system checks the customer receipt preference setting when a customer is added to the transaction. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database or Database |
XML |
|
XML Name |
SkipReceiptPrintingOptions |
|
Function |
The bank name for the store that is franked on the deposited check, money order, mall gift certificate, or traveler's check. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
Made Up Bank |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TenderStoreBankName |
|
Function |
The bank account number for the store that is franked on the check or traveler's check. |
|
Allowed Values |
0000000000 to 9999999999 |
|
Default Value |
1234567890 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TenderStoreBankAccountNumber |
|
Function |
A list of tenders to frank if post voided. |
|
Allowed Values |
None, Deposited Check, e-check, Trav. Check, Mall Gift Cert, Gift Cert., Store Credit, Store Coupon, Money Order, P.O. |
|
Default Value |
Deposited Check, Trav. Check, Mall Gift Cert, Gift Cert, Store Credit, Money Order |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML, Database, or Properties File |
XML |
|
XML Name |
TendersToFrankOnPostVoid |
|
Function |
Determines if VAT codes are printed at the item level on a receipt when VAT is enabled. |
|
Allowed Values |
Yes, No If set to Yes, the VAT codes are printed on the receipt. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
VATCodeReceiptPrinting |
|
Function |
Determines if VAT summary information is printed on a receipt when VAT is enabled. |
|
Allowed Values |
Type 1, Type 2 If set to Type 1, the receipt does not include VAT summary information. |
|
Default Value |
Type 1 |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
VATReceiptType |
|
Function |
Determines whether a receipt can be reprinted on any register. |
|
Allowed Values |
Yes, No If set to Yes, then a user is only allowed to reprint a receipt at the register upon which the transaction is completed. If set to No, the transaction can be printed on any register within the store. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time this parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
VerifyRegisterIDOnReprintReceipt |
|
Function |
Determines if the You Saved statement is printed at the bottom of a receipt. If the amount the customer saved is less than the percent set by this parameter, the You Saved statement will not print on the receipt. |
|
Allowed Values |
0 to 100 |
|
Default Value |
5 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
YouSavedThresholdPercent |
Table 3-21 describes the parameter in the Queue parameter group.
Table 3-21 Point-of-Service Queue Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Enables and disables the Clear Queue feature. |
|
Allowed Values |
Yes, No If set to Yes, the Queue button is visible on the Queue Options screen. If set to No, the button is hidden. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ClearQueue |
Table 3-22 describes the parameters in the Reconciliation parameter group.
Table 3-22 Point-of-Service Reconciliation Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Determines whether one or more than one operator can be assigned to a till on a given business day. Note: Once this parameter is set at installation time, it should not be changed. Changing the accountability after installation could cause unexpected results. |
|
Allowed Values |
Note: For Mobile Point-of-Service, this parameter must be set to Register. |
|
Default Value |
Cashier |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_act |
|
XML Name |
None |
|
Function |
Determines whether or not the expected totals are displayed during till reconcile. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next till reconcile |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Back Office |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
BlindClose |
|
Function |
Determines the type of count to do when cash is loaned. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. Database value is 0. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_lon_csh_cnt |
|
XML Name |
None |
|
Function |
Determines the type of count to do when cash is picked up. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. Database value is 0. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_pkp_csh_cnt |
|
XML Name |
None |
|
Function |
Determines the type of count to do when checks are picked up. |
|
Allowed Values |
No, Detail If set to No, the system does not prompt for a count. Database value is 0. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_pkp_chk_cnt |
|
XML Name |
None |
|
Function |
Determines the type of count to do when the till is opened. Count the amount in the till to use as the float for the beginning of the business day. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. Database value is 0. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_opn_flt_cnt |
|
XML Name |
None |
|
Function |
Determines the type of count to do when the till is closed. Count the amount in the till to use as the float for the beginning of the next business day. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. Database value is 0. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_cl_flt_cnt |
|
XML Name |
None |
|
Function |
Determines the type of count to do when the store is closed. Count the amount in the safe to use as the operating fund. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next end of day |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CountOperatingFundsAtEndOfDay |
|
Function |
Determines the type of count to do when the store is opened. Count the amount in the safe to use as the operating fund. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next start of day |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CountOperatingFundsAtStartOfDay |
|
Function |
Determines the type of count to do when the till is closed. Count the amount in the till. |
|
Allowed Values |
No, Summary, Detail If set to No, the system does not prompt for a count. Database value is 0. |
|
Default Value |
Summary |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next start of day |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cd_cl_tl_cnt |
|
XML Name |
None |
|
Function |
Sets the amount of float that should be in the till when it is opened and closed. |
|
Allowed Values |
0 to 999999.99 |
|
Default Value |
100.00 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: cp_blnc_dflt_opn |
|
XML Name |
None |
|
Function |
Determines whether till pickups and loans use the safe or can be done register to register. |
|
Allowed Values |
Yes, No If set to Yes, pickups are from register to safe and loans are from safe to register. If set to No, pickups and loans can be done from register to register. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next start of day |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OperateWithSafe |
|
Function |
Sets the expected amount for the operating fund during the start of day and end of day processing. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
1000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OperatingFundExpectedAmount |
|
Function |
Sets the tenders that are available for pickup. The function key for a tender is displayed only if that tender is included in this list. |
|
Allowed Values |
Cash, Alternate Cash, Check, Alternate Check |
|
Default Value |
Cash, Alternate Cash, Check, Alternate Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PickupTenders |
|
Function |
Enables and disables the tender buttons for all tender types to be counted during a till reconcile. The function key for a tender is only displayed only if that tender is included in this list. |
|
Allowed Values |
Cash, Check, Credit, Debit, Travel Check, Gift Cert., Coupon, Gift Card, Store Credit, Mall Gift Cert., Purchase Order, Money Order, Canadian Cash, Canadian Traveler's Check, Canadian Check, Canadian Gift Certificate, Canadian Store Credit, Mexican Gift Certificate, Mexican Store Credit, U.K. Cash, U.K. Traveler's Check, U.K. Check, U.K. Gift Certificate, U.K. Store Credit, European Cash, European Traveler's Check, European Check, European Gift Certificate, European Store Credit, Japanese Gift Certificate, Japanese Store Credit, U.S. Cash, U.S. Traveler's Check, U.S. Check, U.S. Gift Certificate, U.S. Store Credit |
|
Default Value |
Cash, Check, Credit, Debit, Travel Check, Gift Cert., Coupon, Gift Card, Store Credit, Mall Gift Cert., Purchase Order, Money Order, Canadian Cash, Canadian Traveler's Check, Canadian Check, Canadian Gift Certificate, Canadian Store Credit, Mexican Gift Certificate, Mexican Store Credit, U.K. Cash, U.K. Traveler's Check, U.K. Check, U.K. Gift Certificate, U.K. Store Credit, European Cash, European Traveler's Check, European Check, European Gift Certificate, European Store Credit, Japanese Gift Certificate, Japanese Store Credit, U.S. Cash, U.S. Traveler's Check, U.S. Check, U.S. Gift Certificate, U.S. Store Credit |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Next till reconcile |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TendersToCountAtTillReconcile |
|
Function |
Determines if the till can be reconciled at the Point-of-Service register. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
Database The following information can be used to update the value for this parameter using a SQL statement: table: as_ws column: fl_rcnl_tl |
|
XML Name |
None |
Table 3-23 describes the parameters in the Return parameter group.
Table 3-23 Point-of-Service Return Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the type of ID that is required from the customer during a return transaction that is using a non-retrieved transaction. |
|
Allowed Values |
None, Customer ID, Personal ID, Customer ID and Personal ID |
|
Default Value |
Customer ID and Personal ID |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FormOfIDForNonretrievedReturn |
|
Function |
Determines if cross-border returns are allowed. |
|
Allowed Values |
Yes, No If set to Yes, cross-border returns are allowed. If set to No, they are not allowed. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AllowCrossBorderReturn |
|
Function |
Determines the method used to identify a cross-border return. |
|
Allowed Values |
Country, Currency If set to Country and the country code of the returning store and country code of the store at which the original sale transaction occurred differ, the return is identified as a cross-border return. If set to Currency and the currency code of the returning store and currency code of the store at which the original sale transaction occurred differ, the return is identified as a cross-border return. |
|
Default Value |
Country |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
DetermineCrossBorderReturnBasedOn |
|
Function |
Sets the type of ID that is required from the customer during a return transaction that is using a retrieved transaction. |
|
Allowed Values |
None, Customer ID, Personal ID, Customer ID and Personal ID |
|
Default Value |
None |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FormOfIDForRetrievedReturn |
|
Function |
Sets the date range options used to search for a non-receipted return when searching by tender account number. Specifies the number of days the search includes for the All selection in menus. |
|
Allowed Values |
-1 to 999 where -1 means to search everything |
|
Default Value |
-1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumSearchDateRange |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with cash. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForCashPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with credit. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Credit, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForCreditPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a debit card. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForDebitPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with an e-check. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForECheckPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a gift card. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForGiftCardPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a gift certificate. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForGiftCertPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a mall gift certificate. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForMallCertPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a money order. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForMoneyOrderPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction is not retrieved and the user has not indicated the tender type on the Return Item Info screen. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForNonRetrievedTrans |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a non-store coupon. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForNonStore CouponPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with a purchase order. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForPurchaseOrderPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with store credit. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForStoreCreditPayment |
|
Function |
Defines the list of tenders made available as refund tenders when the original transaction was paid for with traveler's checks. |
|
Allowed Values |
Cash, Credit, Gift Card, Store Credit, Bank Check |
|
Default Value |
Cash, Gift Card, Store Credit, Bank Check |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RefundTenderForTravelCheckPayment |
|
Function |
Sets the restocking fee amount for an item being returned. The fee is based on the original selling price of the item. |
|
Allowed Values |
0.00 to 100.00 |
|
Default Value |
10.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RestockingFee |
|
Function |
Defines the maximum number of matches to display after searching for a transaction. |
|
Allowed Values |
1 to 999 |
|
Default Value |
20 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ReturnMaximumMatches |
|
Function |
Defines the list of accepted sale tenders. This list displays on the Return Item Information screen. For a return with a retrieved transaction, the value defaults to the tender used for the original sale. For a return with a non-retrieved transaction, the user selects the tender used for the original sale. The value is used to determine the list of available refund tenders. The values in this list must also align with the tenders accepted parameters found in the Tender Group. This list is also used for retrieved transactions that had a zero due in the original transaction, for example, an even exchange or an item discounted 100%. |
|
Allowed Values |
Cash, Check, Credit, Debit, Gift Card, Travel Check, Coupon, Store Credit, Mall Certificate, Purchase Order, Money Order, Gift Certificate |
|
Default Value |
Cash, Check, Credit, Debit, Gift Card, Travel Check, Coupon, Store Credit, Mall Certificate, Purchase Order, Money Order, Gift Certificate |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SaleTendersForRefund |
|
Function |
Determines the selling price of the item in a cross border return.
|
|
Allowed Values |
Lowest in X Days, Current Selling Price |
|
Default Value |
Lowest in X Days |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ReturnPriceForCBR |
|
Function |
Determines whether Oracle Retail Returns Management is used to authorize returns. This parameter can be edited only if integration with Returns Management was enabled at installation time. If set to Yes, Returns Management is used. If set to No, Point-of-Service is used to authorize returns. |
|
Allowed Values |
Yes, No |
|
Default Value |
Value set at installation time |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
UseOracleRetailReturnManagement |
|
Function |
Enables and disables the use of the refund tenders determined by the Returns Management application. This parameter can be edited only if integration with Returns Management was enabled at installation time. Note: Manager Override is always presented with the Returns Management tenders, which if used, will then present the Point-of-Service refund tenders. |
|
Allowed Values |
Yes, No If set to Yes, the applicable Returns Management refund tenders are presented to the operator. If set to No, the Returns Management refund tender options are ignored, and the Point-of-Service refund tenders are presented to the operator. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service |
|
Resides in XML or Database |
XML |
|
XML Name |
UseRMTenders |
Table 3-24 describes the parameters in the Security Access parameter group.
Table 3-24 Point-of-Service Security Access Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Determines if reason codes can be edited through the user interface. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
EditReasonCodes |
|
Function |
Enables manager overrides to not be done on some functions that are common occurrences or situations where it is never allowed, regardless of manager override. |
|
Allowed Values |
Accept Invalid DL format, Add Temp Employee, Administration, Back Office, Bank Deposit, Cancel Order, Cancel Transaction, Clock in out, Close Register, Close Till, Customer Add/Find, Customer Delete, Customer Discount, Daily Operations, Discount Rule – Add/Modify, Discount Rule – End, Electronic Journal, E-Mail, Employee Add/Find, Employee Time Maintenance, End of Day, Item Maintenance, Item/Transaction Discounts, Item/Transaction Gift Registry, Item/Transaction Sales Associate, Item/Transaction Tax Modification, Job Queue, Kit Maintenance, Layaway Delete, Modify Layaway Fees, Modify Markdowns, Money Order, No Sale, Open Register, Open Till, Orders, Override Call Referrals, Override Call Referral for accept check, Override Call Referral for accept credit, Override Call Referral for accept gift card, Override Decline Credit, Override Denied Return Item, Override Refund Tenders, Override Restocking Fee, Override Tender Limits, Parameter Group – Base, Parameter Group – Browser, Parameter Group – Customer, Parameter Group – Daily Operations, Parameter Group – Device Status, Parameter Group – Discount, Parameter Group – E-mail, Parameter Group – Employee, Parameter Group – House Account, Parameter Group – Item, Parameter Group – Job Scheduler, Parameter Group – Inventory, Parameter Group – Layaway, Parameter Group – OperatorParameter Group – OrderParameter Group – PrintingParameter Group – QueueParameter Group – ReconciliationParameter Group – ReturnParameter Group – SendParameter Group – LocalizationParameter Group - TaxParameter Group – Tender, Parameter Group – Tender Authorization, Parameter Group – Time Maintenance, Parameter Group – Transaction, Parameter Group – System Settings, Parameter Modify, Point-of-Sale, Price Adjust, Price Change – Add/Modify, Price Override, Price Promotion – Add/Modify, Print VAT Receipt, Queue Management, Reason Codes, Reconcile Till, Reentry on/off, Refund Tender Override, Report: Associate Productivity, Report: Department Sales, Report: Hourly Sales, Report: Order Status, Report: Order Summary, Report: Queue Transaction, Report: Summary, Report: Suspend Transaction, Reprint Gift Receipt, Reprint Receipt, Reset Hard Totals, Return, Return Manager Override, Role – Add/Find, Schedule Jobs, Service Alert, Start of Day, Store Operations, Till Pay In, Till Pay Out, Till pickup load, Training Mode – Enter/Exit, Transaction Details, Transfer, Web Store Note: The Override Denied Return Item and Override Refund Tenders values are not used when the Use Oracle Retail Returns Management parameter is set to Yes and the Use RM Tenders system setting is set to Yes. Note: The following values are no longer used by Point-of-Service: |
|
Manager Override For Security Access, continued |
Default Value |
Same as Allowed Values above |
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ManagerOverrideForSecurityAccess |
Table 3-25 describes the parameters in the Send parameter group.
Table 3-25 Point-of-Service Send Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the maximum number of sends allowed on a transaction. |
|
Allowed Values |
1 to 10 |
|
Default Value |
10 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumSendsAllowed |
|
Function |
Determines if the Send feature is available. If set to Yes, the Send button is available in the user interface at the item and transaction level. If set to No, it is not available. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SendFeature |
|
Function |
Determines how the system calculates the shipping charge on a send transaction. |
|
Allowed Values |
Weight, Dollar Amount, Flat Rate, None |
|
Default Value |
Weight |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
Database |
|
XML Name |
None |
|
Function |
Sets the item number for the service item that is used to represent the shipping charge. |
|
Allowed Values |
7 to 14 characters |
|
Default Value |
Defined by the retailer |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
Database |
|
XML Name |
None |
Table 3-26 describes the parameters in the Tax parameter group.
Table 3-26 Point-of-Service Tax Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Sets the value of the Tax Authority ID used when the system fails to find a tax rule through Item or Department associations. In this case, the Tax Rate parameter value is used to calculate the tax amount. |
|
Allowed Values |
1 to 2147483647 |
|
Default Value |
111111111 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
DefaultTaxAuthorityID |
|
Function |
Sets the default tax group if an item does not have a tax group defined. |
|
Allowed Values |
-1 to 999999999 |
|
Default Value |
-1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
DefaultTaxGroupID |
|
Function |
Determines if the item tax information is printed for each line item on the receipt or not. When VAT is enabled, this parameter is ignored. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
PrintItemTax |
|
Function |
Determines if the tax exempt certificate number and reason code are required. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RequireCertificateInfo |
|
Function |
Determines if a customer must be linked to a tax exempt transaction. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RequireCustomerLink |
|
Function |
Sets the tax rate. |
|
Allowed Values |
0.00 to 100.00 |
|
Default Value |
8.25 |
|
Entry Field Type |
Numeric (Decimal number) |
|
When the Modification Takes Effect |
Next time the parameter is read |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TaxRate |
Table 3-27 describes the parameters in the Tender parameter group.
Table 3-27 Point-of-Service Tender Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Allows a transaction that had a debit tender applied to be post voided. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AllowPostVoidOnDebitTransaction |
|
Function |
Defines the list of tenders accepted for a bill payment. Note: E-Check is not supported as a tender outside the United States. |
|
Allowed Values |
Cash, Check, Coupon, Credit, Debit, e-Check, Gift Cert., Gift Card, House Account, Instant Credit, Mail Bank Check, Mall Gift Cert., Money Order, P.O., Store Cr., Travel Ck. |
|
Default Value |
Cash |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
BillPayTransactionTenders |
|
Function |
Defines the list of accepted credit card types and their call referral numbers that can be displayed on the Call Referral screen. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
Check 111-111-1111 Visa 222-222-2222 MasterCard 333-333-3333 American Express 444-444-4444 Diners Card 555-555-5555 Discover Card 666-666-6666 JCB Card 777-777-7777 House Account Card 888-888-8888 Gift Card 999-999-9999 |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CallReferralList |
|
Function |
Enables and disables the Cash Tender buttons for all available currency types. |
|
Allowed Values |
None, U.S. Dollars, Canadian Dollars, U.K. Pounds, Euro Note: For Mobile Point-of-Service, this parameter must be set to None. |
|
Default Value |
U.S. Dollars, Canadian Dollars |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CashAccepted |
|
Function |
If the total cash amount in the cash drawer is greater than or equal to the value of this parameter, a warning is displayed. |
|
Allowed Values |
0 to 999999.99 |
|
Default Value |
1000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
CashAmountOverWarningFloat |
|
Function |
If the total cash amount in the cash drawer is less than or equal to the value of this parameter, a warning is displayed. |
|
Allowed Values |
0 to 999999.99 |
|
Default Value |
10.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML or Database |
XML |
|
XML Name |
CashAmountUnderWarningFloat |
|
Function |
Sets the denomination used when cash given for change or a refund needs to be rounded. |
|
Allowed Values |
0.05, 0.10, 0.50, 1.00 |
|
Default Value |
0.05 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CashRoundingDenomination |
|
Function |
Sets the rounding method used when cash given for change or a refund needs to be rounded. This parameter is used in conjunction with the Cash Rounding Denomination parameter. |
|
Allowed Values |
None, Swedish Rounding, Round Up, Round Down Note: If no rounding is to be done, set this parameter to None. |
|
Default Value |
None |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CashRoundingType |
|
Function |
Enables and disables the Check Tender button for all currency types. |
|
Allowed Values |
None, U.S. Dollars, Canadian Dollars Note: For Mobile Point-of-Service, this parameter must be set to None. |
|
Default Value |
U.S. Dollars, Canadian Dollars |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ChecksAccepted |
|
Function |
Determines if an expiration date is computed when store credit is issued. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ComputeStoreCreditExpirationDate |
|
Function |
Determines if credit cards and debit cards are accepted. |
|
Allowed Values |
Yes, No If set to Yes, credit cards and debit cards are accepted and the Credit/Debit tender button is enabled. If set to No, credit cards and debit cards are not accepted and the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CreditCardsAccepted |
|
Function |
Sets the item number to be used on an issue or reload of a gift card. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
70071000 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
DefaultGiftCardItemID |
|
Function |
Determines if the system allows the operator to swipe a driver's license or state ID to capture the number. This is only allowed on an attached MSR (keyboard). |
|
Allowed Values |
Yes, No Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
DriversLicenseSwipe |
|
Function |
Determines if e-checks are accepted. This is dependent on whether the authorizer processes e-Checks. Note: E-Check is not supported as a tender outside the United States. |
|
Allowed Values |
Yes, No Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
E-CheckFunctionality |
|
Function |
Determines whether a bill payment is validated to prevent a payment that is more than the total amount due or less than the minimum amount due. |
|
Allowed Values |
Yes, No If Yes, the payment is validated against the total and minimum amounts due. If the payment is more than the total amount due or less than the minimum amount due, the payment is not allowed. If No, the payment is not validated. Any payment is allowed. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
EnableBillPayOverAndUnderValidation |
|
Function |
Defines the fifth local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
50.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FifthGiftCardReloadAmount |
|
Function |
Defines the first local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
10.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FirstGiftCardReloadAmount |
|
Function |
Determines if foreign currency is accepted. |
|
Allowed Values |
Yes, No If set to Yes, the Foreign tender button on the Tender Options screen is enabled. If set to No, the button is disabled. Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ForeignCurrency |
|
Function |
Defines the fourth local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
FourthGiftCardReloadAmount |
|
Function |
Determines if bin range validation is required on a gift card issued. |
|
Allowed Values |
Yes, No If set to Yes, the retailer, third party processor, or both maintain the bin file. If set to No, the bin file is not maintained. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GiftCardBinFileLookup |
|
Function |
Determines if the expiration date for a gift card is computed. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GiftCardComputeExpirationDate |
|
Function |
Sets the number of days until a gift card expires. |
|
Allowed Values |
1 to 9999 |
|
Default Value |
365 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GiftCardDaysToExpiration |
|
Function |
Determines if gift cards are accepted. |
|
Allowed Values |
Yes, No If set to Yes, gift cards are accepted and the Gift Card tender button is enabled. If set to No, gift cards are not accepted and the button is disabled. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GiftCardsAccepted |
|
Function |
Sets the currency types for which gift certificates are accepted. The Gift Certificate tender button is only available for currencies included in this list. |
|
Allowed Values |
None, U.S. Dollars, Canadian Dollars, Mexican Pesos, Euro, Japanese Yen, U.K. Pounds Note: For Mobile Point-of-Service, this parameter must be set to None. |
|
Default Value |
U.S. Dollars, Canadian Dollars, Mexican Pesos, Euro, Japanese Yen, U.K. Pounds |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GiftCertificatesAccepted |
|
Function |
Determines if a House Account card is accepted. |
|
Allowed Values |
Yes, No If set to Yes, the House Account card is accepted and the House Account tender button is enabled. If set to No, the House Account card is not accepted and the button is disabled. Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
HouseCardsAccepted |
|
Function |
Determines if an expiration date is required for a house account card. |
|
Allowed Values |
Yes, No |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
HouseCardExpDateRequired |
|
Function |
Determines if mall certificates are accepted. |
|
Allowed Values |
Yes, No If set to Yes, mall certificates are accepted and the Mall Certificate tender button is enabled. If set to No, mall certificates are not accepted and the button is disabled. Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MallCertificateAccepted |
|
Function |
If the Mall Certificate Sub Tender Required parameter is set to Yes, this parameter defines what sub-tender options to display. |
|
Allowed Values |
Check, Purchase Order |
|
Default Value |
Check, Purchase Order |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MallCertificateSubTenderAcceptedList |
|
Function |
Determines if sub-tender selection is required and if sub-tender screens are displayed. The Cert. Entry screen is skipped when the MGC number is entered. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MallCertificateSubTenderRequired |
|
Function |
Sets the maximum amount of change that can be issued for Gift Certificate tender. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
1000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a Gift Certificate tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumAmountCashChangeForGiftCertificate |
|
Function |
Sets the maximum amount of cash that can be received as tender for a sale. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
1000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCashAccepted |
|
Function |
Sets the maximum amount of cash change that can be given for a redeem transaction. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
500.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCashBackforRedeem |
|
Function |
Sets the maximum amount of cash change that can be issued for a cash sale. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
50.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCashChange |
|
Function |
Sets the maximum amount of cash change that can be issued for Store Credit tender. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
5.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a Store Credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCashChangeForStoreCredit |
|
Function |
Sets the maximum amount of cash that can be refunded in a return. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
100.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCashRefund |
|
Function |
Sets the maximum amount of cash that can be refunded on a manual return (applies to the whole transaction). Note: This parameter is not used when the Use Oracle Retail Returns Management parameter is set to Yes, the Use RM Tenders system setting is set to Yes, and and communication to Oracle Retail Returns Management is online. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
20.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCashRefundWithoutReceipt |
|
Function |
Sets the maximum sale amount that can be tendered by check. |
|
Allowed Values |
0.00 to 99999.99 |
|
Default Value |
3000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a Check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumCheckAmount |
|
Function |
Sets the maximum amount for which a gift card can be sold. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
500.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumGiftCardIssueAmount |
|
Function |
Sets the maximum amount for which a gift certificate can be issued. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
500.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumGiftCertificateIssueAmount |
|
Function |
Sets the maximum amount that can be accepted as tender using multiple gift certificates (the sum of the all gift certificate tender amounts). |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
3000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Start of Day |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumGiftCertificateTenderAmount |
|
Function |
Sets the maximum amount that can be accepted as tender using multiple mall certificates (the sum of the all mall certificate tender amounts). |
|
Allowed Values |
0.00 to 99999.99 |
|
Default Value |
3000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a Mall Certificate is tendered |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumMallCertificateTenderAmount |
|
Function |
Sets the maximum sale amount that can be tendered using a money order. |
|
Allowed Values |
0.00 to 99999.99 |
|
Default Value |
9999.99 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumMoneyOrderAmount |
|
Function |
Sets the maximum amount of cash change that can be issued on a sale tendered by a check. |
|
Allowed Values |
0.00 to 99.99 |
|
Default Value |
40.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumOvertenderCheckAmount |
|
Function |
Sets the maximum sale amount that can be tendered using Traveler's Checks. |
|
Allowed Values |
0.00 to 99999.99 |
|
Default Value |
1000.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a Traveler's Check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MaximumTravelersCheckAmount |
|
Function |
Sets the minimum sale amount for which a check tender will be accepted. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
5.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumCheckAmount |
|
Function |
The minimum amount for which a gift card can be sold. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
5.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumGiftCardIssueAmount |
|
Function |
The minimum amount for which a gift certificate can be issued. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
5.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumGiftCertificateIssueAmount |
|
Function |
Sets the minimum sale amount for which a gift certificate tender will be accepted. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
0.01 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumGiftCertificateTenderAmount |
|
Function |
Sets the minimum sale amount that can be tendered using a money order. |
|
Allowed Values |
0.00 to 99999.99 |
|
Default Value |
1.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumMoneyOrderAmount |
|
Function |
Sets the minimum sale amount for which a store credit tender will be accepted. |
|
Allowed Values |
0.00 to 99999.99 |
|
Default Value |
5.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumStoreCreditIssuanceAmount |
|
Function |
Sets the minimum sale amount for which a traveler's check tender will be accepted. |
|
Allowed Values |
0.00 to 999.99 |
|
Default Value |
1.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a Traveler's Check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumTravelersCheckAmount |
|
Function |
Determines if money orders are accepted. Enables and disables the Money Order button. |
|
Allowed Values |
Yes, No If set to Yes, money orders are accepted and the Money Order button is enabled. If set to No, money orders are not accepted and the button is disabled. Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MoneyOrderAccepted |
|
Function |
Determines if non-store coupons are accepted. |
|
Allowed Values |
Yes, No If set to Yes, non-store coupons are accepted and the Coupon tender button is enabled. If set to No, non-store coupons are not accepted and the button is disabled. Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
NonStoreCouponsAccepted |
|
Function |
Sets the number used as the coupon number when the Non-Store Coupon number is not known. |
|
Allowed Values |
3 to 12 alphanumeric characters |
|
Default Value |
999 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
NonstoreCouponUnknownTriggerNumber |
|
Function |
Sets the tenders for which the drawer is opened on a post void. |
|
Allowed Values |
Cash, Credit, Check, Gift Cert., Debit, Coupon, Gift Card, Store Credit, Purchase Order Note: For Mobile Point-of-Service, the list for this parameter must be empty. |
|
Default Value |
Cash, Credit, Check, Gift Cert., Debit, Coupon, Gift Card, Store Credit, Purchase Order |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OpenDrawerForPostVoid |
|
Function |
Sets the tenders for which the drawer is opened when accepting the tender. |
|
Allowed Values |
None, Credit, Check, Trav. Check, Gift Cert, Debit, Coupon, Gift Card, Store Credit, Mall Gift Cert., Purchase Order, Money Order, Cash Note: For Mobile Point-of-Service, the list for this parameter must be empty. |
|
Default Value |
None, Credit, Check, Trav. Check, Gift Cert, Debit, Coupon, Gift Card, Store Credit, Mall Gift Cert., Purchase Order, Money Order, Cash |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OpenDrawerForTender |
|
Function |
Determines if a store credit is printed on a receipt (store credit number generated by the system), or is slip printed on a pre-printed form that is supplied by the retailer. |
|
Allowed Values |
Yes, No If Yes, Store Credit is slip printed on a pre-printed form. If No, the customer Copy of the Store Credit is printed on a register receipt. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PrePrintedStoreCredit |
|
Function |
Determines if purchase orders are accepted. |
|
Allowed Values |
Yes, No If set to Yes, purchase orders are accepted and the Purchase Order tender button is enabled. If set to No, purchase orders are not accepted and the button is disabled. Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
PurchaseOrdersAccepted |
|
Function |
Sets the tender types available for a redeem transaction. |
|
Allowed Values |
Cash, Mail Bank Check, Credit |
|
Default Value |
Cash, Mail Bank Check, Credit |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
RedeemTransactionTenders |
|
Function |
Defines the second local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
15.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SecondGiftCardReloadAmount |
|
Function |
Defines the seventh local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
100.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SeventhGiftCardReloadAmount |
|
Function |
Defines the sixth local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
75.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SixthGiftCardReloadAmount |
|
Function |
Sets the percentage of the transaction balance due, including taxes, which must be paid as a deposit when an order is created. |
|
Allowed Values |
0 to 100 percent |
|
Default Value |
25 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Next time the Order function is performed |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SpecialOrderDepositPercent |
|
Function |
Sets the number of days from the date of issue to the store credit expiration date. |
|
Allowed Values |
1 to 9999 |
|
Default Value |
365 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StoreCreditDaysToExpiration |
|
Function |
Sets the list of currencies accepted for store credit. The Store Credit tender button for the currency type is enabled only if the currency is included in this list. |
|
Allowed Values |
None, U.S.Dollars, Canadian Dollars, Mexican Pesos, Euro, Japanese Yen, U.K. Pounds Note: For Mobile Point-of-Service, the list for this parameter must be empty. |
|
Default Value |
U.S.Dollars, Canadian Dollars, Mexican Pesos, Euro, Japanese Yen, U.K. Pounds |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
StoreCreditsAccepted |
|
Function |
Determines if the operator is prompted to scan a check. |
|
Allowed Values |
Yes, No If set to Yes, the operator scans through the MICR. If set to No, the operator is presented with the ’Scan or Manually Enter' screen first. |
|
Default Value |
No |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SwipeMICRFirst |
|
Function |
Sets the types of tender that the operator is not allowed to over tender. |
|
Allowed Values |
Cash, Check, Coupon, Credit/Debit/Gift Card, Gift Cert., House Account, Store Credit Note: For Mobile Point-of-Service, the list for this parameter must be empty. |
|
Default Value |
Credit/Debit/Gift Card, Coupon |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TendersNotAllowedForOvertender |
|
Function |
Defines the third local navigation button for a gift card issue or reload. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
20.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Application restart required |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ThirdGiftCardReloadAmount |
|
Function |
Sets the currency types for which traveler's checks are accepted. The Traveler's Check tender button is only available for currencies included in this list. |
|
Allowed Values |
None, U.S. Dollars, Canadian Dollars, U.K. Pounds, Euro Note: For Mobile Point-of-Service, this parameter must be set to None. |
|
Default Value |
U.S. Dollars, Canadian Dollars |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
TravelersChecksAccepted |
|
Function |
Determines whether the system validates the driver's license format for the state or province. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ValidateDriverLicenseFormat |
|
Function |
Determines the validation used for gift certificates. |
|
Allowed Values |
Yes, No If set to Yes, the system validates the gift certificate. If set to No, the system accepts all gift certificate tenders without validating. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ValidateGiftCertifcate |
|
Function |
Determines the validation used for store credit. |
|
Allowed Values |
Yes, No If set to Yes, the system validates the store credit. If set to No, the system accepts all store credit tenders without validating. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ValidateStoreCredit |
Table 3-28 describes the parameters in the Tender Authorization parameter group.
Table 3-28 Point-of-Service Tender Authorization Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Used by retailers to set the level of risk they are willing to accept for e-Check authorization. The valid values are:
|
|
Allowed Values |
Conversion Only, Verification with Conversion, Guarantee with Conversion |
|
Default Value |
Conversion Only |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
AuthorizationConversion |
|
Function |
Determines if check authorization is enabled. |
|
Allowed Values |
Yes, No |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time a check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CheckAuthActive |
|
Function |
Determines the credit card types displayed in the menu on the Call Referral screen. If the system is able to get the card type from the payment application, that value is the default in the card type list and the field is not editable. If the system is unable to get the card type from the payment application, the list is editable and the operator is required to select the appropriate card type. |
|
Allowed Values |
Visa, MasterCard, AmEx, Discover, Diners Club, House Account, JCB |
|
Default Value |
Visa, MasterCard, AmEx, Discover, Diners Club, House Account, JCB |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Start of next transaction |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CreditCardTypes |
|
Function |
The phone number to be displayed when gift card activation is referred. |
|
Allowed Values |
Information defined by the retailer |
|
Default Value |
999-999-9999 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
GiftCardActivationReferralNumber |
|
Function |
The phone number to be displayed on the call referral screen for house account enrollment. |
|
Allowed Values |
Information defined by the retailer |
|
Default Value |
888-888-8888 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
HouseCardRefPhoneNumber |
|
Function |
Sets the features that require a manager override. |
|
Allowed Values |
None, Check Call Referral Approval Requires Manager Override, Credit Call Referral Requires Manager Override, Gift Card Call Referral Approval Requires Manager Override |
|
Default Value |
Credit Call Referral Requires Manager Override |
|
Entry Field Type |
List |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ManagerOverrideParameters |
|
Function |
The retailer's merchant number displayed on the call referral screen. |
|
Allowed Values |
Information defined by the retailer |
|
Default Value |
51230040171234 |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Next time a Credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MerchantNumber |
|
Function |
Sets the minimum amount for which the authorization process is executed on a check tender. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
10.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumCheckAuthorizationAmount |
|
Function |
Sets the minimum dollar amount that must be met before a signature is required on the amount being charged to an Amex credit card. |
|
Allowed Values |
0.00 to 99.99 If set to 0.00, a signature is always required. |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumSigCapForAmex |
|
Function |
Sets the minimum dollar amount that must be met before a signature is required on the amount being charged to a Diners Club credit card. |
|
Allowed Values |
0.00 to 99.99 If set to 0.00, a signature is always required. |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumSigCapForDinersClub |
|
Function |
Sets the minimum dollar amount that must be met before a signature is required on the amount being charged to a Discover credit card. |
|
Allowed Values |
0.00 to 99.99 If set to 0.00, a signature is always required. |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumSigCapForDiscover |
|
Function |
Sets the minimum dollar amount that must be met before a signature is required on the amount being charged to a JCB credit card. |
|
Allowed Values |
0.00 to 99.99 If set to 0.00, a signature is always required. |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumSigCapForJCB |
|
Function |
Sets the minimum dollar amount that must be met before a signature is required on the amount being charged to a Master Card credit card. |
|
Allowed Values |
0.00 to 99.99 If set to 0.00, a signature is always required. |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumSigCapForMasterCard |
|
Function |
Sets the minimum dollar amount that must be met before a signature is required on the amount being charged to a Visa credit card. |
|
Allowed Values |
0.00 to 99.99 If set to 0.00, a signature is always required. |
|
Default Value |
25.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
MinimumSigCapForVisa |
|
Function |
Sets the maximum sale amount that can be tendered by deposited check when the check authorization service is offline or inactive. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
50.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a check tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OfflineCheckFloorLimit |
|
Function |
Sets the maximum sale amount that can be tendered by credit card without referral when credit authorization is offline or inactive. |
|
Allowed Values |
0.00 to 9999.99 |
|
Default Value |
50.00 |
|
Entry Field Type |
Currency |
|
When the Modification Takes Effect |
Next time a credit tender is used |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
OfflineCreditFloorLimit |
|
Function |
Sets the authorization code to use when the check tender amount is less than the Minimum Check Authorization Amount or the Offline Check Floor Limit. The same code is used for both situations. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
SysAuthCode |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
Start of business day |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SystematicApprovalAuthCode |
Table 3-29 describes the parameters in the Transaction parameter group.
Table 3-29 Point-of-Service Transaction Parameter Group
Parameter | Attribute | Description |
---|---|---|
Function |
Determines if the reason code is captured for a no sale transaction. |
|
Allowed Values |
Yes, No If Yes, the reason code field displays. If No, the reason code field does not display. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
CaptureReasonCodeForNoSale |
|
Function |
Determines whether the suspended transaction can be resumed from the Sell Item screen. |
|
Allowed Values |
Yes, No If Yes, the operator can scan the suspended transaction number and resume the transaction from the Sell Item screen. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
ResumeSuspendedTransactionOnSaleScreen |
|
Function |
Determines whether transactions created during Training Mode will be added to the EJournal. |
|
Allowed Values |
Yes, No If Yes, Training Mode transactions will be added to the EJournal and are annotated with Training Mode. If set to No, Training Mode transactions will not be added to the EJournal. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SendTrainingModeTransactionsToJournal |
|
Function |
Determines whether a suspend reason code is required when suspending a transaction. |
|
Allowed Values |
Yes, No Note: For Mobile Point-of-Service, this parameter must be set to No. |
|
Default Value |
Yes |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Next time a transaction is suspended |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
Point-of-Service, Back Office, Central Office |
|
Resides in XML or Database |
XML |
|
XML Name |
SuspendReasonRequired |
This section describes the system configurations for the Point-of-Service application. For a description of the information in this table, see Table 3-2.
For information on the Audit Log system configurations, see Table 7-1. For information on the Password Policy system configurations, see Table 7-2.
Timeouts can be configured for the ACI PIN Comm and Servebase PC-EFT payment applications:
ACI PIN Comm timeouts:
Every type of request sent to the ACI PIN Comm Authorization Service can be configured with a unique timeout. The timeouts are defined in the following file:
OracleRetailStore\Server\pos\config\technician\PaymentTechnician.xml
Servebase PC-EFT timeouts:
Timeouts are defined in the following configuration file. Consult your Servebase documentation for more information.
Servebase.Pceft.Ped.Service.Ip.exe.config
Configuration of tender card types:
Recognition of card types (Gift Card, House Card, Visa, Master Card, American Express, and so on) can be configured. This configuration is used when identifying cards entered into Point-of-Service for Gift Card and House Account tenders and when the third-party payment application does not return the card type. Card type rules should be configured to the same values in the following files:
OracleRetailStore\Server\pos\config\cardtyperules.xml OracleRetailStore\Client\pos\config\cardtyperules.xml
For additional information on configuration for ACI PIN Comm, see Appendix B.
Table 3-30 describes the Point-of-Service system configurations.
Table 3-30 Point-of-Service System Configurations
System Configuration | Attribute | Description |
---|---|---|
Function |
Sets the length of the sequence number portion of the customer ID. |
|
Allowed Values |
6 to 10 |
|
Default Value |
6 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is CustomerIDSequenceNumberLength. |
|
XML Name |
None |
|
Function |
Sets the maximum value for the sequence number in the customer ID. |
|
Allowed Values |
1 to 999999 |
|
Default Value |
999999 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is CustomerIDSequenceNumberMaximum. |
|
XML Name |
None |
|
Function |
Sets the number of digits (first digits from the credit card, house card, or gift card) of the customer's card that the operator must enter when performing a search by credit card, house card, or gift card in Transaction Tracker. |
|
Allowed Values |
1 to 6 |
|
Default Value |
6 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is digits.unmasked.card.first. |
|
XML Name |
None |
|
Function |
Sets the number of digits (last digits from the credit card, house card, or gift card) of the customer's card that the operator must enter when performing a search by credit card, house card, or gift card in Transaction Tracker. |
|
Allowed Values |
1 to 4 |
|
Default Value |
4 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is digits.unmasked.card.last. |
|
XML Name |
None |
|
Function |
Sets the number of digits (first digits from the check's MICR number) of the customer's MICR number that the operator must enter when performing a search by check in Transaction Tracker. |
|
Allowed Values |
2 to 9 |
|
Default Value |
9 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is digits.unmasked.micr.first. |
|
XML Name |
None |
|
Function |
Sets the number of digits (last digits from the check's MICR number) of the customer's MICR number that the operator must enter when performing a search by check in Transaction Tracker. |
|
Allowed Values |
3 to 4 |
|
Default Value |
4 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is digits.unmasked.micr.last. |
|
XML Name |
None |
|
Function |
Indicates whether the total value of the targets of a discount rule must be equal to or less than the value of the sources. |
|
Allowed Values |
True, False If set to True, the total value of the targets of a discount rule must be equal to or less than the value of the sources. If set to False, the total value of the targets of a discount rule do not need to be equal to or less than the value of the sources. |
|
Default Value |
False |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
Immediately |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is enableEqualOrLesserValue. |
|
XML Name |
None |
|
Function |
Determines whether the scan sheet is available from the Sell Item screen. |
|
Allowed Values |
True, False If set to True, the scan sheet is available. If set to False, it is not available. |
|
Default Value |
True |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is enableScanSheet. |
|
XML Name |
None |
|
Function |
Determines the default hard total file size. |
|
Allowed Values |
The required minimum file size is 1000000. |
|
Default Value |
1000000 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The session name is SimulatedHardTotalsSession. |
|
XML Name |
None |
|
Function |
Determines if IMEI scanning is enabled for the Item number field on screens. |
|
Allowed Values |
True, False If set to True, IMEI scanning is enabled. If set to False, it is disabled. |
|
Default Value |
False |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is IMEIEnabled. |
|
XML Name |
None |
|
Function |
Maximum grid size of the scan sheet. The total number of items shown in the scan sheet per page is Max Grid Size multipled by Max Grid Size. |
|
Allowed Values |
Defined by the retailer |
|
Default Value |
4 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is maxGridSize. |
|
XML Name |
None |
|
Function |
Defines the maximum number of seconds to wait for the item inventory request to Oracle Retail Store Inventory Management to complete before the request times out. |
|
Allowed Values |
1 to 120 |
|
Default Value |
60 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the category is: |
|
XML Name |
None |
|
Function |
Sets the URL used to access the Oracle Retail Store Inventory Management application. |
|
Allowed Values |
Valid URL address |
|
Default Value |
|
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the category is: |
|
XML Name |
None |
|
Function |
Determines if a gift card number can be entered manually or if the card must be swiped on the payment application device. |
|
Allowed Values |
True, False If set to true, the gift card number can be manually entered. If set to false, the card can only be swiped on the device. |
|
Default Value |
False |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is POSGFCardTenderEntryRequired. |
|
Function |
Enables and disables inventory inquiry to Oracle Retail Store Inventory Management when integrated with Oracle Retail Store Inventory Management. Note: Once this system configuration is set at installation time, it should not be changed except by reinstalling. |
|
Allowed Values |
True, False |
|
Default Value |
Depends on the selection made during installation |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is PSIEnabled. |
|
Function |
Enables and disables inventory reservation functionality (order and layaway) when integrated with Oracle Retail Store Inventory Management. Note: Once this system configuration is set at installation time, it should not be changed except by reinstalling. |
|
Allowed Values |
True, False |
|
Default Value |
Depends on the selection made during installation |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is InventoryReservationEnabled. |
|
Function |
Enables and disables the integration with Oracle Retail Store Inventory Management. Note: Once this system configuration is set at installation time, it should not be changed except by reinstalling. |
|
Allowed Values |
True, False |
|
Default Value |
Depends on the selection made during installation |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is InventoryUpdateEnabled. |
|
Function |
Enables and disables item basket functionality when integrated with with Oracle Retail Store Inventory Management. Note: Once this system configuration is set at installation time, it should not be changed except by reinstalling. |
|
Allowed Values |
True, False |
|
Default Value |
Depends on the selection made during installation |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is ItemBasketEnabled. |
|
Function |
Determines the number of days the system will search for the lowest price on an item being returned in a non-retrieved return transaction. |
|
Allowed Values |
0 to 30 |
|
Default Value |
0 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is ReturnPriceDays. |
|
Function |
Enables and disables serialization functionality (validate and update) when integrated with Oracle Retail Store Inventory Management. Note: Once this system configuration is set at installation time, it should not be changed except by reinstalling. |
|
Allowed Values |
True, False |
|
Default Value |
Depends on the selection made during installation |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is SerializationEnabled. |
|
Function |
Enables and disables the signature capture process using a device for the authorized payment application. |
|
Allowed Values |
True, False |
|
Default Value |
True |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the property is SignatureCaptureEnabled. |
|
Function |
Sets the number of seconds for the system to wait to receive a response from Central Office for both transaction and customer searches. |
|
Allowed Values |
1 to 600 |
|
Default Value |
19 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service, Mobile Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The name of the properties are: |
|
XML Name |
None |
|
Function |
Sets the date format used for the barcode. |
|
Allowed Values |
yyyyMMdd, MMddyyyy |
|
Default Value |
yyyyMMdd |
|
Entry Field Type |
String |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is TransactionIDBarcodeDateFormat. |
|
XML Name |
None |
|
Function |
Sets the length of the sequence number portion of the transaction ID. |
|
Allowed Values |
4 to 10 |
|
Default Value |
4 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is TransactionIDSequenceNumberLength. |
|
XML Name |
None |
|
Function |
Sets the maximum value of the sequence number portion of the transaction ID. |
|
Allowed Values |
1 to 9999 |
|
Default Value |
9999 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is TransactionIDSequenceNumberMaximum. |
|
XML Name |
None |
|
Function |
Determines if zero should be skipped for the sequence number portion of the transaction ID. |
|
Allowed Values |
True, False If set to true, zero is skipped for the sequence number. If set to false, it is not skipped. |
|
Default Value |
False |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is TransactionIDSequenceNumberSkipZero. |
|
XML Name |
None |
|
Function |
Sets the length of the store ID portion of the transaction ID. |
|
Allowed Values |
5 to 7 |
|
Default Value |
5 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is TransactionIDStoreIDLength. |
|
XML Name |
None |
|
Function |
Sets the length of the workstation ID portion of the transaction ID. |
|
Allowed Values |
3 to 5 |
|
Default Value |
3 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
At restart of the application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
Properties File This system configuration is defined in the following file: The property name is TransactionIDWorkstationIDLength. |
|
XML Name |
None |
|
Function |
Determines where transactions are retrieved from for the following:
|
|
Allowed Values |
|
|
Default Value |
Locally Only |
|
Entry Field Type |
Discrete |
|
When the Modification Takes Effect |
At restart of application |
|
Applications Affected by Modifications to the Parameter |
Point-of-Service |
|
Applications Where the Parameter Can be Modified in the User Interface |
None |
|
Resides in XML, Database, or Properties File |
XML This system configuration is defined in the following file: Use store, failover, or enterprise. |
|
XML Name |
ReadTransactionsForReturn |
In Release 13.1.1, parameters used to manage receipts were replaced by components in blueprint files. Table 3-31 lists those receipt components that replaced the parameters.
For more information on receipt components, see "Editing Receipt Components in a Blueprint File" in Chapter 2. For a description of the information in this table, see Table 3-3.
Table 3-31 Point-of-Service Receipt Components
Receipt Component | Attribute | Description |
---|---|---|
Function |
Sets the number of receipts that print for an alteration transaction. If multiple copies print for an alteration transaction (such as one store copy, one customer copy, and one merchandise copy), the number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
3 One store copy, one customer copy, and one merchandise copy |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
AlterationReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
The phone number and other information to be displayed when authorization is referred for a House Account enrollment. The number prints on the Temporary Shopping Pass. |
|
Allowed Values |
Information defined by the retailer |
|
Default Value |
1-800-xxx-xxxx |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TempShoppingPass.bpt |
|
Function |
Sets the number of receipts that print for a canceled transaction. This print control is linked internally to the sale receipt print control. The number of receipts that print for a canceled transaction is determined by multiplying this print control by the sale receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
CanceledReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the text that is printed on a customer survey receipt. |
|
Allowed Values |
0 to 900 Alphanumeric defined by the retailer |
|
Default Value |
Give us your feedback and get 10% off |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
Survey.bpt |
|
Function |
Sets the legal statement printed on the signature slip (bank copy) when the e-check is used to tender the transaction. |
|
Allowed Values |
Any valid text |
|
Default Value |
Authorization Agreement: I authorize |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
ECheckSignatureSlipReceipt.bpt |
|
Function |
Sets the number of receipts that print for an exchange transaction. This print control is linked internally to the sale receipt print control. The number of receipts that print for an exchange transaction is determined by multiplying this print control by the sale receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
ExchangeReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the legal statement printed on the signature slip when the transaction is an exchange transaction with a positive or negative balance due. |
|
Allowed Values |
Any valid text For information on changing legal statements, see the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions. |
|
Default Value |
Exchange Legal statement of liability |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
CreditSignatureSlipReceipt.bpt |
|
Function |
Sets the text printed in the footer for a gift receipt. |
|
Allowed Values |
Any valid text Allows for eight lines of text at the bottom of the receipt. If no text is entered, the receipt will not print any extra lines on the gift receipt. |
|
Default Value |
Congratulations!! |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
GiftReceipt.bpt |
|
Function |
Sets the text printed in the footer for redeem transactions. |
|
Allowed Values |
Any valid text |
|
Default Value |
Thank you for visiting |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
RedeemReceipt.bpt |
|
Function |
Sets the text that is printed in the header for a gift receipt. |
|
Allowed Values |
Any valid text Allows for eight lines of text at the top of the receipt above the store name and address information. If no text is entered, the receipt will not print any extra lines on the gift receipt. |
|
Default Value |
Congratulations |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
GiftReceipt.bpt |
|
Function |
Sets the number of receipts that print for a House Account payment transaction. If multiple copies print for a House Account payment transaction (such as one store copy and one customer copy), the number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
HousePaymentReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a layaway delete transaction. If multiple copies print for a layaway delete transaction (such as one store copy, one customer copy, and one merchandise copy), the number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
LayawayDeleteReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the text for the legal statement printed on the receipt when the transaction is a layaway. |
|
Allowed Values |
Any valid text For information on changing legal statements, see the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions. |
|
Default Value |
Layaway Legal statement of liability |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
LayawayDeleteReceipt.bpt |
|
Function |
Sets the number of receipts that print for a layaway payment transaction. This print control is linked internally to the layaway receipt print control. The number of receipts that print for a layaway payment transaction is determined by multiplying this print control by the layaway receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
LayawayPaymentReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a layaway pickup transaction. This print control is linked internally to the layaway receipt print control. The number of receipts that print for a layaway pickup transaction is determined by multiplying this print control by the layaway receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
LayawayPickupReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a layaway transaction. If multiple copies print for a layaway transaction (such as one store copy, one customer copy, and one merchandise copy), the number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
3 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
LayawayReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a no sale transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
NoSaleSlip.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the text printed for the footer when customer information is collected for a transaction in order to comply with the United States Patriot Act. The information is printed to inform the customer that the customer information collected for the transaction is being sent to the Internal Revenue Service. |
|
Allowed Values |
Any valid text |
|
Default Value |
The amount reflected above, |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
PAT.bpt |
|
Function |
Determines if the customer name is printed on the credit signature slip. |
|
Allowed Values |
Any valid text |
|
Default Value |
Customer name, if available, is printed |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
CreditSignatureSlip.bpt |
|
Function |
Sets the text printed in the footer of a receipt. |
|
Allowed Values |
Any valid text |
|
Default Value |
Thank you for visiting |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
Footer.bpt |
|
Function |
Sets the text printed in the header of a receipt. |
|
Allowed Values |
Any valid text |
|
Default Value |
ORACLE |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
Logo.bpt |
|
Function |
Sets the number of receipts that print for a return transaction. This print control is linked internally to the sale receipt print control. The number of receipts that print for a return transaction is determined by multiplying this print control by the sale receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
ReturnReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the legal statement printed on the signature slip when the transaction is a return. |
|
Allowed Values |
Any valid text For information on changing legal statements, see the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions. |
|
Default Value |
Legal statement of liability |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
CreditSignatureSlipReceipt.bpt |
|
Function |
Sets the number of receipts that print for a sale transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
SaleReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the legal statement printed on the signature slip when the transaction is a sale. |
|
Allowed Values |
Any valid text For information on changing legal statements, see the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions. |
|
Default Value |
Legal statement of liability |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
CreditSignatureSlipReceipt.bpt |
|
Function |
Sets the number of receipts that print for an order cancel transaction. This print control is linked internally to the special order receipt print control. The number of receipts that print for an order cancel transaction is determined by multiplying this print control by the special order receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
SpecialOrderCancelReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for an order complete transaction. This print control is linked internally to the special order receipt print control. The number of receipts that print for an order complete transaction is determined by multiplying this print control by the special order receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
SpecialOrderCompleteReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for an order transaction. If multiple copies print for an order transaction (such as one store copy and one customer copy), the number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
2 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
SpecialOrderReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a suspend transaction. This print control is linked internally to the sale receipt print control. The number of receipts that print for a suspend transaction is determined by multiplying this print control by the sale receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
SuspendReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a tax exempt transaction. This print control is linked internally to the sale receipt print control. The number of receipts that print for a tax exempt transaction is determined by multiplying this print control by the sale receipt print control, as shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TaxExemptReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the information that is printed in the header of a temporary shopping pass. |
|
Allowed Values |
Any valid text |
|
Default Value |
ORACLE |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
Logo.bpt |
|
Function |
Sets the information that is printed in the footer of a temporary shopping pass. |
|
Allowed Values |
Any valid text |
|
Default Value |
Thank you for visiting |
|
Entry Field Type |
Text |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
Footer.bpt |
|
Function |
Determines whether a barcode for the House Account number is printed on a Temporary Shopping Pass. |
|
Allowed Values |
true, false If set to true, the barcode is printed. If set to false, the barcode is not printed. |
|
Default Value |
true |
|
Entry Field Type |
Boolean |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TempShoppingPass.bpt Set printedAsBarcode="true" |
|
Function |
Sets the number of receipts that print for a till loan transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TillLoanReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a till payin transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TillPayInReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a till payout transaction. If multiple copies print for a till payout transaction (such as one store copy, one customer copy, and one merchandise copy), the number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TillPayOutReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a till payroll payout transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TillPayrollPayOutReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a till pickup transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
TillPickupReceipt.bpt Set the number of copies (n) in the following statement: |
|
Function |
Sets the number of receipts that print for a void transaction. The number of receipts that print based on this print control setting are shown in the following examples:
|
|
Allowed Values |
Any whole number |
|
Default Value |
1 |
|
Entry Field Type |
Numeric |
|
When the Modification Takes Effect |
When the blueprint file is distributed, if it is distributed, and read |
|
Blueprint File Name |
VoidHousePaymentReceipt.bpt Set the number of copies (n) in the following statement: VoidLayawayReceipt.bpt Set the number of copies (n) in the following statement: VoidRedeemReceipt.bpt Set the number of copies (n) in the following statement: VoidSaleReceipt.bpt Set the number of copies (n) in the following statement: VoidSpecialOrderReceipt.bpt Set the number of copies (n) in the following statement: VoidTillAdjustmentsReceipt.bpt Set the number of copies (n) in the following statement: |