Working with Admin Properties (CPRP)

Purpose: Use this menu option to define system-wide configuration settings for Order Administration that an administrator would update.

When you update a property setting, your update takes effect immediately.

In this topic:

Work with Admin Properties Screen

Use this screen to define property settings that are available to an administrator user in the application.

How to display this screen: Enter CPRP in the Fast path field or select Work with Admin Properties from a menu.

When you first advance to this screen, property settings display on this screen in ascending property name sequence.

Column sort: You can sort on any column on this screen by clicking the column name. An arrow pointing up displays next to the field when the values for the field display in ascending sequence; an arrow pointing down displays next to the field when the values for the field display in descending sequence.

Field	Description
Group	The type of property setting. Valid values are: Email: The property setting is related to email processing. Logging: The property setting is related to logging. Integration: The property setting is related to an integration with an external system. Monitor: The property setting is related to job monitoring. Printing: The property setting is related to printing. System: The property setting is related to a system-wide function. Enter a full or partial group name to display property settings that contain your entry. Alphanumeric, 25 positions; optional.
Property	The name of the property. Enter a full or partial property name to display property settings that contain your entry. Alphanumeric, 75 positions; optional.
Value	The current setting of the property. If this field is blank, it means a property setting has not been defined. Enter a full or partial property value to display property settings that contain your entry. Alphanumeric, 150 positions; optional.
Type	The type of property setting. Valid values are: Admin = The property setting is a setting available to an administrator user in the application. Customer = The property setting is a setting available to a user in the application. Enter a full or partial property type to display property settings that contain your entry. Alphanumeric, 10 positions; optional.

Screen Option	Procedure
Change the current value defined for a property	Select Change for a property to advance to the Change Property screen.
Switch between viewing admin property settings and customer property settings	Select Admin/Customer. If you are currently on the Work with Admin Properties screen, the system advances you to the Work with Properties Screen. If you are currently on the Work with Properties screen, the system advances you to the Work with Admin Properties Screen.

Screen Option

Procedure

Change the current value defined for a property

Select Change for a property to advance to the Change Property screen.

Switch between viewing admin property settings and customer property settings

Select Admin/Customer.

If you are currently on the Work with Admin Properties screen, the system advances you to the Work with Properties Screen.
If you are currently on the Work with Properties screen, the system advances you to the Work with Admin Properties Screen.

Change Property Screen

Purpose: Use this screen to change a property setting.

How to display this screen: Select Change for a property on the Work with Admin Properties Screen.

Field	Description
Property	The name of the property whose value you wish to update. Alphanumeric, 75 positions; display-only.
Group	The group assigned to the property. Alphanumeric, 25 positions; display-only.
Type	The type of property setting. Valid values are: Admin = The property setting is a setting available to the administrator user. Customer = The property setting is a setting available to customer. Alphanumeric, 10 positions; display-only.
Display	Defines whether you can update the property setting. Valid values are: C = You can change the value defined for the property. D = The value defined for the property is display-only. Alphanumeric, 1 position; display-only.
Value	The current setting of the property. If this field is blank, it means a property setting has not been defined. Note: The system does not validate your entry. Alphanumeric, 150 positions; optional.

Summary of Admin Properties

The property settings that display on the Work with Admin Properties Screen are listed below.

Email Property Settings

See Email Generation Setup for more information on the required and optional setup for generating email notifications through Order Administration.

Property Name	Description
CWEMAIL_TEMPLATE_PATH	The location of the folder containing the template files used to generate HTML-based emails. Not used for shipment emails generated through the Narvar integration.
oms.email.job.queue.output.name	The output queue to use for emails. Output queues are displayed when you select the My Jobs option in Order Administration, where you can use them for filtering purposes. The default output queue is EMAIL. Not used for shipment emails generated through the Narvar integration.
oms.email.support.to	The list of email addresses to receive the Support Notification email when a job is placed in MSG status because an error has occurred, or System Alert email for other errors such as inconsistent system control value setup across companies. Separate each email address with a semi-colon (;), such as: email1@add.com;email2@add.com. Note: You cannot enter an email distribution list in this field. However, you can use an email program, such as Microsoft Outlook®, to create rules to send emails to a distribution list. See Order Administration Support Notification for more information on error email processing.

