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
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.

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 you 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.