Oracle Retail Order Broker Integration Overview

Oracle Retail Order Broker Integration Overview

Purpose: The integration between Oracle Retail Order Broker and Oracle Retail Order Management System enables you to share information on items’ availability and create orders across the enterprise, including:

• providing periodic item and inventory import from Oracle Retail Order Management System to Oracle Retail Order Broker

• providing real-time, on-demand inventory availability information for specific items from the Oracle Retail Order Management System warehouse to the point of sale or the web storefront, and vice versa

• using Oracle Retail Order Broker’s routing engine to automatically assign backordered items to store locations for fulfillment

• searching for store locations that stock a requested item so that the customer can pick up the item at the store

• using Oracle Retail Order Management System to fulfill retail pickup or delivery orders that originated in a retail store location

• creating ship-to-store orders in Oracle Retail Order Management System and shipping the merchandise to a retail store location for customer pickup

• creating store pickup orders so the customer can pick up the order at a retail store location where the merchandise is already in stock

Integrated systems: Oracle Retail Order Broker provides visibility into items and inventory across all integrated systems. Typically, you would integrate Oracle Retail Order Broker with Oracle Retail Order Management System and a POS system, such as Xstore.

Setting up the integration: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker).

Version compatibility: Release 5.0 of Oracle Retail Order Management System is compatible with release 5.0 or higher of Oracle Retail Order Broker. Integration with release 3.0 or 3.1 of Oracle Retail Order Broker is also supported, although features added since that release, such as the ability to send held orders to Oracle Retail Order Broker, are not available.

Integration with other releases of Oracle Retail Order Broker is not supported.

In this chapter:

• Oracle Retail Order Broker’s Product Import Process

• Item Availability Updates

• Brokered Backorder Integration with Oracle Retail Order Broker

• Retail Pickup and Delivery Orders from Oracle Retail Order Broker

• Ship-to-Store Orders

• Store Pickup Orders

• Merchandise Locator Searching

• Store Connect

Oracle Retail Order Broker’s Product Import Process

Overview: The Oracle Retail Order Broker product import process allows you to extract and import item and inventory information from Oracle Retail Order Management System to Oracle Retail Order Broker.

How does the import work? The following periodic functions allow you to generate output files to import into Oracle Retail Order Broker.

• The OBPROD OB Product Output File (program name PFR0127) periodic function allows you to generate a Product output file for import into Oracle Retail Order Broker. This file contains product information for a specified company. See Oracle Retail Order Broker Product Output File for details.

• The OBPRLOC OB Product Location Output File (program name PFR0128) periodic function allows you to generate a Product Location output file for import into Oracle Retail Order Broker. This file contains product location and availability information for a specified company. See Oracle Retail Order Broker Product Location Output File for details.

• The OBINCIN OB Incremental Inventory Output File (program name PFR0129) periodic function allows you to generate an Incremental Inventory output file for import into Oracle Retail Order Broker. This file contains inventory updates for a specified company. See Oracle Retail Order Broker Incremental Inventory Output File for details.

Only items and SKU’s whose OROB eligible flags are selected are eligible for extract. This flag is selected by default.

Required setup: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker).

For more information: See the Oracle Retail Order Broker online help and the Oracle Retail Order Broker Operations Guide.

Location of files: The OROB_DIRECTORY_PATH in Working with Cloud Properties (CPRP) defines the location on the application server where the system creates the output files. An example directory is /usr/local/tomcat01/OMSFiles/OROBData, where /usr/local/tomcat01 is the installed location of Oracle Retail Order Management System. Note: If the OROB_DIRECTORY_PATH is not valid or is blank, or the specified folder does not exist, the system does not create any output files and writes a message to the Application log.

Application log: The system writes any messages related to the Oracle Retail Order Broker product import process to the application log.

Scheduling the import or running it on demand:

• In Oracle Retail Order Management System, you can use the job scheduler to schedule when a periodic process runs. See Scheduling Jobs for instructions.

• In Oracle Retail Order Broker, you use the Schedule Import Process screen in Oracle Retail Order Broker to set up a schedule for importing item and inventory information from Oracle Retail Order Management System. You can also run the import on demand from this screen.

Before you can run the import, you need to complete the required setup in Oracle Retail Order Broker as well as the Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker).

Mapping the Oracle Retail Order Management System item and SKU code to the Oracle Retail Order Broker product or system product code:

• The Oracle Retail Order Management System item and SKU maps to the Oracle Retail Order Broker system product code. The system maps the full 12 positions for the item and the full 14 positions for the SKU; for example: SKU YELW SML WMNS.

• The setting of the OROB Product Code ID (K66) system control value defines which field in Oracle Retail Order Management System is used as the product code in Oracle Retail Order Broker. You can map the item and SKU, reference number, or UPC code to the product code.

Oracle Retail Order Broker Product Output File

Use the OBPROD OB Product Output File (program name PFR0127) periodic function to generate the Oracle Retail Order Broker Product Output file. This file contains product information for a specified company to import into Oracle Retail Order Broker. See Oracle Retail Order Broker’s Product Import Process for processing details.

Location of file: The OROB_DIRECTORY_PATH in Working with Cloud Properties (CPRP) defines the location on the application server where the system creates the output file.

Name of file: The system names the file PRODUCT_SYS.TXT, where SYS is the company code where you submitted the periodic function.

Sample file:

The system includes empty pipes in the file for data that is not included.

Field	Description
system_cd	The company code where the periodic function was submitted. Maps to the Oracle Retail Order Broker system code.
department	The code and description of the long SKU department assigned to the item. Maps to the Oracle Retail Order Broker Department field if the Oracle Retail Order Management System company is the default system.
class	The code and description of the long SKU class assigned to the item. Maps to the Oracle Retail Order Broker Class field if the Oracle Retail Order Management System company is the default system.
subclass	The code and description of the long SKU division assigned to the item. Maps to the Oracle Retail Order Broker Category field if the Oracle Retail Order Management System company is the default system. Derived from the long SKU department.
system_product	The item and SKU. The system includes the full 12 positions for the item and the full 14 positions for the SKU; for example: SKU YELW SML WMNS.
product_cd	The item’s product code in Oracle Retail Order Broker. The setting of the OROB Product Code ID (K66) system control value defines which field in Oracle Retail Order Management System is used as the product code in Oracle Retail Order Broker. Note: When mapping the item and SKU, the system includes the full 12 positions for the item and the full 14 positions for the SKU; for example: SKU YELW SML WMNS.
product_description	A description of the item. Maps to the product description if the Oracle Retail Order Management System company is the default system.
master_style	The item code if the item contains SKUs. Maps to the Oracle Retail Order Broker master style code if the item has SKU’s.

Oracle Retail Order Broker Product Location Output File

Use the OBPRLOC OB Product Location Output File (program name PFR0128) periodic function to generate the Oracle Retail Order Broker Product Location Output file. This file contains product location, attribute, and availability information for a specified company to import into Oracle Retail Order Broker. See Oracle Retail Order Broker’s Product Import Process for processing details.

Location of file: The OROB_DIRECTORY_PATH in Working with Cloud Properties (CPRP) defines the location on the application server where the system creates the output file.

Name of file: The system names the file PRODUCT_LOCATION_SYS.TXT, where SYS is the company code where you submitted the periodic function.

Note: It is important to use Purchase Order Layering to update the PO Layering table before running the import; otherwise, the Next PO date and Next PO quantity sent to Oracle Retail Order Broker will not be up to date.

Send inventory by warehouse? You can either map inventory information for individual item warehouses to the related locations in Oracle Retail Order Broker, or aggregate item warehouse totals across all allocatable warehouses for an item or SKU into a default location representing your distribution center.

If the Send Inventory by Warehouse to OROB (L06) system control value is:

• selected: the import process includes each Item Warehouse record for items flagged OROB eligible if the warehouse has an OROB location specified and the warehouse is flagged as Allocatable. Any purchase order information is related to that warehouse only.

• unselected: the import process sends the total available quantity for the item in all allocatable warehouses, regardless of whether the warehouse has an OROB location specified, and updates the product location in Oracle Retail Order Broker using the OROB Default Location (K51). Any purchase order information is the earliest eligible purchase order across all allocatable warehouses.

