Set Up Features, Manage Change, and More for Drop Ship

Set Up Features

Each feature comes predefined as already available except for Fulfill a Customer Order Through Drop Shipment and Handle Landed Cost Charges for Drop Ship Receipts. Each feature includes a predefined job role.

Feature	Setup Required
Analytics with Supplier Source	No
Automate Financial Flow	Yes
Automatic Change Management on Drop Ship Orders	No
Change Drop Ship Orders from Check Availability Page	No
Create Accounts Payable Invoices for Drop Ship Receipts	Yes
Create ASNs for Drop Ship Receipts	Yes
Create Relationship between Selling Business Unit and Requisition Business Unit	Yes
Fulfill a Customer Order Through Drop Shipment	Yes
Handle Landed Cost Charges for Drop Ship Receipts	Yes
Keep the Dates for Your Sales Orders and Purchase Orders Synchronized	No
Order Promising for Drop Ship	Yes
Partial Shipment on Drop Ship Orders	No
Process Accounting for Drop Ship Transactions	No
Report Gross Margins for Drop Ship Orders	No
Report In-transit Inventory for Drop Shipments	No
Use Global Order Promising to Recalculate Dates in Order Management	Yes

This topic uses predefined job roles. You must create your own job roles, depending on your security requirements. For details, see Privileges That You Need to Implement Order Management.

Aggregate Fulfillment Lines

To improve performance, you can aggregate fulfillment lines before you send them to Procurement. The aggregator aggregates change requests for each combination of sales order and purchase order. If you modify a fulfillment line during a drop shipment, then the aggregator sends each combination as a single request to Oracle Procurement. The aggregator sends these details when a time limit expires or when it aggregates a specific number of lines.

If a sales order has a large number of order lines, then the aggregator only aggregates some of the changed lines according to a time limit. This behavior might cause the sales order to become stuck in Order Management because an error happens during the change or the buyer in Procurement makes a change at the same time while the purchase order isn't on hold.

To avoid this problem in a drop ship flow, Order Management comes predefined to use the Aggregate According to Number of Order Lines That Changed profile option, and the aggregator aggregates according to the number of order lines that you change in the sales order's current revision, by default. If you don't want to aggregate according to change, but instead want to aggregate according to time or number of lines, then set this profile option to No, and set a value for the Aggregator Hold Timeout Period in Minutes profile option. For details, see Use Order Profiles to Control Order Management Behavior.

For more, see Actions That You Can Set When Routing Requests to Fulfillment Systems and Aggregate Requests That Order Management Sends to Your Fulfillment System .

Manage Processing Constraints

Order Management uses predefined constraints to prevent you from changing values on the fulfillment line.

Constraint	Description
Constraint. Display Name: Update Fulfillment Line That Drop Ships Constraint Name: DOO_DS_FULFILLMENT_LINE_UPDATE Constraint. Display Name: Cancel Fulfillment Line That Drop Ships Constraint Name: DOO_DS_FULFILLMENT_LINE_CANCEL	Prevents the Order Entry Specialist from updating or canceling the fulfillment line when the purchase request in Oracle Procurement is at the Purchase Order stage. For example, if you attempt to update, then Order Management displays a message. `Order management can't update the fulfillment line because the purchase request in the procurement application is at the Purchase Order stage.` Order Management applies these constraints until the received quantity or invoiced quantity equals the quantity on the order line. These constraints help to keep the sales order in Order Management and the purchase order in Oracle Procurement synchronized with each other. If you disable these constraints but Procurement can't accept an update or cancel because the supplier rejects the change, then you must create and enable your own constraint that prevents the user from updating or canceling the line. If you must allow your users to cancel a fulfillment line that's at the Awaiting Shipping status in a drop shipment, and if DOO_DS_FULFILLMENT_LINE_CANCEL is enabled, then tell your users to cancel the purchase order, wait until Order Management receives the updated status for the purchase order, revise the sales order, cancel the order line, and then submit the revision. If you disable DOO_DS_FULFILLMENT_LINE_CANCEL, and if you haven't created your own constraint that prevents the user from canceling, then the user can use the Order Management work area to cancel a fulfillment line that's at the Awaiting Shipping status in a drop shipment. Procurement will also cancel the purchase order and the purchase requisition for the fulfillment line.
Display Name: Update Fulfillment Line When Purchase Order Isn't Available Constraint Name: DOO_FULFILLMENTLINE_DROPSHIP_PO_RECEIVED_UPDATE	Prevents the Order Entry Specialist from revising a fulfillment line for the drop ship when any of these conditions exist. The purchase order for the line is frozen or is on hold. The quantity received or the quantity billed doesn't equal the quantity shipped. If the quantity that Order Management shipped doesn't match the quantity that Procurement received or billed, then you can't change the value for. Any attribute that's eligible for a constraint. An attachment, extensible flexfield, tax determinant, payment term, or accounting detail. An attribute in Order Management that isn't mapped to Procurement, but that's eligible for a constraint. This condition applies until the quantity that Order Management shipped matches the quantity that Procurement received or billed. Order Management prevents these changes at run time on order lines that it has shipped and on lines that it hasn't shipped. You can change the value of an attribute that isn't eligible for a constraint regardless of whether its mapped between Order Management and Procurement.
Display Name: Cancel Fulfillment Line When Purchase Order Isn't Available Constraint Name: DOO_FULFILLMENTLINE_DROPSHIP_PO_RECEIVED_CANCEL	Prevents the Order Entry Specialist from canceling a fulfillment line for the drop ship when any of these conditions exist. The purchase order for the line is frozen or is on hold. The quantity that Order Management shipped doesn't match the quantity that Procurement received or billed.
Constraint. Display Name: Create Purchase Request Validation Constraint Name: DOO_CREATE_PURCHASE_REQUEST_VALIDATION Constraint. Display Name: Update Purchase Request Validation Constraint Name: DOO_UPDATE_PURCHASE_REQUEST_VALIDATION	If the Scheduled Arrival Date attribute on the fulfillment line is empty, and if it's a drop shipment, then this constraint makes sure: The Requested Arrival Date or the Scheduled Arrival Date on the fulfillment line contains a value. The ordered quantity on the fulfillment line is greater than zero. The Record Set contains the values that the Update Purchase Request fulfillment task requires. If you Don't Use Global Order Promising, and if you: Enable the buyer to manage transportation for the supplier agreement, then Order Management requires the ship date. Don't enable the buyer to manage transportation for the supplier agreement, then Order Management requires the arrival date. Order Management makes sure the required date contains a value when you submit the sales order.
Constraint Name: DOO_UPDATE_EFF_FULFILLMENTLINE_DROPSHIP Display Name: Submit Changes to Extensible Flexfield on Fulfillment Line During Requisition	Prevents the Order Entry Specialist from modifying an extensible flexfield on the fulfillment line when the line is at the requisition stage in Procurement.

Constraint

Description

Constraint.

Display Name: Update Fulfillment Line That Drop Ships
Constraint Name: DOO_DS_FULFILLMENT_LINE_UPDATE

Constraint.

Display Name: Cancel Fulfillment Line That Drop Ships
Constraint Name: DOO_DS_FULFILLMENT_LINE_CANCEL

Prevents the Order Entry Specialist from updating or canceling the fulfillment line when the purchase request in Oracle Procurement is at the Purchase Order stage. For example, if you attempt to update, then Order Management displays a message.

Order management can't update the fulfillment line because the purchase request in the procurement application is at the Purchase Order stage.

Order Management applies these constraints until the received quantity or invoiced quantity equals the quantity on the order line.

These constraints help to keep the sales order in Order Management and the purchase order in Oracle Procurement synchronized with each other. If you disable these constraints but Procurement can't accept an update or cancel because the supplier rejects the change, then you must create and enable your own constraint that prevents the user from updating or canceling the line.

If you must allow your users to cancel a fulfillment line that's at the Awaiting Shipping status in a drop shipment, and if DOO_DS_FULFILLMENT_LINE_CANCEL is enabled, then tell your users to cancel the purchase order, wait until Order Management receives the updated status for the purchase order, revise the sales order, cancel the order line, and then submit the revision.

If you disable DOO_DS_FULFILLMENT_LINE_CANCEL, and if you haven't created your own constraint that prevents the user from canceling, then the user can use the Order Management work area to cancel a fulfillment line that's at the Awaiting Shipping status in a drop shipment. Procurement will also cancel the purchase order and the purchase requisition for the fulfillment line.

Display Name: Update Fulfillment Line When Purchase Order Isn't Available

Constraint Name: DOO_FULFILLMENTLINE_DROPSHIP_PO_RECEIVED_UPDATE

Prevents the Order Entry Specialist from revising a fulfillment line for the drop ship when any of these conditions exist.

The purchase order for the line is frozen or is on hold.
The quantity received or the quantity billed doesn't equal the quantity shipped.

If the quantity that Order Management shipped doesn't match the quantity that Procurement received or billed, then you can't change the value for.