Property Name

Description

CWEMAIL_TEMPLATE_PATH

The location of the folder containing the template files used to generate HTML-based emails.

Not used for shipment emails generated through the Narvar integration.

oms.email.job.queue.output.name

The output queue to use for emails. Output queues are displayed when you select the My Jobs option in Order Administration, where you can use them for filtering purposes.

The default output queue is EMAIL.

Not used for shipment emails generated through the Narvar integration.

oms.email.support.to

The list of email addresses to receive the Support Notification email when a job is placed in MSG status because an error has occurred, or System Alert email for other errors such as inconsistent system control value setup across companies. Separate each email address with a semi-colon (;), such as: email1@add.com;email2@add.com.

Note: You cannot enter an email distribution list in this field. However, you can use an email program, such as Microsoft Outlook®, to create rules to send emails to a distribution list.

See Order Administration Support Notification for more information on error email processing.

Forms Property Settings

Property Name	Description
BI_BYPASS_CACHE_ENABLE	Defines whether the system bypasses caching for reports generated using Oracle Business Intelligence Publisher. true = Bypass caching for reports generated using Oracle Business Intelligence Publisher. false = Cache reports generated using Oracle Business Intelligence Publisher.
BI_REST_REPORTS_FOLDER	The location in Oracle Analytics Cloud where Order Administration reports are stored. Needs to be set to OMSCS/Reports/.
BI_REST_URL	The name of the host where Oracle Business Intelligence Publisher is running. The system uses this property to build the URL for communication with Oracle Business Intelligence Publisher. For example: https://<host>:<port>/xmlpserver/services/rest/reports where: host is the setting in the BI_REST_URL. port is the setting in the BI_REST_PORT. xmlpserver/service/rest/reports is the setting in the BI_REST_SERVER_PATH.
BI_REST_PORT	The IP port number where Oracle Business Intelligence Publisher is running. The system uses this property to build the URL for communication with Oracle Business Intelligence Publisher. For example: https://<host>:<port>/xmlpserver/services/rest/reports where: host is the setting in the BI_REST_URL. port is the setting in the BI_REST_PORT. xmlpserver/service/rest/reports is the setting in the BI_REST_SERVER_PATH.
BI_REST_SERVER_PATH	The fixed prefix for Oracle Business Intelligence Publisher REST report resource. The system uses this property to build the URL for communication with Oracle Business Intelligence Publisher. For example: https://<host>:<port>/xmlpserver/services/rest/v1/reports where: host is the setting in the BI_REST_URL. port is the setting in the BI_REST_PORT. xmlpserver/service/rest/v1/reports is the setting in the BI_REST_SERVER_PATH.
BI_REST_USER	The user ID used to connect to Oracle Business Intelligence Publisher.
BI_REST_PASSWORD	The password for the user ID used to connect to Oracle Business Intelligence Publisher. For security, the system encrypts the password.

Integration Property Settings

See Integrations for more information on the set up required for integrations with Order Administration.

