Systems

Purpose: Use the Systems screen to review or work with external databases or business entities that integrate with Order Orchestration for the Routing Engine (including, optionally, the Store Connect module) or Supplier Direct Fulfillment. For example, a system might be a database in Xstore or a company in Order Administration System.

System relationships: See Organization, System, and Location for an overview of the data hierarchy in Order Orchestration, including products.

Created how? You need to use this screen to create each system that will integrate with Order Orchestration. See Setting Up Data for the Routing Engine Module or Setting Up Data for the Supplier Direct Fulfillment Module for more information.

How to display this screen: Select Systems from the Home Screen or from the Systems Menu.

Note:

Only users with Systems authority can display this screen. See Roles for more information.

Options at this screen

Option	Procedure
create a system	Optionally, select a different organization from the Organization drop-down box. See Data Hierarchy for more information on how systems are integrated within organizations. Enter a system code in the System field. System codes can be 1 to 10 positions in length, can include spaces and special characters, and must be unique. Note: When creating the Store Connect system, you should not use a system code that begins with `STC-`, as these characters are used as part of the name for the user group in IDCS or OCI IAM. You can use `STC_` (with an underscore rather than a hyphen) instead. Optionally, enter a name in the Name field. Names can be 1 to 40 positions in length and can include spaces and special characters. If you do not enter a name here, you need to enter it at the System screen when creating a system. Click New. If: the system already exists in the organization, or if you did not select an organization or enter a System code, Order Orchestration displays an error message; otherwise, you advance to the System screen, where you can complete the creation of the system. The Organization Default flag is selected when you create the first system for an organization, and the flag cannot be unselected at this time. To designate a different system as the default, you need to create another system and flag that system as the default; this unflags the first system. Note: If you click Cancel at the System screen after clicking New, the system is not created. Order Administration integration: The code representing the Order Administration system must match the setting of the OROB System (K50) system control value.
search for a system	Use any combination of the fields at the top of the screen to restrict the search results to matching systems: Optionally, select a different organization from the from the Organization drop-down box to restrict your results to this organization. Note: You can select a blank organization to remove this field from your selection criteria. Enter a full or partial system code in the System field to restrict your results to system codes starting with your entry. Enter a full or partial name in the Name field to restrict your results to systems whose names contain your entry. Click Search. Case: The System and Name are case-sensitive for searching; for example, an entry of `p` does not match a system code of `POS`.
select a system for review or maintenance	Click the edit icon () to advance to the System screen. Note: If the System screen is already open in another tab, you advance to that screen, where the previously-selected system is displayed.
delete a system	Click the delete icon () next to a system to delete the system from Order Orchestration. This option is available only if there is not an existing system product or location for the system.

Fields at this screen

Field	Description
Search/new fields:
Organization	Your Default Organization, defined through the Users screen, is selected by default, and the systems associated with that organization are displayed. See organization. Note: You must complete the Preferences screen for an organization before you can select it.
System	See system. System codes can be 1 to 10 positions in length, can include spaces and special characters, and must be unique. Case-sensitive for searching; for example, an entry of `p` does not match a system code of `POS`.
Name	The Name of a system. Names can be 1 to 40 positions in length and can include spaces and special characters. Case-sensitive for searching; for example, an entry of `p` does not match a system name of `POS`.
Results fields:
Organization	See organization.
System	See system. Click a system code to advance to the System screen. Note: If the System screen is already open, you advance to the screen where the previously-selected system is displayed.
Name	The Name of a system.
Online	A check () indicates that this is an online system; otherwise, it is an offline system.
Default	A check () indicates that this is the default system.
Edit	Click the edit icon () for a system to advance to the System screen. At that screen, the settings you can review or change include: database connection settings for product and inventory updates polling and status update settings reserved statuses to subtract from the availably quantity Note: If the System screen is already open in another tab, you advance to that screen, where the previously-selected location is displayed.
Delete	Select the delete icon () for a system to delete the system from Order Orchestration. You can delete the system if there are no existing system product or location records.

System

Purpose: Use the System screen to:

set a system as the default system for the organization
indicate whether the system is an online system or offline system (Routing Engine only)
specify how to obtain interactive inventory information for an online system (Routing Engine only)
specify whether the system requires status updates from assigned fulfilling locations (Routing Engine only)
specify whether the Routing Engine should place a delivery or ship-for-pickup order in another location within the system when the first selected location rejects the order (Routing Engine only)
specify whether to create more than one delivery, ship-for-pickup, or pickup order using the same order number and line number
specify whether to subtract the quantities on orders in certain statuses in determining the available quantity for a product location (Routing Engine only)
create a default vendor system so that you can create vendors to fulfill drop ship orders (Supplier Direct Fulfillment module only)
create a default Store Connect system so that you can fulfill orders through the Store Connect module
set configuration options for integration with Oracle Retail Integration Cloud Service (RICS) for order communication with Oracle Retail Merchandising Foundation Cloud Service (RMFCS), as well as Oracle Retail Store Inventory Management (SIM) and Enterprise Inventory Cloud Service (EICS)
set configuration options for integration with Omnichannel Cloud Data Service (OCDS) or Merchandising Omni Services to import locations, products, system products, and product locations

System relationships: See Organization, System, and Location for an overview of the data hierarchy in Order Orchestration, including products.

First system for an organization is flagged as the default: The Organization Default flag is selected when you create the first system for an organization, and the flag cannot be unselected at this time. To designate a different system as the default, you need to create another system and flag that system as the default; this unflags the first system.

How to display this screen:

Create a new system at the Systems screen

Note:
If you click Cancel after advancing to the System screen, the system is not created.
Click the edit icon () for an existing system code at the Systems screen

Note:

Only users with Systems authority can display this screen. See Roles for more information.
If the System screen was already open in another tab when you clicked the edit icon, you advance to this screen with the previously-selected system displayed.

In this topic:

Options at this screen

