Properties | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Using the CWProcessIn Message to Start a Periodic Process |
Working with Customer Properties (PROP)
Purpose: Use this menu option to define system-wide configuration settings for Order Management System Cloud Service that an administrator type user would update.
When you update a property setting, unless otherwise noted, your update takes effect immediately.
In this chapter:
• Summary of Customer Properties
- Integration Property Settings
How to display this screen: Enter PROP in the Fast path field or select Refresh System Properties from a menu.
Authority: Users with ALLOW or DISPLAY authority to this menu option can update the settings in the properties files with the new values.
When you first advance to this screen, property settings display in ascending property name sequence.
Field |
Description |
Group |
The type of property setting. Valid values are: • Forms: The property setting is related to forms processing. • Integration: The property setting is related to an integration with an external system. • 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 a property. Enter a full or partial property name to display property settings that contain your entry. You can expand the Property column to review the full name of the property setting. 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. You can expand the Current Value column if its full value does not display. Alphanumeric, 150 positions; optional. |
Type |
The type of property setting. This setting is always set to CUSTOMER indicating the property setting is a setting available to the customer. 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. |
Summary of Customer Properties
The property settings that display on the Work with Properties Screen are listed below.
• Integration Property Settings
Property Name |
Description |
BOCARDS BOCARDS |
Controls whether certain information prints on the Backorder Card. Currently, there is no information to define. |
CAMPAIGNPERF
CAMPAIGN_PERFORMANCE |
Controls whether certain information prints on the Campaign Performance Report (PCPR). Currently, there is no information to define. |
CPGSKUEXUPLOAD
CPG_SKU_EXCLUSION_UPLOAD_ERROR |
Controls whether certain information prints on the CPG Item/SKU Exclusions Upload Error Records Report. Currently, there is no information to define. |
CRTBCHRCP
CART_BATCH_RECAP |
Controls whether certain information prints on the Cart Batch Recap. Currently, there is no information to define. |
CSHLDORD
HELD_ORDER_BY_REASON_REPORT |
Controls whether certain information prints on the Held Order by Reason Code Report. Currently, there is no information to define. |
CSHLDORDCSV
HELD_ORDER_BY_REASON_REPORT_CSV |
Controls whether certain information prints on the Held Order by Reason Code Report in spreadsheet format. Currently, there is no information to define. |
EMSTSRPT
CUSTOMER_EMAIL_STATUS_REPORT |
Controls whether certain information prints on the Unmatched Email Status Report. Currently, there is no information to define. |
EXCARSNNOITM
EXCHANGE_ALL_REASON_NO_ITEM |
Controls whether certain information prints on the Exchange Reason Report when the exchange reason code and item are not defined. Currently, there is no information to define. |
EXCARSNNOITMCSV
EXCHANGE_ALL_REASON_NO_ITEM_CSV |
Controls whether certain information prints on the Exchange Reason Report in spreadsheet format when the exchange reason code and item are not defined. Currently, there is no information to define. |
EXCARSNWITM
EXCHANGE_ALL_REASON_WITH_ITEM |
Controls whether certain information prints on the Exchange Reason Report when an item is defined. Currently, there is no information to define. |
EXCARSNWITMCSV
EXCHANGE_ALL_REASON_WITH_ITEM_CSV |
Controls whether certain information prints on the Exchange Reason Report in spreadsheet format when an item is defined. Currently, there is no information to define. |
EXCRSNNOITM
EXCHANGE_SPECIFIC_REASON_NO_ITEM |
Controls whether certain information prints on the Exchange Reason Report when an exchange reason code is defined. Currently, there is no information to define. |
EXCRSNNOITMCSV
EXCHANGE_SPECIFIC_REASON_NO_ITEM_CSV |
Controls whether certain information prints on the Exchange Reason Report in spreadsheet format when an exchange reason code is defined. Currently, there is no information to define. |
EXCRSNWITM
EXCHANGE_SPECIFIC_REASON_WITH_ITEM |
Controls whether certain information prints on the Exchange Reason Report when an exchange reason code and item are defined. Currently, there is no information to define. |
EXCRSNWITMCSV
EXCHANGE_SPECIFIC_REASON_WITH_ITEM_CSV |
Controls whether certain information prints on the Exchange Reason Report in spreadsheet format when an exchange reason code and item are defined. Currently, there is no information to define. |
FLASHPIECHARTS
FLASHPIECHARTSFULL |
Defines the order statistics that display on the Menu Driver Screen. • FLASHPIECHARTS = The order statistics section of the menu screen displays total numbers and dollars of orders created by the current date, current week, current month, year to date, and previous year. Use this setting if the Delay Billing Updates (K85) system control value is selected. • FLASHPIECHARTSFULL = The order statistics section of the menu screen displays total numbers and dollars of orders created and shipped by the current date, current week, current month, year to date, and previous year. Use this setting if the Delay Billing Updates (K85) system control value is unselected. |
FLASHREPORT
FLASHREPORT |
Controls whether certain information displays in Reviewing Operations Control Summary (FLSH). Currently, there is no information to define. |
=GIFTACKDB,SUPPRESS_IMAGES=N,INPUT_TYPE=DB Note: These settings also apply to your graphical custom gift acknowledgement. Each option is available only if your gift acknowledgement print program supports it. |
Defines whether images print on the graphical Gift Acknowledgement. SUPPRESS_IMAGES Controls whether the system prints images on the graphical gift acknowledgement. • N (default) = Print images on the graphical gift acknowledgement. • Y = Suppress images on the graphical gift acknowledgement. Note: The SUPPRESS_IMAGES value should be N for the graphical gift acknowledgement. INPUT_TYPE Controls the means by which your gift acknowledgement printing program obtains the data to print on the gift acknowledgement. Valid values are: • XML = The program uses the Pick Message from Order Management System (CWPickOut) to generate the gift acknowledgement. • DB = The program queries the database to generate the gift acknowledgement. The INPUT_TYPE setting for the standard printing program GIFTACKG is DB. |
JFLR0393
PICKING_PULLSHEET_CARTBIN |
Controls whether certain information prints on the Cart/Bin Batch Picking Pullsheet. Currently, there is no information to define. |
JFLR0393CSV
PICKING_PULLSHEET_CARTBIN_CSV |
Controls whether certain information prints on the Cart/Bin Batch Picking Pullsheet in spreadsheet format. Currently, there is no information to define. |
JFLR0397
PICKING_PULLSHEET |
Controls whether certain information prints on the Picking Pullsheet. Currently, there is no information to define. |
JFLR0397CSV
PICKING_PULLSHEET_CSV |
Controls whether certain information prints on the Picking Pullsheet in spreadsheet format. Currently, there is no information to define. |
ORDERRECG
ORDERREC,SUPPRESS_IMAGES=N Note: These settings also apply to your graphical custom order receipt. This option is available only if your order receipt print program supports it. |
Defines whether images print on the graphical Order Receipt. SUPPRESS_IMAGES Controls whether the system prints images on the graphical order receipt. • N (default) = Print images on the graphical order receipt. • Y = Suppress images on the graphical order receipt. Note: The SUPPRESS_IMAGES value should be N for the graphical order receipt. |
ORDERSUM
ORDERSUM,SUPPRESS_IMAGES=Y Note: These settings also apply to your non-graphical custom order summary. This option is available only if your order summary print program supports it. |
Defines whether images print on the non-graphical Order Summary. SUPPRESS_IMAGES Controls whether the system prints images on the non-graphical order summary. • N = Print images on the non-graphical order summary. • Y (default) = Suppress images on the non-graphical order summary. Note: The SUPPRESS_IMAGES value should be Y for the non-graphical order summary. |
ORDERSUMG
ORDERSUM,SUPPRESS_IMAGES=N Note: These settings also apply to your graphical custom order summary. This option is available only if your order summary print program supports it. |
Defines whether images print on the graphical Order Summary. SUPPRESS_IMAGES Controls whether the system prints images on the graphical order summary. • N (default) = Print images on the graphical order summary. • Y = Suppress images on the graphical order summary. Note: The SUPPRESS_IMAGES value should be N for the graphical order summary. |
=PICKDB,SUPPRESS_IMAGES=N,BARCODE_IMAGE=Code39,ORDER_BARCODE_IMAGE=Code39;INPUT_TYPE=XML Note: These settings also apply to your graphical custom pick slip. Each option is available only if your pick slip print program supports it. |
Defines whether images and barcodes print on the graphical Pick Slip. SUPPRESS_IMAGES Controls whether the system prints images on the graphical pick slip. • N (default) = Print images on the graphical pick slip. • Y = Suppress images on the graphical pick slip. Note: The SUPPRESS_IMAGES value should be N for the graphical pick slip. |
Controls whether the system prints a barcode on the graphical pick slip. • Code39 (default) = Print this type of barcode on the graphical pick slip. • Code128 = Print this type of barcode on the graphical pick slip. Note: Code 39 is a low-density format that encodes upper case letters (A to Z), digits (0 to 9), and some special characters. Code 128 is a high-density format that accepts alphanumeric or numeric-only codes, or all 128 ASCII characters. • NOT DISPLAYED = Do not print barcodes on the graphical pick slip. Note: This value is case-sensitive. |
|
|
ORDER_BARCODE_IMAGE Controls whether the system prints the order barcode on the graphical pick slip. The barcode is comprised of the company code, order number, and ship to number. • Code39 (default) = Print this type of order barcode on the graphical pick slip. • Code128 = Print this type of order barcode on the graphical pick slip. • NOT DISPLAYED = Do not print the order barcode on the graphical pick slip. Note: This value is case-sensitive. |
|
INPUT_TYPE Controls the means by which your pick slip printing program obtains the data to print on the pick slip. Valid values are: • XML = The program uses the Pick Message from Order Management System (CWPickOut) to generate the pick slip. • DB = The program queries the database to generate the pick slip. The INPUT_TYPE setting for the standard printing program PICKG is DB. |
PICKAUTH
PICK_AUTH_REPORT |
Controls whether certain information prints on the Pick Authorization Error Report. Currently, there is no information to define. |
PICKLBL,SUPPRESS_IMAGES=Y,BARCODE_IMAGE=Code39 Note: These settings also apply to your non-graphical custom pick label. Each option is available only if your pick label print program supports it. |
Defines whether images and barcodes print on the non-graphical pick label, as defined in the Pick Label Print Program (F28) system control value. SUPPRESS_IMAGES Controls whether the system prints images on the non-graphical pick label. • N = Print images on the non-graphical pick label. • Y (default) = Suppress images on the non-graphical pick label. Note: The SUPPRESS_IMAGES value should be Y for the non-graphical pick label. BARCODE_IMAGE Controls whether the system prints a barcode on the non-graphical pick label. • Code39 (default) = Print this type of barcode on the non-graphical pick label. • Code128 = Print this type of barcode on the non-graphical pick label. Note: Code 39 is a low-density format that encodes upper case letters (A to Z), digits (0 to 9), and some special characters. Code 128 is a high-density format that accepts alphanumeric or numeric-only codes, or all 128 ASCII characters. • NOT DISPLAYED = Do not print barcodes on the non-graphical pick label. Note: This value is case-sensitive. |
PICKPACK
PICKPACK,SUPPRESS_IMAGES=Y Note: These settings also apply to your non-graphical custom pack slip. Each option is available only if your pack slip print program supports it. |
Defines whether images print on the non-graphical Pack Slip. SUPPRESS_IMAGES Controls whether the system prints images on the non-graphical pack slip. • N = Print images on the non-graphical pack slip. • Y (default) = Suppress images on the non-graphical pack slip. Note: The SUPPRESS_IMAGES value should be Y for the non-graphical pack slip. |
PICKPACKG
PICKPACK,SUPPRESS_IMAGES=N Note: These settings also apply to your graphical custom pack slip. This option is available only if your pack slip print program supports it. |
Defines whether images print on the graphical Pack Slip. SUPPRESS_IMAGES Controls whether the system prints images on the graphical pack slip. • N (default) = Print images on the graphical pack slip. • Y = Suppress images on the graphical pack slip. Note: The SUPPRESS_IMAGES value should be N for the graphical pack slip. |
PICKUNIT
PICK_UNIT_REPORT |
Controls whether certain information prints on the Pick Unit Report. Currently, there is no information to define. |
PPRORDERED
PRODUCT_PERFORMANCE_ORDERED |
Controls whether certain information prints on the Product Performance Report (Ordered Totals). Currently, there is no information to define. |
PPRORDEREDF
PRODUCT_PERFORMANCE_ORDERED_FAST |
Controls whether certain information prints on the Product Performance Report (Ordered Totals). Currently, there is no information to define. |
PPRORDEREDFCSV
PRODUCT_PERFORMANCE_ORDERED_FAST_CSV |
Controls whether certain information prints on the Product Performance Report (Ordered Totals) in spreadsheet format. Currently, there is no information to define. |
PPRORDEREDOT
PRODUCT_PERFORMANCE_ORDERED_BY_ORDER_TYPE |
Controls whether certain information prints on the Product Performance Report (Ordered Totals). Currently, there is no information to define. |
PPRSHIPPED
PRODUCT_PERFORMANCE_SHIPPED |
Controls whether certain information prints on the Product Performance Report (Shipped Totals). Currently, there is no information to define. |
PPRSHIPPEDF
PRODUCT_PERFORMANCE_SHIPPED_FAST |
Controls whether certain information prints on the Product Performance Report (Shipped Totals). Currently, there is no information to define. |
PPRSHIPPEDFCSV
PRODUCT_PERFORMANCE_SHIPPED_FAST_CSV |
Controls whether certain information prints on the Product Performance Report (Shipped Totals) in spreadsheet format. Currently, there is no information to define. |
PPRSHIPPEDOT
PRODUCT_PERFORMANCE_SHIPPED_BY_ORDER_TYPE |
Controls whether certain information prints on the Product Performance Report (Shipped Totals). Currently, there is no information to define. |
PRCCDUPLDERR
PRICE_CODE_UPLOAD_ERROR_REPORT |
Controls whether certain information prints on the Price Code Upload Errors Report. Currently, there is no information to define. |
PROMOUPLDERR
PROMOTION_UPLOAD_ERROR_REPORT |
Controls whether certain information prints on the Promotion Upload Error Records Report. Currently, there is no information to define. |
PROVRCIRPT
PRICE_OVERRIDE_REASON_BY_CODE_AND_ITEM |
Controls whether certain information prints on the Price Override Reason Report by reason code and item. Currently, there is no information to define. |
PROVRCIRPTCSV
PRICE_OVERRIDE_REASON_BY_CODE_AND_ITEM_CSV |
Controls whether certain information prints on the Price Override Reason Report by reason code and item in spreadsheet format. Currently, there is no information to define. |
PROVRCRPT
PRICE_OVERRIDE_REASON_BY_CODE |
Controls whether certain information prints on the Price Override Reason Report by reason code. Currently, there is no information to define. |
PROVRCRPTCSV
PRICE_OVERRIDE_REASON_BY_CODE_CSV |
Controls whether certain information prints on the Price Override Reason Report by reason code in spreadsheet format. Currently, there is no information to define. |
PROVRIRPT
PRICE_OVERRIDE_REASON_BY_ITEM |
Controls whether certain information prints on the Price Override Reason Report by item. Currently, there is no information to define. |
PROVRIRPTCSV
PRICE_OVERRIDE_REASON_BY_ITEM_CSV |
Controls whether certain information prints on the Price Override Reason Report by item in spreadsheet format. Currently, there is no information to define. |
PROVRRPT
PRICE_OVERRIDE_REASON |
Controls whether certain information prints on the Price Override Reason Report. Currently, there is no information to define. |
PROVRRPTCSV
PRICE_OVERRIDE_REASON_CSV |
Controls whether certain information prints on the Price Override Reason Report in spreadsheet format. Currently, there is no information to define. |
PROVRUCIRPT
PRICE_OVERRIDE_REASON_BY_USER_CODE_AND_ITEM |
Controls whether certain information prints on the Price Override Reason Report by user code and item. Currently, there is no information to define. |
PROVRUCIRPTCSV
PRICE_OVERRIDE_REASON_BY_USER_CODE_AND_ITEM_CSV |
Controls whether certain information prints on the Price Override Reason Report by user code and item in spreadsheet format. Currently, there is no information to define. |
PROVRUCRPT
PRICE_OVERRIDE_REASON_BY_USER_AND_CODE |
Controls whether certain information prints on the Price Override Reason Report by user code and reason code. Currently, there is no information to define. |
PROVRUCRPTCSV
PRICE_OVERRIDE_REASON_BY_USER_AND_CODE_CSV |
Controls whether certain information prints on the Price Override Reason Report by user code and reason code in spreadsheet format. Currently, there is no information to define. |
PROVRUIRPT
PRICE_OVERRIDE_REASON_BY_USER_AND_ITEM |
Controls whether certain information prints on the Price Override Reason Report by user code and item. Currently, there is no information to define. |
PROVRUIRPTCSV
PRICE_OVERRIDE_REASON_BY_USER_AND_ITEM_CSV |
Controls whether certain information prints on the Price Override Reason Report by user code and item in spreadsheet format. Currently, there is no information to define. |
PROVRURPT
PRICE_OVERRIDE_REASON_BY_USER |
Controls whether certain information prints on the Price Override Reason Report by user. Currently, there is no information to define. |
PROVRURPTCSV
PRICE_OVERRIDE_REASON_BY_USER_CSV |
Controls whether certain information prints on the Price Override Reason Report by user in spreadsheet format. Currently, there is no information to define. |
PURCHORDG
PURCHORD,SUPPRESS_IMAGES=N Note: These settings also apply to your graphical custom purchase order. This option is available only if your purchase order print program supports it. |
Defines whether images print on the graphical Purchase Order. SUPPRESS_IMAGES Controls whether the system prints images on the graphical purchase order. • N (default) = Print images on the graphical purchase order. • Y = Suppress images on the graphical purchase order. Note: The SUPPRESS_IMAGES value should be N for the graphical purchase order. |
QUOTE
QUOTE,SUPPRESS_IMAGES=Y Note: These settings also apply to your non-graphical custom quote form. This option is available only if your quote print program supports it. |
Defines whether images print on the non-graphical Quote Form. SUPPRESS_IMAGES Controls whether the system prints images on the non-graphical quote form. • N = Print images on the non-graphical quote form. • Y (default) = Suppress images on the non-graphical quote form. Note: The SUPPRESS_IMAGES value should be Y for the non-graphical quote form. |
QUOTEG
QUOTE,SUPPRESS_IMAGES=N Note: These settings also apply to your graphical custom quote form. This option is available only if your quote print program supports it. |
Defines whether images print on the graphical Quote Form. SUPPRESS_IMAGES Controls whether the system prints images on the graphical quote form. • N (default) = Print images on the graphical quote form. • Y = Suppress images on the graphical quote form. Note: The SUPPRESS_IMAGES value should be N for the graphical quote form. |
REFCHECK
REFCHECK,SUPPRESS_IMAGES=Y,TEXT_AMOUNT_UPPERCASE=N,INCLUDE_DOLLAR_SIGN=Y Note: These settings also apply to your non-graphical custom refund check. This option is available only if your refund check print program supports it. |
Defines whether images and a dollar sign print on the non-graphical Refund Check. SUPPRESS_IMAGES Controls whether the system prints images on the non-graphical refund check. • N = Print images on the non-graphical refund check. • Y (default) = Suppress images on the non-graphical refund check. Note: The SUPPRESS_IMAGES value should be Y for the non-graphical refund check. TEXT_AMOUNT_UPPERCASE Defines whether the system prints text on the non-graphical refund check in all uppercase. • N = Print text on the non-graphical refund check in upper and lower case. • Y = Print text on the non-graphical refund check in all uppercase. INCLUDE_DOLLAR_SIGN Defines whether the system prints the dollar sign on the non-graphical refund check. • N = Do not print the dollar sign on the non-graphical refund check. • Y = Print the dollar sign on the non-graphical refund check. |
REFCHECKG
REFCHECK,SUPPRESS_IMAGES=N,TEXT_AMOUNT_UPPERCASE=N,INCLUDE_DOLLAR_SIGN=Y Note: These settings also apply to your graphical custom refund check. This option is available only if your refund check print program supports it. |
Defines whether images and a dollar sign print on the graphical Refund Check. SUPPRESS_IMAGES Controls whether the system prints images on the graphical refund check. • N (default) = Print images on the graphical refund check. • Y = Suppress images on the graphical refund check. Note: The SUPPRESS_IMAGES value should be N for the graphical refund check. TEXT_AMOUNT_UPPERCASE Defines whether the system prints text on the graphical refund check in all uppercase. • N = Print text on the graphical refund check in upper and lower case. • Y = Print text on the graphical refund check in all uppercase. INCLUDE_DOLLAR_SIGN Defines whether the system prints the dollar sign on the graphical refund check. • N = Do not print the dollar sign on the graphical refund check. • Y = Print the dollar sign on the graphical refund check. |
REPLENDTLSHC
REPLENDTLSHC,BARCODE_IMAGE=Code128 |
|
RESAUDITLOG
RESET_AUDIT_LOG |
Controls whether certain information prints on the Print Reset Audit Log. Currently, there is no information to define. |
RESETBO
RESET_AUDIT_LOG_QTY_BACKORDERED |
Controls whether certain information prints on the Reset Audit Log for Quantity on Backorder. Currently, there is no information to define. |
RESETONHAND
RESET_AUDIT_LOG_QTY_ON_HAND |
Controls whether certain information prints on the Reset Audit Log for Quantity On Hand. Currently, there is no information to define. |
RESETPRT
RESET_AUDIT_LOG_QTY_PRINTED_ITEM_LOC |
Controls whether certain information prints on the Reset Audit Log for Quantity Printed. Currently, there is no information to define. |
RESETRSV
RESET_AUDIT_LOG_QTY_RESERVED |
Controls whether certain information prints on the Reset Audit Log for Quantity Reserved. Currently, there is no information to define. |
RESETSKU
RESET_AUDIT_LOG_SKU_QTYS |
Controls whether certain information prints on the Reset Audit Log for SKU Quantities. Currently, there is no information to define. |
RETARSNNOITM
RETURN_ALL_REASON_NO_ITEM |
Controls whether certain information prints on the Return Reason Report. Currently, there is no information to define. |
RETARSNNOITMCSV
RETURN_ALL_REASON_NO_ITEM_CSV |
Controls whether certain information prints on the Return Reason Report in spreadsheet format. Currently, there is no information to define. |
RETARSNWITM
RETURN_ALL_REASON_WITH_ITEM |
Controls whether certain information prints on the Return Reason Report by item. Currently, there is no information to define. |
RETARSNWITMCSV
RETURN_ALL_REASON_WITH_ITEM_CSV |
Controls whether certain information prints on the Return Reason Report by item in spreadsheet format. Currently, there is no information to define. |
RETRSNNOITM
RETURN_SPECIFIC_REASON_NO_ITEM |
Controls whether certain information prints on the Return Reason Report by reason code. Currently, there is no information to define. |
RETRSNNOITMCSV
RETURN_SPECIFIC_REASON_NO_ITEM_CSV |
Controls whether certain information prints on the Return Reason Report by reason code in spreadsheet format. Currently, there is no information to define. |
RETRSNWITM
RETURN_SPECIFIC_REASON_WITH_ITEM |
Controls whether certain information prints on the Return Reason Report by reason code and item. Currently, there is no information to define. |
RETRSNWITMCSV
RETURN_SPECIFIC_REASON_WITH_ITEM_CSV |
Controls whether certain information prints on the Return Reason Report by reason code and item in spreadsheet format. Currently, there is no information to define. |
SLSJRN
SALES_JOURNAL |
Controls whether certain information prints on the Standard Sales Journal. Currently, there is no information to define. |
SLSJRNCSV
SALES_JOURNAL_CSV |
Controls whether certain information prints on the Standard Sales Journal in spreadsheet format. Currently, there is no information to define. |
SLSJRNDIV
SALES_JOURNAL_BY_DIV |
Controls whether certain information prints on the Sales Journal by Division. Currently, there is no information to define. |
SLSJRNDIVCSV
SALES_JOURNAL_BY_DIV_CSV |
Controls whether certain information prints on the Sales Journal by Division in spreadsheet format. Currently, there is no information to define. |
SLSUPERR
SALES_REP_UPDATE_ERROR |
Controls whether certain information prints on the Sales Rep Update Errors Report. Currently, there is no information to define. |
SOLDOUT
SOLDOUT |
Controls whether certain information prints on the Soldout Notification Card. Currently, there is no information to define. |
STRUPERR
STORE_UPDATE_ERROR |
Controls whether certain information prints on the Store Update Errors Report. Currently, there is no information to define. |
TAXJUR
TAX_JURISDICTION_REPORT |
Controls whether certain information prints on the Tax Jurisdiction Report. Currently, there is no information to define. |
UTJOBMRPT
JOB_MONITOR_STS_TXT |
Controls whether certain information prints on the job monitor alert email; see Monitoring Jobs. Currently, there is no information to define. |
UTSTSRPT
SERENADE_STATUS_REPORT |
Controls whether certain information prints on the Order Management System Cloud Service Status report. Currently, there is no information to define. |
Property Name |
Description |
ADDRESS_SERVICE_ENDPOINT_URL |
Verify the URL used to connect to EDQ. This setting is delivered with the application and should not be changed. |
ADDRESS_SERVICE_RETURN_LAYOUT |
The name of the custom layout used for data mapping. This layout resides with Experian and should be set to Serenade. Do not change this setting. |
API_SERVER_URL |
Information will be provided at a later date. |
API_TENANT_ACCESS_KEY |
Information will be provided at a later date. |
API_TENANT_SECRET_KEY |
Information will be provided at a later date. |
The directory the Salesman Associate Upload Process monitors for new Salesman Associate files to process, if the File Storage API is not in use. However, even if the file storage API is enabled, the process still uses this folder to place files that have been uploaded prior to additional processing, so this property must be set up even if you use the file storage API. An example directory on the application server is /domain/conf/OMSFiles/File/Associate/, where domain is the WebLogic domain directory for Order Management System Cloud Service. 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. If you use the File Storage API, you can 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. |
|
The account ID used for communication with the AvaTax tax interface when a company-specific account ID has not been provided in the AvaTax Account (M37) system control value. See Avalara AvaTax Setup for more information. |
|
The license ID used for communication with the AvaTax tax interface when a company-specific license ID has not been provided in the AvaTax License (M38) system control value. The system encrypts this entry. See Avalara AvaTax Setup for more information. |
|
CA_INVENTORY_FILE_LOCAL_FOLDER |
The folder on the Order Management System Cloud Service server where the CAINV periodic function writes the inventory file. See Sending Current Inventory Information to ChannelAdvisor for background. Note: You should create this folder on your server if the folder does not already exist. |
CA_INVENTORY_FILE_NAME |
The file name for the CAINV periodic function to use when creating a file of current inventory levels for items. See Sending Current Inventory Information to ChannelAdvisor for background. |
CHANNELADVISOR_ORDER_URL |
The URL for: • the CAORDUP periodic function to use when requesting new orders from ChannelAdvisor; see Importing Orders from ChannelAdvisor for background. • Processing Refunds (MREF) to use when sending refund information to ChannelAdvisor; see Submitting Refunds for ChannelAdvisor Orders for background. |
CHANNELADVISOR_SHIPPING_URL |
The URL for the CASHIP periodic function to use when sending shipment confirmations to ChannelAdvisor; see Sending Shipment Confirmations to ChannelAdvisorfor background. |
The maximum number of orders that the GetOrderList function processes at once before sending the notification to ChannelAdvisor that the orders were successfully received and created. Each batch can include up to 50 orders. For example, if you set this property to 100, the function imports two batches of 50 orders. If no maximum is specified, a default of 50 orders applies. |
|
CW_FTP_POS_LOG_FILE |
If set to Y, indicates to FTP the POSLog file using the poslog_ftp_commands.script, described below. FTP script: The FTP script for POSLog integration is defined in the poslog_ftp_commands.script file. This file is located in the CWDIRECTCP_ FTP_FOLDER property. The script consists of: open | server | userID | passwd put | /poslog/FTP_REMOTE_FILE_NAME where: • server = the name of the destination server • userID = a valid user ID for the destination system • passwd = the user ID’s password Note: You should not modify the second line of the command file. |
OROB_LIMITED_STATUS_BEG_TIME |
Defines settings for the Daily Status Inquiry Time Window (all versions). These settings apply to retail pickup and ship-for-pickup orders. Overview: For certain Order Broker statuses, it is not necessary to send a status inquiry as frequently as the Order Broker Status Update Interval (K10), because no immediate action is required in Order Management System Cloud Service. These statuses apply to retail pickup or ship-to store orders: • In transit: the order has been shipped to the store location • received: the order has been received at the store location, but the customer has not yet picked it up • partially fulfilled: the customer has picked up some of the items, or quantity of items on the order, but has not yet received the entire order In order to avoid sending unnecessary status inquiry messages for orders in these statuses, the BROKER process checks their status once daily during a specified time window. It uses the following two additional properties to determine the start and end of the window: • OROB_LIMITED_STATUS_BEG_TIME=123456 • OROB_LIMITED_STATUS_END_TIME=123456 Each time is indicated in HHMMSS format, military time. For example, if you set these properties to: OROB_LIMITED_STATUS_BEG_TIME=180000 OROB_LIMITED_STATUS_END_TIME=210000 Then the BROKER process can send status inquiry requests for these orders between 6:00 p.m. and 9:00 p.m. daily. Orders are eligible for status inquiry if one has not taken place in the previous 12 hours. You should set the time window long enough to process status inquiries for all orders in the related statuses; also, the time window should not cross midnight. |
OROB_LIMITED_STATUS_END_TIME |
|
CW_MANIFST_ENVIRONMENT_ID |
The environment ID that identifies the Order Management System Cloud Service database environment associated with the Manifest Web Service. The environment ID associated with a database environment is defined in the dbconfig.properties file. You can locate the environment ID in this file by locating the database; the number in the first column for the database represents the environment ID. The default environment ID is 1. Required. |
CW_MANIFST_USER_ID |
The user ID that the Manifest Web Service uses to connect to the Order Management System Cloud Service database environment specified in the CW_MANIFEST_ENVIRONMENT_ID property. Note: You must also create this user ID inOrder Management System Cloud Service: • as a valid user ID with administrator authority in Work with Users (WUSR), and • as a user with advanced commands and all job authority in User Control (creating a user control record is available by selecting Advanced Commands > User Control under My Docs, My Forms, or My Jobs). See User Configuration in the Administration Guide for more information on creating a user ID in Order Management System Cloud Service. Required. |
CW_POS_LOG_FILE_NAME |
Specifies the name of the POSLog file, with the pound sign (#) indicating where to insert the three-position Default Location for ORCE Integration (K69). For example, if you set this property to Store #.POL, the file is named Store #123.POL, where 123 is the Default Location for ORCE Integration (K69). |
The location on the 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, if the File Storage API is not in use. However, even if the file storage API is enabled, the process still uses this folder to place files that have been uploaded prior to additional processing, so this property must be set up even if you use the file storage API. An example directory is /domain/conf/OMSFiles/LZIP/ctystate.txt, where domain is the WebLogic domain directory for Order Management System Cloud Service. 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. |
|
CYB_PAY_LINK_DECISION_MANAGER_ENABLED |
Defines whether Cybersource Decision Manager Fraud Scoring processing is enabled in the Order Management System Cloud Service Point-to-Point integration with Cybersource. false = the Order Management System Cloud Service Point-to-Point integration with Cybersource does not support Decision Manager processing in Cybersource. Order Management System Cloud Service sends all authorization transactions to Cybersource with the decisionManager_enabled tag set to false, indicating Decision Manager processing should not occur. However, you can use Cybersource’s Decision Manager for authorization transactions you process on your web storefront. true = the Order Management System Cloud Service Point-to-Point integration with Cybersource supports Decision Manager processing in Cybersource. Order Management System Cloud Service sends all authorization transactions to Cybersource with the decisionManager_enabled tag set to true, indicating Decision Manager processing should occur. See Cybersource Point-to-Point Decision Manager Process for more details. |
CYB_PAY_LINK_DECISION_MANAGER_KEY |
A key, generated in Cybersource Decision Manager, that is used to authenticate the Cybersource Decision Manager Update periodic function (CYBDMUP). |
CYB_PAY_LINK_DECISION_MANAGER_MERCHANT_ID_OVERRIDE |
The merchant ID provided by Cybersource to use during Decision Manager Fraud Scoring processing. If this setting is blank, the system uses the following hierarchy to determine the merchant ID to use: • Merchant # field in the CC Paytype Cross Ref table • Merchant ID field in the Merchant ID Override table • Merchant ID field in the Authorization Services table |
CYB_PAY_LINK_DECISION_MANAGER_PASSWORD |
Note: The Cybersource Decision Manager Update periodic function no longer uses this property, and the property has been discontinued. |
CYB_PAY_LINK_DECISION_MANAGER_SEND_TO_PRODUCTION |
Defines whether transactions are sent to the Cybersource Decision Manager TEST server or PRODUCTION server. true = Order Management System Cloud Service sends transactions to the Cybersource Decision Manager PRODUCTION server. false = Order Management System Cloud Service sends transactions to the Cybersource Decision Manager TEST server. |
CYB_PAY_LINK_DECISION_MANAGER_SECRET_KEY |
A key, generated in Cybersource Decision Manager, that is used to authenticate the Cybersource Decision Manager Update periodic function (CYBDMUP). |
CYB_PAY_LINK_DECISION_MANAGER_USER_ID |
Note: The Cybersource Decision Manager Update periodic function no longer uses this property, and the property has been discontinued. |
CYB_PAY_LINK_SERVICE |
The name of the external system. Set this to Cybersource. |
CYB_PAY_LINK_SERVICE_ENABLE_LOG |
Defines whether the web service logs request and response messages. true = Order Management System Cloud Service writes request and response messages to the Cybersource log. false = Order Management System Cloud Service does not write request and response messages to the Cybersource log. Data security: Set this value to false unless you are troubleshooting the Order Management System Cloud Service integration with Cybersource. Once you are done troubleshooting, delete any log files that are created. |
CYB_PAY_LINK _SERVICE_LOG_DIRECTORY |
The location of the log written by the web service API program. Use this log to review the transactions processed between Order Management System Cloud Service and Cybersource. Data security: For data security, Order Management System Cloud Service masks credit card information in this log. An example directory is domain/conf/OMSFiles/Integrations/Cybersource/Log, where domain is the WebLogic domain directory for Order Management System Cloud Service. |
CYB_PAY_LINK_ SERVICE_KEY_ DIRECTORY |
The location of the encrypted security key file used by the web service API program to validate and secure transactions from Order Management System Cloud Service. An example directory is domain/conf/OMSFiles/Integrations/Cybersource/Key, where domain is the WebLogic domain directory for Order Management System Cloud Service. |
CYB_PAY_LINK_SERVICE_SEND_TO_PRODUCTION |
Defines whether transactions are sent to the Cybersource TEST server or PRODUCTION server. true = Order Management System Cloud Service sends transactions to the Cybersource PRODUCTION server. false = Order Management System Cloud Service sends transactions to the Cybersource TEST server. |
Defines whether to place file data for export in the FILE_STORAGE table rather than placing the files in a folder for FTP. Set to true if the file storage API is enabled for exports; otherwise, false. See File Storage API for information. |
|
Defines whether to use the FILE_STORAGE table and the file storage API, rather than FTP, to upload files. Set to true if the file storage API is enabled for imports; otherwise, false. See File Storage API for information. |
|
The maximum size, in bytes, of a file that can be uploaded to the FILE_STORAGE table. Applies only if the FILE_STORAGE_IMPORTS_ENABLED property is set to true. If a file’s size exceeds this maximum, the API returns a 403 error and the upload fails. Uploaded files should be less than 1G in size, so this property should be set to 1073741824 or less. |
|
Specifies the prefix to use for the URL of a company logo or an entity logo and the menu driver image to display on menu screens or print on forms, including the pick slip, purchase order, quote form, gift acknowledgement, and order receipt. Must point to a publicly available server. For example, set this property to https://SERVER:7500/images where SERVER is the name of the server, 7500 is the port, and images is the folder where company and entity logo images are stored. The URL for image.png might then be https://SERVER:7500/images/image.png. See Setting Up Company Logos for Menu Screens, Setting Up Menu Driver Images for Companies, and Setting Up Company Logos for Forms for more information. Note: This URL is not used for item images. You need to specify the complete URL. See Setting Up Item Images for background. |
|
Defines the URL to receive the Job Notification Outbound Message. When you set this URL, the change takes effect immediately. Required to generate the Job Notification message. See Using the Job Notification Outbound REST Message for more information. If the endpoint is not valid or cannot be reached for any reason, an error is written to the CWDirect.log. However, if the property is blank, a message such as the following is written to the APP log: DEBUG APP - message: Job Notification Outbound Webservice URL not mentioned in Property. |
|
LOYALTY_REWARDS_ACCOUNT_INQUIRY_PROCESSING |
Not implemented. |
LOYALTY_REWARDS_REDEEM_CERTIFICATE_PROCESSING |
Not implemented. |
LOYALTY_REWARDS_VOID_CERTIFICATE_PROCESSING |
Not implemented. |
MASS_CUSTDWNLD_CUSTOMER_CLASSES |
The customer class used to determine which sold to customers to include in the Mass Customer Download. To define more than one customer class, separate the values with a comma. Example: CL,NR Note: You cannot add a blank value to this setting to include sold to customers that do not have a customer class defined. For example, you cannot enter CL, ,NR or CL,’’,NR. Leave this setting blank if you wish to include all sold to customers, regardless of the assigned customer class, in the Mass Customer Download. |
MASS_ CUSTDWNLD_ DOWNLOAD_ DIRECTORY |
Required. The directory where Order Management System Cloud Service places the Mass Customer Download file to be sent to an external system. This can be a directory on the Order Management System Cloud Service application server or on another server. An example directory is domain/conf/OMSFiles/Integrations/Xlink, where domain is the WebLogic domain directory for Order Management System Cloud Service. Note: If you define a directory on an external server, the remote destination folder must be a shared folder. See Mass Customer Download for more information. |
MASS_CUSTDWNLD_FILE_NAME |
Required. The name of the Mass Customer Download file. The delivered setting is MassCustomerDownload. • During processing, Order Management System Cloud Service adds the prefix TEMP to the name of the file; for example: TEMP_MassCustomerDownload • Once processing is complete, Order Management System Cloud Service adds a date and time stamp to the file name; for example: MassCustomerDownload.20110128.170150340 • Order Management System Cloud Service also archives the file in zip format; for example: MassCustomerDownload.20110128.170150340.zip |
MASS_CUSTDWNLD_MESSAGE_WRAPPER |
The XML root element name Order Management System Cloud Service adds to the beginning and end of the Mass Customer Download file to make the contents of the file a valid XML document. If you leave this setting blank, the file will not be a valid XML document; however, each message in the file will be a valid XML message. |
ORCE_ALT_ID_OROMS |
Indicates the Alt Key Type of the alternate key in Oracle Retail Customer Engagement that maps to the Order Management System Cloud Service customer number. Oracle Retail Customer Engagement automatically creates this entry for a customer when you send the customer to Oracle Retail Customer Engagement if it does not already exist. Also, Oracle Retail Customer Engagement adds a row to the CST_ALT_KEY_TYPCODE table in the Oracle Retail Customer Engagement database if it does not already exist. An example of this setting is: ORCE_ALT_ID_OROMS=OROMS_ID |
ORCE_ALT_ID_POS |
Not currently implemented. |
ORCE_ALT_ID_WEB |
Indicates the Alt Key Type of the alternate key in Oracle Retail Customer Engagement that maps to the e-commerce site’s customer number. How to define in Oracle Retail Customer Engagement? You can create a alternate key type such as EONE_USER_ID in Oracle Retail Customer Engagement by: • sending the Customer Engagement Add or Update Customer Message from your e-commerce system with an AlternateKey whose TypeCode is EONE_USER_ID • adding a row to the CST_ALT_KEY_TYPCODE table in the Oracle Retail Customer Engagement database Note: See the Customer Engagement Customer Integration for information on how the e-commerce customer ID is used to identify the customer in the order API. An example of this setting is: ORCE_ALT_ID_WEB=OCP_CUST_ID |
ORCE_CARD_SERVICE_SUFFIX |
The system uses this property, along with the ORCE_CUSTOMER_SERVICE_PREFIX and the value in the ORCE Organization Descriptor (L50) to build the URL for communication with Oracle Retail Customer Engagement using the Oracle Retail Customer Engagement Card Services API. Set this to /OrceWebServices/v2_1/CardServicesApiService?wsdl where 2_1 is the version of the Card Services API. |
ORCE_CUSTOMER_ID_DIRECTORY_PATH |
Defines the location on the Order Management System Cloud Service application server where the RLTCSID 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 Management System Cloud Service application server. An example directory setting is /domain/conf/OMSFiles/RelateData/customerID/, where domain is the installed location of Order Management System Cloud Service. |
The system uses this property to build the URL for communication with Oracle Retail Customer Engagement. Set this to https://server:8447/ where: • server = the name of your Oracle Retail Customer Engagement server • 8447 = the port to use on the Oracle Retail Customer Engagement server |
|
ORCE_CUSTOMER_SERVICE_SUFFIX |
The system uses this property, along with the ORCE_CUSTOMER_SERVICE_PREFIX and the value in the ORCE Organization Descriptor (L50) to build the URL for communication with Oracle Retail Customer Engagement using the Customer Services API. Set this to /OrceWebServices/v2_3/CustomerServicesApiService?wsdl where 2_3 is the version of the Customer Services API. |
ORCE_CUSTOMER_WITHOUT_ORCE_ID_DIRECTORY_PATH |
Defines the location on the Order Management System Cloud Service application server where the RLTNOID Report Customer with No Relate ID Report periodic function (program name PFRCNI) generates the Customers without Relate IDs report. See Oracle Retail Order Management System Customers without Relate ID Report. This setting must be a valid location on the Order Management System Cloud Service application server. An example directory is /domain/conf/OMSFiles/RelateData/customerWithoutRelateIdReports/, where domain is the WebLogic domain directory for Order Management System Cloud Service. |
ORCE_DAY_PHONE_LABEL |
Indicates the Telephone Type in Oracle Retail Customer Engagement that maps to the daytime phone number in Order Management System Cloud Service. Should be set to BUSINESS. How to define in Oracle Retail Customer Engagement? You can create a telephone type of BUSINESS in Oracle Retail Customer Engagement by: • sending the Customer Engagement Add or Update Customer Message with a ContactType of Phone and a SubTypeCode BUSINESS • adding a row to the CST_PHONE_TYPCODE table in the Oracle Retail Customer Engagement database An example of this setting is: ORCE_DAY_PHONE_LABEL=BUSINESS |
ORCE_DIRECTORY_PATH |
Defines the location where Order Management System Cloud Service places the batch files to send to Oracle Retail Customer Engagement. If this setting is blank or an invalid path, the system writes a message to the Application LogOrder Management System Cloud Service: Item Feed not run because the ORCE_DIRECTORY_PATH was not set up on this server. See Working with Customer Properties (PROP). Note: Not related to the Customer Engagement Customer Integration. Order Management System Cloud Service application server example: /domain/conf/OMSFiles/RelateData/ where, domain is the WebLogic domain directory for Order Management System Cloud Service. |
ORCE_EVE_PHONE_LABEL |
Indicates the Telephone Type in Oracle Retail Customer Engagement that maps to the evening phone number in Order Management System Cloud Service. How to define in Oracle Retail Customer Engagement? You can create a telephone type of HOME in Oracle Retail Customer Engagement by: • sending the Customer Engagement Add or Update Customer Message with a ContactType of Phone and a SubTypeCode HOME • adding a row to the CST_PHONE_TYPCODE table in the Oracle Retail Customer Engagement database An example of this setting is: ORCE_EVE_PHONE_LABEL=HOME |
ORCE_FAX_PHONE_LABEL |
Indicates the Telephone Type in Oracle Retail Customer Engagement that maps to the third phone number in Order Management System Cloud Service. The Third Phone Number Type (L53) system control value controls whether the third phone number is labeled as the mobile or fax number in Order Management System Cloud Service. Note: The name entered in the Third Phone Number Type (L53) system control value should match the value defined for the ORCE_FAX_PHONE_LABEL. How to define in Oracle Retail Customer Engagement? You can create a telephone type of FAX or MOBILE in Oracle Retail Customer Engagement by: • sending the Customer Engagement Add or Update Customer Message with a ContactType of Phone and a SubTypeCode FAX or MOBILE • adding a row to the CST_PHONE_TYPCODE table in the Oracle Retail Customer Engagement database An example of this setting is: ORCE_FAX_PHONE_LABEL=MOBILE |
ORCE_LOYALTY_AWARD_SERVICE_SUFFIX |
The system uses this property, along with the ORCE_CUSTOMER_SERVICE_PREFIX and the value in the ORCE Organization Descriptor (L50) to build the URL for communication with Oracle Retail Customer Engagement using the Oracle Retail Customer Engagement Award Account Services API. Set this to /OrceWebServices/v1_2/AwardAccountServicesApiService?wsdl where 1_2 is the version of the Award Account Services API. |
ORCE_LOYALTY_PROMPT_ATTRIBUTE |
Defines the corresponding Oracle Retail Customer Engagement custom attribute to identify whether Order Management System Cloud Service should automatically display the Customer Loyalty Registration Window for a customer that is not already assigned to a loyalty card. See Oracle Retail Customer Engagement PROMPT_TO_JOIN_LOYALTY Attribute Definition for setup instructions. |
ORCE_LOYALTY_REG_MESSAGE |
The text to display on the Customer Loyalty Registration Window, up to 55 positions. |
ORCE_LOYALTY_SERVICE_SUFFIX |
The system uses this property, along with the ORCE_CUSTOMER_SERVICE_PREFIX and the value in the ORCE Organization Descriptor (L50) to build the URL for communication with Oracle Retail Customer Engagement using the Oracle Retail Customer Engagement Loyalty Account Services API. Set this to /OrceWebServices/v1_2/LoyaltyAccountServicesApiService?wsdl where 1_2 is the version of the Loyalty Account Services API. |
The Oracle Retail Customer Engagement user ID with Security Group permission included in the Oracle Retail Customer Engagement API messages. This setting must be a valid user ID in Oracle Retail Customer Engagement that has Security Group permission. |
|
The system uses this property, along with the ORCE_CUSTOMER_SERVICE_PREFIX and the value in the ORCE Organization Descriptor (L50) to build the URL for communication with Oracle Retail Customer Engagement using the Oracle Retail Customer Engagement Stored Value Card Transaction Services API. Set this to /OrceWebServices/v3_1/SvcTransactionServicesApiService?wsdl where 3_1 is the version of the Stored Value Card Transaction Services API. |
|
OROB_DISCOVERY_SERVICES_WSDL_LOCATION |
The endpoint for the Discovery Services web service. This entry should be set to https://SERVER:8443/Locate/DiscoveryServices, where SERVER is the name of your Oracle Retail Order Broker server. See Importing Store Cross Reference Locations through Order Broker’s Discovery Web Service. |
OROB_IMPORTS_ENABLED |
Defines whether the system uses the Order Broker Import RESTful web service to automatically upload product, product location, and incremental inventory import files to the OROB-Imports location on the Order Broker application server. • true = The system uses the Order Broker Import RESTful web service to automatically upload product, product location, and incremental inventory files to the OROB-Imports location in Order Broker. Note: Set this value to true only if you are use Order Broker version 18.0 or higher. • false = The system does not use the Order Broker Import RESTful web service to automatically upload product, product location, and incremental inventory files to Order Broker. Instead, the system places the generated file in the location on the application server defined in the OROB_DIRECTORY_PATH property and you must use sFTP to move the files to the OROB-Imports location in Order Broker. Once the import file is in the OROB-Imports location in Order Broker, you must use the Schedule Import Process screen in Oracle Retail Order Broker to process the import. You can also run the import on demand from this screen. See Order Broker’s Product, Product Location, and Incremental Inventory Import Process. |
Defines the message version to include in Order Broker and merchandise locator request messages that Order Management System Cloud Service sends to Order Broker. A message version of 5.0 or higher is required to use the status list request message and streamlined allocation at pick slip generation. See Use OROB Status Inquiry List Web Service (M05) and Use Streamlined Allocation (L63) for background. A message version of 16.0 or higher is required to use the Ship-for-Pickup Orders integration with Order Broker. Note: To avoid unpredictable results, do not leave this property blank. |
|
Indicates the maximum number of drop ship updates for Oracle Retail Order Broker to include in drop ship status inquiry responses. For example, you might set this number to 100 to prevent a large number of status updates from impeding system performance. If this property is blank, Oracle Retail Order Broker does not limit the number of updates included in the response message. |
|
Specifies the outbound message version to send to Oracle Retail Order Broker for integration with the Supplier Direct Fulfillment module. Should be set to 4.5 or higher. |
|
The endpoint for the Purchasing Services web service. This entry should be set to https://SERVER:8443/Locate/PurchasingServices, where SERVER is the name of your Oracle Retail Order Broker server. |
|
OROB_SERVICES_WSDL_LOCATION |
The endpoint for the Services web service. This entry should be set to https://SERVER:8443/Locate/LocateServices, where SERVER is the name of your Oracle Retail Order Broker server. |
PMD_PAY_LINK_SERVICE |
The name of the external system. Note: This field is not currently implemented. |
PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT |
The port number used to connect to Paymentech to process batch deposit transactions. Note: Defining a separate port number to process batch deposit transactions allows you to run pick slip generation (batch authorizations) and deposits at the same time. Leave this setting blank if you wish to use the port number defined for the PMD_PAY_LINK_SERVICE_BATCH_PORT property to process both batch authorization and deposit transactions; if you use the same port number to process batch authorization and deposit transactions, you cannot run pick slip generation and deposits at the same time. Note: This setting is not currently implemented. |
PMD_PAY_LINK_SERVICE_BATCH_IP_ADDRESS |
The IP address used to connect to Paymentech to process batch transactions. Note: This setting is not currently implemented. |
PMD_PAY_LINK_SERVICE_BATCH_PORT |
The port number used to connect to Paymentech to process batch transactions. Note: This setting is not currently implemented. |
PMD_PAY_LINK_SERVICE_ONLINE_IP_ADDRESS |
The IP address used to connect to Paymentech to process online transactions. Note: If you change this setting you must restart the PMD_ONLINE Integration Layer Job. Note: This setting is not currently implemented. |
PMD_PAY_LINK_SERVICE_ONLINE_PORT |
The port number used to connect to Paymentech to process online transactions. Note: This setting is not currently implemented. |
QAS ADDRESS SERVICE TOKEN |
Enter the address service token used by EDQ to identify a customer; this is a token you created in the EDQ self service portal. |
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. An example directory on the application server is /domain/conf/OMSFiles/File/Store/, where domain is the WebLogic domain directory for Order Management System Cloud Service. See Store Upload. Note: The File Storage API does not support uploading stores. If the file storage API is enabled, you need to use Work with File Uploads (WUPL) to upload stores. |
|
Select this property to have the warehouse on-order quantity updated through the purchase order layering process. Default = false. • You should set this property to TRUE if you upgrade to 19.0 or higher from a release prior to 18.0, in order to have PO layering update the on-order quantity consistently with prior functionality. • You should leave this property set to FALSE if you use the enterprise order integration for future receipts and pre-order processing. See Purchase Order Layering for background on the purchase order layering process. |
|
VERTEX_PASSWORD |
The user ID and password used to connect to Vertex. The password is encrypted. See Vertex Setup. |
VERTEX_USER |
|
VERTEX_SERVICE_ENDPOINT_URL |
The URL used to communicate with Vertex, such as http://example.com/vertex-ws/services/CalculateTax80, where 80 indicates the version of Vertex, such as 8.0. See Vertex Setup. |
WMSKUBLOCKER_HOST |
Defines the IP address used to connect to the external system that determines item eligibility for an order. See Second Compatibility Code used to Trigger SKU Blocking (K84) for more information. Contact your Oracle Retail Order Management System representative for more information about creating a unique program to transmit SKU Blocking messages between Oracle Retail Order Management System and an external system. |
WMSKUBLOCKER_PORT |
Defines the port number used to connect to the external system that determines item eligibility for an order. See Second Compatibility Code used to Trigger SKU Blocking (K84) for more information. Contact your Order Management System Cloud Service representative for more information about creating a unique program to transmit SKU Blocking messages between Order Management System Cloud Service and an external system. |
The directory where the POSLOGX periodic function archives a copy of the custom POSlog sent to Xlink. This directory is used if the FILE_STORAGE_EXPORTS_ENABLED property is set to false. Otherwise, if file storage exports are enabled, the function adds a record to the OMS-POSLOG container of the FILE_STORAGE table with a zip file containing the POSlog file, and you can use the file storage API to retrieve the file. The zip file has the same name as the POSlog file, except for the .zip extension. See File Storage API for background. |
|
XLINK_DIRECTORY_PATH |
The directory where the POSLOGX periodic function places a custom POSlog to send to Xlink if you are not using the file storage API, as described above. |
XLINK_POSLOG_FILE_DATETIME |
Used to create the name of a custom POSLog: • the date and time format. • the file extension. • the file format. • the file prefix. • the file trigger extension. |
XLINK_POSLOG_FILE_EXTENSION |
|
XLINK_POSLOG_FILE_FORMAT |
|
XLINK_POSLOG_FILE_PREFIX |
|
XLINK_POSLOG_FILE_TRIGGER_EXTENSION |
The settings below define configuration settings for the Order Management System Cloud Service application server.
Property Name |
Description |
The location on the Order Management System Cloud Service 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. An example directory is /domain/conf/OMSFiles/LZIP/ctystate.txt/, where domain is the WebLogic domain directory for Order Management System Cloud Service. Note that even if you use the File Storage API, the upload process uses the folder specified in this property, so you must set it up. 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. |
|
The character format used to indicate the decimal place in a number on screens. Valid value are: . (period); default , (comma) For example, if you enter . (period) as the decimal separator, a number with decimals displays as 123.45. If you enter , (comma) as the decimal separator, a number with decimals displays as 123,45. During installation, the system prompts for the default decimal separator of Order Management System Cloud Service. The system stores the default decimal separator in this property. Important: If you change the default decimal separator from the decimal separator selected during installation, the new default decimal separator applies only to new data; seed data provided during installation will not be translated to the new decimal separator format. The decimal separator used on reports generated through BI Publisher is based on the BI Date and Separator Format defined for the company. See Regional Settings for an overview, and see Where are Number Format Applied? for more information on the decimal separator that defaults to different areas of the application. |
|
The default date format used in the application. Valid values are: • DMY (DDMMYY) = If the date is December 25 2018, the date displays as 251218. • MDY (MMDDYY) = If the date is December 25 2018, the date displays as 122518. • YMD (YYMMDD) = If the date is December 25 2018, the date displays as 161228. During installation, the system prompts for the default date format of Order Management System Cloud Service. The system: • Stores the default date format in this property. Important: If you change the default date format from the date format selected during installation, the new default date format applies only to new users and companies; seed data provided during installation will not be translated to the new default date format. • Defaults this date format to the admin user that is created during installation. • Defaults this date format to the Date format field in the Company table for the companies delivered with Order Management System Cloud Service. However, you can change the date format for a company in the Work with Company (WCMP) menu option. • When you create a new user or company, the system assigns the default date format to the user or company. However, you can change the date format defined for a user in the Work with Users (WUSR) menu option and you can change the date format for a company in the Work with Company (WCMP) menu option. Note: Regardless of the date format that displays on screens, dates are stored in the database in CYYMMDD format. The date format to use on reports generated through BI Publisher is based on the BI Date and Separator Format defined for the company. Note: In order to have a consistent date format on all reports, this property and the Date Format defined for the company should be the same. See Regional Settings for an overview and see Where are Date Formats Applied? for more information on the date format used for different areas of the application. |
|
The default locale used in the application, indicating the default language for the application. During installation, the system: • Stores the default locale in this property. • Defaults this locale to the admin user that is created during installation. • Defaults this locale to the Locale field in the Company table for the companies delivered with Order Management System Cloud Service. • When you create a new user or company, this default locale defaults, but you can override it. See: • Regional Settings for an overview. • Where are Date Formats Applied? for more information on which date format the system uses in different areas of the application. • Where are Number Format Applied? for more information on the decimal and thousand separators the system uses in different areas of the application. |
|
ECOMMERCE_AVAILABILITY_XML_VERSION |
The XML version of the AvailabilityWeb XML message received from an external system; see E-Commerce Availability Web API. |
ECOMMERCE_PRODUCT_XML_VERSION |
The XML version of the ProductWeb XML message generated through Downloading E-Commerce Offer Files (EOFR) when the Generate E-Commerce Offer Tables (M29) system control value is unselected. |
The character format used to separate groups of thousands. Valid value are: , (comma); default . (period) For example, if you enter . (decimal) as the thousand separator, a number with thousand displays as 1.000. If you enter , (comma) as the thousand separator, a number with thousand displays as 1,000. During installation, the system prompts for the default thousand separator of Order Management System Cloud Service. The system stores the default thousand separator in this property. Important: If you change the default thousand separator from the thousand separator selected during installation, the new default thousand separator applies only to new data; seed data provided during installation will not be translated to the new thousand separator format. The thousand separator used on reports generated through BI Publisher is based on the BI Date and Separator Format defined for the company. See Regional Settings for an overview and see Where are Number Format Applied? for more information on the thousand separator that defaults to different areas of the application. |