Property Name	Description
ASSOCIATE_FILE_PATH	The directory the Salesman Associate Upload Process monitors for new Salesman Associate files to place files that have been uploaded prior to additional processing. This setting is defined by Oracle and cannot be changed. Note: The name of the file must start with SR and have a .TXT file extension; for example: SR00001.txt and SR00002.txt. If there are multiple eligible files, they are processed sequentially based on file name; SR00001 processes before SR00002. You can use the file storage API to upload a zip file that contains a single text file with the same name, for example: SR00001.ZIP containing a text file named SR00001.TXT.
CA_INVENTORY_FILE_LOCAL_FOLDER	The folder on the Order Administration server where the CAINV periodic function writes the inventory file. See Sending Current Inventory Information to ChannelAdvisor for background. This property is set by Oracle and cannot be changed.
CWDIRECTCP_UPLOAD_ BATCH_SIZE	Defines the number of records to process in an upload file at a time. The default setting is 2500, indicating the system inserts records from the upload file into the Order Administration database in batches of 2500. If a record in a batch contains an error, the system does not insert any of the records in the batch into the Order Administration database and places the upload file in an error status. For troubleshooting purposes, you can decrease the UPLOAD_BATCH_SIZE and reprocess the file upload to help you determine which record contains the error. Example: In this example, the CWDIRECTCP_UPLOAD_BATCH_SIZE is 10. You process an upload file containing 30 records. In this situation, the system processes the upload file in 3 batches: the first batch contains records 1-10; the second batch contains records 11-20; and the third batch contains records 21-30. If a record in the second batch fails, the system does not process any of the records in the second batch, but does process all of the records in the first batch and third batch. See Work with File Uploads (WUPL) for more information.
	Setting for pick slip forms generated through the database: If you use a pick slip form that is generated directly through the database, set this value to 999999. The INPUT_TYPE setting for your pick slip form in the Forms Properties indicates the means by which your pick slip printing program obtains the data to print on the pick slip. Valid values are: XML (default) = The program uses the Pick Message from Order Administration (CWPickOut) to generate the pick slip. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). DB = The program queries the database to generate the pick slip. This option is available only if your pick slip printing program supports it. Note: If no INPUT_TYPE is specified, the program uses the CWPickOut message.
