5/25/24, 7:51 AM Document 2204415.

1
Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.

Crossdocking Overview Setup And Troubleshooting In Warehouse Management (Doc ID

2204415.1)

In this Document

Goal
Solution
Introduction
Types of Crossdocking
Crossdocking Planning & Execution
Setup And Process flow
Demonstration
Implementation Considerations
Troubleshooting
Diagnostics Scripts
Documentation
Webinar/Presentation
References

APPLIES TO:

Oracle Warehouse Management - Version 12.1.3 and later

Information in this document applies to any platform.

GOAL

The purpose of this document is to provide overview of Crossdocking features available in WMS.

SOLUTION

Introduction

In a warehouse, the traditional material handling process is to first receive the material and store into an inventory area. Later,
when demands are placed, operators pick the material from storage area and bring it to shipping area for shipment.
To achieve faster flow-through times and optimize warehouse resources, warehouses use a different process called
Crossdocking.

So what happens in Crossdocking is that material is received in the receiving docks and matched to outbound demands. Then
the received material is moved directly to the shipping docks for shipping, bypassing the inventory storage and
pick retrieval processes. The matching of outbound shipments to scheduled receipts could be done minutes, hours, or even
days in advance. On the other hand, some times, this matching of demands to received material could also be done
at the time of receipt.

Types of Crossdocking

Oracle Warehouse Management supports following two types of Crossdocking

Planned Crossdocking

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=f5wcgj7lq_256&id=2204415.1 1/5
5/25/24, 7:51 AM Document 2204415.1
Planned Crossdocking involves pre-allocation of an incoming supply source to a given demand source. It is a demand driven
planning. When demands are placed, system checks to see if there are any planned inbound material
that will be coming to the warehouse around the same time when the outbound shipments are required to be shipped to
satisfy that demand. If it finds any such matches based on business rules, system plans to use
those incoming supplies for this demand. Later, when material arrives at the warehouse, it is moved directly to the shipping
area for fulfilling this demand. Planned crossdocking of supplies to demands can be created based on business rules
and this process is triggered during the pick release process

Opportunistic Crossdocking

Opportunistic Crossdocking involves dynamic allocation of incoming supply source to a demand source on receipt. The
assignment is ‘postponed’ until the material is received into the warehouse.
As compared to planned Crossdocking, opportunistic Crossdocking is supply driven. Here, planning is done at the time of
material receipt.

When material arrives at the warehouse, system checks to see if there are any demands that need to be fulfilled now that
could be fulfilled using this material, based on business rules. If it finds any such matching, then the received material is
moved directly to the shipping area for fulfilling this demand. In this release, opportunistic cross docks of supplies to demands
can be created based on business rules and this process is triggered during the receipt of material.

Crossdocking Planning & Execution

This functionality can be divided into 2 parts – Crossdock Planning & Crossdock Execution. This is applicable for Both
Planned and Opportunistic Crossdocking types

Crossdock Planning

Here are some of the major components of Crossdock Planning. .

-Define Crossdock criteria which represent the business rules on which the system makes Crossdocking decisions.
-Determine which supply and demand documents are eligible for Crossdocking, and the relative priority of these documents
-Define Crossdocking goal helps us determine the exact supplies or Demand from that list of eligible documents that will be
used for Crossdocking

Crossdock Execution

Here are some of the major components of Crossdock execution

- On Crossdock execution, the delivery line is either merged with an existing delivery or a new delivery is created for the
delivery line.
- The final staging lane can be determined on the basis of a series of rules
- During crossdock execution , the inbound operation plan uses defined outbound consolidation plans to determine where to
drop the material.
- Crossdock tasks are created at receipt that can be managed from the warehouse control board

Setup And Process flow

Crossdock Planning

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=f5wcgj7lq_256&id=2204415.1 2/5
5/25/24, 7:51 AM Document 2204415.1

Crossdock Execution

Demonstration

For Planned Crossdocking Demo, Click Here

Opportunistic Crossdocking Demo, Click Here

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=f5wcgj7lq_256&id=2204415.1 3/5
5/25/24, 7:51 AM Document 2204415.1

Implementation Considerations

While planning for crossdock, system first tries to use existing reservations and checks if it can crossdock them.
For PJM organizations, system matches the project and task for crossdock planning.
Crossdocked demand lines can not be shipped using “direct ship” process.
Crossdocking is not supported for
lot indivisible or non-transactable or non-reservable items
Drop ship purchase orders
Documents with expense or shop floor destinations
If a demand is partially reserved to a WIP supply, then it can only be crossdocked to that WIP supply. If one doesn’t
want this restriction, then one can use a stub API - WMS_XDOCK_CUSTOM_APIS_PUB() to override this behavior.

Below are the list of default behavior that customers could modify using stub API –

1. Prioritization of supplies and demands for planned crossdock and opportunistic crossdock, respectively. For this
customer can choose the crossdock goal as “custom” and implement the stub to incorporate their own logic.
2. Crossdock criteria selection
3. Override expected supply arrival and expected demand departure time
4. Override the restriction of not allow crossdocking for a demand that is partially reserved to a different WIP supply

To implement the stub, customers can use the following package – WMS_XDOCK_CUSTOM_APIS_PUB()

Troubleshooting

Incorrect/Missing Setup

Here are few setups which need to be checked when facing issues during Planning/ Execution

Verify Crossdock Criteria Setup

For Crossdock Time Fence validation, List of Eligible Supply/Demand Sources
Verify Rules workbench setup
Verify Org Parameters setup (for Opportunistic Crossdocking)
Verify Default Staging Subinventory/Locator Setup
Verify WMS Pick/Putaway Rules Setup
Verify Operation Plan related Setups.

Error/Warning

The following are the key Debug Log files which will be useful while troubleshooting Crossdocking Issues with errors/warnings

Planned Crossdocking Errors

I. Pick release concurrent request Log with INV Debug Enabled.(For Planning Issues)
II. Pre-generate Putaway Suggestions concurrent request Log with FND/INV Debug Enabled (Execution Issues )

For Opportunistic Crossdocking

I. Pre-generate Putaway Suggestions concurrent request Log with INV/FND Debug Enabled (Planning and Execution
Issues)

Diagnostics Scripts

Here are the list of Diagnostics scripts which will be useful to troubleshoot Crossdocking issues

<DOC ID 2038363.1> - Sales Order Analyzer

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=f5wcgj7lq_256&id=2204415.1 4/5
5/25/24, 7:51 AM Document 2204415.1
<DOC ID 133464.1> - Sales Order Diagnostic Script

<DOC ID 463602.1> - Item Diagnostics Script DOC ID 276207.1 - Diagnostics: Apps Check Concurrent Program

<DOC ID 1913250.1> - LPN Diagnostics Run from Desktop>

<DOC ID 463636.1> - Inventory Purchase Orders Data Collection Test

Documentation

WMS User Guide - Click here

WMS Implementation Guide - Click here

Webinar/Presentation

Webinar Recording URL - Click here

Webinar PPT Slides - Click Here

REFERENCES

NOTE:430935.1 - How to Setup and Diagnose WMS Planned and Opportunistic Crossdocking Functionality
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=f5wcgj7lq_256&id=2204415.1 5/5