IT systems · Practical guide

SAP EWM: testing handling units and repacking under GxP

Repacking can leave the total quantity unchanged while the batch reference, packaging hierarchy or label no longer matches the contents. Trace the identity of the goods through each packing step as well as the warehouse posting.

Table of contents

At a glance

What should you validate for handling units in SAP EWM?

Test the packing process against known starting data. Include handling unit identity, product, batch, quantity, unit and hierarchy across packing, unpacking, repacking, partial quantities and status or label transitions. Cover scanners, roles, interfaces and interrupted actions. A technically successful handling unit movement does not demonstrate that it was attributed correctly.

Distinguish handling unit from product identity

A Handling Unit captures packaging and associated contents within the logistics process. SAP documents for EWM, among other things, packing, unpacking, and repackaging of products and HUs into other HUs. The functions, applications, and limitations applicable depend on edition, release, and configuration. This guide uses the SAP documentation for S/4HANA On-Premise 2025 FPS01 as a functional reference; your actual implementation will be assessed separately.

A HU identifier is not equivalent to a batch or a medicinal product release status. A pallet may contain multiple packaging units, and a packaging unit may include different products or batches depending on the approved process. Therefore, define the allowable relationships. Validation assesses whether physical content, electronic assignment, and required labeling are consistent. A barcode that is correctly read addresses only part of this question.

Sources: [1] [2]

Clearly describe the authorized packaging process

Define the required packaging levels and permitted mixtures. Describe source HU, target HU, product, batch, quantity, unit, and relevant status information. Extend the process for partial withdrawal, damaged packaging, and reprinting. The rules must be professionally justified and technically or organizationally implementable. A general statement such as "batches must not be confused" is insufficient as an acceptance criterion.

Determine the relevant booking timestamp. When does the content become considered transferred, and what physical actions may the employee perform prior to that point? If goods are already repackaged but the electronic booking fails, a divergent state arises. For such a scenario, a clearly defined exception process is required. Also consider work assignment: one employee performs scanning, another performs packing. The assignment must not be based solely on the unverified assumption that both individuals are always performing the same operation.

Sources: [2]

Example: two batches and one pallet

In this example, Palette P-10 includes cartons K-11 and K-12. Carton K-11 contains 20 units of Charge C-1, while carton K-12 contains 20 units of Charge C-2. Ten units from K-11 are repackaged into a new carton K-13. The intended action is: carton K-11 retains ten units of C-1, carton K-13 contains ten units of C-1, and carton K-12 remains unchanged. The pallet assignment is updated accordingly to reflect the planned workflow.

Perform physical and electronic inspection separately, followed by a combined review. A correct total inventory of 40 units may mask an incorrect batch assignment. The same applies to an unchanged pallet identifier despite changes in internal structure. The inspector is aware of the initial configuration and the required state prior to execution. The following matrix is a methodological suggestion; it does not claim universal SAP lock logic or legal obligation to display the depicted packaging hierarchy.

Own work aid – Example: two batches and one pallet
CaseActionExpected process outcome
Subset 10 units C-1 in K-13 Sources and destinations match individually
Incorrect source Scan K-12 instead of K-11 Mix-up due to process rule oversight
Nesting Assign K-13 to a pallet Proper substructure searchable
Unpacking Remove HU content The goods remain linked to the correct handling unit
Cancellation Booking interrupted during repackaging Physical and electronic status confirmed
Repetition Repeat the order again. No undetected duplicate transfer posting

Sources: [2] [1]

Verify quantities, units, and residual contents

Verify source and target quantities, as well as total inventory, in the appropriate professional unit. Packaging units, pieces, kilograms, and base quantity units may require different conversion factors. Define allowable rounding rules and procedures for handling residual amounts. A difference of zero in an aggregated display does not confirm that each unit has been correctly filled. Compare at the level where errors or mislabeling could occur.

Add edge cases: last unit, partial packages, empty HU, quantity exceeding availability, and an unauthorized combination. Expected rejection or documented exception is derived from the respective process. Verify whether an error message truly prevents a booking or merely serves as an informational alert. For authorized manual corrections, permissions, rationale, and traceable consequences are assessed. A correction pathway must not constitute a convenient bypass of the intended identity control.

Sources: [2] [3]

Verify the scanner, label, and display as a single, integrated chain.

SAP describes the operation at the packaging workstation primarily through mouse, keyboard, or scanner input, depending on available data and configuration. Verify the actual input method being used. A successful mouse test does not validate the correct interpretation of a multi-part barcode. Consider scanner format, prefixes, leading zeros, delimiters, and handling of unreadable codes. The expected identity is independently defined.

When a label is generated following repackaging, verify its alignment with the relevant data version. An outdated print queue may produce a formally legible but professionally incorrect label. Define the reprint process and the handling of obsolete labeling. Also assess whether an order involving multiple units of issue receives the correct output. The label is part of the identity chain; successful technical generation alone does not constitute valid professional evidence.