Example:

Item AB100 is stocked in:

• Warehouse 1 (allocatable, OROB location = DC1)

- Available quantity = 100

- Next purchase order date = 6/30

- Next purchase order quantity = 15

• Warehouse 2 (allocatable, OROB location = S2)

- Available quantity = -10

- No open purchase orders

• Warehouse 3 (allocatable, no OROB location)

- Available quantity = 5

- Next purchase order date = 6/28

- Next purchase order quantity = 50

OROB Default Location (K51) is set to DC.

Results when sending by warehouse:

If Send Inventory by Warehouse to OROB (L06) is selected, update:

OROB location DC1:

• Available quantity = 100

• Next purchase order date = 6/30

• Next purchase order quantity = 15

OROB location S2:

• Available quantity = -10

• No purchase order information is included

Warehouse 3 is not included because there is no OROB location.

Results when sending sum:

If Send Inventory by Warehouse to OROB (L06) is unselected, update:

OROB location DC:

• Available quantity = 95 (warehouse 1 + warehouse 2 + warehouse 3)

• Next purchase order date = 6/28

• Next purchase order quantity = 50

Availability for Drop Ship and Non-Inventory Items, including Set Masters

• Drop ship items: If an item is flagged as Drop ship, the available quantity passed to Oracle Retail Order Broker is 9999, unless you actually have an available quantity of the drop ship item in the warehouse; in this case, the available quantity sent to Oracle Retail Order Broker is based on the standard availability calculation described above. Also, in this case, if there are any open purchase orders for the drop ship item tracked in the Purchase Order Layering table, then the next PO date and quantity from the first Purchase Order Layering record is also passed to Oracle Retail Order Broker. (Purchase orders for drop ship items are in the Purchase Order Layering table only if they are not generated through customer orders, but are requesting shipment to the warehouse.)

Example:

12 units in warehouse 2 (OROB location = 2)

0 units in warehouse 3 (OROB location = DC; this is the OROB Default Location (K51))

If the Send Inventory by Warehouse to OROB (L06) system control value is:

• selected: the available quantity reported for each OROB location:

- 2 = 12

- DC = 9999

• unselected: the available quantity reported for OROB location DC = 12

Note: If there is a quantity on-hand in the warehouse, but it is not currently available (for example, because it is reserved against an order), then the available quantity reported is 9999.

• Set master items and other non-inventory items: The available quantity reported for the set master item is typically 0; however, if you actually have an available quantity of the item in the warehouse, this quantity is used. To determine the true availability of a set, check the set components and the set quantity of each component required to make up a set, or look up the set master item in Entering Set Information (WSET).

Sample file:

7|1|SKU YELW SML WMNS|1000|200|2015-12-07||1|||

The system includes empty pipes in the file for data that is not included.

Field	Description
system_cd	The company code where the periodic function was submitted. Maps to the Oracle Retail Order Broker system code.
location_cd	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is from the OROB Default Location (K51), even if the item is not stored in this warehouse, but is stored in another allocatable warehouse; otherwise, this is the OROB location specified for the warehouse. If the Send Inventory by Warehouse to OROB (L06) is selected and the warehouse does not have a OROB location, the information is not sent to Oracle Retail Order Broker. Maps to a Oracle Retail Order Broker location.
product_cd	The item and SKU. The system includes the full 12 positions for the item and the full 14 positions for the SKU; for example: SKU YELW SML WMNS.
available_qty	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the total quantity available across all allocatable warehouses; otherwise, this is the total quantity available for the warehouse. Calculated as: On hand - Protected - Reserved - Reserve Transfer - Backordered = Quantity available. See Availability for Drop Ship and Non-Inventory Items, including Set Masters for a discussion on drop ship and non-inventory items, such as set master items.
next_po_qty	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the quantity expected on the next open purchase order that might be able to fulfill a new backorder; otherwise, this is the quantity expected on the next eligible open purchase order for that warehouse only. From the Purchase Order Layering table.
next_po_date	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the date of the next open purchase order that might be able to fulfill a new backorder; otherwise, this is the date of the next eligible open purchase order for that warehouse only. From the Purchase Order Layering table.
daily_sell_through_qty	This value is not populated.
sell_qty_multiple	The Sell Quantity defined for the item.
minimum_sell_qty	This value is not populated.
shrink_rate	This value is not populated.
sales_velocity	This value is not populated.

