Oracle Retail Xstore Office Configuration Options

Country Pack - Brazil

Days Back for SPED Export

The SPED (Sistema Público de Escrituração Digital) export process creates the Brazilian SPED report for a single day. To allow for any delays in replication, the report is generated on a delay. This configuration specifies the number of days to wait before generating the report for a specific date. The task creates a daily XML file for each shop. Each XML file is made available for download through the File REsTful resource. For more details on the File resource, see Xstore Office Services in the Oracle Retail Xstore Suite Services Guide.

Deployment Category

Automatically Deploy Data Manager Changes?

If set to true, Oracle Retail Xstore Office automatically deploys pending Data Manager changes at a specified time each day. The time of day is determined by the Data Manager Automatic Deployment Time setting.
Data Manager Automatic Deployment Time

The time of the day to start the auto deployment of undeployed Data Manager changes. The time should be in the format of HH:MM using the 24 hr clock. This setting is only relevant when the Automatically Deploy Data Manager Changes? setting is enabled.
Deployment Download Connection Timeout

The amount of time, in seconds, that Oracle Retail Xenvironment will spend attempting to connect to Xcenter (part of Oracle Retail Xstore Office) to download a deployment. Once the time has elapsed with no connection detected, the attempt will be considered a failure. This setting is used by Oracle Retail Xenvironment at the store.
Deployment Download Retries

The number of times Oracle Retail Xenvironment will attempt to download updates from Oracle Retail Xstore Office before failing. The default value is 10 attempts. A setting of zero (0) means never retry, which is not recommended. This setting is used by Oracle Retail Xenvironment at the store.
Deployment Download Retry Interval

The time interval, in seconds, that Oracle Retail Xenvironment will wait after a failed deployment download attempt before it tries to download the deployment again.

This setting is used by Oracle Retail Xenvironment at the store.
Detection Interval for Automatically Deployed Data Files

How often (in minutes) the system checks theDirectory for Automatically Deployed Data Files to be deployed automatically to all stores.
Directory for Automatically Deployed Data Files

The directory into which DataLoader files can be placed for automatic deployment. Dataloader files placed in this directory will be automatically detected by Oracle Retail Xstore Office and will be deployed to the appropriate stores that are identified within the file.
Interval for Checking for Deployment Waves That Require Approval

The time interval, in minutes, for running the Wave Approval email service. The default value is 60 minutes. For example, if set to 60 minutes, the service will run every hour to scan for new waves and send emails. An email will be sent for waves that meet the Number of Days Before Deployment Wave to Send Notification requirement.
Number of Days Before Deployment Wave to Send Notification

The number of days prior to the projected launch date of a wave with a launch type of Approval Required that an email notification goes out. Valid values are from 1 to 365. The default value is 3 days.
Number of Records in Deployment Viewer

The maximum number of Deployment records to display per page in the Deployment Viewer.

General Category

Beginning Time of the Business Day

To support alert reporting, this is the time-in hours from 00:00 UTC, that denotes the corporate start time of the business day. (For example, 5 is 05:00 UTC.)
Default Country Code

The default country code for use in Xadmin.
Default Currency Code

The default currency code for use in Xadmin. All monetary values entered and displayed across Xadmin are assumed to be of the default currency.
Default Deposit Bank Account Number

When creating a new store, this is the default deposit bank account number.
Default Deposit Bank Name

When creating a new store, this is the default deposit bank name.
Default Locale Code

The default locale code (language) used in Xadmin for automated and system functions. The list of available locales includes all those which are officially part of Xadmin and are included in the list of the available locales for the organization.
Delete FIFO data after report generation?

When enabled (true), FIFO data is deleted after a FIFO report is generated.
Enable the Option to Create Store-Specific Configurations?

When enabled (true), users have the ability to create or override configurations for a specific store in Configurator. See Configurator, section Managing Configurations.
Enable the Option to Delete Configurations?

When enabled (true), configurations for profile or store-specific overrides can be deleted in Configurator. If set to false, all access to this functionality is disabled within Oracle Retail Xstore Office, regardless of the privileges.
File Upload Directory

The directory in which files are stored that are uploaded by users via the File Upload feature.
Interval for Checking for Missing Registers

How frequently Xcenter checks for missing registers, in minutes. The default value is 15 minutes. The value of this setting should be less than the Time Before Register Is Considered Missing setting.
Number of Records in POSLog Publisher Result Page

The maximum number of POSLog records displayed per page on the POSLog publisher result page. The minimum value allowed is 1.
POSLog Publish Max Search Results

The maximum number of POSLog records returned from the database for republishing.
Published POSLog Directory

The directory where the published PosLog file will be saved.
Time Before Missing Register Is Ignored

Once a device has been missing for the amount of time specified here (in hours), it is no longer reported as a problem. The default value is 72 hours.
Time Before Register Is Considered Missing

The amount of time-in minutes- that must elapse since a register's last check-in before it is considered missing. The default value is 61 minutes.
Use Till Based Accountability?

When creating a new store, this option determines whether Till Accountability mode or Register Accountability mode is used as the default setting.

Omni Channel Data Service

Note:

The Omni Channel Data Service settings were moved to the xcenter.properties file.

Purge

Enable Data Purge?

Enable to purge old data and files per the additional settings in this category.
Data Purge Execution Time

The time of day to start the automatic purge of data. Sets UTC time at which the job will occur. Enter this value in HH:MM format.
Number of Days to Keep Transactions

The age in days that all transaction data (including line items, tenders, and so on), Order Broker order data, and inventory control documents that are part of end of year processing is kept in the Xcenter database when the purge process runs.

The number of days specified here should be greater than the number of days to keep customers and customer accounts.

This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.

The purge setting for transactions must not be more aggressive than the possible period for customer accounts like layaways and special orders to be completed. If one of the transactions related to a customer account is purged before the customer account is closed AND the in-store database is replaced (for example, as part of a hardware refresh) the customer account will not be serviceable. Specifically, the items on the account cannot be picked up, nor can the payments be refunded.
Number of Days to Keep POSLogs

The age in days that all POSLog data is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Customers and Customer Accounts

The age in days that all identifying customer data, loyalty data, and customer relationship data is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Event Logs

The age in days that all sourcing and targeting information for application updates to be delivered to/installed on clients is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Cycle Questions

The age in days that location data involving open/close process questions and answers, business date, workstation status, and retail location status are kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Discounts and Deals

The age in days that discount and deal data, including concurrent discount compatibility data, customer group discount mapping data, item exclusion/inclusion data, eligibility data, deal definition data, customer group deal mapping data, item-based deal rules, matching rules, deal triggers, and time-based deal rules is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Email

The age in days that all emails associated with transactions is kept in the Xcenter database when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Employee Hours and Payroll

The age in days that all employee data in the Xcenter database concerning employment dates, pay, vacation, tasks, schedule, and timeclock entries is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Inventory

The age in days that all inventory data in the Xcenter database concerning inventory buckets, cartons, counts, count sheets, and count snapshots is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Invoices and Documents

The age in days that all invoice and document data, including country pack related invoices and documents, is kept in the Xcenter database when the purge process runs. This setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Items

The age in days that all item data in the Xcenter database such as attached items, item messages, prices, deal properties, restrictions, refund schedule, and warranty information is kept in the Xcenter database when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Orders

The age in days that all cancelled and completed order data, including customer data associated with the order, fulfillment details, sourcing details, payment information, and balance data is kept in the Xcenter database when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Report and Receipt Output

The age in days that all report data, including country pack related, and common data such as receipt text, work order service locations, vendor addresses, airport zones, and reason codes is kept in the Xcenter database when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Tax

The age in days that all tax data in the Xcenter database including exemptions, rules, and rule overrides is kept in the Xcenter database, when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Tender, Voucher and Session Info

The age in days that all tender, voucher, and session data from the Xcenter database including denominations, availability, user settings, and options is kept in the Xcenter database when the purge process runs. This purge setting does not affect data, kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Flight Info

The age in days that all flight data is kept in the Xcenter database when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data is deleted. If set to -1 the data is kept indefinitely.
Number of Days to Keep Completed Deployments

The age in days that completed or canceled deployment files, transferred to the file server, will be kept when the purge process runs. If set to 0 all of these files are deleted. If set to -1 the files are kept indefinitely.
Number of Days to Keep File Transfer Archives

