Field
Description
UI Timeout
The number of minutes that Order Broker should wait before timing out a user’s inactive session. When the session times out, the screen displays an error when the user next clicks an option or attempts to navigate in Order Broker, and needs to close the browser before logging back in to Order Broker.
Your entry can be 1 to 999 minutes. Required.
The default setting is 30 minutes.
Select this option to be able to use the Routing Engine and see related screens.
Required settings:
• If you select the Use Store Connect option but not this option, this option is selected automatically.
• Order Broker requires that at least this option or the Use Vendor Portal option are selected. If you don’t select any of the module use options, the Use Routing Engine option is selected automatically.
See the Home Screen for information on screen access controlled by this setting.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Lock Out
The number of unsuccessful, sequential login attempts that triggers Order Broker to disable a user account. When a user attempts to log in with a disabled account, Order Broker displays a general error indicating that the login failed.
Example: If you set this number to 4, a user account is disabled after the entry of 4 incorrect passwords in a row.
Reset: A user’s counter is reset:
• after a successful login (for example, if there are 3 unsuccessful login attempts, followed by a successful login, the counter is reset to 0
• when you re-enable the account at the User Profiles screen or the User Profile Configuration screen
Note: If you change the user account back to Active status, the account remains disabled until the Lockout Duration specified in the User Lockout options in WebLogic has passed.
Your entry can be 1 to 99 login attempts. The default setting is 5. Required.
Select this option to be able to have the Store Connect module available and to have a process poll for new delivery or pickup orders assigned to Store Connect locations. This option also requires the Routing Engine. If you select this option and don’t select Use Routing Engine, the Use Routing Engine option is selected automatically.
See the Home Screen for information on screen access controlled by this setting.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Tenant Logo
The URL for the logo to display at the Store Connect login page at a size of 254 x 33 pixels.
Preview the logo:
After entering the URL, click the preview icon (
) to preview the image at
254 x 33.
This field is also available to a retailer user at the Tenant (retailer information) screen.
Note: For a cloud implementation, Oracle staff need to make sure that this URL is added to the proxy server’s allow list.
Select this option to have the Drop Ship (Supplier Direct Fulfillment) module available.
See the Home Screen for information on screen access controlled by this setting.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Account
The name of the Order Broker database. The destination specified in inbound XML messages must match this setting. The default setting is locate. Required.
Once you set the account, it should not ordinarily be changed.
Time Zone
The time zone to use when setting schedules and displaying dates and times on screens, in reports, and in email notifications. This is the retailer’s time zone, which can be different from the system time zone and the user’s time zone. See Time Zones for a discussion. Display-only.
Changing the time zone: When the time zone here is reset by the retailer, the following should also be reset:
• New order polling schedule at the Store Connect Preferences screen
• Report schedules, through the Schedule Reports screen
• Imports, through the Schedule Jobs screen
• Incremental inventory import, probable quantity update and export, and fulfilled inventory export, at the System screen
• Jobs scheduled through the Schedule Jobs screen
Indicates the number of records to include in each batch for all imports. The default setting is 1000, the maximum setting is 50,000, and the minimum setting is 10.
See Importing Items/Products, Inventory, Barcodes, and Locations into the Database.
Indicates the number of threads to allot to a background job that calculates probable quantity updates for the Inventory Quantity Export. If this field is set to 0, no calculation takes place. Defaults to 0.
This flag must be selected for an Order Broker Cloud Service upgrade or new installation for release 18.0 or higher. When this flag is selected:
• Authentication for all users, including Web Service Authentication users, takes place using the password defined for the user in Oracle Identity Cloud Service (IDCS).
• All users must be created in IDCS and imported into Order Broker. See the Identity Cloud User Synchronization job for more information. You cannot create a user in Order Broker.
• Order Broker, Store Connect, and vendor users can use the Can’t sign in? link at the login page to reset their passwords.
• You cannot enter or reset a password for an Order Broker user, Store Connect user, Vendor Portal user, or web service user at any Order Broker screen.
• After enabling IDCS for an existing installation, your Oracle representative will provide you with the new URL to log into Order Broker, Store Connect, and the Vendor Portal.
Important: Once this flag is selected, it cannot be changed at this screen.
For more information: See Identity Cloud User Synchronization for more setup information.
The Name identifying Order Broker as an application in IDCS. Typically formatted as RGBU_OBCS_ENV_APPID where OBCS identifies Order Broker and ENV identifies the environment, such as production.
Alphanumeric, 255 positions. Required to use IDCS for authentication of users or web service requests and to use the options at the Manage External Application Access screen.
Can be used as the default client ID for OAuth authentication for the Inventory Service, See the Manage External Application Access for more information.
The URL to use for requests to IDCS.
Alphanumeric, 255 positions. Required to use IDCS for authentication of users or web server requests and to use the options at the Manage External Application Access screen.
The client secret assigned by IDCS and used for OAuth authentication. Required to use the options at the Manage External Application Access screen.
Can be used as the default client secret for OAuth authentication for the Inventory Service. See the Manage External Application Access for more information.
Alphanumeric, 80 positions. Masked on this screen.
Email Template Path
The folder on the Order Broker server where email templates are stored.
The template path should not ordinarily be changed. The default is DOMAIN_HOME/<DOMAIN_FOLDER>/conf/emailtemplates, where DOMAIN_HOME is the location of the WebLogic domain. Required.
The following settings control the number of days to retain certain types of files on a server or records in the database.
If set to 0 days: If you set one of the following to 0 days, then all files or records are purged the day after creation.
Report Files
The number of days to retain records of generated reports. After this number of days, the daily cleanup job automatically deletes the database records, so it is no longer possible to print the reports. Can be from 0 to 30 days. Required.
Pack Slip Files
The number of days to retain pack slip records for purchase orders that have been shipped through the Vendor Portal. After this number of days, the daily cleanup job automatically deletes the database records, so it is no longer possible for the vendor to print the pack slips. Can be from 0 to 30 days. Required.
Note:
• This setting does not control the retention of pack slip records generated through Store Connect. The daily cleanup job automatically deletes these database records after one day. The store associate cannot reprint pack slips using these records.
• Used only by the Supplier Direct Fulfillment module.
The number of days to retain import error files before the daily cleanup job automatically deletes them. Can be from 0 to 30 days. Required.
For more information: See Importing Items/Products, Inventory, Barcodes, and Locations into the Database and Incremental Inventory Import for background.
RICS Log History
The number of days to retain records in the RICS_LOG table of messages between Order Broker and Oracle Retail Integration Cloud Service (RICS) before the daily cleanup job automatically deletes them. Can be from 0 to 30 days. Required.
RICS log records whose Retry Status is Failed are not eligible to be purged.
The RICS log history messages are available for review at the RICS Log tab if the system is configured for order integration through RICS. See Order Fulfillment through RICS Integration for background.
Extract Log History
The number of days to retain extract job history records before the daily cleanup job automatically deletes them. The View Sales Order Data Extract Job History screen displays these records. See Sales Order Data Extract for information on scheduling the extract.
Can be from 0 to 30 days. Defaults to 30. Required.
Trace Log History
The number of days to retain trace log history records for closed, completed, canceled, or unfulfillable orders before the daily cleanup job automatically deletes them. If the Trace Shopping Logic field is set to Detailed at the Event Logging screen, the Routing Engine records the reasons why individual locations are eliminated when selecting a location to source an order. You can use the Trace Shopping Log screen to review these shopping trace records; see that screen for information on tracing shopping logic.
Can be from 0 to 30 days. Defaults to 30. Required.
Indicates where to place the pipe-delimited files containing:
• the location, product, product location (including attributes), and product barcode information for the import process, or the MOMZIP files for import from RMFCS.
• the interim product location updates for the incremental import process.
Ordinarily used only if you use secure FTP rather than File Storage API for Imports and Exports. in this case, this must be a shared folder that is accessible through secure FTP. Once set, this should not ordinarily be changed.
The default is u01/orob_data/ProductUploadData. The error subfolder includes a copy of each file in error (error records only).
For more information: See Importing Items/Products, Inventory, Barcodes, and Locations into the Database and Incremental Inventory Import.
The folder on the Order Broker server where:
• Fulfilled Quantity export: The Fulfilled Inventory Export program writes the pipe-delimited file listing recently fulfilled order lines.
• Probable quantity export: The probable quantity export writes a pipe-delimited file of updated product locations, including the probable quantity. See Inventory Quantity Exportfor more information.
• Sales Order Data Extract: The sales order data export writes a zip file containing pipe-delimited files of order-related information. See Sales Order Data Extract for more information.
Ordinarily used only if you use secure FTP rather than File Storage API for Imports and Exports. in this case, this must be a shared folder that is accessible through secure FTP. Once set, this should not ordinarily be changed.
The default is /u01/orob_data/ExportData.
Proximity Upload Files
The folder on the Order Broker server where Order Broker places files you upload through the Proximity Uploads screen. You use this screen to upload the .CSV (comma-separated value) files. Once set, this should not ordinarily be changed.
Ordinarily used only if you use secure FTP rather than File Storage API for Imports and Exports. in this case, this must be a shared folder that is accessible through secure FTP. Once set, this should not ordinarily be changed.
The default is /u01/orob_data/ProximityUploadData. Required.
Geocode Address
The URL to use when generating geocode requests to determine the latitude and longitude for:
• a location, when the location is created or has its address updated, either through the New Location or Edit Location screens, or through the import process
• a customer’s address, in order to calculate proximity for an order or inventory request, such as the SubmitOrder or the LocateItems request message
If you specify a URL here, Order Broker uses the Oracle Maps Cloud Service to determine latitude or longitude. Otherwise, if this field is blank, Order Broker uses the proximity database.
Invalid URL? If the URL specified here is invalid, the error is logged in the error.log file based on your specified logging level. Also, web service request messages that require lookup of the customer address return an error indicating Customer Address not found. This error is returned only if the Shop Order When Proximity Unknown preference is unselected.
Proxy required: Use of a proxy server is required to use the Oracle Maps Cloud Service. See Proxy Server Settings below for more information.
For more information: See Proximity Locator Searching for background.
Connection Timeout
The number of seconds to wait for a response from Oracle Maps Cloud Service. If there is no response within that number of seconds, Order Broker returns an error to a product availability, locate items, or submit order request:
• Product availability or locate items request: error is 1012 Customer Address not found.
• Submit order request: error is 2084 Customer Address not found
Note: The 2084 error is returned only if the Acknowledge Order Before Brokering preference is not selected.
Applies to both regular Geocode requests and to Turn-by-Turn requests.
Defaults to 30 seconds.
The URL where Order Broker submits requests for turn-by-turn distance calculation. Used only when a Carrier for Turn-by-Turn Distance Evaluation is selected at the Preferences screen, and that carrier is used in a locate items, product availability, or submit order request. See Turn-by-Turn Distance Calculation for Delivery Orders for a discussion.
Failed Geocode Request Threshold
Defines the number of consecutive failed interactive inventory request attempts that, if exceeded, should trigger putting the Geocode requests in a wait time. For example, if this field is set to 5, and 6 requests in a row fail to get a response, Geocode requests are halted for the defined wait time. Applies to both regular Geocode requests and to Turn-by-Turn requests. Defaults to 0.
Can be left set to 0, indicating that failed requests are not evaluated, or from 1 to 10000 if failed requests should be evaluated.
Failed Geocode Request Wait Time
Defines the number of miênutes to wait after the defined number of failed requests have been exceeded. For example, if this field is set to 10, Geocode requests are halted for 10 minutes. Applies to both regular Geocode requests and to Turn-by-Turn requests. Defaults to 0.
Can be left set to 0 only if the Failed Geocode Request Threshold is also set to 0; otherwise, can be set from 1 to 60.
Proxy Address
If your network requires a proxy server to get to external IP addresses, enter the address of the proxy server.
Proxy Port
If your network requires a proxy server to get to external IP addresses, enter the port of the proxy server.