Cross-Dock Configuration

To allocate orders for cross-dock, two conditions must be met:

  • The order must have the appropriate order type configured;
  • The ordered SKU and quantity must exactly match the contents of the LPN being received.
  • The ordered SKU detail must have the “Required LPN” field populated with the LPN number for the LPN being received.

Step 1: Create the Cross-Dock Order Type

Order types are used to differentiate between cross-dock and non cross-dock orders.
  1. Go to the “Order Type” screen and click the Create button to create a new order type. Make sure that the “Flowthrough” and “Partial allocation” flags are checked.

    Creating a cross dock Order Type
  2. Click “Save”.

Step 2: Adding the RF Screen for Cross-Dock Receiving

The next step is to add a receiving RF module specific to Cross-Dock.

  1. Go to “Screen Configuration”.
  2. Click on “Generate Screens” and select one of the following:
    • “RF-Text: Recv {lpn} Load” if receiving via Loads.
    • “RF-Text: Recv {lpn} Shipment” if receiving via ASNs.
  3. Press “Save” when you have finished.
  4. Once the RF screens are added, the cross-dock specific functionality must be enabled within its parameters. To access the module’s parameters, select the module and click on Details.
  5. Within the parameters, select the “xdock-mode” module parameter and click Edit. Select the appropriate cross-dock mode from the drop-down.

    Selecting a Cross Dock Mode

    Cross Dock Parameter Description

    • None: Cross dock functionality is disabled.
    • LPN Nbr, single or multi sku xdock: Cross dock functionality is enabled for single and multi-SKU LPNs. Cross dock orders do not need to populate the “Required Container Number” in the Order detail record.
    • LPN Nbr Xdock: Cross dock functionality is enabled for single and multi-SKU LPNs. It will only work if its cross dock orders have the “Required Container Number” populated in the Order detail record. *Auto creation of cross dock orders is not possible with this option.
    • LPN Nbr and single-SKU Xdock: Cross dock functionality is enabled for single SKU LPNs. Cross dock orders do not need to populate the “Required Container Number” in the Order detail record.
  6. Click “Save”.
    Note: Cross-dock functionality is supported through the below RF screens based on the configuration of the xdock-mode screen parameter.
    • RF Receive IB Shipment
    • RF Receive IB Load
    • RF Distribute LPN
    • RF Putaway

Company Parameter Configuration impacting Cross-Dock Functionality

Company Parameter Valid Values Functionality Additional Comments
XDOCK_ORD_INV_ATTR_CHECKS
  • Blank(Not configured)
  • EXACT

Controls if LPNs allocated through cross-dock should have inventory attributes matching that on order details.

  • When left blank, the cross-dock allocation logic will ignore inventory attributes.
  • When set to ‘EXACT,’ the LPN’s inventory will have to match all the order detail inventory attribute values for a successful cross-dock allocation.
From the Company Parameters UI, search for the XDOCK_ORD_INV_ATTR_CHECKS parameter key. Click Edit to set the parameter value
From the Company Parameters UI, search for the XDOCK_ORD_INV_ATTR_CHECKS parameter key. Click Edit to set the parameter value.

Xdock Company Parameter

Allocate a Multi-SKU LPN to more than one Order for the Same Destination

Also, with the Cross-Dock parameter (xdock-mode), you can allocate a multi-SKU LPN to multiple orders for the same destination if the company parameter MULTISKU_LPN_XDOCK_ONE_ORDER_ONLY is set to “No.”

From the Company Parameters UI, search for the MULTISKU_LPN_XDOCK_ONE_ORDER_ONLY parameter key. Click Edit to set the parameter value.

Executing Cross-Dock

  1. Before the ASN can be received, it must be checked into a dock door.
    1. If you are using appointments, go to the “Appointment” screen, select the appointment, select a dock door from the drop-down, and click “Check In”.
    2. If appointments are not used, go to the “Inbound Loads” screen, select the Inbound Load, select an appointment, click “Check In”.
    3. Select a dock door from the drop-down, and click “Submit”.

      Checking in Appointments
  2. After the ASN is checked in, you may now receive merchandise with the RF. Go to the “Receive ASN XDock” RF module. Scan the dock door – the Shipment and Trailers, if specified, will auto-populate. If the trailer is not populated, the user must enter the trailer number and press tab to proceed.

    Receiving a Cross-Dock LPN
  3. Scan the LPN number.
    1. If the LPN number is specified in the ASN, Oracle WMS Cloud recognizes the LPN’s contents and displays a message. Press Ctrl-A to proceed.
    2. If the LPN number is not specified in the ASN (blind receipt), the RF will then prompt the user for the SKU and quantity.

      Entering the LPN contents

    Enter the Item Code and quantity. Press Ctrl-E to close the LPN.

  4. If everything was done correctly, the RF will display the message “XDock allocation succeeded”. Press ctrl-A to proceed.

Cross-Dock Receiving with Auto-Order Creation

If some information about the to-be-cross-docked LPN is known beforehand, there is an option to receive such shipments without having to manually create an order. This requires the use of the ASN interface with specific fields populated.

Step 1: Configure the Oracle WMS Cloud for cross-dock

To enable automatic creation of cross-dock orders during receipt, two facility parameters must be modified.

  1. Go to the “Facility Parameters” screen.
  2. Select parameter key “AUTOCREATE_XDOCK_ORDER_TYPE” and click edit. For the value, type in the cross-dock order type code. Click “Save”.
  3. Select parameter key “AUTOCREATE_XDOCK_SHIPMENT_TYPES” and click edit. For the value, type in the cross-dock shipment type code. Click “Save”.
    1. If the shipment type has not been created, go to the “ASN Types” screen and use the Create button to create one.

      Facility parameters necessary for cross-dock

Step 2: Create the Cross-Dock ASN file

Open the “ISSR” interface file.

Populate the basic ASN information. See example below:

Creating the ASN interface file for cross-dock

When creating the ASN file for cross-dock, three fields are required in order for this process to work:

  1. Shipment_type (column H): the ASN type for cross-dock shipments.
  2. lpn_nbr (column D): the LPN number for the cross-docked merchandise. If the LPN number is not known, this method will not work.
  3. recv_xdock_facility_code (column AA): the facility (warehouse) that is receiving the ASN. Enter the appropriate facility code.

    Once the ISSR file is complete, upload it to Oracle WMS Cloud. From the “Input Interfaces” screen, select the “Inbound Shipment” from the drop-down.

  4. Click “Upload Files”, select the ISSR file, and click OK.
  5. Click “Run Interface” to process the file. If everything was done correctly, Oracle WMS Cloud will display the message “Interface completed”.
  6. For receiving, receive this ASN like any other cross-dock flow. During RF receipt, the system will automatically create a cross-dock order for the received LPN.

Cancel Orders after Shipment Verification

Oracle WMS Cloud allows you to cancel unallocated order details. You can cancel order details that have the “Required Container” field populated with the Inbound LPNs that were not received. This is controlled in the Shipment Type UI with the “Unallocated order details to cancel on ASN Verify” mode. The “Unallocated order details to cancel on ASN Verify” mode has the following options:

Unallocated order details to cancel on ASN verify
  • With Matching Container and Shipment: When a shipment is verified, the application cancels unallocated order details that have the “Required Container” field populated with the Inbound LPNs that were not received, provided that the ‘Shipment Number’ order detail field is also populated.
  • With Matching Container Only: When a shipment is verified, the application cancels unallocated order details that have the ‘Required Container’ field populated with the Inbound LPNs that were not received, regardless of whether the ‘Shipment Number’ order detail field is populated or not. This is useful for customers dealing with cross-dock orders that do not have the ‘Shipment Number’ order detail field populated.
  • Do Not Cancel: No unallocated order details are cancelled.