Order Management - ...
 
Notifications
Clear all

Order Management - Default Wahrehouse

0 Posts
1 Users
0 Reactions
10 Views
0
Topic starter

How can I achieve the following customizations in Oracle Fusion Order Management?

Customization 1: Auto-Assign “Ship From Warehouse” Based on Nearest Location (Without Using GOP feature. Want to use GOP for ATP but not for WHS defaulting)

I want to automatically assign the “Ship From Warehouse” based on the nearest warehouse to the customer’s Ship-To Site — instead of relying on GOP sourcing rules where we give ship from WHS rankings.

Example:
Suppose there are five warehouses — North, South, East, West, and Central.
I plan to create a value set (named “State–WHS Matrix”) that maps each customer state to its nearest warehouse. All states of a country nearest North warhouse will be mapped with North Warehouse and simillar for other arehouses too.

So, when a sales order is entered, the system should derive the Ship From Warehouse by checking the Ship-To Site’s state and fetching the corresponding WHS from the “State–WHS Matrix.”
This approach helps reduce transportation and operational costs.

In EBS, I achieved this by:

  1. Creating a value set to define and store the relationship between states and their nearest warehouses.

  2. Developing a custom API to return the appropriate WHS code by passing the Ship-To Site from the sales order header to the “State–WHS Matrix.”

  3. Using this API in Warehouse Defaulting Rules to automatically populate the “Ship From Warehouse.”

Question:
How can I implement this same logic in Oracle Fusion Order Management?


Customization 2: Cross-Warehouse Shipping with Prioritization

In addition to the above, I want to enable cross-warehouse shipping.
If the default warehouse (say WHS1) does not have sufficient stock to fulfill the ordered quantity, the system should automatically check the next priority warehouse (WHS2, WHS3, etc.) until it finds one that can fulfill (partially or fully).
If no warehouse can fulfill the order, then the default WHS (from the State–WHS Matrix) should remain assigned.

In EBS, I achieved this by:

  1. Creating a lookup to define warehouse prioritization (e.g., WHS1 > WHS2 > WHS3...).

  2. Calling the Available to Reserve (ATR) API for each sales order line to check availability.

  3. Comparing the ordered quantity with ATR; if sufficient, assign that WHS. Otherwise, check the next one until fulfillment.

  4. If none can fulfill, assign the default WHS derived from the “State–WHS Matrix.”

Question:
What is the best approach to replicate this warehouse prioritization and cross-shipping logic in Oracle Fusion Cloud OM?

Customization 3: Weekly shipment customers

I want to create weekly shipment calendars and assign them to customers for Scheduling/ATP.

Example:
If Customer ABC has a weekly calendar set to Wednesday, all their orders should ship only on Wednesdays if the total order value exceeds $10K.
If the order value is below $10K, it should follow the inventory calendar instead of the customer-specific one.

In EBS, we achieved this by customizing the ATP hook to:

  • Identify customers with assigned shipment calendars,

  • Dynamically calculate the sales order total value, and

  • Assign the inventory calendar if below $10K, or the customer-specific calendar if above $10K for ATP, scheduled ship date, and arrival date.

 
 

Shopping Cart
Feedback

How would you rate your experience on OracleErpGuide.com?

Poor Amazing
Feedback (optional)

How would you rate your purchase experience today?

Poor Amazing

Where did you first learn about us?