What's new in version 2601.4.0.0

Warehouse Management System  •  Release Note  •  5/27/2026  • 

Enhancements/Modifications

With this release of the Aptean Warehouse Management System extension,

  • The system automatically distributes the scanned quantity across multiple production order lines for the same item when posting production consumption from the WMS scanner, filling each line's remaining need in sequence.

  • The system automatically extracts the quantity from scanned SSCC barcodes that contain GS1-128 Application Identifier AI 37 (Count of items) or AI 30 (Variable count) and applies it to the order line in the WMS scanner. If the scanned quantity differs from the existing quantity, a confirmation dialog appears so that you can accept or reject the scanned value.

  • The system ensures that the correct number of labels is printed for each license plate number (LPN) assigned to a shipment line when you use the Print Label(s) action on the Warehouse Shipment page.

  • You can create, validate, modify, and delete license plate number (LPN) and bin assignments directly in the sub-module template lines within the Ad Hoc movement flow.

  • The system triggers the SSCC notification in the Ad Hoc movement place line through a long-press interaction when the Scan Destination Plate Validation toggle is turned on for the location.

  • This extension has been updated to ensure interoperability with the recent changes in the Aptean Labeling (LBL) extension. To know more, see What's new in Aptean Labeling extension, version 2602.4.0.0..

  • The OnBeforeAdhocMvtTemplateValidate event has been added to the AdhocMvtTemplateCheck139FDW codeunit to allow skipping the template validation during ad hoc movement processing. This enhancement enables greater flexibility by allowing the system to bypass the validation logic and return a handled result without executing the standard template check.

Resolved issues

The following issues have been resolved in this release.

IDDescription
359378The system fails to update the Quantity field value in the warehouse receipt module of the WMS scanner when scanning a barcode that contains both a license plate and a quantity.
366178The system fails to perform bulk move operations for items that are not tracked with license plates in the WMS scanner.
372272The system fails to validate the Allow Over-consumption field value on the Location Setup page during production consumption posting from the WMS scanner. This issue occurs when the Allow Over-consumption field value is set to No, allowing over-consumption of production order components.
362182The system fails to validate the Destination Bin and License Plate Number (LPN) attributes on the Place screen during Ad Hoc movement operations. This issue causes incorrect placement behavior for LPN-tracked and non-LPN-tracked items, including allowing the same LPN to be placed across multiple bins and not enforcing destination LPN validation based on item tracking requirements.
367454The system fails to correctly process Ad Hoc Movement transactions in multiplace and single movement modes for lot-tracked, LPN-tracked, lot and LPN-tracked, and non-tracked items. This issue results in errors and incorrect movement behavior during Take and Place operations, particularly when multiple tracking types are involved in the same or separate movements.
367612The system fails to assign the correct license plate type from the Warehouse Template page to the destination license plate on the movement page during inventory movements. This issue occurs when the destination license plate has no existing content or license plate type, causing the configured license plate type not to be automatically applied.
370464The system displays inconsistent header behavior across WMS screens as the item list page header is built using different logic and structure than the document titles in the document list page.
275627The system fails to correctly determine the destination license plate type during WMS pick flows based on the warehouse template and module configuration. Additionally, the system fails to prompt a default license plate type when multiple license plate types exist and validation is enabled, and it does not automatically assign the license plate type when validation is disabled or only one license plate type exists.
362849The system fails to correctly calculate bin license plate capacity during put-away operations based on the current bin status. When the bin is empty, it does not use the License Plate Type Floor Spaces field value of the license plate type being placed. When the bin contains inventory, it does not use the Put-Away Available Cap. 139FDW field value on the Bin Content page to determine available LP capacity.

The minimum version required for the Aptean WMS app to operate with this release is 1.16.319124.0.