Option	Procedure
Flag a system as the organization default	Select the Organization Default flag and click Save. When you select this flag for a system, it clears the flag for the system that was previously the organization default. See the description of the Organization Default flag for background. Note: The system flagged as the Vendor Default should not be the default system for the organization.
Flag a system as the vendor default for the organization so that you can create vendors for the organization (Supplier Direct Fulfillment module only)	Select the Vendor Default flag and click Save. An organization can have only one vendor default system. Once you flag a system as the vendor default for an organization, you cannot change the vendor default assignment to a different system. Note: The system flagged as the Vendor Default should not be the default system for the organization. It is not necessary to specify any additional information for the vendor default system besides the organization, name, and this flag.
Configure a system for a RESTful web service connection for interactive inventory updates (URL) (Routing Engine only)	At the Inventory tab: Select the Online flag. Select the Inventory Qty Export flag. Select a Track Fulfilled Quantity setting to indicate whether to track the fulfilled quantity for a product location when you ship a delivery order (status is fulfilled), transfer a ship-for-pickup order (status is intransit), or when a pickup order is picked up (status is fulfilled) At the Inventory Service drop-down, select the External Service Code that identifies the external service to use for inventory updates, as configured through the External Services screen in Modern View. Required and used only if the Online flag is enabled at the Inventory tab. Click Save. See the Inventory tab for field details. Note: You must first define inventory services at the External Services screen in Modern View before you can select an inventory service at the Inventory tab. Order Administration Cloud Service integration: See Work with Web Service Authentication (WWSA) in the Order Administration Classic View online help for information on setting up authentication for the CWServiceIn web service. If you enter a user ID at the System screen, it must be in all capital letters. See Generic Web Services in the Order Administration Classic View online help for more information. For more information: See Additional Types of Import Processes (Other than RMFCS File Upload and OCDS or Merchandising Omni Services) in the overview for background, and see the RESTful Inventory Request and Response Messages chapter in the Web Services Guide on My Oracle Support (2953017.1) for details and more setup requirements. Also, see Additional Types of Import Processes (Other than RMFCS File Upload and OCDS or Merchandising Omni Services) for a discussion of interactive inventory updates from SIM.
Configure a system to require a status update before flagging an order as Polled (Routing Engine only)	At the Orders tab, select the Require Status Update flag. Enter the number of Polling Retries indicating how many times to include an order in the fulfillment response message to a fulfilling location before it is included in a notification email to the system administrator. You can enter any number from 1 to 99. Optionally, enter one or more email addresses in the System Ops Email field to receive the Polling Status Email. If you enter multiple email addresses, separate each with a semicolon (;). Order Orchestration verifies that the email addresses you enter are formatted correctly. Click Save. For more information: See Require Status Update for Assigned Orders? for a discussion. Note: This setting does not apply to Store Connect locations, which do not use the fulfillment request and response message.
Configure a system to subtract the total reserved quantity when calculating the effective available quantity of an item in a location (Routing Engine only)	You can configure a system so that, when Order Orchestration determines the current available quantity of an item in a location, it subtracts the total quantity currently reserved for orders from the reported available quantity in order to determine the effective available quantity. This calculation helps you prevent overcommitting the inventory for the location. Example: The available quantity reported by a system for a product location is 37; however, the location is assigned to fulfill an order for 4 units, and the order is in new_order status, indicating that the location has not yet polled for new orders and been notified of this order assignment. As a result, the effective available quantity is actually 33 (37-4). You can configure the system to consider order lines in new_order status as reserved, and subtract the total quantity of order lines in this status from the reported available quantity to determine the effective available quantity for a fulfilling location. To configure the system for reserved quantity calculation: At the Reservation tab, select the Include Reserved flag to make the Reserved Statuses flags available for selection. Select each status that should be considered reserved, indicating that order lines in this status should be subtracted from the available quantity to avoid overcommitting the inventory. Click Save. The screen displays a message indicating that it is updating the reserved quantities based on your selection. The number of product locations affected by the update determines how long this calculation takes to complete. Processing the update does not affect any existing orders that are already assigned to a location for fulfillment. For example, an order is currently assigned to a location whose on-hand quantity of an item is 5. After processing the update, the on-hand quantity of the item is now -1. However, the order remains assigned to the location and is not automatically rejected. For more information: See Calculating the Available to Promise Quantity for an overview.
Prevent the Routing Engine from assigning delivery orders to another location in the originating system (Routing Engine only)	You can configure a system so that, when a delivery order originates in a location within that system, the Routing Engine does not assign the order to another location that is also within the system. Example: System A includes locations DC1 and DC2, both distribution centers for the same enterprise sharing the same order database. When DC1 submits a delivery order, you do not want that order assigned to DC2. Note: This setting also prevents the locate items response from including locations within the system submitting the request. To prevent order assignment to a location within the system: At the Orders tab, select the Disallow shopping within same system flag. Click Save. For more information: See the Disallow shopping within same system flag.
Flag a system as the Store Connect default (Store Connect module only)	Select the Store Connect Default flag. Use the Reservation tab to specify the statuses to include in the reserved quantity for each Store Connect location. Typically, the reserved statuses are New Order, Accepted, Picked, and Polled. Click Save. About the Store Connect system: Locations associated with the Store Connect system are eligible for assignment to store associates, who can log into the Store Connect module to work with orders assigned to these locations. Orders assigned to these locations are ordinarily updated by store associates working through the Store Connect screens rather than through XML messages. Store Connect locations do not poll for newly assigned orders; instead, a background job updates new orders to polled status, making the orders available for store associates to work with, based on your settings at the Store Connect Preferences screen. Order Orchestration generates email notifications to store locations associated with this system when new orders are ready for processing. You can import barcodes from RMFCS for this system. See Importing UPC Barcodes through File Storage API for background. For more information: See the Store Connect Overview for background. Note: Once you create any locations for the Store Connect system, you cannot change the setting of this flag for the Store Connect system or for any other systems in the organization.
Configure communication with Oracle Retail Integration Cloud Service (RICS) for order information Required and used only if the Online flag is selected at the RICS Integration tab.	Select the RICS Integration tab. Use this tab to specify settings for communication with Oracle Retail Integration Cloud Service (RICS) to communicate order information between Order Orchestration and Oracle Retail Merchandising Foundation Cloud Service (RMFCS), as well as Oracle Retail Store Inventory Management (SIM) or Enterprise Inventory Cloud Service (EICS). Note: You must first define orders data services at the External Services screen in Modern View before you can select an orders service at this tab. For more information: See the RICS Integration tab.
Configure communication with Omnichannel Cloud Data Service (OCDS) or Merchandising Omni Services for location, product, system product, item image URL, barcode, and product location imports	Select the OCDS Integration tab. Use this tab to select a Foundation Data Service to use for communication with Omnichannel Cloud Data Service (OCDS) or Merchandising Omni Services to obtain location, product, system product, and product location information, as well as selecting a Default Store Location Type and a Default Warehouse Location Type. The Default Store Location Type and Default Warehouse Location Type fields will be required if an External Service is selected in the Foundation Data Service dropdown. Note: You must first define foundation data services at the External Services screen in Modern View before you can select foundation services at this tab. For more information: See the OCDS Integration tab.

Configuring System Connections for Supported Integrations (Routing Engine)

See Importing Items/Products, Inventory, Barcodes, Images, and Locations into the Database for an overview, and see the Schedule Jobs screen for additional required setup. The steps to complete this screen are listed under Options at this screen.

Also, see:

Configure a system for a RESTful web service connection for interactive inventory updates (URL) for information on how to integrate with Order Administration System for interactive inventory updates, including SIM or EICS.
Configure communication with Oracle Retail Integration Cloud Service (RICS) for order information.
Configure communication with Omnichannel Cloud Data Service for location, product, system product, and product location imports.

Order Administration Setup for Polling

If the Routing Engine sends orders to Order Administration for fulfillment, your setup related to requiring status updates should be consistent at the System screen in Order Orchestration and for the related system control value in Order Administration:

Setup	Status Update Required	No Status Update Required
Require Status Update at the System screen in Order Orchestration:	selected; also, complete the Polling Retries and System Ops Email fields	unselected
Re-polling for Orders Brokered to OACS or Re-polling for Orders Brokered to OACS system control value in Order Administration (labeled Re-polling at the Order Broker Values(K15) screen):	selected	unselected

For more information: See Require Status Update for Assigned Orders? for a discussion.

Fields at this screen

Update any of the fields described below and click Save, or click Cancel to return to the Systems screen without making any changes. See the Fields at this screen for more information.

Note:

If you are creating a new system, clicking Cancel prevents the creation.

Field	Description
Organization	See organization.
System	See system. The system code can be 1 to 10 positions in length, can include special characters, and must be unique in Order Orchestration. Required if you are creating a system; otherwise, display-only. Order Administration integration: The code representing the Order Administration system must match the setting of the OROB System (K50) system control value. However, names for systems do not need to be the same as the Order Administration company descriptions.
System fields
Name	The Name of a system. System names can be 1 to 40 positions in length and can include special characters. Required.
Organization Default	Select this check box to flag the system as the default system for the organization. Products in Order Orchestration can have relationships with every integrated system, but they are defined by the default system. You should load the Order Orchestration database with the default system’s products first, and then create system products for each additional integrated system. An organization can have only one default system. First system created: The Organization Default flag is selected when you create the first system for an organization, and the flag cannot be unselected at this time. To designate a different system as the default, you need to create another system and flag that system as the default; this unflags the first system. Note: The system flagged as the Vendor Default should not be the default system for the organization.
Vendor Default	Select this checkbox to flag the system as the vendor default for the organization. A vendor default system is required before you can create any vendors for the organization. An organization can have only one vendor default system. When you select this flag for a system, it clears the flag for the system that was previously the vendor default. Note: The system flagged as the Vendor Default should not be the default system for the organization. The vendor system cannot originate sales orders or purchase orders. It is not necessary to specify any additional information for the vendor default system besides the organization, name, and this flag. Used for the Supplier Direct Fulfillment module only. Available if Use Vendor Portal is selected at the Tenant screen.
Store Connect Default	Select this checkbox to flag the system as the Store Connect system. About the Store Connect system: Locations associated with the Store Connect system are eligible for assignment to store associates, who can log into the Store Connect module to work with orders assigned to these locations. Delivery and pickup orders assigned to these locations are ordinarily updated by store associates working through the Store Connect screens rather than through XML messages. You use the Store Connect Preferences screen to set up preferences related strictly to Store Connect, as opposed to the general Routing Engine preferences you set up at the Preferences screen. Store Connect locations do not poll for newly assigned delivery or pickup orders; instead, a background job updates new orders to polled status, making the orders available for store associates to work with. Your settings at the Store Connect Preferences screen control when the orders are updated to polled status. Order Orchestration generates an email notification to the store location when new delivery or pickup orders are polled. Optionally, Order Orchestration generates pickup-ready notification emails to customers for pickup orders or shipment notification emails for shipped delivery orders. The Store Connect system cannot originate orders. You can import barcodes from RMFCS for this system. See Importing UPC Barcodes through File Storage API for background. For more information: See the Store Connect Overview for background. Note: Once you create any locations for the Store Connect system, you cannot change the setting of this flag for the Store Connect system or for any other systems in the organization. Used for the Store Connect module only. Available if Use Store Connect is selected at the Tenant-Admin screen.
Inventory tab	Use this tab to configure a system for a RESTful web service connection for interactive inventory updates (URL). Available only with the Routing Engine module. Note that you must first use the External Services screen in Modern View to define Inventory external services before you can select them at this tab. Inventory integration conversion: When you upgrade from Order Broker to Order Orchestration, the previous settings from the Inventory tab are used to create an Inventory record at the External Services screen, with the following exceptions: Inventory services: Set to the previous settings from the Inventory tab at the System screen with the following exceptions: External service code: Set to INVENTORY, appended with an incremental number, such as INVENTORY1 and INVENTORY2. External service type: Set to Inventory. Inventory service: Set to SIOCS Integration if the Connection Type was set to SIM; otherwise, set to Standard Inventory Service if the Connection Type was set to URL. Description: Set to SIOCS Integration or StandardInventoryService for SYS DESCRIPTION, based on the selected Connection Type, and where SYS is the system code, and DESCRIPTION is the description of the organization. Note: The 23.2.301.0 release of Order Administration (formerly Order Management System) does not support basic authentication for inbound messages. OAuth is required. Optionally, you can delete a migrated record in order to assign a different code, since the external service code itself cannot be changed. After using the External Services screen and windows to review and verify each migrated service, you need to use the System screen in Classic View to update the external services at the related tabs and verify that the information displayed there is also correct.
Online	Select this check box to indicate that this is an online system, meaning that Order Orchestration requests interactive inventory updates when it receives a locate items request, product availability search request, or needs to select a fulfilling location for a delivery order, either as part of initial order creation or through the status update process. If the Online checkbox is selected, you need to select an Inventory Service at this tab. About online processing: If Order Orchestration is unable to retrieve an interactive update from the system, it uses the available quantity stored in the Order Orchestration database (offline inventory). This available quantity is updated either through a recent online inventory inquiry, or through the most recent inventory download from the system. Typically, inventory levels in the Order Orchestration database are updated daily, or whenever scheduled by your systems administrator. See Example: Searching for Items for more information. Offline system: If the check box is not selected, this is on offline system, meaning that Order Orchestration does not request interactive inventory updates; instead, it relies on the available quantity stored in the Order Orchestration database (offline inventory). Typically, inventory levels in the Order Orchestration database are updated daily, or whenever scheduled by your system administrator. Changing to offline: You can temporarily change a system from online to offline if you know that communication with the system will not be available and you would like to avoid unnecessary processing time for locate items requests. When you clear the checkbox, the Inventory Service information is retained so that you will not need to specify it again if the system goes back online. Changing to online: When you change a system to online, you need to specify the URL and other inventory service information, described below. For more information: See Configure a system for a RESTful web service connection for interactive inventory updates (URL) for setup steps.
Inventory Qty Export	Indicates whether to include updated product locations from this system in the pipe-delimited file generated when you run the inventory quantity export for any system in the organization. This setting does not control whether a background job monitors changes that could affect probability rules calculations. See Inventory Quantity Export for information on running the export.
Track Fulfilled Quantity	Indicates whether to track the fulfilled quantity for a product location when you ship a delivery order (status is fulfilled), transfer a ship-for-pickup order (status is intransit), or when a pickup order is picked up (status is fulfilled): Do Not Track Fulfilled: Do not update a product location’s fulfilled quantity when a delivery or pickup order is fulfilled, or when a ship-for-pickup order is intransit. Used when? You might use this setting for a system that tracks its own inventory levels, tracks order fulfillments through status inquiry requests, and keeps Order Orchestration product locations in sync through interactive inventory updates. In this case, you would not typically use the Fulfilled Inventory Export. Note: If you change to Do Not Track Fulfilled from another setting, the fulfilled quantities for product locations within the system are reset to 0. Reset During Inventory Export: Update a product location’s fulfilled quantity when a delivery or pickup order is fulfilled, or when a ship-for-pickup order is intransit. When the Fulfilled Inventory Export runs, reset the product location’s fulfilled quantity to 0, and subtract the fulfilled quantity from the product location’s available quantity. These updates leave the product location’s available to promise quantity unchanged (available to promise = available quantity - reserved quantity + fulfilled quantity). Used when? You might use this setting for a system such as Store Connect, that typically relies on Order Orchestration to manage order activity, and uses the fulfilled inventory export for updates on fulfilled orders. Tracking the fulfilled quantity enables you to avoid overstating the actual quantity available for orders. Note: If you select this setting, you should have at least one day selected for the Fulfilled Inventory Export. Reset During Product Import: Update a product location’s fulfilled quantity when a delivery or pickup order is fulfilled, or when a ship-for-pickup order is intransit. When the import process runs, reset the product location’s fulfilled quantity to 0. Do not subtract the fulfilled quantity from the available quantity; instead, update the product location’s inventory information with the current information received in the import, if any. If the product location is not included in the import, the fulfilled quantity is still reset to 0. Note: The fulfilled quantity is not reset through the Incremental Inventory Import, only through the Product Import. Used when? You might use this setting for a system that periodically updates inventory levels based on activity outside of Order Orchestration and also receives information on fulfilled orders through status update requests, but uses the fulfilled quantity to calculate a more accurate available to promise quantity in the interval between product imports. Note: The above settings are available for selection regardless of whether the system is flagged as Online. For more information: See below for examples of the calculations for each setting. Examples of fulfilled quantity updates Track Fulfilled Quantity set to Do Not Track Fulfilled: A product location has: Available: 10 Reserved: 0 Fulfilled: 0 Available to Promise: 10 The location is assigned a new delivery order for a quantity of 2: Available: 10 Reserved: 2 Fulfilled: 0 Available to Promise: 8 The order is fulfilled: Available: 10 Reserved: 0 Fulfilled: 0 Available to Promise: 10 The next time the system updates the product location through a periodic product and inventory import or an interactive inventory update, it resets the available quantity to the current level. Track Fulfilled Quantity set to Reset During Inventory Export: A product location has: Available: 10 Reserved: 0 Fulfilled: 0 Available to Promise: 10 The location is assigned a new delivery order for a quantity of 2: Available: 10 Reserved: 2 Fulfilled: 0 Available to Promise: 8 The order is fulfilled: Available: 10 Reserved: 0 Fulfilled: 2 Available to Promise: 8 The Fulfilled Inventory Export runs: Available: 8 Reserved: 0 Fulfilled: 0 Available to Promise: 8 The next time the system updates the product location through a periodic product and inventory import, it resets the available quantity to the current level if it is different. Track Fulfilled Quantity set to Reset During Product Import: A product location has: Available: 10 Reserved: 0 Fulfilled: 0 Available to Promise: 10 The location is assigned a new delivery order for a quantity of 2: Available: 10 Reserved: 2 Fulfilled: 0 Available to Promise: 8 The order is fulfilled: Available: 10 Reserved: 0 Fulfilled: 2 Available to Promise: 8 If the Fulfilled Inventory Export runs, there is no update. The product and inventory import runs, passing an available quantity of 3 as a result of additional activity within the system: Available: 3 Reserved: 0 Fulfilled: 0 Available to Promise: 3 The fulfilled quantity is not subtracted from the available quantity, since the product and inventory import provides the most current inventory level based on all activity.
Inventory Service	Select the inventory service to use for an Online system. Inventory services are configured at the External Services screen in Modern View. Required if the Online flag is selected. Note that the 23.2.301.0 release of Order Administration (formerly Order Management System) or higher does not support basic authentication for inbound messages. Leave this field set to None for an offline system. For more information: See Importing Items/Products, Inventory, Barcodes, Images, and Locations into the Database in the overview.
Orders tab	Use these fields to control: Whether the Routing Engine can assign an order to another location within the system Whether the Routing Engine continues to include a new order in the fulfillments response to the assigned fulfilling location until the location sends a status update. See Require Status Update for Assigned Orders? for a discussion. Available only with the Routing Engine module.
Order Orchestration Shopping: Disallow shopping within same system	Indicates whether the Routing Engine should assign a ship-for-pickup or delivery order to another location in the same system. If the Disallow shopping within same system flag is: Selected: The Routing Engine does not assign an order to another location within the same system that submitted the order. The order can be assigned to a location in a different system, based on the rules set up at the Preferences screen; otherwise, it is unfulfillable. Also, the locate items response does not include any locations within the system submitting the request, unless the requested location is within the same system. Note: If the submit order message specifies a location within the same system, the order is created in the specified location regardless of the setting of this flag. Unselected (default): The Routing Engine can assign the order to another location within the system, based on the rules set up at the Preferences screen. Also, the locate items response can include locations within the system submitting the request. When to disallow shopping? You might use this field to disallow shopping if your order management system, such as Order Administration System, supports multiple warehouses and each warehouse is represented as a separate location in Order Orchestration.
Order Fulfillment	Order Administration System setup: If you send orders to Order Administration warehouses for fulfillment, check Order Administration Setup for Polling for more information.
Require Status Update	Fulfillment response message: Indicates whether to automatically flag an order or line as Polled when it is included in the fulfillment response message, or to continue including it in the fulfillments response message until the assigned location sends a status update message accepting the order: Selected = Order Orchestration continues to send an order or line in the fulfillments response message when the assigned fulfilling location polls for new orders until the order is flagged as polled: The order is flagged as polled when the location sends a status update message to with a status of polled or accepted. Order Orchestration uses the order’s or line’s Poll Count field to track the number of times it has been included in the fulfillments response message. When the order’s or line’s Poll Count exceeds the Polling Retries specified for the system, Order Orchestration includes the order in the Polling Status Email sent to the System Ops Email specified for the system. Each item’s current Poll Count is indicated on the Order screen. Possible risk: With this setting, there is a potential risk that an order could be created twice in the integrating system if, for example, that system does not complete creating the new orders in the fulfillments response message and sending the status update messages for them before it sends a new fulfillments request message to Order Orchestration. Unselected (default) = Flag the order or line as Polled when it is included in a fulfillment response message to the location; do not include the order or line more than once. Possible risk: With this setting, there is a potential risk that an order might not be created in the integrating system if, for example, the integrating system does not receive the fulfillments response, or fails to create all orders in the response. Note: This setting does not apply to Store Connect locations, which do not use the fulfillment request and response message. Also, it does not apply to orders fulfilled through Order Fulfillment through RICS Integration. Intransit response message: If the Require Status Update flag is: Selected = the Routing Engine continues to include a ship-for-pickup order in the intransit response message to a pickup location or system, until the location or system sends a status update indicating that the order or order line is intransit polled. Unselected = the Routing Engine includes each ship-for-pickup order or line just once in the intransit response message to a pickup location, and then changes the status to intransit polled. Polling count: The polling count for the order line is initially set to 0 when it is in transit. Each time the Routing Engine includes an order or line in the intransit response message, it increases the order line’s Poll Count. Unlike the rules for the fulfillment response, the rules for the intransit response do not include generating the Polling Status Email when an in transit order exceeds the Polling Retries specified for the system. Note: The setting of this flag does not affect Order Fulfillment through RICS Integration.
Use Requesting System Line Number in Status Update	Controls how the `line_no` in the status update request identifies the order line to update when the Allow Split Line preference is selected but the Allow Partial Updates preference is not. Applies to specific configuration only: The `line_no` is interpreted as the originating system's line number ONLY if: the Allow Split Order and Allow Split Line preferences are selected, AND the Allow Partial Updates preference is unselected, AND the request message is from the originating location for the order, AND this flag is selected Otherwise, the `line_no` identifies the current line number in Order Orchestration. Example: The configuration described above is in place. The originating location submits a status update request to cancel line 1, referencing its own line number rather than the Order Orchestration line number. Line 1 originated with 4 units, but has since split across 2 locations, resulting in lines 1 and 2 in Order Orchestration for 2 units each, with an originating line number of 1. The result is that the update request cancels both order lines. Otherwise, if the configuration described above is not in place, or if the originating location did not submit the status request, only the first of the two lines is canceled. When the organization has Allow Split Line selected and Allow Partial Updates unselected, this flag should be: selected for a system such as Order Administration, which includes its line number in the status update request unselected (default) for a system such as Xstore, which includes the Order Orchestration line number in the status update request Note: When the Allow Partial Updates preference is selected, the requesting system needs to first obtain the current line numbers in Order Orchestration before submitting a status update.
Polling Retries	The number of times to include the order or line in a fulfillment response message before including the order in the Polling Status Email. If the Require Status Update flag is: Selected: You can enter any number from 1 to 99 Unselected: Enter 0 Required. Order Orchestration tracks the number of retries in the Poll Count field at the Order screen. Note: This setting does not apply to Store Connect locations, which do not use the fulfillment request and response message.
System Ops Email	The email address where Order Orchestration should send the notification email listing orders that have not been acknowledged after the number of Polling Retries has been reached. If you enter multiple email addresses, separate each with a semicolon (;). Order Orchestration verifies that the email address you enter are formatted correctly. Optional, even if the Require Status Update flag is selected.
Reservation tab	Use this tab to indicate the order or order line statuses to subtract from a location’s available quantity in order to determine the quantity that is actually available to fulfill new orders. Typically, the reserved statuses for a Store Connect system are New Order, Accepted, Picked, and Polled. Inventory quantity export: Changes to the reserved statuses at this tab do not trigger probability rule calculation for the inventory quantity web service, as described under Tracking Probability Rules for Incremental Updates on Inventory Availability; however, these changes do factor into the calculation for the Full Overlay Inventory Quantity Extract File. See Probability Rules Update and Incremental Quantity Web Service for background. Available only with the Routing Engine module.
Include Reserved	Select this check box to have Order Orchestration subtract reserved order lines from the reported available quantity for a product location. This calculation helps you prevent overcommitting inventory when assigning orders, responding to locate items requests, or evaluating selected fulfilling locations. If this check box is selected, the Reserved Statuses listed below are available for selection. Once you select any statuses and click update, Order Orchestration calculates the total reserved quantity for each product location in the system currently assigned to any selected status. For more information: See Calculating the Available to Promise Quantity for an overview.
Reserved Statuses	These statuses are available for selection if you select the Include Reserved checkbox. Select each status that indicates that inventory is reserved for an open order line and should not be assigned to new orders or listed in the LocateItems response message. For more information: See Calculating the Available to Promise Quantity for an overview. Possible statuses are: New Order Accepted Canceled Picked Fulfilled Unfulfillable Polled Posted Processed Verified Intransit Intransit Polled Received Partially Fulfilled Typically, reserved statuses for your Store Connect system are New_Order, Accepted, Polled, and Picked.
RICS Integration tab	Use this tab to set up integration with the Oracle Retail Integration Cloud Service (RICS) to communicate order information between Order Orchestration and: Oracle Retail Merchandising Foundation Cloud Service (RMFCS), as well as Oracle Retail Store Inventory Management (SIM) or Enterprise Inventory Cloud Service (EICS). Note that you must first use the External Services screen in Modern View to define Orders external services before you can select them at this tab. For more information: See Order Fulfillment through RICS Integration for background. RICS integration conversion: When you upgrade from Order Broker to Order Orchestration, the previous settings from the RICS Integration tab are used to create an Orders record at the External Services screen, with the following exceptions: External service code: Set to RICS, appended with an incremental number, such as RICS1 and RICS2. External service type: Set to Orders. Description: Set to RICS Orders Service for ORG -SYS DESCRIPTION, where ORG is the organization code, SYS is the system code, and DESCRIPTION is the description of the organization. Note that existing RICS records are migrated only if they have URLs defined. Note: Optionally, you can delete a migrated record in order to assign a different code, since the external service code itself cannot be changed. After using the External Services screen and windows to review and verify each migrated service, you need to use the System screen in Classic View to update the external services at the related tabs and verify that the information displayed there is also correct.
Online	Select this check box to indicate that this is a system is: Oracle Retail Merchandising Foundation Cloud Service (RMFCS), or Oracle Retail Store Inventory Management (SIM); or Enterprise Inventory Cloud Service (EICS) Order Orchestration integrates with these systems through the Oracle Retail Integration Cloud Service (RICS). When you select this check box, you need to specify the Outbound Orders Service information, described below. For more information: See Order Fulfillment through RICS Integration for background.
Send Release Reservation Inventory Message	Select this check box to send an order cancellation message through RICS when an order is rejected or canceled.
Hold Under Review Orders	Select this check box to post an order through RICS to RMFCS or SIM only when the order is not currently held for review, based on its Under Review flag. When you clear the Under Review flag for the order, it is then posted automatically. See Order Fulfillment through RICS Integration for background. Note: This flag should be selected.
Orders Service	Select the orders service to use for an Online system. Orders services are configured at the External Services screen in Modern View. Leave this field set to None if the system does not use the orders integration.
OCDS Integration Import tab	Use this tab to set up integration with the Omnichannel Cloud Data Service (OCDS) or Merchandising Omni Services to import warehouse or store location, product, and product location information from Oracle Retail Merchandising Foundation Cloud Service (RMFCS). The product image import is also supported for the default system of the organization. When you use ODCS or Merchandising Omni Services for these imports, Order Orchestration generates web service requests for this information rather than processing an upload file. Note that you use the External Services screen in Modern View to define Foundation Data services. OCDS integration conversion: When you upgrade from Order Broker to Order Orchestration, the previous settings from the OCDS Integration tab are used to create an Orders record at the External Services screen, with the following exceptions: External service code: Set to OCDS, appended with an incremental number, such as OCDS1 and OCDS2. External service type: Set to Foundation Data. Description: Set to FOUNDATION DATA forSYS DESCRIPTION, where SYS is the system code, and DESCRIPTION is the description of the organization. Note that existing OCDS records are migrated only if they have URLs defined. Note: Optionally, you can delete a migrated record in order to assign a different code, since the external service code itself cannot be changed. After using the External Services screen and windows to review and verify each migrated service, you need to use the System screen in Classic View to update the external services at the related tabs and verify that the information displayed there is also correct. For more information: See: OCDS or Merchandising Omni Services Imports and Importing Data from Merchandising Cloud Services (RMFCS) through the Omnichannel Cloud Data Service (OCDS) or Merchandising Omni Services for an overview and mapping details. Schedule Jobs screen for information on scheduling the imports or running them on demand.
Foundation Data Service	Select the foundation data service to use for an Online system. Foundation data services are configured at the External Services screen in Modern View. Leave this field set to None if the system does not use the foundation data integration.
Default Store Location Type	Select the code for a store location type to associate with the store locations imported through the Store Location URL. All location types in your organization with a Category of Store are available for selection. Required if the Active flag is selected for store locations and if an external service is selected at the Foundation Data Service drop-down. Note: If you change this setting after initially importing store locations, existing store location records are not updated.
Default Warehouse Location Type	Select the code for a warehouse location type to associate with the virtual warehouse locations imported through the Warehouse Location URL. All location types in your organization with a Category of Warehouse are available for selection. Required if the Active flag is selected for warehouse locations and if an external service is selected at the Foundation Data Service drop-down. Note: If you change this setting after initially importing warehouse locations, existing warehouse location records are not updated.