A handling unit (HU) in SAP Extended Warehouse Management is an identifiable physical logistics package: packaging material such as a pallet or carton together with its contents. The HU has its own identifier and can carry information about products, quantities, weight, dimensions and status. Staff can scan or move the package as a unit without losing the link to what is inside it.
Why warehouses represent packages separately from products
A product number describes what the item is; a storage bin describes where stock sits. A handling unit describes the packaged physical unit that a warehouse worker can receive, label, put away, repack or ship. Two identical cartons may hold the same material but have different HU numbers because they are two different physical packages.
That distinction matters when a truck unloads mixed pallets, a worker scans one pallet barcode, or stock is consolidated into a shipping carton. The package may change location or contents while product master data remains the same. HU visibility helps connect a physical action with a traceable system object rather than relying on handwritten labels.
What information belongs to an HU?
An HU normally has an identification number and can hold packaging information, contained materials and quantities, dimensions, weight, status and related logistics information. In scenarios using batch-managed products, batch details remain relevant to the contents. In some processes, a pallet HU contains smaller carton HUs: the outer and inner units are distinct but related.
The identifier matters. A label may use a locally assigned number or a standard such as the Serial Shipping Container Code (SSCC), depending on end-to-end integration and uniqueness requirements. Identification must not be ambiguous during scanning or cross-system communication.
Follow one pallet through goods receipt
A supplier arrives with one pallet carrying twenty-four cases of a finished component. Each case holds twelve units, so the total physical quantity is 288 units. The pallet can be represented by a parent HU; cases may also be represented by inner HUs if the process needs that detail. The design depends on warehouse requirements—not every carton needs its own unique HU.
At receipt, the team compares the delivered packaging with the inbound-delivery expectation. A label is scanned or an HU is created, discrepancies are recorded, and goods receipt and warehouse tasks follow the configured process. A later repack or split should keep the resulting HU and product quantities consistent. If a scanner reads the right barcode but the wrong physical package is present, operational checks still matter.
HU structure: packaging, contents and traceability
Think of the HU as a parent logistics object rather than another product or storage address. Its header describes the package; its items describe what is inside. Nesting can express a pallet made up of cartons, provided that the physical packing agrees with the system hierarchy.
Where handling units add value
- Inbound: receipt, unloading, packing-data capture and putaway of labeled packages.
- Internal moves: tracking packages through storage bins, staging, consolidation or repacking.
- Outbound: picking, packing, loading and handover of shipment-ready logistics units.
- Exceptions: investigating damaged labels, mismatched quantities, incorrect nesting or blocked HUs.
Handling units do not replace inventory quantities, batches or warehouse-task records. They connect that information to a physical package. The degree of HU-managed processing varies by storage type, process design and deployment; do not assume every movement has identical packing requirements.
Controls and decisions for an EWM consultant
Ask whether goods arrive pre-labeled, who creates or verifies HU numbers, how partner labels are mapped, which storage types accept or require packed stock, and whether repacking creates new identifiers. Clarify physical scan points, exception queues, label reprints, parent-child nesting rules and integration to supplying and receiving systems.
Design tests for a correct scan, a duplicate label, a missing carton, a mixed-batch package, a nested HU and a partial repack. The objective is not merely to demonstrate that a barcode reader works; it is to prove that physical inventory, EWM objects and document flow still agree after a real warehouse exception.
Related concepts
Start with the warehouse product master for warehouse-specific product data, storage types for where packed stock is handled, storage sections and bins for physical addresses and activity areas for execution-oriented bin grouping. Return to SAP EWM.