Order Orchestration Integration

Order Orchestration: Integration with the Routing Engine module in Order Orchestration supports fulfilling orders across the enterprise.

Use the Order Orchestration integration for the following:

  • brokered backorders: Automatically send backordered lines to the Routing Engine module in Order Orchestration, so the orders can be assigned to locations for fulfillment.

    • If the Use OROB for Fulfillment Assignment (M31) system control value is selected, the system bypasses reservation in order to send all eligible items to Order Orchestration for fulfillment assignment, even if the item is available in the warehouse. In this situation, the fulfilling location may be a store location or an Order Administration warehouse.

    • If the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS, the system bypasses reservation in order to send eligible items on a ship-for-pickup order to Order Orchestration for fulfillment assignment. In this situation, the fulfilling location may be a store location or an Order Administration warehouse.

  • receive retail pickup (including ship-for-pickup) or delivery orders from Order Orchestration: Receive and fulfill orders in Order Administration. If the order is a retail pickup order, Order Administration sends the merchandise to the customer’s selected store for pickup. If the order is a delivery order, Order Administration ships the merchandise to the customer’s ship-to address. Typically, retail pickup and delivery orders originated in an external retail location. In addition:

    • If the Use OROB for Fulfillment Assignment (M31) system control value is selected, Order Orchestration may send a delivery order to Order Administration that originated as a brokered backorder in Order Administration. In this situation, Order Orchestration determined that an Order Administration warehouse was the best location to fulfill the order.

    • If the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS, Order Orchestration may send a retail pickup order to Order Administration that originated as a ship-for-pickup order in Order Administration. In this situation, Order Orchestration determined that an Order Administration warehouse was the best location to fulfill the order.

  • send ship-for-pickup orders during pick slip generation/drop ship processing to Order Orchestration: If the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to NEVER, ship orders to an external retail location for customer pickup if the merchandise is not already available at that location.

  • send store pickup orders to Order Orchestration: Notify an external retail location that has inventory available that a customer will pick up an order.

Version compatibility: Fulfillment assignment and ship-for-pickup functionality is available in release 16.0 or higher of Order Management System, or Order Administration, and release 16.0 or higher of Order Broker, or Order Orchestration. Also, in order to use ship-for-pickup processing, you must select the Enable Ship For Pickup option on the Organization window in Order Orchestration. Once you enable ship for pickup, the Organization window in Order Orchestration displays the Ship for Pickup Enabled Date, and you cannot deselect this option. 

An OROB_MESSAGE_VERSION of 16.0 or higher is required to use the Ship-for-Pickup Orders integration with Order Orchestration.

A message version of 19.0 or higher is required to include the shipment_date tag in the status inquiry response message from Order Orchestration. This date indicates the actual date when the order line was shipped by the fulfilling location, provided the fulfilling system passed this date when it submitted the status update to Order Orchestration when reporting the fulfillment. The shipment date is available to include in shipment notifications to the customer; see Outbound Email API in the Web Services Guide on My Oracle Support (ID 2953017.1) for more information.

Note:

Up to version 21.1 of OROB_MESSAGE_VERSION is supported. but this property cannot be set higher than 19.9 for integration with Order Broker 19.x, or higher than 21.1 for integration with Order Orchestration 22.2.301.0 or higher.

For more information: See:

  • Order Orchestration Integration Overview for general background on integration between Order Orchestration and Order Administration.

  • Order Orchestration Configuration for required setup in Order Administration.

  • the Order Orchestration Operations Guide for details on each request and response message, as well as details on logging and troubleshooting in Order Orchestration.

  • the Order Orchestration online help for step-by-step instructions on populating the Order Orchestration database and on scheduling item and inventory imports.

For information on Order Orchestration processing in Order Administration, see: