Table of contents
At a glance
What should validation demonstrate for SAP Extended Warehouse Management?
Show that the configured warehouse processes preserve material identity, permitted use and traceable goods movements. Test stock types, batches, quality decisions, shelf life, roles, interfaces and failure handling. Define the system boundary for embedded or decentralised EWM. A warehouse posting or unrestricted-use stock status alone cannot demonstrate legally required batch certification.
- Determine test scope from the deployment model, release and actual integrations.
- Check stock type, storage bin, batch and quality decision separately.
- FEFO sorting and remaining shelf-life checks serve different purposes.
- Test disruptions, RF exceptions and inventory differences across the end-to-end process.
Set the system boundary for embedded or decentralised EWM
SAP Extended Warehouse Management can be embedded in S/4HANA or run as a decentralised system connected to an ERP. SAP also distinguishes older SCM-based EWM releases and warehouse management in Public Edition. Functions and integration paths differ. The cited SAP EWM product help covers S/4HANA 2025 FPS01, February 2026.
Record production releases, plants, storage locations, warehouse numbers and relevant components. Which data are shared or transferred? Where does the authoritative quality status originate? Which extensions change standard processing? Saying that EWM is part of the S/4 project leaves these boundaries unclear.
Embedded EWM can still use messages and separate process states. For direct posting changes, SAP Help distinguishes synchronous goods movement to inventory management from message-based methods. The synchronous option described there is unavailable in decentralised EWM. Test the process your team actually configured.
Define GMP scope by the material decisions affected
This guide covers warehousing for human medicinal product manufacturing. Determine whether EWM affects material identity, a block or the supply of materials to production. A convenience feature can carry a different risk from a rule that decides which stock may be picked.
Annex 11 addresses validation of the application and qualification of the supporting IT infrastructure. The EU index listed the January 2011 edition. Chapter 5 covers quarantine, orderly storage and prevention of mix-ups. Link the configured controls to the operating procedure. A “GMP relevant” label does not establish that link.
The table links process questions to observable evidence. Determine the applicable scope separately for GDP, medical devices and additional FDA requirements. Part 11 applicability depends on the electronic record and its regulatory context. Using SAP alone does not establish it.
| Process | Question | Possible evidence |
|---|---|---|
| Goods receipt | Are material, batch, quantity and required inspection status linked correctly? | A known test receipt, including missing or incorrect data. |
| Quarantine and blocking | Which use is prohibited and which controlled movements remain permissible? | Attempt to pick the stock and perform a permitted movement with the intended roles. |
| Production supply | Does precisely the permitted stock reach the intended supply area? | Traceable production order, batch and quantity reconciliation. |
| Outbound delivery | Are identity, status and remaining shelf life preserved at handover? | Reconcile the warehouse order with the physical container and the confirmation. |
| Physical inventory correction | Is the difference justified and reflected in both inventory systems? | Count, assess, correct and reconcile after posting. |
Distinguish a block, a stock type and a warehouse movement
SAP describes a posting change as a change to the stock key of a quant, recorded in a goods movement document. Physical movement may also take place. Documented examples include quality inspection stock, unrestricted-use stock and blocked stock. Whether a warehouse task is involved depends on the configured process.
A quality decision, assignment to a stock type and a change of location are separate events. Define what a block must prevent, such as production consumption, picking, dispatch or specified posting changes. A controlled move to quarantine may be permitted while use remains prohibited. A test that rejects every movement would then have the wrong expected result.
Stock determination applies configured rules when a warehouse task is created. Test actual picking as well as the stock display. Include tasks created before the block. Which checks must run again and where must staff intervene? The standard stock type name does not answer these questions.
Trace the QM decision to its logistical outcome
For embedded EWM, SAP distinguishes QM integration with and without inspection rules. With inspection rules, SAP describes inspection lots of origin 17. The process covers determining inspection relevance, recording results, making a usage decision and triggering logistical follow-up actions. Partial quantities may have separate decisions and outcomes. These details apply to the integration described.
For decentralised EWM, SAP lists separate configuration steps and QM integration for inspection object types 4 and 5. Identify which system creates the inspection, decision and stock change. Do not assume inspection lot logic from SAP Business ByDesign or another S/4 edition applies because the terminology is similar.
Test fully accepted, rejected and partly accepted quantities. What happens to the remainder and when is picking possible? For finished medicinal products, address certification and release under Annex 16 separately. A usage decision or logistics status can form part of the process but does not automatically fulfil it.
Check batch identity, FEFO and remaining shelf life separately
EWM can use batch numbers and characteristics in inbound and outbound deliveries. SAP describes transferring expiry dates and supplier batches, and distinguishes a batch number assigned externally from a proposed number. The permitted changes may differ. Verify the source and authority of the assigned batch and which batch splits are allowed.
The shelf-life expiration date removal strategy prioritises the earliest date, often called first-expired, first-out (FEFO). A remaining shelf-life check serves another purpose. The cited help describes checks on inbound deliveries that depend on configuration and may allow manual approval. It does not establish automatic blocking of all expired stock or identical behaviour on every outbound delivery.
Specify receipt, storage and dispatch requirements separately. Test boundary dates, missing values and permitted exceptions. The earliest-expiring stock may be ineligible for picking because it is blocked. Test status, batch and sorting together.
Control messages, confirmations and restart
SAP documents asynchronous qRFC messages with sequencing for the delivery-related communication between EWM and S/4HANA described here. Updates can therefore arrive at different times. Assess other paths separately, including certain synchronous goods movements in embedded EWM.
On both sides, check material, batch, unit, quantity, status and document reference. Include interruptions, invalid messages, reprocessing and reversals. Technical delivery does not establish correct meaning. After a unit conversion, the target must represent the same physical quantity.
Assign someone to detect blocked messages, decide what use may continue and reconcile the records after correction. An empty error queue cannot rule out earlier duplicate postings. Check the business document and stock. Use controlled test data and a suitable environment for disruption cases.
Test RF devices and exceptions using the actual operator roles
The SAP radio frequency (RF) framework supports mobile warehouse workflows and barcode input. SAP Learning describes configurable screens, identification and verification fields, and exceptions. A desktop test may miss a differently configured RF workflow. Test the devices, screens and input methods in use.
Scan a different handling unit or the wrong storage bin. Which fields does the application verify and which does it accept as entered? Where applicable, test manual entry as an alternative to scanning. A readable barcode does not establish that the operator chose the right package. Define the expected state after logging back in and resuming a task.
Use representative roles for warehouse operators, the quality function, stock adjustments and administration. Test prohibited as well as permitted actions. Exception codes can trigger further process steps. Permissions and effects must fit your procedure. Testing only with broad administrator privileges can hide the very control that routine operation depends on.
Check identity and meaning in physical inventory and stock migration
SAP describes storage-bin-specific and product-specific physical inventory, several counting procedures, separate items by stock type and ERP integration for posting differences. Treat a quantity correction as a controlled business transaction.
Test a difference with its batch, handling unit, unit of measure and status. Does a blocked partial quantity stay blocked after correcting the count? Does the correction reach the ERP with a traceable reference? Define the assessment, authority to correct and handling of movements in progress. Establish tolerances for your process.
Totals alone cannot establish correct migration. Reconcile stock type, batch assignments, relevant dates and open transactions. A total of 100 units is wrong in business terms if 20 were blocked before transfer and all 100 are now unrestricted. Decide which histories the new system or controlled legacy environment must retain. An import success message does not demonstrate acceptance for use.
Test scenario: the warehouse receives a block late
This worked example has not been executed in an SAP installation. A company uses decentralised EWM and holds 100 units of test batch TEST-01. Following a quality assessment, the authoritative system blocks 20 units. The warehouse test system initially does not process the update.
The remaining 80 units may be used. Verify how the configured solution prevents or controls unauthorised use of the affected 20 units while the systems disagree. Define the block, process interruption or tested alternative control beforehand. The table specifies the example requirement. It does not assert standard SAP behaviour.
For acceptance, record the states before and after the interruption, the relevant documents and what can actually be picked. Reconcile quantities and statuses after reprocessing. The example still has 100 units in total, with 20 blocked and 80 permitted for the specified use. The partial block is a requirement of this example.
| Step | Controlled test action | Expected evidence |
|---|---|---|
| Starting condition | Reconcile TEST-01 with 100 units in both systems. | Same batch and unit, with a traceable initial status. |
| Disruption | Interrupt transfer of the relevant status event in the test process. | The discrepancy is detected and the specified protective response takes effect. |
| New pick | Request the affected quantity for a prohibited use. | No undetected use in breach of the specified block. |
| Open task | Check a warehouse task already created and its continuation on the RF device. | The agreed rule also takes effect for work already in progress. |
| Restart | Correct the cause and process the message under control. | No additional quantity or unjustified status change. |
| Closure | Check stock, documents and the permitted downstream process. | 100 total = 20 blocked + 80 permitted. The evidence agrees. |
Checklist for project participation and continued control
In an SME, handovers and exceptions generally affect the validation effort more than the number of bins. Prepare process maps, roles, batch and stock rules, and representative test data. Warehouse management and QA define expected outcomes. IT and the implementation partner explain configuration and message paths. Include the RF devices used in practice in acceptance testing.
After introduction, assess changes to stock determination, QM integration, roles, interfaces and extensions. Select relevant regression tests and consider known issues in the release. Include relevant incidents and the effectiveness of operating controls in periodic evaluation. Restoration and long-term readability of records are separate tasks.
- Document the deployment model, release, warehouse structure and integration boundaries.
- Identify the authoritative material, batch and quality information.
- Define prohibited uses and permitted movements for each block.
- Link QM decisions, partial quantities and logistical follow-up actions.
- Assess FEFO, remaining shelf life and manual exceptions separately.
- Define testable expected outcomes for message errors, restarts and reversals.
- Test RF screens and alternative input methods using the intended roles.
- Check that inventory adjustments and migration preserve identity, quantity and the meaning of stock status.
- Resolve the handling of deviations, decision authority and operational handover.
- Keep changes, restoration and record retention under control.
Sources: [1]
Project experience and collaboration
Trace a batch through stock type, warehouse activity and confirmation
With warehouse operations, Quality and IT, we follow a known EWM transaction from goods receipt to the intended withdrawal. We compare identity, quantity and quality status after an interruption or changed confirmation. Existing standard evidence may support focused additional testing. Special warehouse strategies and custom interfaces need specific cases. We record which action the system permits and which business decision remains outstanding. Unrestricted-use stock in SAP does not establish that the required batch certification has taken place.
Frequently asked questions about SAP EWM
Must we revalidate all of S/4HANA for SAP EWM?
How do tests differ between embedded and decentralised EWM?
System boundaries and communication paths change. Embedded EWM may share data and use synchronous goods movements for certain processes. Decentralised EWM has separate ERP handovers. Establish where a status originates and when it takes effect. Test failures and follow-up actions. Embedded does not always mean interface-free, and asynchronous communication does not apply to every EWM process.
Does a blocked stock display demonstrate effective quarantine?
The display alone is insufficient. Identify the use the block must prevent and the controlled movements it may allow. Test picking, production supply or dispatch, including open tasks and exceptional roles. Movement to quarantine may be permitted while consumption remains prohibited. Check the outcome against your configuration and operating procedure.
Does a positive QM usage decision release a medicinal product batch?
Not automatically. The usage decision controls the configured inspection and follow-up process. For finished medicinal products, Annex 16 addresses certification and release. Define how that decision becomes logistical availability. Check roles, prerequisites and the stock change that actually takes effect. An SAP status alone does not demonstrate the complete regulatory release process.
Does FEFO automatically prevent shipment of expired goods?
The described FEFO strategy prioritises the earliest expiry or best-before date. Separately define and test remaining shelf life, quality status and exception handling. The cited remaining shelf-life check concerns inbound deliveries. Do not assume the same behaviour at dispatch. Check who can approve exceptions manually.
Which interface failures should we test in EWM?
Choose faults that can change identity, quantity, status or permitted use. Examples include blocked messages, incorrect units, incomplete transfers and reprocessing after an interruption. Select cases for the actual communication path. Check the business documents and stock on each side as well as technical messages. Define the expected response before the test.
Do RF scanners need separate validation evidence?
Cover the RF process as used. This does not require an identical validation file for each scanner. Assess the device type, configuration, screens, scan processing and alternative inputs. Test wrong identifiers, interruption and resumption. A passed desktop test may not cover a different mobile screen or exception.
Why is a quantity check insufficient for stock migration?
Quantities have meaning only with their material, batch, unit and stock status. Total quantity can stay constant while a block is lost. Reconcile the relevant attributes, partial quantities and open transactions. Record how history is handled and accessed. The accountable process owners should assess the evidence for acceptance.
What should the warehouse, QA and IT prepare?
Define material flow, responsibilities and rules for blocks, inspection and picking. Identify releases, extensions, interfaces and representative data. Ask warehouse operators to explain exceptions and RF use. Unresolved decisions and conflicting system states strongly influence the effort. Address them before estimating time or test counts.
Which changes require further testing after go-live?
Assess changes to processes, configuration, roles, data transfers and software. A revised exception code or new stock determination rule can change the route that matters. Select regression tests for the effect and assess existing evidence. A new version does not automatically require a full retest, and an unchanged version does not prove unchanged process behaviour.
Sources and review date
The product features were checked against official SAP sources on 6 October 2026. The EWM help covers SAP S/4HANA 2025 FPS01, February 2026. SAP learning materials explain deployment models and radio frequency (RF) operation. Check other releases, Public Edition and older SCM installations separately. We developed the tables and test batch as planning aids.
- EU GMP Annex 11: Computerised Systems
- European Commission: EudraLex Volume 4
- EU GMP Chapter 5: Production
- FDA: Part 11, Electronic Records; Electronic Signatures – Scope and Application
- SAP Learning: Introducing SAP S4/HANA Extended Warehouse Management
- SAP EWM, Posting Changes
- SAP EWM, Stock Determination
- SAP EWM, Quality Management for Embedded EWM
- SAP EWM, Configuring Quality Management for Decentralised EWM
- SAP EWM, Connection of Delivery Processing to Batch Management
- SAP EWM, stock removal strategy by shelf-life expiration date
- SAP EWM, checking the shelf-life expiration or best-before date
- SAP EWM, communication between EWM and SAP S/4HANA
- SAP Learning, Outlining the Radio Frequency (RF) Framework
- SAP EWM, Physical Inventory
- EU GMP Annex 16: Certification by a Qualified Person and Batch Release
Sources checked: .
Discuss a critical handover in your warehouse
We help your warehouse, quality and SAP teams define a validation scope that connects material movements, quality decisions and the actual SAP configuration.
- 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.

