Brokered Backorders

Purpose: If the Send B/O to OROB (K08) system control value is selected, you can use the Order Orchestration Integration to send backordered order lines to Order Orchestration for fulfillment.

If the Use OROB for Fulfillment Assignment (M31) system control value is unselected, the system sends eligible backordered items to Order Orchestration for fulfillment. Order Orchestration will choose the best store location to fulfill and ship the item to the customer. Items that are in stock follow normal reservation and fulfillment processing.
If the Use OROB for Fulfillment Assignment (M31) system control value is selected, the system bypasses reservation and places all eligible items on backorder, even if the item is available in an Order Administration warehouse. Order Orchestration will choose the best store location or Order Administration location to fulfill and ship the item to the customer.
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 and the merchandise is shipped to the customer’s selected store for pickup. See Creating a Ship-for-Pickup Order in Order Administration for more information on how to create a ship-for-pickup order.

Note:

If the item is flagged as a active PO item the system does not submit it to Order Orchestration for fulfillment using the standard process described here; instead, it uses the process described under Enterprise Order Integration (Future Receipts and Active PO/Pre-Order Processing).

When using Order Orchestration for fulfillment assignment, the fulfilling location can be a store location or an OACS warehouse location. In addition, for ship-for-pickup orders, the fulfilling location ships the order to the customer’s selected store for pickup.

In this topic:

Brokered Backorder Processing Overview

Order Orchestration assignment: Assigning a backordered item to Order Orchestration can occur through:

order entry or order API: When you create an order that includes a backordered line, Order Administration assigns the line, if eligible, to Order Orchestration for fulfillment, and withholds it from normal fulfillment processing within Order Administration.
Note:
- If the Use OROB for Fulfillment Assignment (M31) system control value is selected, the system bypasses reservation for all eligible items on an order and places them on backorder so that Order Orchestration can determine the fulfilling location.
- If the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS, the system bypasses reservation for all eligible items on a ship-for-pickup order and places them on backorder so that Order Orchestration can determine the fulfilling location.
batch process: A periodic function finds eligible backordered lines and assigns them to Order Orchestration.

Eligibility rules: Order Administration determines whether an order line is eligible for Order Orchestration fulfillment based on certain basic criteria, such as whether it is fully backordered and authorized; also, you can use related system control values to further restrict Order Orchestration assignment based on your business rules, such as omitting items you are due to receive soon on open purchase orders. Also, the item must be flagged as OROB eligible. See Rules for Submitting Backorders to Order Orchestration for details.

If the authorization for the order line has expired, the system obtains a new authorization.

Does each line create a separate order in Order Orchestration? Each eligible backordered line on an order is sent to Order Orchestration:

as a separate order if the Use Split Order (L56) system control value is unselected. In this case, the fulfillment of each line is tracked individually. Order Orchestration does not attempt to assign multiple order lines from the same fulfilling location.
as part of a single order if the Use Split Order (L56) system control value is selected. In this case, Order Orchestration attempts to assign all lines on the same order to the same fulfilling location; however, it notifies Order Administration about multiple assigned fulfilling locations if the order or lines are split. If a single backordered item is unfulfillable through Order Orchestration, that line returns to standard backorder processing, but additional lines on the order can still be fulfilled through Order Orchestration.

What information is sent to Order Orchestration? Order Administration sends the following information to Order Orchestration:

sold-to and ship-to customers’ names and addresses.
details on the requested item.

It does not send payment information, although only fully paid and authorized items are eligible for Order Orchestration fulfillment. If the Payment at POS for Ship for Pickup Orders (L60) system control value is selected, ship-for-pickup orders are authorized for verification only and payment is collected when the customer picks up the items at the store.

If the authorization for an order line has expired, the system obtains a new authorization.

For more information on the information sent to Order Orchestration, see Sample Order Orchestration Messages in the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Brokered Backorder Fulfillment: Initial Order Creation

