Allocate and Pick Specific Serial Numbers on an Order

To help support warehouse scenarios where there is a recall or specific serial numbers to be repaired/refurbished, you may need to place sales orders with specific serial number(s). Warehouse Management supports bringing in sales orders stipulating one or more required serials. This capability empowers you to proactively handle product returns and repairs and fulfill inventory with specific serial number as stipulated on the order detail.

Only Deallocate on Short Flag

When the only_deallocate_on_short flag is set to yes, the system now allows interfacing an order with required serial number(s).

When you edit the order type on the order with required serials, with another order type (that has this flag set to False), the system will display an error when you save.

Interfacing Required Serial Numbers

Now, when external systems pass an order with one or more order lines and the corresponding required serial numbers are also passed, the system will populate the required serial numbers in the Order Inquiry UI.

Note: Required serial numbers are supported only in JSON format.

Associate Required Serial Number

From the Order Header -> Details UI, you can add and associate required serial numbers for corresponding order lines (when using a serialized item with end to end tracking) using the new Required Serial Number column and hyperlink.

• The Required Serial Number hyperlink is enabled only if:
  • the underlying company tracks serials end to end.
  • the selected movement request detail item has required serial number tracking enabled.

• The application displays an error message when you add new serial numbers or edit the serial number for corresponding movement request detail.

Required Serials During Allocation

During a FULL LPN allocation flow, Wave allocation will consider order details with required serial number first, before allocating the order lines that have the required serial number(s) not populated for the following allocation types:

• Full LPN
• LPN Units - Allocation Distribution Mode is 'No Distribution'

Regarding Serials during a Picking Wave Allocation, note the following guidelines:

• Picking Wave supports Full LPN Allocation’s flow and Unit Picking Allocations flow only for orders that include required serials.

• Order details with required serial numbers will be allocated first compared to orders without required serials numbers.

• If for any reason the order quantity and the required number of serials do not match (number of serials is less than the order quantity) then do not consider the order for allocation.

• Distribution flows will be blocked for orders that contain required serial numbers.

Note: If Orders without required serials and orders with required serials are part of different waves, the application could potentially pick up inventory with serials that are reserved for a different order. This behavior needs to be considered when orchestrating the flows with required serial numbers.

Picking

With the allocation of required serials, the user needs to know the specific serials that were allocated for the order and that it needs to be specifically picked against that order.

You can then specify the quantity to pick for each LPN. The following Picking transactions now support required serials:

• Pack LPN (rf.outbound.cwrfpacklpn)
• Pack NC (rf.outbound.cwrfpackncactiveorder)
• Direct Allocation (rf.outbound.cwrfdirectallocation)
• Pick Confirm API

Wave Template Flags 'Cancel Unallocated' and 'Cancel Partly Allocated'

The following table shows the behavior for removing serials depending on the following flags:

Flag	Behavior
Cancel Fully Unallocated and/or Cancel Partially Unallocated	When set on the Wave template, the system removes the unallocated serials from the order detail along with the other existing updates related to cancelling unallocated order details.
Cancel partially unallocated and Cancel fully unallocated	For Movement Request, when set on the replenishment template, when the order details are cancelled, the required serials not allocated for that detail will be removed.

Replenishment

Similar to the picking wave, during the replenishment wave also, first, the order details with the required serials should be considered for replenishing the destination location, then the other order details without required serials populated, are considered.

Order details for required serials will now be considered during:

• Standalone Replenishment - (REPLEN_CS_PK_UNITS mode, UOM = Units)
• RF Distibute Replenishment - (rf.inbound.cwrfdistlpnreplen)

Ignore Serials During Wave During Replenishment with a Picking Flow

The system now ignores the order details with required serials in the wave for replenishment allocations.

• The system also ignores the inventory containing the required serials in the LPN/location, i.e., for the required serials of the order details within this wave

• Regardless of the replenishment mode selected, (for example, Full LPN, Cases Replenishment or Consolidate Replenishment) the above behavior applies when replenishment with picking is configured.

The following table details the additional transactions that will ignore serials and lists the associated scenarios:

Transactions	Scenario
Consolidation Replenishment (Mode 3) NOTE: Consolidation and Distribution flag is set to true.	System ignores the order details with required serials, in the wave, for replenishment allocations.
RF IBLPN Pick for Consolidation Replenishment	While picking for the order without a required serial, the system errors out, when user scans a required serial. (safety check). While picking for non required serials, substitution does not steal the inventory with required serials for an Order >Created and < Shipped status.
Consolidation Distribution (Allocation Distribution Mode for Consolidate and Distribute)	System ignores the order details with required serials, in the wave, for allocating against the order.
Distribution with and Without Residuals (Allocation Distribution Mode as Distribution with residuals (or Distribution, no residuals)	For these two modes of distribution, the order details with required serials are ignored for allocation.
RF Repack OBLPN	RF does not allow scanning a 'From OBLPN' linked to required serial allocations. While picking for the order without a required serial, system errors out, when user scans a required serial.
Xdock	The system checks if the order has required serial numbers present/specified, then should skip performing XDOCK to those order details.
Distribute LPN	The system checks if the order has required serial numbers present/specified, then should skip performing distribution to those order details.

Additional System Checks for Required Serial Numbers

For the following transactions, the system will check to see if the serial required for any order has a required serial on it:

• RF Cycle Count (rf.inbound.cwrfcyclecountlocn and rf.inbound.cwrfcyclecountiblpn)
• RF Pick Cart (rf.outbound.cwrfpickcart)
• RF Outbound Audit (rf.outbound.cwrfauditlpnplt)
• RF Pack OBLPN from IBLPNs (rf.outbound.cwrfpackoblpnfromiblpn)
• RF Pick IBLPN (rf.outbound.cwrfpickiblpn)
• RF Split IBLPN (rf.inbound.cwrfsplitcntr)

Note: If there is a required serial, the system will display an error message. If there is not a serial number, the transaction will proceed.

Substitution - Allocations with Required Serial Numbers

For allocations with required serials numbers, the system will prevent substitutions in the following transactions:

• Pick Confirm API (Units)
• Full LPN Transactions (RF Pack OBLPn)
• Non-cubed Picking transactions (RF PackNCActive Order)
• Full LPN API
• RF - Replenish Full LPN (rf.inbound.cwrfreplenlocn)