Purpose: Use the Order Inquiry screen to search for and review Order Broker orders sent from an integrated system, such as Xstore or Order Management System, for fulfillment by another integrated system.
Used for the Routing Engine module.
How to display this screen: Select Order Inquiry from the Home Screen or the Orders Menu.
Note: Available if Use Routing Engine is selected at the Tenant screen.This screen is accessible to users with Order Inquiry authority. See the Role Wizard for more information.
In this topic:
• How to display orders on this screen
How to display orders on this screen
When you first advance to the Order Inquiry screen, the organization associated with your Default Shipping System is selected by default, but no orders are displayed. Click Search to retrieve the last 50 orders in your organization, or select additional search criteria.
Sort order: The orders are sorted based on Request ID. The Request ID is a unique number assigned by the Routing Engine when an integrated system assigns an order or order line to the Order Broker for fulfillment.
How to view order updates? Click Search to refresh the screen.
Note: This screen functions only after you have created at least one order in Order Broker.
Customer name anonymized? If the customer data on an order has been anonymized (deleted and replaced with asterisks), the customer name is displayed as:
*** ***
***
In this case, searching by customer name or company name is not supported.
An order is eligible to be anonymized only if it is no longer open.
See Anonymizing Data for background.
Option |
Procedure |
---|---|
When you first advance to this screen, no orders are displayed and the organization associated with your Default Shipping System is selected by default. Use any combination of the fields at the top of the screen to restrict the search results. Case? All the enterable fields on this screen are case-insensitive for searching; for example, an entry of a or A matches a name of Adams. |
|
review the reasons why the Routing Engine eliminated individual locations from sourcing the order |
Click the Trace Log icon ( Note: • The Routing Engine traces shopping logic only if the Trace Shopping Logic field is set to Detailed at the Event Logging screen. Typically, you would select to trace shopping logic only to research why certain locations are or aren’t selected to fulfill orders. • These history records are retained only for the number of Trace Log History days specified at the Tenant-Admin screen; after that number of days, the daily cleanup job automatically deletes the records. • If the Trace Shopping Logic screen is already open in another tab, you advance to that screen, where the previously-selected order is displayed. |
Click the Edit/Display icon ( Note: If the Order screen is already open in another tab, you advance to that screen, where the previously-selected order is displayed. |
Fields |
Description |
---|---|
Search fields Case? All the enterable fields on this screen support case-insensitive searching; for example, an entry of a or A matches a name of Adams. |
|
Organization |
See organization. Defaults from the organization associated with the Default Shipping System from your user profile, but you can override this default. |
A unique number to identify the order within Order Broker. Assigned by the Routing Engine when it creates the order. Depending on your integration and the type of order, each individual order line might create a separate order in the Order Broker, or might be included with other lines from the originating order in the external system. Note: The numbers might not always be in sequential order. |
|
The number or code identifying the order in the originating system. From the order id passed in the submit order message. Can be up to 30 positions. Case: If the originating system includes any lowercase letters in the order number, Order Broker converts them to uppercase when creating the order. Not case-sensitive for searching; an entry of A or a matches an order number of A12345. |
|
Placed Location |
The location where the order originated; see placed location for a discussion. |
Sourced Location |
The location supplying the inventory for a ship-for-pickup order. Displayed only if ship-for-pickup is enabled; see Enable Ship-For-Pickup? for background. Multiple locations? If an order includes lines assigned to multiple sourcing locations, searching based on a sourcing location produces a list of orders that include lines assigned to the specified location. |
Pickup Location |
The location where the customer picks up a pickup order or ship-for-pickup order. Displayed only if ship-for-pickup is enabled; see Enable Ship-For-Pickup? for background. |
Fulfilling Location |
See fulfilling location. Displayed only if the organization supports Retail Pickup and Ship to Store orders rather than Ship-For-Pickup orders; see Enable Ship-For-Pickup? for background. Multiple locations? If an order includes lines assigned to multiple fulfilling locations, searching based on a fulfilling location produces a list of orders that include lines assigned to the specified location. |
The transaction date passed in the submit order message. Might not be the same as the date when the order was created. |
|
The order-level status, which can be different from the various line-level statuses if the Allow Split Order preference is selected. The list of available statuses varies, depend9ing on whether ship-for-pickup orders are enabled. See Order and Line Statuses. Under Review? The words Under Review follow the order status in parentheses if the order’s Under Review flag is selected. You might need to adjust the column widths to display these words. |
|
Possible order types are: • Delivery = The order is shipped to the customer from the fulfilling location. See Delivery Order for a discussion. • Pickup = The customer goes to the fulfilling location, where the merchandise is already in stock, to pick up the order, See Pickup Order for a discussion. • Retail Pickup = The customer wants to pick up in the store location where she or he places the order, but since the merchandise is not available there, it must first be shipped to the store from a fulfilling location. See Retail Pickup Order for a discussion. Displayed only if ship-for-pickup is not enabled; see Enable Ship-For-Pickup? for background. • Ship For Pickup = The customer wants to pick up the order in a store location, and the inventory can be sourced from a location that differs from the pickup location and the originating location. Displayed only if ship-for-pickup is enabled; see Enable Ship-For-Pickup? for background. • Ship To Store = The customer goes to the fulfilling location to pick up the order, after the merchandise is shipped to the store from the location that originated the order. This scenario is typical of an OMS-to-retail order. See Ship-to-Store Order for a discussion. Displayed only if ship-for-pickup is not enabled; see Enable Ship-For-Pickup? for background. |
|
Customer name anonymized? If the customer data on an order has been anonymized (deleted and replaced with asterisks), searching by the original company name, first name, or last name is not supported. See Anonymizing Data for background. |
|
Company Name |
The sold-to customer’s company name, if it was passed in the submit order message. Not case-sensitive for searching; an entry of A or a matches a company name of Acme. |
First Name |
The sold-to customer’s first name, if it was passed in the submit order message. Not case-sensitive for searching; an entry of A or a matches a first name of Alice. |
Last Name |
The sold-to customer’s last name, if it was passed in the submit order message. Not case-sensitive for searching; an entry of A or a matches a last name of Allen. |
The sold-to customer’s postal or zip code from the submit order message. Case: If the originating system includes any lowercase letters in the postal code, Order Broker converts them to uppercase when creating the order. Not case-sensitive for searching; an entry of A or a matches a postal code of A1A OB1. |
|
Result fields |
|
Request ID |
The screen sorts by Request ID. |
See Order Number. |
|
Customer |
The sold-to customer’s first and last name, followed by the customer’s company name. Based on the information passed in the submit order message for the customer. Customer name anonymized? If the customer data on an order has been anonymized (deleted and replaced with asterisks), the customer name is displayed as: *** *** *** See Anonymizing Data for background. |
Placed Location |
The location that originated the order. Displayed only if ship-for-pickup is enabled; see Enable Ship-For-Pickup? for background. |
Sourced Location |
The location supplying the inventory for the order. A location of Multiple is listed if Split Order is enabled and the order is split across sourcing locations. Displayed only if ship-for-pickup is enabled; see Enable Ship-For-Pickup? for background. |
Pickup Location |
The location where the customer picks up the order. Blank for a delivery order. Displayed only if ship-for-pickup is enabled; see Enable Ship-For-Pickup? for background. |
Locations |
The first line is the placed location, and the second line is the fulfilling location. The information varies depending on the type of order: Delivery order: • Placed: the location originating the order request. • Shipment: the location to ship the order to the customer. The Routing Engine selects the location to ship the order unless it is specified in the submit order message. A location of Multiple is listed if Split Order is enabled and the order is split across sourcing locations. Pickup order: • Placed: the location originating the order request. • Pickup: the location where the customer wants to pick up the order. The inventory is already on-hand in this location. Retail pickup order: • Placed / Pickup: the location originating the order request, and where the customer picks it up. • Sourced: the location that transfers the inventory to the placed (originating) location. The Routing Engine selects the location to source the order unless it is specified in the submit order message. A location of Multiple is listed if Split Order is enabled and the order is split across sourcing locations. Ship To Store order: • Sourced / placed: the location originating the order request, and which transfers the inventory to the fulfilling location. Typically, this is the call center or the web storefront. • Pickup: the location where the placed (originating) location is transferring the inventory and where the customer picks up the order. Both the location code and name are displayed for each location. Note: An integrated system might use a different term for the placed or fulfilling location. For example, in Order Management System the location where a ship-to-store order originates is designated as the fulfilling location, because it transfers the merchandise to the location where a customer will pick it up. Displayed only if ship-for-pickup is not enabled; see Enable Ship-For-Pickup? for background. For more information: See The Routing Engine for a discussion. |
Date Ordered |
The transaction date passed in the submit order message. Might not be the same as the date when the order was created. |
Order Status |
Under Review? If the order is currently flagged as Under Review, meaning that the fulfilling system needs to delay shipping or fulfilling the order, the message (Under Review) is listed next to the order status. Depending on your browser settings, you might need to broaden the column to read this message. See the Under Review field at the Order screen for more information. |
Order Type |
See Order Type. |
Postal Code |
The sold-to customer’s Postal Code or zip code. |
Trace Log |
Click the Trace Log icon ( Note: • The Routing Engine traces shopping logic only if the Trace Shopping Logic field is set to Detailed at the Event Logging screen. Typically, you would select to trace shopping logic only to research why certain locations are or aren’t selected to fulfill orders. • These history records are retained only for the number of Trace Log History days specified at the Tenant-Admin screen; after that number of days, the daily cleanup job automatically deletes the records. • If the Trace Shopping Logic screen is already open in another tab, you advance to that screen, where the previously-selected order is displayed. |
Edit |
Click the Edit/Display icon ( If the Order screen is already open in another tab, you advance to that screen, where the previously-selected order is displayed. |
________________________________
Copyright © 2021,
2022, Oracle and/or its affiliates. All rights reserved.
Legal Notices