#	Step
1.	The process begins when you create an order in Order Administration. If the Send B/O to OROB (K08) system control value is selected, the system sends eligible backordered items to Order Orchestration to determine the fulfilling location. In addition: If the Use OROB for Fulfillment Assignment (M31) system control value is selected, the system bypasses reservation and places all eligible items on backorder, even if the item is available in an Order Administration warehouse, in order to have Order Orchestration determine the fulfilling location. If the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS, the system bypasses reservation and places all eligible items on a ship-for-pickup order on backorder, even if the item is available in an Order Administration warehouse, in order to have Order Orchestration determine the fulfilling location. The order creation can occur through interactive order entry, batch order entry, or the order API. You can also use the BROKER periodic function to submit existing backordered lines to the Order Orchestration for fulfillment; see Additional Order Orchestration Setup in Order Administration for more information.
2.	If the order line meets the Rules for Submitting Backorders to Order Orchestration, the BROKER_ORD process in Order Administration generates a request message to Order Orchestration and creates an Order Orchestration record. Note: Order lines that meet the Rules for Submitting Backorders to Order Orchestration do not sell out initially, even if the items are flagged with soldout control codes. See Brokering Items with Soldout Control Codes for more information. If the order includes multiple backordered lines and the Use Split Order (L56) system control value is selected, the request message includes all eligible backordered lines; otherwise, each backordered item is submitted as a separate order. Each Order Orchestration record has a status of R (ready) at creation. Also, the order line is updated to restrict it from standard backorder processing in Order Administration: the Drop ship flag is set to D. the Printed quantity is updated to the ordered quantity. an order line that is assigned to Order Orchestration for fulfillment displays a status of OBR in standard order inquiry. the quantity to be brokered does not update the Backordered quantity for the Item Warehouse. if the Use OROB for Fulfillment Assignment (M31) system control value is selected, the Bypass reservation flag is selected with a Backorder reason of `Reservation bypassed` indicating the brokered backorder was created for fulfillment assignment. if the order is a ship-for-pickup order sent for fulfillment assignment, the Bypass reservation flag is selected with a Backorder reason of `Reservation bypassed` indicating the brokered backorder was created for fulfillment assignment. Note: Order Orchestration status is not displayed in Streamlined Order Inquiry (DORI).
3.	If the BROKER_ORD process in Working with Integration Layer Processes (IJCT) is active, it immediately generates the submit order request message to Order Orchestration to request order creation and assignment in Order Orchestration. At this time, it also changes each Order Orchestration record’s status to W (waiting) and creates an Order Orchestration History record for each line to track the order submission (`A - Send Order Request`). See the Sample Order Orchestration Messages in the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). Note: Although the BROKER_ORD process generates the submit order requests (and cancellation requests, if needed), the BROKER process handles other requests to Order Orchestration.
4.	The Routing Engine module in Order Orchestration receives the submit order message. If Order Administration sent each line separately, Order Orchestration creates each order line as a separate order in its database; otherwise, if you use the split order option, Order Orchestration creates a single order including all of the order lines that were eligible for submission as brokered backorders. Order Orchestration assigns each order or line to a location for fulfillment based on inventory availability and the business rules you have defined in Order Orchestration. At this point, the order status in the Order Orchestration database is new_order.
5.	Order Orchestration sends a response message to Order Administration indicating each assigned fulfilling location and the unique request ID it uses to identify each order. See the Submit Order Response Message Sample in the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). Note: The message version is specified in the Order Orchestration Properties; this property must be set to `16.0` or higher in order to use brokered backorders for fulfillment assignment and to use ship-for-pickup processing.
6.	If Order Orchestration successfully created an order and assigned it to one or more fulfilling locations, Order Administration: updates each Order Orchestration record with: the fulfilling location, using the description set up through the Work with Store Cross Reference (WSCR) option. the request ID. a status of A (acknowledged). writes an Order Transaction History message indicating that the order line was acknowledged by Order Orchestration (for example, `Ln#: 2 Acknowledged by Broker`). creates an Order Orchestration History record (`B - Receive Order Response`).

Split line? If the Allow Split Line? preference in Order Orchestration is selected, Order Orchestration might split the quantity of a single brokered backorder line across more than one fulfilling location. For example, you create an order for item AB100 with a quantity of 10. There is no single location that has a quantity of 10 available. Order Orchestration assigns 8 units to location 100, and 2 units to location 200.

Order Orchestration splits order lines or line quantities only if you have selected the Allow Split Order? and Allow Split Line? preferences in Order Orchestration, and if there is not a single location that can fulfill the entire order or line quantity. See the Use Split Order (L56) system control value for examples, and see the Order Orchestration Operations Guide or online help for background.

If Order Administration is the fulfilling location: If the Use OROB for Fulfillment Assignment (M31) system control value is selected or the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS, Order Orchestration may determine that a warehouse in Order Administration is the best location to fulfill the order, or some portion of the order. In this situation:

Order Orchestration assigns the Order Administration location to the order in Order Orchestration as the Fulfilling location.
When the order in the fulfillments response message is received:
- If the original order is not a ship-for-pickup order, it creates a new delivery order and assigns the order type defined in the Order Type for Delivery Orders Originating in OROMS (M33) system control value to the order.
- If the original order is a ship-for-pickup order, it creates a new retail pickup order and assigns the order type defined in the Order Type for Retail Pickup Orders Originating in OROMS (M35) system control value to the order.
In order to tie the originating order (the original order sent to Order Orchestration for fulfillment assignment) with the new fulfilling order (the delivery or retail pickup order created to fulfill the original order), Order Administration:
- stores the originating order number in the E-commerce order number field in the Order Header Extended table for the newly created sourcing order. For example, the system updates the E-commerce order number with ORIG#: 9999-001, where ORIG#: indicates the order has been created as a result of OROB fulfillment assignment, 9999 is the order number, and 001 is the ship-to number.
- assigns the Request ID defined for the originating order to the newly created sourcing order.

See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for more information on how Order Administration processes a delivery or retail pickup order.

If the assigned fulfilling location rejects the order: The location assigned to fulfill an order or line can reject it if, for example, it does not have sufficient inventory. In this situation, Order Orchestration uses the rules set up at the Preferences screen in Order Orchestration to select another location to fulfill the order. If the location where the order is currently assigned changes, Order Administration updates this information the next time it sends a status inquiry to Order Orchestration, typically through pick slip generation, and receives the new information in the response.

Note:

An order normally remains in Rejected status in Order Orchestration only for a moment. If for any reason Order Orchestration receives a status inquiry request when the order’s status is Rejected, Order Administration does not update the order until the next time it sends a periodic status inquiry.

What if Order Orchestration cannot find a location to fulfill the order or line? In some cases, Order Orchestration cannot assign an order to a location because there are no locations with sufficient inventory that are eligible based on the business rules set up in Order Orchestration at the Preferences screen. In this situation, Order Orchestration assigns the order to the Default Unfulfillable Location specified in Order Orchestration, which should match the setting of the OROB Default Location Code for Unfulfillable Orders (K56) system control value. When Order Administration receives a response message indicating that the order was assigned to the unfulfillable location and has a status of Unfulfillable, it:

Clears the Drop ship flag and the Printed quantity on the Order Detail line.
If the Use OROB for Fulfillment Assignment (M31) system control value is selected or the original order is a ship-for-pickup order, unselects the Bypass reservation flag and updates the Backorder reason to Not enough avail in whse.
Changes the status of the Order Orchestration record to U (unfulfillable).
Writes an Order Transaction History record (for example, Ln#: 2 Unfulfillable by Broker).
Returns the line to standard backorder or soldout processing, including updating the Backorder quantity for the Item Warehouse and updating the PO Layering record.

An order might be flagged as unfulfillable when Order Orchestration first receives the request message, or after one or more locations have rejected the order for fulfillment; in this case, Order Administration receives notification the next time it sends a periodic status inquiry, as described below.

Notifying the customer of fulfillment assignment through Order Orchestration: The order confirmation email indicate a status of Store Ship for order lines assigned to Order Orchestration. See the Order Confirmation Email Sample and Contents for more information.

Fulfillment Process: After Order Creation and Status Updates

Status list inquiry request and response process: The BROKER IJCT job no longer calls the OOCS Status List request message for the latest status where the brokered status is still considered open. Instead, a web service is used to accept status updates from OOCS real-time. After each status update is complete in OOCS, a new Status Update message is sent immediately to OACS giving the current Quantity and Status of every line that was sent in the Status Update request.

If status has not changed: Once the order line is in Accepted status, Order Administration does not write a history record for the status list inquiry response as long as the record remains in this status.

Activity	Status in OOCS	Status in OACS	Updates to Order Orchestration and Order Transaction History
Order Administration sends the submit order message to Order Orchestration and restricts the order line from standard processing in Order Administration by setting the Drop ship flag and the Printed quantity.	not yet created	Waiting (W)	creates an Order Orchestration History record to track the order submission (`A - Send Order Request)`
Order Administration receives the submit order response from Order Orchestration	new_order	Acknowledged (K)	If there is a single fulfilling location: creates an Order Orchestration History record to track the response (`B - Receive Order Response`) updates the Order Orchestration record with the assigned fulfilling location writes an Order Transaction History message (for example, `Ln#: 1 Acknowledged by Broker`) Otherwise, if there are multiple fulfilling locations, Order Administration sends a status inquiry request to Order Orchestration and performs the above activities when it receives the response.
Polling: Each fulfilling location is responsible for polling Order Orchestration periodically to check for new orders. Once Order Orchestration receives a polling request from a location, it sends a polling response, listing the details of all new orders assigned to the location for fulfillment.	polled	Polled (P) (after receiving status inquiry response)	creates an Order Orchestration History record (`D - Receive Status Response`) writes an Order Transaction History message (for example, `Ln#: 1 Polled by Broker`)
Order accepted? If the assigned location can fulfill the order or line, it sends a status update message accepting the order or line to Order Orchestration.	accepted	Accepted (A) (after receiving status inquiry response)	creates an Order Orchestration History record (`D - Receive Status Response`) writes an Order Transaction History message (for example, `Ln#: 1 Accepted by Broker`) Note: Once the order line is in Accepted status, Order Administration does not write a history record for the status inquiry response as long as the record remains in this status.
Order rejected? If the assigned fulfilling or sourcing location cannot fulfill the order or line, or the pickup location for a ship-for-pickup order indicates that the inventory for the item was not received or was damaged in transit, it sends a status update rejecting the order or line to Order Orchestration. Order Orchestration then:
Attempts to find another location, subject to the rules you have set up in Order Orchestration. If it finds another location, Order Orchestration updates the record in its database and changes the order status back to new_order. Then the process begins again as Order Orchestration waits until the newly-assigned location polls for orders.	new_order	Acknowledged (K) (after receiving status inquiry response)	creates an Order Orchestration History record (`D - Receive Status Response`) writes an Order Transaction History message (for example, `Ln#: 1 Acknowledged by Broker`)
If Order Orchestration does not find another fulfilling location, it flags the order or line as unfulfillable by assigning it to the Default Unfulfillable Location you have set up in Order Orchestration (matching the OROB Default Location Code for Unfulfillable Orders (K56) in Order Administration). When Order Administration receives the status inquiry update indicating a fulfilling location that matches the OROB Default Location Code for Unfulfillable Orders (K56), it flags the order or line as unfulfillable and returns the line to standard backorder or soldout processing, clearing the Drop ship flag and the Printed quantity for the order line.	new_order	unfulfillable (U) (after receiving status inquiry response)	creates an Order Orchestration History record (`D - Receive Status Response`) writes an Order Transaction History message (for example, `Ln#: 5 Unfulfillable by Broker`)
In Transit (ship-for-pickup, retail pickup): The location assigned to fulfill a ship-for-pickup order has sent the inventory to the location where the customer will pick up the order. Once the fulfilling location has shipped the order or line, it sends a status update message to Order Orchestration, providing the ship via and tracking number if available. Order Orchestration changes the status to In Transit and stores the ship via and tracking number so that it can send this information to Order Administration. The tracking number is not available as a live link on screens.	In Transit	intransit	creates an Order Orchestration History record (`D - Receive Status Response`) writes Order Transaction History messages indicating the ship via and the tracking number passed from Order Orchestration (for example, `----VIA: UPS and ----TRK#: ABCDEFG1234567890`). If there is not tracking information available, writes an Order Transaction History message such as `Ln#: 1 Store Shipped Order` Create invoice? If the Invoice Ship For Pickup Order Once Intransit (M73) system control value is selected, Order Administration may create the invoice for the originating order when it receives a status inquiry response from Order Orchestration indicating that order lines on a ship-for-pickup order are now in transit. See that system control value for more information. Note: OACS no longer tries to combine Order Orchestration fulfillments into a single invoice but rather it is based on how the fulfilling system sends the request to OOCS. Therefore, for integrating systems, if you send status updates, you need to consider if you send them together or one at a time.
Intransit Polled (ship-for-pickup): The pickup location for a ship-for-pickup order: has received the order in the intransit response message, if the system is not flagged to Require Status Update; or has sent a status update request changing the status to intransit polled	In Transit Polled	intransit polled	creates an Order Orchestration History record (`D - Receive Status Response`) writes an Order Transaction History message (for example, `Ln#: 1 Intransit Polled by Broker`) Create invoice? If the Invoice Ship For Pickup Order Once Intransit (M73) system control value is selected, Order Administration may create the invoice for the originating order when it receives a status inquiry response from Order Orchestration indicating that order lines on a ship-for-pickup order are now in transit polled, if the invoice was not already created. See that system control value for more information. Note: OACS no longer tries to combine Order Orchestration fulfillments into a single invoice but rather it is based on how the fulfilling system sends the request to OOCS. Therefore, for integrating systems, if you send status updates, you need to consider if you send them together or one at a time.
Received (ship-for-pickup, retail pickup): The transferred inventory has been received at the location where the customer is picking up a ship-for-pickup order.	Received	received	creates an Order Orchestration History record (`D - Receive Status Response`) writes an Order Transaction History message (for example, `Ln#: 1 Store Received`) Create invoice? If the Invoice Ship For Pickup Order Once Intransit (M73) system control value is selected, Order Administration may create the invoice for the originating order when it receives a status inquiry response from Order Orchestration indicating that order lines on a ship-for-pickup order are now received, if the invoice was not already created. See that system control value for more information. Note: OACS no longer tries to combine Order Orchestration fulfillments into a single invoice but rather it is based on how the fulfilling system sends the request to OOCS. Therefore, for integrating systems, if you send status updates, you need to consider if you send them together or one at a time.
Order shipped (delivery) or picked up (ship-for-pickup, retail pickup): Once the fulfilling location has shipped the order or line (delivery) or the customer has picked up the merchandise at the store location (ship-for--pickup), it sends a status update message to Order Orchestration. For delivery orders, the update message also provides the ship via and tracking number if available. Order Orchestration changes the status to fulfilled and stores the ship via and tracking number so that it can send this information to Order Administration. When Order Administration receives notification, it clears the Drop ship flag and the Printed quantity, and submits the order line to billing. If Order Orchestration provides a valid ship via code and a tracking number, the tracking number is a live link in the shipment confirmation email, although not on screens. See the OrderShipmentLineDetail in the outbound email message for details. For more information see the Web Services Guide on https://support.oracle.com My Oracle Support (ID 2953017.1).	fulfilled	completed (X) (after receiving status inquiry or inquiry list response)	writes an Order Transaction History message (for example, `Ln#: 2 Store Shipped Order`) writes Order Transaction History messages indicating the ship via and the tracking number passed, if any, from Order Orchestration (for example, `----VIA: UPS` and `----TRK#: ABCDEFG1234567890`) Billing the order: When processing status update responses for the same order, if the status of an order line changes to fulfilled, the BROKER job: Changes the status to fulfilled for each order line if that status is indicated in the response message; Identifies the order lines that were previously in the same status, such as accepted, and are now in fulfilled status; Submits these order lines to billing as a single billing header record. Example: An order previously had two lines in accepted status and one line in acknowledged status. The response message indicates that all three lines are now in fulfilled status. The two order lines whose status changed from accepted to fulfilled are submitted to billing under a single billing header record, creating a single invoice. The one order line whose status changed from acknowledged to fulfilled are submitted to billing as a separate billing header record, creating a separate invoice. Note: Generating a single invoice takes place regardless of whether the fulfilled order lines have different Order Orchestration request IDs, provided the updates take place as described above. Note: The billing async job does not complete billing the order until one of the following occurs: The BROKER job ends, or Another brokered order is submitted to the billing data queue, or All the current status inquiry responses are processed for the company. If a large number of orders were submitted in the status list request, there could be a delay of several minutes before the order is billed. Note: If there are multiple order lines confirmed as fulfilled on a single order, but for different ship-tos, this generates separate billing header records and invoice ship-tos. Multiple invoices are created for a single order if not all order lines are included in the same status list response message.
Order status changes? If the Send Held Orders to OROB (M18) system control value is selected, Order Administration sends held brokered backorders to Order Orchestration, but with the Under Review flag set to Y; also, Order Administration sends an order update to Order Orchestration if the order’s status changes from held to open, or vice versa.	no change	no change	when the change occurs after initial order creation and submission, writes an Order Transaction History message (for example, `Request ID: 78390 Under Review: N`)

Picked? If the assigned fulfilling location reports that a brokered backorder is in Picked status, the Working with Order Broker (WOBR) option indicates a status of Accepted.

Canceling a brokered backorder: See Canceling a Brokered Backorder Request for a discussion of the updates that take place when you cancel an Order Orchestration request at the Work with Order Broker Screen or in order maintenance.

Reviewing brokered backorders in order inquiry: You can use the Brokered Backorder Summary Screen to review the current status of all brokered backordered lines on a single order. Also, you can select D/S Status for a single brokered backorder line at the Order Inquiry Detail Screen to advance to the Display Order Broker Details Screen, where you can review a single brokered backorder line on the order.

Quantity not indicated in order transaction history messages: The order transaction history messages do not specify the quantity affected by the update; however, if you split orders and lines, the quantity affected may be less than the total order line quantity. For example, if Order Orchestration splits an order line across two locations for fulfillment, and one of the locations fulfills its assigned quantity, the order transaction history message of Ln#: 2 Store Shipped Order does not indicate the fulfilled quantity.

Rules for Submitting Backorders to Order Orchestration

To be eligible for submission to Order Orchestration, the backordered item must have the OROB eligible flag selected. Also, the order line must be:

fully backordered
in open status

In addition, if the Use OROB for Fulfillment Assignment (M31) system control value is selected or the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS and the original order is a ship-for-pickup order, the order or order line can include the following; otherwise, the order or order line cannot include the following.

be gift wrapped
have any special handling

Note:
only custom special handling instructions are sent to Order Orchestration in the submit order request; however, the system does not prevent items with standard special handling from being sent to Order Orchestration
have a future arrival date or be flagged as a future order
be for a customer flagged to bypass reservation

If the Use OROB for Fulfillment Assignment (M31) system control value is set to ALWAYS, the originating location passed to Order Orchestration on a delivery order is the location defined in the Originating Location to Pass to OROB (M32) system control value.

Also, if the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS, the order line can be on a ship-for-pickup order; otherwise, if this system control value is set to NEVER or blank, order lines on a ship-for-pickup order are not eligible for submission to Order Orchestration to determine fulfillment assignment and instead are sent to Order Orchestration during pick slip generation and drop ship order processing time; see Ship-for-Pickup Orders.

Regardless of the settings of the Use OROB for Fulfillment Assignment (M31) and Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control values, the order line must not be:

Flagged as a drop ship item
A retail pickup or delivery order received from Order Orchestration
A main set item or a set component
A membership item
A stored value card item
A non-inventory item

Order Administration does not consider the item’s Projected returns quantity, if any, when determining whether the item is eligible for fulfillment through Order Orchestration.

Also, the order must be:

Open, if the Send Held Orders to OROB (M18) system control value is unselected; otherwise, the order can be held. In this case, the order’s Under Review flag is selected. See the system control value for more information.
Fully paid and authorized. If the Payment at POS for Ship for Pickup Orders (L60) system control value is selected, ship-for-pickup orders are authorized for verification only and payment is collected when the customer picks up the items at the store.

System control values: If the Use OROB for Fulfillment Assignment (M31) system control value is selected or if the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to ALWAYS and the original order is a ship-for-pickup order, regardless of the setting of the following system control values, the system sends items to Order Orchestration for fulfillment assignment. Otherwise, the following system control values also determine whether an order line is eligible to send to Order Orchestration for fulfillment:

Order Broker Due Date Threshold (K11): the system does not send an item to Order Orchestration if the item is expected on an open purchase order line for the related warehouse with a due date within the threshold defined in this system control value.
Order Broker Include Ship Complete Orders (K12): if this system control value is unselected, the system does not send items to Order Orchestration that are on an order flagged to ship complete.
Order Broker Include Coordinate Grouped Orders (K13): if this system control value is unselected, the system does not send items to Order Orchestration that are coordinate grouped with other items.
Order Broker Include Gift Orders (K14): if this system control value is unselected, the system does not send items to Order Orchestration that are on a gift order.

Sellout prevented: If an order line meets all of the criteria, it is brokered even if the item is flagged with a soldout control code. See Brokering Items with Soldout Control Codes for a discussion.

BROKER Periodic Function

The BROKER periodic function submits orders to Order Orchestration if they were not eligible for submission when they were created. For example, the periodic function submits order lines if:

Your company was not configured to send brokered backorders to Order Orchestration when the order was created.
The order was in held status at initial creation and was subsequently released from hold, and the Send Held Orders to OROB (M18) system control value is unselected.
The order previously included an active PO item (see About Active PO Items for background).
The order line was partially reserved, but then the reserved quantity was shipped and there is still a backordered quantity remaining on the order line. The order line is not eligible to be submitted to Order Orchestration until any reserved quantity is printed and shipped.

Note:
This situation occurs only if the Use OROB for Fulfillment Assignment (M31) system control value is unselected; also, this situation does not apply to ship-for-pickup orders sent to Order Orchestration for fulfillment assignment.

Note:

When the periodic function submits an order line as a brokered backorder, the function performs all the updates described under Brokered Backorder Fulfillment: Initial Order Creation, but also decreases the Backorder quantity for the Item Warehouse record, since this quantity had been increased when the line was created.

If an authorization is required, the BROKER function obtains an authorization for the entire order.

See Additional Order Orchestration Setup in Order Administration for background on setting up the BROKER periodic function.

Brokering Items with Soldout Control Codes

Items that are OROB eligible and flagged with a S/O control code are still eligible for brokering rather than selling out, provided they meet the Rules for Submitting Backorders to Order Orchestration.

In addition, the following applies if the Use OROB for Fulfillment Assignment (M31) system control value is unselected and the order is not a ship-for-pickup order.

If the soldout control status is:

sell out immediately: the item is eligible for brokering even if there is an available quantity in an allocatable warehouse.
include on-order: the item is eligible for brokering if it is backordered. There cannot be an open purchase order that could fulfill the order that is due within Order Orchestration Due Date Threshold (K11), if specified. If no Order Broker Due Date Threshold (K11) is specified, the item is eligible for brokering regardless of open purchase orders. The Projected returns quantity, if any, for the item is not evaluated; see Projected Returns for background on how you can use the Projected returns quantity to prevent selling out items in certain situations.
exclude on-order: the item is eligible for brokering if it is backordered, regardless of whether there are any open purchase orders.

If the item is unfulfillable: If Order Orchestration is unable to fulfill an order line, the line returns to standard backorder or soldout processing. The process flow is:

An item is assigned a soldout control value and would be sold out on the order if the item were not OROB eligible. Order Administration submits the order line to Order Orchestration, but there is no store location that can fulfill the item, so Order Orchestration returns a status of Unfulfillable.
When Order Administration receives the status update from Order Orchestration, it changes the order line status to sold out (S) if the order line is currently eligible to sell out based on the soldout control value and availability.
The next time you use the Processing Auto Soldout Cancellations (MASO) option, the soldout line is listed on the Auto Soldout Register, even though it did not sell out through Process Auto Soldouts and even if it is not assigned a soldout control status of 1 (sell out immediately).
The next time you use the Generating Soldout Notifications (MSON) option, Order Administration generates a soldout notification.

The same processing occurs if Order Orchestration returns an error for the brokered order line.

Gift wrap or special handling: Based on the Rules for Submitting Backorders to Order Orchestration, if the Use OROB for Fulfillment Assignment (M31) system control value is unselected or the order is not a ship-for-pickup order, an order line is not eligible for brokering if it is flagged for gift wrap or special handling. If gift wrap or special handling applies to the item:

When the order line is initially created, then the line does not broker; instead, it sells out or remains backordered, as if it were not flagged as OROB eligible. This is the case when the order API or ecommerce interface creates the order.
After the order line is initially created (for example, by selecting Special Handling for the line in order entry), then if the soldout control status is:
- sell out immediately: the line sells out the next time you use Processing Auto Soldout Cancellations (MASO).
- include on-order quantity or exclude on-order quantity: the line does not sell out automatically.

You can use a backorder report to identify order lines that could not be brokered because of gift wrap or special handling, and that did not sell out automatically. See Order Status and Activity Reports for more information.

Future orders: If the Use OROB for Fulfillment Assignment (M31) system control value is unselected or the order is not a ship-for-pickup order, future orders are not eligible to be brokered; in this situation, items flagged OROB eligible and assigned soldout control values sell out automatically on future orders, just as they would if they were not flagged OROB eligible. Once an order is no longer considered a future order, OROB eligible items on the order can be brokered through the BROKER periodic function if they meet the Rules for Submitting Backorders to Order Orchestration.

If reserving against a non-allocatable warehouse: Based on the Reserve from Non-Allocatable Warehouse (J25) and Disregard Soldout Controls for Non-Allocatable Warehouses (J27) system control values, you can reserve inventory against a non-allocatable (retail) warehouse for a retail order, and disregard an item’s soldout control assignment. In this case, even if the item’s OROB eligible field is selected, the item reserves against the non-allocatable (retail) warehouse if the order type is associated with that warehouse and there is inventory in that warehouse.

Things to Note About Brokered Backorders

Canceling order lines: It is important to confirm that the remote store location assigned to fulfill the order line has not begun the shipment process before you cancel an order line or Order Orchestration request in Order Administration. Depending on the Order Broker Status Update Interval (K10), the most current information about the Order Orchestration request in Order Administration might be out of date.

Freight charges included? Freight charges for the order are included in the SubmitOrder message only if the Use Split Order (L56) system control value is selected.

Customer address updates: If you change the customer’s name or address in Order Administration after generating the initial Order Orchestration request, the Order Orchestration integration does not send this updated information to the assigned fulfilling location. For ship-for-pickup orders, the system does not allow you to change the store location defined as the one-time ship-to address on the order once the order is accepted.

Held orders submitted? When the Send Held Orders to OROB (M18) system control value is unselected, if an order is initially created in held status and then released from hold, Order Administration does not automatically submit the order to Order Orchestration. To submit the order, you can run the BROKER Periodic Function (program PFR0083). See Order Orchestration Configuration for background.

Order lines not resubmitted: If an order line has previously been submitted to Order Orchestration and the Order Orchestration request was flagged as unfulfillable or put in error status, the BROKER periodic function does not resubmit the order line to Order Orchestration for fulfillment.

Reserve quantity limit: If an order line exceeds the Reserve qty (Reserve quantity limit) specified for an item, Order Administration still submits the order line to Order Orchestration for fulfillment, provided the line is eligible based on the Rules for Submitting Backorders to Order Orchestration.

Inventory transaction history: If the Create Item Transaction History for Non-Inventory Items (E39) system control value is selected, Order Administration writes a NONINVISSU transaction record when the BROKER process receives a status update indicating that the assigned location has shipped the order or line. See that system control value for more information.

Backorder notices: The Generate Backorder Notices (GBOC) option does not generate backorder notices for an order line when it has an Order Orchestration request in process; however, if the status of the Order Orchestration request changes to unfulfillable (U) or error (E), or if you cancel the Order Orchestration request (Z) without canceling the order line itself, the order line returns to standard backorder processing and is eligible to have backorder notices generated.

Tracking numbers in shipment confirmation email: If the fulfilling location supplies information on the shipping agent and a tracking number, Order Orchestration passes this information to Order Administration. If the shipping agent matches a valid ship via code in Order Administration, the shipment confirmation email lists the description of the ship via and the tracking number as a live link. Otherwise, if the shipping agent does not match a ship via set up in Order Administration, then the shipment confirmation lists the shipping agent as it was passed from Order Orchestration, and the tracking number is plain text.

Note:

If a brokered backorder ships on the same day as a warehouse shipment, the shipment confirmation email includes just the tracking number for the brokered backorder. This occurs regardless of whether you consolidate invoices.

See the Shipment Confirmation Email Sample and Contents for more information, and see the OrderShipmentLineDetail for detailed mapping.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Important:

In Order Management System 21.0 or higher, or Order Administration, you cannot select the Consolidated Invoice system control value if it is not already selected. If the system control value is currently selected (set to Y) and you deselect it (change it to N or blank), you cannot then change it back to selected. The option to consolidate invoices will be removed at a later date.

Tracking numbers in customer history API: If Order Orchestration passes the shipping agent and a tracking number, the Detailed Order Inquiry Response XML Message (CWORDEROUT) includes this information provided Order Administration can link the line number, shipping agent, and tracking number from the Order Transaction History messages to the invoice based on date.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Example:

The fulfilling location supplies information on the shipping agent and the tracking number to Order Orchestration, and Order Orchestration passes this information to Order Administration.

Order Administration writes Order Transaction History records such as:

SHIPMENT Ln#: 5 Store Shipped Order

SHIPMENT ----VIA: ABC

SHIPMENT ----TRK#: ABI123

The Order Transaction History records have the same date as the invoice.

The CWORDEROUT message passed through the customer history API includes the tracking information, for example:

<Shipment invoice_nbr="123456" invoice_ship_quantity="1" invoice_ship_date="11292011" invoice_tracking_nbr="ABI123" invoice_ship_via_desc="ABC"/>

Note:

If Order Administration writes the Order Transaction History for the shipment of a brokered backorder on a date that differs from the invoice date, then no tracking information is included in the customer history response. This situation might occur if, for example, Order Administration receives the status update of the shipment before midnight, but the billing async job does not create the invoice until after the job is automatically stopped and restarted, so that the next date is assigned to the invoice.
The tracking information from Order Orchestration is not available as a live link on screens.

Other Order Orchestration orders not eligible: Order Administration does not submit a backordered delivery or retail pickup order to Order Orchestration for fulfillment. In addition, if the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to NEVER or blank, Order Administration does not submit a backordered ship-for-pickup order to Order Orchestration for fulfillment.

Line_locate_eligible flag in the CWORDEROUT message: If the Send B/O to OROB (K08) system control value is selected, the Detailed Order XML Response (CWORDEROUT) message used in the generic order API includes a flag for each order line to indicate whether the order line meets the Rules for Submitting Backorders to Order Orchestration. Even if this flag is set to Y, it is possible that the line cannot be fulfilled as a brokered backorder if, for example, Order Orchestration does not find a location that has the item available.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

The Generic Customer History API also uses the CWORDEROUT message. The message includes the line_locate_eligible flag if the order line is still open. In the case of the generic customer history API, the line_locate_eligible flag might be set to Y even if, for example, the line was already submitted to Order Orchestration, and then returned to normal backorder processing because Order Orchestration did not find a location to fulfill it.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Order Orchestration requires postal code: If the shipping address on a brokered backorder does not include a postal code, the Order Orchestration Order Orchestration rejects it. The Require postal code? flag for the country determines whether a postal code is required. See Setting Up the Country Table (WCTY) for background.

The OBR status remains on each order line that is fully or partially fulfilled through Order Orchestration as a brokered backorder. This status is displayed on the Order Inquiry Detail Screen.

The original backorder reason remains on the order line after fulfillment through Order Orchestration as a brokered backorder. This reason is displayed on the Display Order Detail Screen (Reviewing Order Line Detail). Typically, the backorder warehouse also remains on the order line as well, and is displayed on the Display Order Detail Screen (Reviewing Order Line Detail); however, if a shipment from the warehouse follows the fulfillment through Order Orchestration, the backorder warehouse field is cleared.