Item Availability Updates

The Oracle Retail Order Broker item availability update process allows Oracle Retail Order Broker to obtain up-to-date inventory information from Oracle Retail Order Management System.

How does the update work?

• The OBINCIN OB Incremental Inventory Output File (program name PFR0129) periodic function allows you to generate an Incremental Inventory output file for import into Oracle Retail Order Broker. This file contains inventory updates for a specified company since the last time the periodic function was run. See Oracle Retail Order Broker Incremental Inventory Output File for details.

• The Order Broker Product Inventory Availability API returns location availability information for a specific product, based on a request from Oracle Retail Order Broker.

Oracle Retail Order Broker Incremental Inventory Output File

Use the OBINCIN OB Incremental Inventory Output File (program name PFR0129) periodic function to generate an Incremental Inventory output file to send to Oracle Retail Order Broker. This file contains inventory updates for a specified company to send to Oracle Retail Order Broker.

Include only items with changed availability: When you run this periodic function, the system calculates the quantity currently available and updates the Virtual current available field in the Item Warehouse table. If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the total quantity available across all allocatable warehouses; otherwise, this is the total quantity available for the warehouse. Calculated as: On hand - Protected - Reserved - Reserve Transfer - Backordered = Quantity available. See Availability for Drop Ship and Non-Inventory Items, including Set Masters for a discussion on drop ship and non-inventory items, such as set master items.

The system compares the quantity in the Virtual current available to the quantity in the Last available sent field in the Item Warehouse table. If the quantities do not match, the system:

• includes the item in the incremental inventory output file, updating the available_qty in the file with the Virtual current available quantity.

• updates the Last available sent field with the quantity defined in the Virtual current available field.

Note: If the quantities in the Virtual current available and Last available sent match, the system does not include the item in the incremental inventory output file.

If the Send Inventory by Warehouse to OROB (L06) system control value is:

• selected: the import process includes availability for items flagged OROB eligible if the warehouse has an OROB location specified and the warehouse is flagged as Allocatable. Any purchase order information is related to that warehouse only. Only warehouses whose available quantity has changed are included.

Example:

Item AB100 is stocked in:

• Warehouse 1 (allocatable, OROB location = DC1)

- Available quantity = 100

- Next purchase order date = 6/30

- Next purchase order quantity = 15

• Warehouse 2 (allocatable, OROB location = S2)

- Available quantity = -10

- No open purchase orders

• Warehouse 3 (allocatable, no OROB location)

- Available quantity = 5

- Next purchase order date = 6/28

- Next purchase order quantity = 50

OROB Default Location (K51) is set to DC.

Results when sending by warehouse:

If Send Inventory by Warehouse to OROB (L06) is selected, update:

OROB location DC1:

• Available quantity = 100

• Next purchase order date = 6/30

• Next purchase order quantity = 15

OROB location S2:

• Available quantity = -10

• No purchase order information is included

Warehouse 3 is not included because there is no OROB location.

Results when sending sum:

If Send Inventory by Warehouse to OROB (L06) is unselected, update:

OROB location DC:

• Available quantity = 95 (warehouse 1 + warehouse 2 + warehouse 3)

• Next purchase order date = 6/28

• Next purchase order quantity = 50

See Availability for Drop Ship and Non-Inventory Items, including Set Masters for more information on how the system determines the available quantity for drop ship items, non-inventory items, and set master items.

Location of file: The OROB_DIRECTORY_PATH in Working with Cloud Properties (CPRP) defines the location on the application server where the system downloads the Incremental Inventory output file. An example directory is /usr/local/tomcat01/OMSFiles/OROBData, where /usr/local/tomcat01 is the installed location of Oracle Retail Order Management System. Note: If the OROB_DIRECTORY_PATH is not valid or is blank, or the specified folder does not exist, the system does not generate the Incremental Inventory file and writes a message to the Application log.

