Opportunistic cross docking is supply initiated. When you receive materials against a PO, Warehouse Management System can use those newly receiving material to fulfill an existing demand like a SO (scheduled or backordered), an Internal order (scheduled or backordered),  a WIP Component demand(backordered),  if you enable Opportunistic Cross docking on the Organization Parameters window.

Warehouse Management uses the rules workbench to determine the appropriate crossdock criterion to use for supply. Depending on the eligible demand sources, crossdocking goal, and time fences that you specify in the opportunistic crossdock criteria, the system determines to which demand to crossdock the supply. It then stamps and operation plan on the material. To perform opportunistic crossdocking, the system:

1. Validates supply source
2. Determines eligibility pool
3. Performs pegging
4. Creates reservations
5. Creates delivery

1. Validates supply source
When you receive material, WMS first checks if opportunistic cross dock is enabled or not for the organization. If it’s enabled then system picks up the relevant cross dock criteria to check if there is any available demand for which you can cross dock the received material.

2. Determines eligibility pool
If you can crossdock the supply, then the system identifies the eligible delivery lines for crossdocking based on the crossdock criteria. The available demand sources are scheduled sales orders, backordered sales orders, scheduled internal orders, backordered internal orders, and backordered WIP component demand.

Warehouse Management performs the following checks to determine eligible demand:
• The delivery line item and the received line item are the same.
• The crossdock criteria allow the demand document type.
• If the received items are associated with a project and task, and the organization does not allow fulfillment across project and tasks, then only demand that belongs to the same project and task, or common demand, is eligible for crossdocking.
Note: If the organization allows fulfillment across project and task, then Oracle Warehouse Management ignores the project and task on supply and demand sources for crossdocking.

3. Pegging
After the system creates a list of eligible delivery lines, then the crossdocking algorithm performs pegging and selects one more demands sources for crossdocking. If you select the Document Priority check box, then the system considers the document type with the highest demand first.

4. Reservation Linking
Oracle Warehouse Management creates a reservation that links the demand to incoming supply.

5. Create Delivery
The system merges the delivery lines with an existing delivery if the outbound delivery is within the crossdock window. If no delivery is within the crossdock window, then the system creates a new delivery for the crossdocked items.

6. Opportunistic Crossdock Receipt Validations Crossdocking execution performs the following validations upon receipt:
• Verifies whether supply source is already planned for crossdocking: If the supply source is already planned for crossdocking and has a valid demand source, then the system chooses an operation plan for the item.
• Supply source is ineligible for crossdocking or crossdocking is not allowed: If the supply source is ineligible, or crossdocking is not allowed for the organization, then the system directs you to put away the material.
• Supply source is reserved to a demand source and opportunistic crossdocking is enabled: The system uses the crossdock criteria to validate the supply and demand sources. If both are eligible for crossdocking, then the system identifies the received material for crossdocking, and assigns an operation plan.
• Supply source is not reserved and opportunistic crossdocking is enabled: The system uses the crossdocking criteria to validate the supply source. If the supply source can be crossdocked, then the system identifies the appropriate demand source. The system then uses the crossdocking algorithm to identify the exact demand source.