Planned crossdocking occurs during pick release. Oracle Warehouse Management uses release sequence rules to sequence demand sources, and fulfills the demand based on the allocation method that you specify during pick release. When you run pick release, the system uses the allocation method to determine whether crossdock should be planned. If crossdock should be planned, then the system uses the crossdock criteria that you specified to determine the eligible supply. If you did not define the crossdock criteria during pick release, then the system uses the rules workbench to determine the appropriate planned crossdock criteria to use for the demand.
If the system identifies a supply source other than inventory for fulfillment, then it determines the scheduled ship time for the delivery lines, and assigns the scheduled ship date and times to delivery lines as follows:
If an outbound trip exists, then the system bases the departure time on the dock schedule.
If the sales order is associated with a delivery, then the system checks to see whether a carrier exists. If a carrier exists, then the system bases the departure dated on the carrier time and dock door appointment.
If multiple dock door appointments for the carrier exist, then the system selects the dock door and appointment that is closest to the scheduled ship date and time.
If the sales order has a specified ship method, then the system determines the carrier and the exact time for the carrier if the carrier has a dock door appointment for the same day. If multiple appointments exist, then the system selects the appointment that is closest to the scheduled ship time and date.
If none of these conditions apply, then the system uses the departure time as the scheduled ship time for the order; however, if the crossdock criteria allow scheduling flexibility, then the system assumes the order can ship anytime during the day.
To perform planned crossdocking Oracle Warehouse Management:
Determines supply eligibility
Performs pegging
Creates delivery
Links reservation to supply and demand
Assigns crossdock operation plan
Changes delivery line status to Planned for Crossdock
The available supply sources for planned crossdocking are approved PO, ASN, internal requisition, intransit shipments, and material in receiving. You can peg material in receiving only if the material is not associated with a putaway suggestion. To peg material in receiving, you must turn off the organization parameter Pregenerate after Receipt. See Warehouse Organization Setup for more information. When the system identifies the eligible supply lines, it performs the following checks:
The supply and demand items must be the same. You cannot use a substitute item.
If a delivery line is associated with a project and task, then the system does not allow fulfillment across projects and tasks. It considers only material that belongs to the same project and task, or common stock.
Note: If the organization allows fulfillment across projects and tasks, then crossdock planning ignores the project and task information on supply and demand sources.
The scheduled receipt time of the supply must be within the crossdock window. The system automatically assumes that all past-due supply lines are available for crossdocking if they satisfy the past-due supply cutoff. The system assigns scheduled receipt lines a receipt date and time as follows:
If an inbound trip exists, then the system assigns the arrival time based on the dock appointment.
If an ASN exists, then the system assigns the arrival time based on the ASN.
If neither condition applies, then the system assigns the receipt date and time based on the PO promise date. If the crossdock criteria are flexible, then the system assumes the receipt can occur anytime during the day.
After Oracle Warehouse Management creates the eligible supply list, it runs the crossdocking algorithm to perform pegging. It then selects one or more supply sources for crossdocking. If you select the prioritize document on the Crossdock Criteria window, then the system considers the document with the highest priority first.
If a demand is already pegged to a supply, then the system considers only the reserved supply for crossdocking. It uses the crossdock criteria to check whether the supply is eligible for crossdocking and whether the scheduled receipt date occurs within the crossdock window. If the supply meets the criteria, then the system considers the prior reservation and modifies the reservation record to enable crossdocking.
Oracle Warehouse Management creates a reservation that links the supply to an existing demand. For more information about reservations, see Item Reservations.
If the delivery lines are linked to a delivery or crossdock planning run, Oracle Warehouse Management does not create a delivery. If no link exists, then it merges the delivery lines with the outbound crossdock delivery if it occurs within the crossdock window. If the delivery does not occur within the crossdock window, then it creates a new delivery for the crossdocked lines.
After Oracle Warehouse Management creates the delivery, it assigns the appropriate operation plan to the material. For more information about operation plans see Set Up Operation Plans.
After Oracle Warehouse Management pegs the supply, creates the reservation and delivery, and assigns and operation plan, it changes the status of the crossdock lines to Planned for Crossdock. It ignores these lines in future pick releases and planned crossdocking runs.