Any attribute that's eligible for a constraint.
An attachment, extensible flexfield, tax determinant, payment term, or accounting detail.
An attribute in Order Management that isn't mapped to Procurement, but that's eligible for a constraint. This condition applies until the quantity that Order Management shipped matches the quantity that Procurement received or billed.

Order Management prevents these changes at run time on order lines that it has shipped and on lines that it hasn't shipped.

You can change the value of an attribute that isn't eligible for a constraint regardless of whether its mapped between Order Management and Procurement.

Display Name: Cancel Fulfillment Line When Purchase Order Isn't Available

Constraint Name: DOO_FULFILLMENTLINE_DROPSHIP_PO_RECEIVED_CANCEL

Prevents the Order Entry Specialist from canceling a fulfillment line for the drop ship when any of these conditions exist.

The purchase order for the line is frozen or is on hold.
The quantity that Order Management shipped doesn't match the quantity that Procurement received or billed.

Constraint.

Display Name: Create Purchase Request Validation
Constraint Name: DOO_CREATE_PURCHASE_REQUEST_VALIDATION

Constraint.

Display Name: Update Purchase Request Validation
Constraint Name: DOO_UPDATE_PURCHASE_REQUEST_VALIDATION

If the Scheduled Arrival Date attribute on the fulfillment line is empty, and if it's a drop shipment, then this constraint makes sure:

The Requested Arrival Date or the Scheduled Arrival Date on the fulfillment line contains a value.
The ordered quantity on the fulfillment line is greater than zero.
The Record Set contains the values that the Update Purchase Request fulfillment task requires.

If you Don't Use Global Order Promising, and if you:

Enable the buyer to manage transportation for the supplier agreement, then Order Management requires the ship date.
Don't enable the buyer to manage transportation for the supplier agreement, then Order Management requires the arrival date.

Order Management makes sure the required date contains a value when you submit the sales order.

Constraint Name: DOO_UPDATE_EFF_FULFILLMENTLINE_DROPSHIP

Display Name: Submit Changes to Extensible Flexfield on Fulfillment Line During Requisition

Prevents the Order Entry Specialist from modifying an extensible flexfield on the fulfillment line when the line is at the requisition stage in Procurement.

If you disable these constraints to meet your business requirements, then you must create your own constraints that prevent Order Management from accepting a sales order revision that Procurement rejects. For example, create a constraint that implements this logic:

If the supplier can fulfill the change when it happens two days or more before the ship date, then reject the change only if it happens within two days before the ship date.

For details, see Processing Constraints.

Add Drop Ship Details to Reports

In Oracle Transactional Business Intelligence, on the Catalog page, click New > Analysis.
In the Select Subject Area dialog, click Order Management - Fulfillment Lines Real Time.
On the Untitled page, in the Subject Areas tree, expand Drop Shipment Details.
Drag attributes from the Subject Areas tree and drop them onto the Selected Columns area.

For details, see Use Reports and Analytics with Order Management.

Reject an Over-Receipt

If the quantity on the advance shipment notice (ASN) exceeds the ordered quantity, then Oracle Receiving will reject the fulfillment request and display a message requesting the user to modify the quantity regardless of how you set the Over-Receipt Action attribute on the Manage Receiving Parameters page in the Setup and Maintenance work area. If receiving rejects the request, you must correct the quantity on the ASN or in receiving.

For details, see General Receiving Parameter Options.

Global Order Promising

Note these points if you use Global Order Promising with a drop shipment.

Promising considers the UPTZ (User Preference Time Zone) when it calculates dates. For details, see Time Zone Differences in Order Management.
Promising displays the scheduled ship date in the time zone where the supplier or supplier site is located.
Promising displays the scheduled arrival date in the time zone where the customer site is located.
Promising searches for and identifies supply according to the local time zone of your organization.

You can use File-Based Data Import to upload the time zones for your supplier sites. You can also specify them in the Global Order Promising work area. If you don't upload or specify them, then Promising uses UTC (Coordinated Universal Time).

Do Other Setups

Here are some other set ups that you might need to do, depending on your drop ship requirements.

Create a separate requisition and purchase order for each order line.
If you use a source system as part of your drop ship flow, then you might need to specify a Drop Ship Validation Organization. You can also set up transit times, and a drop ship plan. For details, see Drop Shipments in Supply Planning.
Set up a promising rule. For details, see Set Up Promising Rules and Sourcing Rules for Order Management.
Use Global Order Promising to recalculate dates in Order Management. For details, see Use Order Profiles to Control Order Management Behavior.