Name of file: The system names the file INCREMENTAL_INVENTORY_999_YYMMDDHHMMSS.TXT, where 999 is the company code where you submitted the periodic function and YYMMDDHHMMSS is the date and time when the download occurred. The file has a .tmp suffix while it is being generated.

Application log: The system writes any messages related to the download to the application log.

Sample file:

9|1|2006 PINK S REG|10|20|2015-10-31

The system includes empty pipes in the file for data that is not included.

Field	Description
system_cd	The company code where the periodic function was submitted. Maps to the Oracle Retail Order Broker system code.
location_cd	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is from the OROB Default Location (K51), even if the item is not stored in this warehouse, but is stored in another allocatable warehouse; otherwise, this is the OROB location specified for the warehouse. If the Send Inventory by Warehouse to OROB (L06) is selected and the warehouse does not have a OROB location, the information is not sent to Oracle Retail Order Broker. Maps to a Oracle Retail Order Broker location.
product_cd	The item and SKU. The system includes the full 12 positions for the item and the full 14 positions for the SKU; for example: SKU YELW SML WMNS.
available_qty	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the total quantity available across all allocatable warehouses; otherwise, this is the total quantity available for the warehouse. Calculated as: On hand - Protected - Reserved - Reserve Transfer - Backordered = Quantity available. See Availability for Drop Ship and Non-Inventory Items, including Set Masters for a discussion on drop ship and non-inventory items, such as set master items.
next_po_qty	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the quantity expected on the next open purchase order that might be able to fulfill a new backorder; otherwise, this is the quantity expected on the next eligible open purchase order for that warehouse only. From the Purchase Order Layering table.
next_po_date	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the date of the next open purchase order that might be able to fulfill a new backorder; otherwise, this is the date of the next eligible open purchase order for that warehouse only. From the Purchase Order Layering table.

Order Broker Product Inventory Availability API

Use the Order Broker Product Inventory Availability API to return location availability information for a specific product, based on a request from Oracle Retail Order Broker.

Process overview: When a remote system requests inventory information, Oracle Retail Order Broker checks for current inventory information from Oracle Retail Order Management System if:

• the system representing Oracle Retail Order Management System is configured in Oracle Retail Order Broker as an online system, and

• there is a product location record in Oracle Retail Order Broker indicating that the item is stocked in a Oracle Retail Order Management System warehouse. This record is normally created automatically through Oracle Retail Order Broker’s Product Import Process.

If the above conditions are true, Oracle Retail Order Broker automatically checks the item’s inventory information in Oracle Retail Order Management System, and updates the product location record for the product in the OROB Default Location (K51) if the Send Inventory by Warehouse to OROB (L06) system control value is unselected; otherwise, it updates the location matching the warehouse’s OROB location. The rules used to update the product location’s Available quantity, Next PO quantity, and Next PO date are the same as those used for Oracle Retail Order Broker’s Product Import Process.

Setup:

• Complete all the setup required for Oracle Retail Order Broker’s Product Import Process.

• Flag the Oracle Retail Order Management System system in Oracle Retail Order Broker as Online.

• Complete the setup required for the Order Broker Availability API.

Order Broker Availability API setup: The CWServiceIn Web Service allows an external system to post the Order Broker Product Inventory Availability Request directly to Oracle Retail Order Management System and receive a response without the need of any queues.

Web service authentication? The Require_Auth field in the Webservice table defines whether the web service requires basic web service authentication. By default, this field is set to Y, indicating the web service requires authentication. See Working with Web Service Authentication (WWSA) for an overview.

Web service type? You can use the CWServiceIn RESTful web service for the Order Broker Product Inventory Availability API. You POST the Order Broker Product Inventory Availability Request to the web service’s URL, or endpoint, of the RESTful service. The web service routes the messages sent to the endpoint and dispatches them to the Item Availability Update process. When the Item Availability Update process generates an Order Broker Product Inventory Availability Response, the CWServiceIn web service routes the response.

Determine the endpoint: The individual URL for the CWServiceIn RESTful service used for the Order Broker Product Inventory Availability API uses the following format: http://server/SerenadeSeam/sxrs/Inventory, where server identifies the application server where the RESTful service is located.

Errors: If the Order Broker Product Inventory Availability Request fails, the response returns with an error message. Possible errors are:

Error Message	Reason
Message is Invalid	The message is not in the correct JSON format.
Product Code in Invalid	The product code must be a valid item in Oracle Retail Order Management System.
System Code in Invalid	The system code must be a valid company code in Oracle Retail Order Management System.

Order Broker Product Inventory Availability Request

See Order Broker Product Inventory Availability: Sample Messages for sample messages.

Name	Type	Length	Comments
urlString			Identifies the URL for the Oracle Retail Order Management System web service. The individual URL for the CWServiceIn RESTful service uses the following format: http://server/SerenadeSeam/sxrs/Inventory, where server identifies the application server where the RESTful service is located.
productCd	alpha	12	The Oracle Retail Order Management System item number and SKU.
systemCd	numeric	3	The Oracle Retail Order Management System company code.
Response			Not used.
systemId			Not used.
timeOut			Not used.

Order Broker Product Inventory Availability Response

See Order Broker Product Inventory Availability: Sample Messages for sample messages.

Name	Type	Length	Comments
ProductCode	alpha	12	The item and SKU. The system includes the full 12 positions for the item and the full 14 positions for the SKU; for example: SKU YELW SML WMNS.
LocationCode	numeric	3	If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is from the OROB Default Location (K51), even if the item is not stored in this warehouse, but is stored in another allocatable warehouse; otherwise, this is the OROB location specified for the warehouse. If the Send Inventory by Warehouse to OROB (L06) is selected and the warehouse does not have a OROB location, the information is not sent to Oracle Retail Order Broker. Maps to a Oracle Retail Order Broker location.
AvailableQuantity			If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the total quantity available across all allocatable warehouses; otherwise, this is the total quantity available for the warehouse. Calculated as: On hand - Protected - Reserved - Reserve Transfer - Backordered = Quantity available. A negative quantity indicates the item in on backorder. See Availability for Drop Ship and Non-Inventory Items, including Set Masters for a discussion on drop ship and non-inventory items, such as set master items.
NextPOQuantity			If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the quantity expected on the next open purchase order that might be able to fulfill a new backorder; otherwise, this is the quantity expected on the next eligible open purchase order for that warehouse only. From the Purchase Order Layering table.
NextPODate			If the Send Inventory by Warehouse to OROB (L06) system control value is unselected, this is the date and time, in YYYY-MM-DD HH:MM:SS format, of the next open purchase order that might be able to fulfill a new backorder; otherwise, this is the date of the next eligible open purchase order for that warehouse only. From the Purchase Order Layering table.

Order Broker Product Inventory Availability: Sample Messages

Samples of the Order Broker Availability messages are presented below.

Successful Order Broker Availability Request:

{"urlString":"https://wbooms55app2/SerenadeSeam/sxrs/Inventory","productCd":"LOCATE","systemCd":"7","response":"-1","systemId":425430,"timeOut":30000}

Order Broker Availability Response:

[

{

"ProductCode": "LOCATE",

"LocationCode": "S2",

"AvailableQuantity": -10,

"NextPOQuantity": 0,

"NextPODate": ""

{

"ProductCode": "LOCATE",

"LocationCode": "1",

"AvailableQuantity": 100,

"NextPOQuantity": 15,

"NextPODate": "2016-01-30 12:00:00 AM"

}

]

Unsuccessful Order Broker Availability Request:

{"urlString":"https://wbooms55app2/SerenadeSeam/sxrs/Inventory","productCd":"ITM","systemCd":"7","response":"-1","systemId":425430,"timeOut":30000}

Order Broker Availability Response:

{"error": "Product Code is Invalid"}

Brokered Backorder Integration with Oracle Retail Order Broker

Brokered backorder: Use the brokered backorder integration with Oracle Retail Order Broker to automatically send backordered lines to the Order Broker module in Oracle Retail Order Broker for fulfillment. Unlike the merchandise locator API, the brokered backorder integration with Oracle Retail Order Broker enables you to fulfill these orders automatically “behind the scenes” using business rules you have configured in Oracle Retail Order Broker and Oracle Retail Order Management System, without the need to select a fulfilling location; the Order Broker selects the location for you.

Note: This is an example of a delivery order sent to the Order Broker for fulfillment. See Retail Pickup and Delivery Orders from Oracle Retail Order Broker for another example in which the order originates in a retail location and is assigned to Oracle Retail Order Management System for fulfillment.

For more information: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker) and Brokered Backorders.