Sources: [1] [2]

Awarely address status and system boundaries

Unpacking must not alter relevant product or inventory states without detection. Describe which status information is pivotal and how it is synchronized across ERP, EWM, and, if applicable, other systems. A logistical status is not automatically equivalent to regulatory batch release. Verify the precise meaning of each field used and avoid blanket equivalences in test scripts and work instructions.

At interface points, delayed, duplicate, and rejected messages are reviewed. One system may recognize a new HU, while the other continues to display the old structure. Define the actions permitted until clarification is achieved. The retry must preserve the correct technical sequence and prevent duplicate processing. A manual data reconciliation can serve as a transitional control, but requires clear criteria and a designated responsible party. Simply displaying "message processed" does not constitute evidence of a complete and accurate audit trail.

Sources: [2]

Demonstrate history, authorizations, and exceptions

Determine who is authorized to create HUs, modify contents, correct packaging operations, and reprint labels. Test using predefined roles and an unauthorized user. An administrator's access may mask necessary restrictions. Also consider technical users and mobile devices. The identity of the performing employee must remain clearly traceable to the required extent.

Conduct a historical investigation: Originating from which source is the content of K-13? What volume was transferred when, and what correction was subsequently applied? The required documentation format shall be determined based on the process and risk profile. Define which protocols, records, or change documentation are used to support this. A screenshot of the current content does not suffice to establish the historical record. Exceptions must be resolved through technical and scientific evaluation, and confirmed physical integrity must be established prior to uncontrolled continuation of the process.

Sources: [2] [3]

Limit release to the verified process

The closure combines configuration status, permitted packaging rules, test data, results, and operating procedures. Do not list unaddressed variants. A validated partial sample is not a complete justification for any form of nested HUs, automated packaging, or external warehousing integration. The suitability determination must demonstrate which actual operational scope is feasible and which conditions prevail in practice.

Define triggers for re-evaluation: new packaging material, modified barcode, additional unit, new printing service, additional batch mixing, or release change. Retain representative reference cases. Following a change, these cases enable targeted review of affected relationships. Robust validation safeguards professional identity throughout the entire process. It is not exhausted by a successful scanner beep nor by formal compliance of total volume.

Sources: [2]

Project experience and collaboration

Preserve handling unit identity through repacking and restart

With warehouse staff, we prepare known handling units containing different batches and partial quantities. During packing, unpacking and repacking, we compare identity, hierarchy, unit of measure and label reference. A simple structure may need focused tests. Nested HUs, scanners and interrupted steps require additional reference cases. With IT, we follow the resumed transaction to the actual stock balance. A successful HU movement is only part of the evidence.

Frequently asked questions about SAP EWM: Handling Units

Is a Handling Unit the same as a batch?

No. A UH describes a logistic packaging unit associated with a specific content. A batch refers to a technical product or manufacturing reference. The relationships may vary depending on the process. Define and evaluate which products, batches, and packaging levels may be combined within your application.

Is it sufficient to verify the total quantity after repackaging?

No. A correct quantity can mask incorrect source or target assignments. Verify quantity, unit, product, and batch for each relevant packaging unit, as well as the hierarchy. For partial quantities and remaining bound batches, each individual relationship must align with the independently defined target.

Must each scanner be validated separately?

Assess device type, configuration, and integration into the process. Representative testing may be appropriate for similar, controlled devices. Different formats, firmware versions, input pathways, or error handling mechanisms require individual evaluation. A general release based solely on the same manufacturer name is not sufficient.

Can a HU contain multiple batches?

This depends on your approved packaging and quality process, as well as the specific system configuration. This article does not establish a general mixing rule. Review approved combinations and rejected cases. Post-identification and traceability must be maintained for the structure used.

What should happen if repacking is interrupted?

First assess the physical and electronic status. Prevent uncontrolled further processing until content and assignment are once again consistent. Use the predefined correction procedure with appropriate authorizations and documentation. Simple repetition may result in a double booking during partial processing.

Is a HU status considered a regulatory batch release?

Not automatically. Logistic statuses and regulatory release decisions have different meanings and responsible parties. Verify the specific assignment and the lead process. A technical status indication must not be interpreted unconditionally as certification or release of a medicinal product batch.

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. SAP S/4HANA: Packing at the Work CenterReference 2025 FPS01: Packing, unpacking, and repacking of products and nested HUs; verify own workstation. Reviewed on 14.10.2026.
  2. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • SAP S/4HANA validation →

    Support an SAP go-live with evidence your team can defend at audit while keeping validation on schedule. We take a risk-based approach from the template to the interface for greenfield or brownfield projects and existing ECC systems.

Send a project enquiry Customer testimonials →