ELO_CONFIG_URL	Defines the URL to use to establish a connection with Oracle Retail EFTConnect when you open the Payment Configurations page in Modern View. Contact your Oracle representative if this property is not defined, or if the Payment Configurations page in Modern View displays an error.
ELO_IDCS_ENDPOINT_URL	Defines the URL to use when requesting the token for OAuth authentication for the integration with EFTConnect. Setup of the EFTConnect outbound web service authentication is required in Work with Web Service Authentication (WWSA). Contact your Oracle representative if this property is not defined.
ELO_PAYMENT_URL	Defines the URL to use for any transactional communication with EFTConnect, such as obtaining a form token, authorization, or deposit. Required for use of the Payment Configurations page in Modern View. Contact your Oracle representative if this property is not defined.
ELO_POLL_COUNT_THRESHOLD	Indicates how many times a Capture, Refund, or Auth+Capture call to EFTConnect can be made to check to see if it has the status of the transaction from the payment provider before its status changes to Unconfirmed. The current poll count is tracked on the Credit Card Deposit record. If the poll count is equal to or greater than the setting of this property, the Credit Card Deposit record is deleted and the deposit is unconfirmed. You can then use Resubmit Rejected Deposits in Modern View to attempt to resubmit the deposit. Defaults to 3. Must be at least 1 and cannot be higher than 99. A change to this setting takes effect immediately.
ELO_THRESHOLD_TIME	Used for logging purposes. Compares the elapsed time of the web service with the this setting. If the elapsed time exceeds the threshold, a message is logged.
ELO_TIMEOUT	Defines the number of milliseconds to wait before requests from Order Administration to EFTConnect time out. Defaults to 12000 milliseconds (12 seconds). Depending on the type of request and the payment provider, the record might stay in SENT status or RDY status; or, in the case of a new payment method, the payment information might not be saved and an error displayed.
IDCS_ENABLED	Defines whether the IDCS (Oracle Identity Cloud Service) or OCI IAM (Oracle Cloud Infrastructure Identity and Access Management) integration is enabled. false = The system uses internal password authentication. true (default) = The system uses IDCS or OCI IAM for password authentication. Note: Once you change this property to true, the setting can no longer be changed. If you need to change this setting back to false, you must contact your support representative to disable IDCS or OCI IAM. New cloud installations of Order Management System version 17.1 and later, or Order Administration, will have this setting delivered as true. When you enable the IDCS or OCI IAM integration, the system no longer creates records in the Password Audit table to track when a user’s password is updated. Before you change this value to true, make sure your admin user and other users in Order Administration are set up in IDCS or OCI IAM and match the exact format of the user name. When this property is set to true, multi-factor authentication is disabled. See Multi-Factor Authentication in the Administration Guide for background. When defining a user ID in IDCS or OCI IAM, the user ID is NOT case-sensitive. If this property is set to true, when users sign out of Order Administration or OACS Modern View, they return to the IDCS or OCI IAM login page. When this property is set to true, working with User Control records is not available through the Advanced Commands option. See Oracle Authentication (IDCS or OCI IAM) in the Administration Guide for more information.
IDCS_ACCESS_ APPLICATION_ID	Not currently implemented.
INVOIC_OUT_MAX_THREADS	Controls the maximum number of threads that the INVOIC_OUT job spawns to process invoice trigger records. Defaults to 10. Optionally, set it to a higher number to enhance performance. If this property is not set to a whole number larger than 0, a setting of 1 applies. See the Generic Invoice Download API for more information on the INVOIC_OUT process in the Web Services Guide on My Oracle Support (ID 2953017.1)
OCDS_RESPONSE_BATCH_SIZE	The number of records to request at a time for different types of data imported through the integration with Omnichannel Cloud Data Service (OCDS). Background: The OCDSITM periodic function requests merchandise hierarchy information, item information, item image information, item location attribute information, and pricing information, if the related system control value for each type of data is configured. Limiting the number of records in the response: For each of these types of data (with the exception of merchandise hierarchy information), the function requests the number of records specified in this property; for example, it requests up to 15,000 pricing information records when this property is set to 15,000. Oracle recommends that you set this property no higher than 100,000. The default setting is 10,000. If property not set: if this property is blank, the import requests the number of records defined in the INT_OCDS_CONFIG table for the import type. For example, if this property is blank and the quantity defined in the table for the item image import is 10,000, then the item image request specifies a quantity of 10,000. INT_OCDS_CONFIG defaults: The default settings in this table are 10,000 for each type of imported information. Note: This setting does not control the number of records requested for the merchandise hierarchy import; instead, it always uses the setting from the INT_OCDS_CONFIG table. For more information: See Importing Enterprise Foundation Data through Omnichannel Cloud Data Service (OCDS).
oms.car.scope	The scope used for Oracle Retail Collect and Receive Cloud Service (CaR). Provided by your Oracle representative. Defaults to domain:scope.
oms.cloud.file.transfer.bucket	This auto populated property displays the bucket value for file transfers that is specific to each environment.
oms.cloud.file.transfer.timeout	The timeout for the file transfer service. Default 15000.
oms.cloud.file.transfer.url	This auto populated property holds the file transfer service (FTS) base URL value.
oms.cloud.file.transfer.version	The version of the file transfer service (FTS) such as /fts/v1.
oms.promotion.engine.token.url	Defines the URL to use when requesting the token for OAuth authentication for the integration with ORPE. Setup of the ORPE outbound web service authentication is required in Work with Web Service Authentication (WWSA). Contact your Oracle representative if this property is not defined.
ORCE_CUSTOMER_ID_DIRECTORY_PATH	Defines the location on the Order Administration application server where the Update Customer with Relate ID periodic function (program name PFRCIU) looks for the Oracle Retail Customer Engagement query results comma separated value file (CSV) to process. See Customer Engagement Update Customer with Relate ID Process. This setting must be a valid location on the Order Administration application server. An example directory setting is `/domain/conf/OACSFiles/RelateData/customerID/,` where `domain` is the installed location of Order Administration.
ORCE_DIRECTORY_PATH	Defines the location where Order Administration places the batch files to send to Oracle Retail Customer Engagement. Note: This setting is defined by Oracle and cannot be changed. Not related to the Customer Engagement Customer Integration. Because Order Administration uses this directory to stage files before executing a transfer through the file transfer service, this setting still needs to specify a valid path if you use Customer Engagement File Transfer Service (FTS).
QAS SERVICES WSDL LOCATION	The location of the ProOnDemandService.wsdl file. The recommended location is file:///domain/conf/cwdirectcpproperties/ProOnDemandService.wsdl, where domain is the WebLogic domain directory for Order Administration. The ProOnDemandService.wsdl is delivered with Order Administration and should not be changed.
STORE_FILE_PATH	The directory the Store Upload Process monitors for new Store files to process. Note: The name of the file must start with ST and have a .TXT file extension; for example: ST00001.txt and ST00002.txt. See Store Upload. This property is set by Oracle and cannot be changed. Note: You need to use Work with File Uploads (WUPL) to upload stores.
XLINK_DIRECTORY_PATH	The directory where the POSLOGX periodic function places a custom POSlog to send to Xlink when you are not using the file storage API. This property is set by Oracle and cannot be changed.

