Table of Contents

WMS handling-unit details in FMS

Warehouse operators record the handling units that physically arrive, move and leave the warehouse. Forwarding planners need the same package information when preparing cargo for a shared container movement. Transferring handling-unit details from WMS to FMS avoids entering the same package numbers and measurements twice.

The transfer updates handling-unit detail lines on the related FMS consolidation and shipment cargo lines. It uses the handling-unit number to find an existing detail, or creates a detail when needed. Package information and dimensions can then be used in forwarding operations and configured reports.

How the transfer works

  1. Record the handling units and their measurements on the WMS document.
  2. Run the configured status transition on that WMS document.
  3. Review the handling-unit details on the related FMS consolidation and shipment, including package type, length, width and height.

The process follows existing document-line relations. It does not find a forwarding shipment merely because its external reference matches the warehouse document.

Configuration hints

  • Configure Update Handling Unit details to Shipment in the WMS document-header status flow. The function is available in codeunit 11191025, WMS Status Functions FMS, function 1.
  • Ensure that the WMS document line is linked to the FMS consolidation cargo line and that the consolidation line is linked to the individual shipment cargo line.
  • Maintain the package mapping required for the WMS carrier/package type to become the FMS Outer Package Type.
  • Test an initial transfer and a repeated transfer, checking the details in both FMS documents before relying on report output.
Important

The transfer can remove existing FMS handling-unit details that are no longer present in the WMS selection. Review the effect on executed cargo events before configuring the status function. The parameters SkipOuterPkgMapping and SkipDelExecCargoEv change package-mapping and executed-event deletion behavior; leave these exceptions unset unless your implementation specifically requires them.

See also