Retail Pickup and Delivery Orders from Oracle Retail Order Broker

Purpose: Use the retail pickup or delivery order integration with Oracle Retail Order Broker to receive and fulfill orders in Oracle Retail Order Management System that originated in an external retail location.

Retail pickup order: The Order Broker sends a retail pickup order to Oracle Retail Order Management System for fulfillment when the customer would like to pick up the order at the originating retail location, but the inventory is not available. The ship-to address on a retail pickup order sent to Oracle Retail Order Management System for fulfilment is the name and address of the originating store location.

Delivery order: The Order Broker sends a delivery order to Oracle Retail Order Management System for fulfillment when the customer would like the order shipped to his or her home, but the inventory is not available at the originating location. The ship-to address on a delivery order is the name and address of the customer.

Note: This is an example of a delivery order sent to by Order Broker to Oracle Retail Order Management System for fulfillment. See Brokered Backorder Integration with Oracle Retail Order Broker for another example in which the order originates in Oracle Retail Order Management System and is assigned to a retail location for fulfillment.

For more information: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker) and Retail Pickup or Delivery Orders.

Ship-to-Store Orders

Ship-to-store order: Use the ship-to-store integration with Oracle Retail Order Broker to send orders to an external retail location for customer pickup if the merchandise is not available at that location. The ship-to address on a ship-to-store order sent from Oracle Retail Order Management System to the Order Broker is the name and address of the store location.

For more information: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker) and Ship-to-Store Orders.

Store Pickup Orders

Store pickup order: Use the store pickup integration with Oracle Retail Order Broker to send orders to an external retail location where the merchandise is already available for pickup. Unlike a ship-to-store order, a store pickup order does not require Oracle Retail Order Management System to transfer the inventory to the store. The ship-to address on a retail pickup order sent from Oracle Retail Order Management System to the Order Broker is the name and address of the originating store location.

For more information: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker) and Store Pickup Orders.

Merchandise Locator Searching

Merchandise locator searching: This integration with Oracle Retail Order Broker provides a way to search for a location across the enterprise where the customer can pick up an item. This option is available in item availability, order entry, and order maintenance. The results are informational only.

For more information: See Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker), and the Merchandise Locator API.

Store Connect

Overview: Store Connect is a module of Oracle Retail Order Broker that provides store associates with a suite of screens to process delivery orders (brokered backorders from Oracle Retail Order Management System) or store pickup orders. Store Connect is represented in Oracle Retail Order Broker as a separate integrated system, and stores using Store Connect identified as locations; however, the Order Broker assigns and tracks orders assigned to Store Connect locations as it does for any other orders.

Types of orders: Only delivery orders (brokered backorders) and store pickup orders can be fulfilled through Store Connect:

• Brokered backorders (delivery orders): When Oracle Retail Order Broker receives a brokered backorder from Oracle Retail Order Management System, it assigns the order to a fulfilling location using standard Order Broker rules. If the selected location is part of the Store Connect system, the associates use Store Connect to accept, print, pick, and ship the order, and Oracle Retail Order Management System tracks the activity as with any other brokered backorder.

• Store pickup orders: Selecting a fulfilling location for a store pickup order uses standard Order Broker rules; however, since Store Connect is represented in Oracle Retail Order Broker as a separate system, you need to associate Store Connect store locations with that system code, either through the Store Cross Reference record or through a default specified in a system control value. The store associate uses Store Connect to accept, print, and pick the order, and to confirm customer pickup.

For more information: See:

• the Oracle Retail Order Broker Operations Guide and online help

• Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker)

• Brokered Backorders

• Store Pickup Orders

Oracle Retail Order Broker Integration

Contents

SCVs

Search

Glossary

Reports

Solutions

XML

Index

Order Broker Integration

LO01_01 OROMS 15.1 June 2016 OTN