Logging Property Settings

See Logs for more information on the logs that are available to help troubleshoot Order Administration processing.

Property Name	Description
CUST_FILE_NAME	The name of the log that stores Customer API transaction information. The delivered setting is CUST.log. If you Use Multiple Application Servers If you use multiple application servers, rename the log so that it identifies the server where the log is located. For example, if you use two application servers named SERVER1 and SERVER2, rename the CUST log on each server to CUSTSERVER1.log and CUSTSERVER2.log.
OCDS_JOB_HISTORY_RETENTION_DAYS	Defines the number of days to retain records in the INT_OCDS_STATUS table. This table tracks activity of the and the OCDSFA periodic function (see Importing Future Available Information (OCDSFA Periodic Function) for background). You can review these records at the Enterprise Data Import History page in Modern View. The OCDSITM periodic function purges records older than the number of days specified here. Default = 30 days. If this property is blank, the periodic function does not purge records.
oms.promotion.engine.service.timeout	Defines the number of seconds to wait before requests from Order Administration to the ORPE Promotion /dealServices/applyDeals method time out. Defaults to 500 seconds.
oms.db.query.log.threshold	Oracle staff can use this property to control when to log longer-running queries for troubleshooting purposes. Queries that run for longer than the number of milliseconds defined here create log entries that include terms such as `Query Timer` and `took longer than logging threshold`. Defaults to 4000 milliseconds.

Monitor Property Settings

The settings below are used by Oracle staff to manage system processing.

For more information: See:

Monitoring Jobs for more information on how the system monitor jobs to ensure that they are running correctly.
Long Running Jobs Monitor for more information on how the system watches the batch jobs running on the Job Management Screen and sends a Long Running Job Email to a specified email address if a job runs without ending longer than a specified time.
Working with Required Responses (WREQ) and Required Response Processing for more information on how to respond to Order Administration jobs that require user intervention in order to proceed.
Running a Periodic Process on Server Startup for more information on how to run a periodic process when the Order Administration application server is restarted.

Property Name	Description
oms.reports.service.active.procedures	Used to filter data on the Managed Services report.
oms.reports.service.email.to	The email addresses that receive Managed Services reports. Separate email addresses with a semi-colon.
ALLOW_JOB_MONITOR	Indicates whether the job monitor runs on this application server. Valid values: Y = The job monitor runs on this server. N (default) or blank = The job monitor does not run on this server. In this situation, the only option on the Work with Job Monitor Rules Screen is to display a rule’s settings. Note: Set this value to Y for all application servers that you wish to collect data on the Work with Job Monitor Screen (WJMO).
oms.reports.service.processes	Used to filter data on the Managed Services report.
oms.job.history.purge.retain.days	Defines how long to retain a batch job in the Job History table before the system purges it automatically based on the job’s End date. The default setting is 30 days. The system submits the Job History purge process each time you start the application server. Job History records that do not have an End Date (indicating the job did not end) are not purged. Note: This setting does not apply to the history records in the job_run_history table. These records are not currently purged. The job_run_history table contains records for the BILLUPD and SCHDDEP periodic functions. See Display Job History (DJHY) for more information.
JOB_MONITOR_QUERY_ DIRECTORY	The directory on the application server where you store queries used by the job monitor. An example directory is domain/conf/OACSFiles/JobMonitorQueries/, where domain is the installed location of Order Administration.
REPORT_TYPE	Indicates the format of the Managed Services report. pdf = Generate the Managed Services report in .pdf portable document format. rtf = Generate the Managed Services report in .rtf rich text format. txt = Generate the Managed Services report in .txt text format.
RESPONSE_EMAILS	The list of email addresses that receive the Response Required Email when a job requires user intervention. Each email address entered must be separated by a semi-colon (;). For example: email1@add.com;email2@add.com.
RESPONSE_RETRIES	The number of times Order Administration looks for a response to a job that requires user intervention before using the default response in order to proceed with the job. For example, if this setting is 5, Order Administration will look for a user response five times, waiting 60 seconds between each timeSee Working with Required Responses (WREQ).
oms.reports.service.email.subject	The text that displays in a Managed Services email.
oms.reports.service.email.disabled	Defines whether a Managed Services email is generated. Y = Do no generate Managed Services emails. N = Generate Managed Services emails.
TRACK_ALERTS_IN_LOG	Indicates whether you log all alerts generated by the job monitor. Valid values: Y = Log all alerts generated by the job monitor in the Alert Log. N or blank = Do not log alerts generated by the job monitor.

