Oracle Fusion Design Tool

Location Architecture Advisor

Think about some typical reference locations for this exercise. At the end, review the reasoning and if you want to change your answers, just go back and try again!

Step 1 of 6 17%

1. Geography and operating footprint

How geographically separated are the locations you are comparing?
Closer / more connected Farther / more independent
Would the business normally consider these locations part of the same operational area?

2. Procurement organization

Remember to think future state, not just how things operate today.

How similar are the suppliers and supplier master data used by these areas?
Who performs sourcing and procurement activities?
Do the areas have meaningfully different procurement rules, catalogs, approvals, or buying practices?

3. Inventory Organization boundary

Don't think about warehouses: Inventory Organization relationships can also affect which Deliver-To locations users can conveniently select in Self Service Procurement. It does not have anything to do with actual stocked inventory.

Do the same receiving or delivery teams service both of the reference locations you are imagining?
"Should a user be able to order there" test If you worked on the third floor of the Gym, should the second floor of the Library normally be available as another delivery choice?
Is stocked inventory managed independently between these areas?

4. Receiving and Ship-To design

The Ship-To represents where the supplier is instructed to ship. The Deliver-To represents the user's final internal destination. In some cases, the same location can serve as both, but requesters can only see the Deliver-To when placing a request.

How do supplier shipments normally reach the final destination?
Could the same final destination use different docks depending on the shipment?
Because the supplier delivers directly to the destination, a separate receiving dock may not be needed. The Deliver-To can also serve as the Ship-To location.

5. Location visibility and Location Sets

Location Sets reflect who actually needs access to operational locations rather than making every location visible everywhere for convenience.

Which Requisitioning BUs should normally be able to order to these locations?
Should requesters in other buildings or operational areas be able to find and select these locations? For example, should someone working in the Gym normally be able to select a Deliver-To location inside the Library?

6. Build an example location name

We'll build a location name structure from these answers. Use only the fields that make sense for this location; blank fields will be left out of the recommendation.

Example: ST.MARY, LIB, GYM, NORTH
Example: FL2 or 2
Example: RM123, HR, LAB4
Example: DOCK, MAIN, REC, HAZMAT
Only needed when the same destination can use multiple receiving routes.
Used for the Location Set example, not the Deliver-To name.
Read Original Article
Recommended Design

Your Oracle Fusion Location Recommendations

These recommendations are directional design guidance based on the business relationships you described. Validate the structure against your broader financial, legal, tax, security, and enterprise design.

Requisitioning BU Structure
Procurement BU Structure
Inventory Org Structure

Why the advisor reached this conclusion

Requisitioning BU factors

    Procurement BU factors

      Inventory Organization factors

        Design Correlation Scores

        Separate Req BUs
        Separate Inventory Orgs
        Central Procurement

        Suggested Location Set approach

        Receiving and Ship-To design

        Suggested naming convention

        Final Deliver-To Name
        Ship-To
        Naming principle: Keep the final destination first because that is generally what the requester recognizes. When a separate Ship-To dock exists, append it after a slash.

        Example: MARY-FL2-RM123 / DOCK

        Oracle RSSP consideration