The age in days that archive folders from the AutoFileTransferDirectory will be kept when the purge process runs. If set to 0 all of these files are deleted. If set to -1 the files are kept indefinitely.
Number of Days to Keep File Uploads

The age in days that files uploaded via Xadmin will be kept when the purge process runs. If set to 0 all of these files are deleted. If set to -1 the files are kept indefinitely.
Number of Days to Keep POSPoll Files

The age in days that old files from Xcenter's POSPoll File Directory will be kept when the purge process runs. If set to 0 all of these files are deleted. If set to -1 the files are kept indefinitely.
Number of Days to Keep Republished POSLogs

The age in days that old POSLogs from the POSLog Publisher Remote File Directory will be kept when the purge process runs. If set to 0 all of these files are deleted. If set to -1 the files are kept indefinitely.
Number of Days to Keep Temporary Store Requests

The age in days that all temporary store request data is kept in the Xcenter database when the purge process runs. This purge setting does not affect data kept in stores. If set to 0 all of this data will be deleted. If set to -1 files are kept indefinitely.

Temporary Store Server Management

Temporary Store Employee Message Duration

Duration (in days) employee message must be on when status of temporary store request changes.

Reports Category

Default Report Output Format.

The report output format to be used as the default type when running reports. Valid values include:
- PDF (Portable Document Format)
- HTML (Hyper Text Markup Language)
- XLS (Spreadsheet file format created by Microsoft for use with MS Excel)
- XLSX (MS Excel 2007 or newer)
- PPTX (MS PowerPoint)
- RTF (Rich Text Format)
- DOCX (Microsoft Office Open XML Format Document)
Enable DOCX (MS Word) as a Report Output Format?

If true, reports can be produced in DOCX format.
Enable HTML (Hyper Text Markup Language) as a Report Output Format?

If true, reports can be produced in HTML format.
Enable PDF (Portable Document Format) as a Report Output Format?

If true, reports can be produced in PDF format.
Enable PPTX (MS PowerPoint) as a Report Output Format?

If true, reports can be produced in PPTX format.
Enable RTF (Rich Text Format) as a Report Output Format?

If true, reports can be produced in RTF format.
Enable XLS (MS Excel) as a Report Output Format?

If true, reports can be produced in XLS format.
Enable XLSX (MS Excel 2007 or Newer) as a Report Output Format?

If true, reports can be produced in XLSX format.

User Account Category

Default Domain Name for LDAP.

The default domain name to be used when authenticating users using LDAP.
Enable LDAP Authentication Option?

If set to Yes, enables Oracle Retail Xstore Office to authenticate users using LDAP directory. This is the global on/off switch.
LDAP Provider URL.

The URL to be used to connect to the LDAP server.
Method of Creating Password for New Users.

The method used to create the password for newly added users. See Password Options - Non LDAP for more information about the three options available.
Number of Capital Letters Required for a Password.

The minimum number of capital letters that should appear in a password. The default value is 1. The minimum number is zero (0).
Number of Changes Before a Password Can Be Reused.

The number of password resets within which associates are not allowed to reuse the same password. For example, setting the value to 12 ensures a user's new password cannot match any of his/her 12 previous passwords. A setting of zero (0) means that the same password can always be reused.
Number of Consecutive Characters Allowed in a Password.

The maximum number of times that any given symbol or character can repeat consecutively within the password string. The default value is 2.
Number of Login Attempts Before Account Is Locked.

The number of times an invalid password can be entered before the Oracle Retail Xstore Office user account is locked.
Number of Numbers Required for a Password.

The minimum number of digits that should appear in a password

(accepted values = 0-9). The minimum number is zero (0). The default value is 1.
Number of Special Characters Required for a Password.

The minimum number of special characters that should appear in a password. The default value is 1 special character. See Passwords: Special Characters & Rules for a list of valid special characters.
Password Expiration Days.

The number of days that a password can be used before it expires. The default value is 90 days.
Password Length.

The minimum length of a password. The default value is 8.

Note:

If this value is set to less than 1, passwords have no minimum length, but cannot be empty/blank.
User ID Length.

The minimum number of characters in an Oracle Retail Xstore Office user ID. Valid values are 1 through 30.