System Property Settings

The settings below define configuration settings for the Order Administration application server.

Property Name	Description
CC_TOKENIZATION_DEFAULT_LOG_LEVEL	Information will be provided at a later date.
CC_TOKENIZATION_LOG_NAME	Information will be provided at a later date.
CHECK_AUTHS_IN_PICKS	Defines whether you can process Streamlined Pick Slip Generation (WSPS) when records exist for your company in the CC Authorization Transaction table. Valid values are: Y or this setting does not exist = Before processing Streamlined Pick Slip Generation (WSPS), the system first looks for records in the CC Authorization Transaction table for the company for which you are generating pick slips. If records exist in the CC Authorization Transaction table, the system does not continue with pick slip generation and instead generates a Pick Authorization Error Report and a Order Administration Support Notification. Review the records in the CC Authorization Transaction table to determine if you need to use the Reprocess Authorizations Screen (RPAA) to reprocess authorizations and clear the records from the CC Authorization Transaction table. N = The system allows you to run Streamlined Pick Slip Generation (WSPS) when records exist for your company in the CC Authorization Transaction table. Any records in the CC Authorization Transaction table will be resent for authorization. See Pick Slip Generation Overview.
COMMIT_RATE	The number of records that the Batch Inventory Overlay Upload should process at a time. Normally set to 1000.
CWDIRECTCP_FTP_FOLDER	The location of the FTP script for the POSLog integration (poslog_ftp_commands.script file). This property is set by Oracle and cannot be changed. This folder is also used for the following integrations: Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service Working with the Marketing Download Extract See these integrations for more information.
The CWDIRECTCP_LINK_TEXT and CWDIRECTCP_LINK_URL settings below allow you to add a link to all screens in Order Administration (with the exception of the menu screens, the DITH and MMCM menu options, and the administrative screens such as Job Management and Document Management).	Example: If you enter Go To Google in the CWDIRECTCP_LINK_TEXT setting and http://www.google.com in the CWDIRECTCP_LINK_URL setting, then each screen will have a link that reads Go To Google that will open a new browser window and launch the URL to the Google web site.
CWDIRECTCP_LINK_TEXT	Defines the text to display on the Order Administration screens for the link. Example: If you enter Go To CNN, then each screen will have a link that reads Go To CNN. If you are Using Multiple Application Servers If you are using multiple application servers, you will need to update this setting on each server.
CWDIRECTCP_LINK_URL	Defines the URL to launch when a user clicks the link on a Order Administration screen. Example: If you enter http://www.cnn.com, the system opens a new browser window and launches the URL to advance to the CNN web site. If you are Using Multiple Application Servers If you are using multiple application servers, you will need to update this setting on each server.
Password Rules	The following settings identify the requirements for user passwords, including the minimum and maximum length and any required numeric, uppercase, or special characters. Note: These settings are not currently used. When you change password rules: Your new password rules take effect for new users the next time you reboot Order Administration or the server itself. However, your password rules do not prevent existing users from logging in using passwords created under the previous rules. The new rules apply only when you attempt to change user control record settings or change the password itself. To make sure a user will change the password to conform to the new rules upon the next login, set the user’s Password Expired field to a date that is earlier than the current date. See User Configuration in the Administration Guide for more information.
CWDIRECTCP_UPLOAD_DIRECTORY	The location where an import process initially uploads files. This property is set by Oracle and cannot be changed. See Work with File Uploads (WUPL) for more information.
CWDIRECTCP_USPS_UPLOAD_ FILE	The temporary location on the Order Administration application server where the system should look for the City State data file when you use the Load USPS Zip Code File (LZPS) to update postal code data. This property is set by Oracle and cannot be changed. Note: If you are using multiple application servers, you need to update this setting on each server where you plan to use the Load USPS Zip Code File (LZPS) to update postal code data.
CWMQ_TARGET_CLIENT	The default setting is 1.
CWMQ_WAIT_TIME	The default setting is -1.
DEPOSIT_MAX_THREADS	Controls the number of threads available to process deposits. The default setting is 1. Optionally, set it to a higher number to enhance performance. You can enter any positive integer. If the property is empty, missing, or not set to an integer, a setting of 1 defaults. For more information: See Processing Auto Deposits (SDEP).
ECOMMERCE_DIRECTORY_PATH	Defines the location on the application server where the system downloads product offer and customer merge information. The system downloads product offer information to this directory when you download e-commerce offer files (EOFR) and the Generate E-Commerce Offer Tables (M29) system control value is unselected. See Downloading E-Commerce Offer Files (EOFR) for processing details. The system downloads customer merge information to this directory when Performing a Merge using the Working with Merge/Purge Sold-to Names (MMCS) menu option if the Generate E-Commerce Customer Merge Staging Files (H86) system control value is selected. The system downloads the AvailabilityWeb XML file to this directory when it receives the E-Commerce Availability Web Request XML Message (AvailabilityWebRequest). This property is set by Oracle and cannot be changed. For more information, see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1)
END_ORDERIN_IJCT_ON_CONNECTION_ERROR	Indicates the action to take when the order API generates an Invalid XML error response, since this error can indicate a database connection problem. If this property is set to Y, when the order API generates an Invalid XML error response, it attempts to verify the database connection. If the attempt is unsuccessful, the system ends the ORDER_IN job and sends a support notification. Otherwise, if this property is set to N or blank or does not exist, the order API continues trying to process order messages in the event of an Invalid XML error response.
oms.job.purge.retain.days	The number of days to store jobs and generated reports and forms before they are eligible for deletion. Each time you restart Order Administration, the start up process deletes the following if they are older than the number of days specified here: archived reports, including PDF files, XML files, and text files. job logs. entries in the dbo.Jenasysjob table. This table is used to track submitted jobs. If you do not define the retention days, Order Administration does not delete outdated documents. Note: The deletion uses both the date and the time in determining whether to purge a document. For example, the current time is 7:00 a.m. and the oms.job.purge.retain.days is set to 30. If the report was created earlier than 7:00 30 days ago, it is eligible for deletion; otherwise, if it was created later than 7:00 30 days ago, it is not currently eligible. Certain text files might have a later date than the related PDF files, and so might not be eligible to purge at the same time as the related PDF. For example, if you view a PDF file for a form a day after creating it, Order Administration creates a text file logging that activity for the date when you viewed the PDF.
OROB_DIRECTORY_PATH	The location on the application server where the system creates Order Orchestration product, product location, and incremental inventory files to import into Order Orchestration. This property is set by Oracle and cannot be changed. See Order Orchestration’s Product, Product Location, and Incremental Inventory Import Process.
OROB_IMPORTS_URL	The URL used to call the Order Orchestration RESTful web service when sending product, product location, and incremental inventory data to Order Orchestration. For example: https://order_broker_url:port, where order_broker_url is the URL used to connect to Order Orchestration and port if the port number used to connect to Order Orchestration. See Order Orchestration’s Product, Product Location, and Incremental Inventory Import Process.
OVERLAY_DEBUG	If this property is set to Y, the Batch Inventory Overlay Upload writes entries in the Job.log file, for example: File: INV_OVERLAY_005.TXT Rows: 4 Success: 1 Errors: 3 Start Time: Mon Mar 04 16:03:11 EST 2019 End Time: Mon Mar 04 16:03:11 EST 2019 Time In Seconds: 0.041420431 Time In Minutes: 6.903405166666667E-4
PICKS_IN_SPOOL_FILE	The maximum number of pick slips in a single PDF document. The system continues to break pick slips into separate PDF documents using the criteria outlined under Sorting Pick Slips into Separate PDF Documents; however, if the number of pick slips in a PDF document reaches the number defined in the PICKS_IN_SPOOL_FILE setting, the system creates a new PDF document. Note: The system uses the PICKS_IN_SPOOL_FILE setting when printing pick slips through Streamlined Pick Slip Generation (WSPS) and Reprinting and Voiding Pick Slips (WVRP or WSVP). Also, the system uses this setting when printing Gift Acknowledgements. Working with the pick slip form: Once the system finishes processing one pick slip PDF document, you can open and print the pick slips in the document using the Forms Management Screen; you do not have to wait until all of the PDF documents for the pick slip generation run have generated. When printing pick slips, the system includes a PDF document sort number in the name of the document generated for the pick slip. For example, if the system generates two pick slip documents for warehouse 1, ship via priority 5, the system names the documents PICKG.KBROWN.20090804.103001456_001.PDF and PICKG.KBROWN.20090804.103001456_002.PDF, where PICKG is the name of the print program, KBROWN is the user ID of the person who generated the pick slips, 20090804.103001456 is the date and time stamp, and 001 and 002 is the PDF document sort number. See Form Naming Conventions for more information. Recommended setting: The recommended setting is 250 picks. The system also uses 250 as the default value if this setting is blank or missing.
	Example: When the PICKS_IN_SPOOL_FILE setting is 600, the system creates the following spool files for a pick slip generation run: 50 pick slips for warehouse 1, ship via priority 1 (PICKG.KBROWN.20090804.103000123_001.PDF) 300 pick slips for warehouse 1, ship via priority 5 (PICKG.KBROWN.20090804.103001456_001.PDF) 510 pick slips for warehouse 1, ship via priority 9 (PICKG.KBROWN.20090804.103003789_001.PDF) 75 pick slips for warehouse 2, ship via priority 1 (PICKG.KBROWN.20090804.103006912_001.PDF) 225 pick slips for warehouse 2, ship via priority 5 (PICKG.KBROWN.20090804.103007134_001.PDF) 25 pick slips for warehouse 2, ship via priority 9 (PICKG.KBROWN.20090804.103008112_001.PDF)
	When the PICKS_IN_SPOOL_FILE setting is 250, the system creates the following spool files for the same pick slip generation run: 50 pick slips for warehouse 1, ship via priority 1 (PICKG.KBROWN.20090804.103000123_001.PDF) 250 pick slips for warehouse 1, ship via priority 5 (PICKG.KBROWN.20090804.103001456_001.PDF) 50 pick slips for warehouse 1, ship via priority 5 (PICKG.KBROWN.20090804.103001456_002.PDF) 250 pick slips for warehouse 1, ship via priority 9 (PICKG.KBROWN.20090804.103003789_001.PDF) 250 pick slips for warehouse 1, ship via priority 9 (PICKG.KBROWN.20090804.103003789_002.PDF) 10 pick slips for warehouse 1, ship via priority 9 (PICKG.KBROWN.20090804.103003789_003.PDF) 75 pick slips for warehouse 2, ship via priority 1 (PICKG.KBROWN.20090804.103006912_001.PDF) 225 pick slips for warehouse 2, ship via priority 5 (PICKG.KBROWN.20090804.103007134_001.PDF) 25 pick slips for warehouse 2, ship via priority 9 (PICKG.KBROWN.20090804.103008112_001.PDF) Notice that the system creates multiple spool files for pick slips in warehouse 1, ship via priority 5 and for pick slips in warehouse 1, ship via priority 9, based on 250 in the PICKS_IN_SPOOL_FILE setting.