AdvancedSAP ERP / S/4HANAQM / EWM and WM Integration

SAP QM Integration With EWM and WM: Steps and Configuration

Question
sap qm integration with ewm

Also searched as

  • sap ewm qm integration configuration
  • sap qm and ewm integration
  • sap wm qm integration
  • wm and qm steps in sap
  • sap ewm qm integration blog

Short answer

With WM, the goods receipt creates an inspection lot in QM and posts stock to quality inspection; the usage decision then triggers stock postings that the warehouse moves with transfer orders. With EWM, inspections are driven by inspection rules and the Quality Inspection Engine (QIE), tied to inbound delivery documents, and the result updates stock types and putaway.

Applies to: SAP ECC with WM, S/4HANA with embedded or decentralized EWM; names of customizing nodes differ by release

End-to-end process (high level)

  1. 1Activate QM in the plant and set inspection type 01 equivalents for goods receipt in the material master QM view.
  2. 2Post the goods receipt against the purchase order or production order. SAP creates the inspection lot and moves stock to quality inspection.
  3. 3In WM, the goods receipt also creates a transfer requirement. Put the material away to the inspection or interim storage area as your design requires.
  4. 4In EWM, the inbound delivery triggers an inspection document through the inspection rule, and goods are staged or put away to an inspection area.
  5. 5Record results in QE51N and make the usage decision in QA11, or in EWM the inspection result updates through the inspection document.
  6. 6The usage decision posts stock from quality inspection to unrestricted, blocked or scrap via the standard movement types.
  7. 7The warehouse then moves goods to final bins with transfer orders (WM) or warehouse tasks (EWM).

WM and QM: the classic model

In WM the QM inspection lot is created in Inventory Management at goods receipt, and stock is posted to the quality inspection stock type. The warehouse side is driven by transfer requirements and orders, and a storage type for inspection stock helps operators see what is waiting.

When the usage decision is made, QM triggers stock postings such as quality inspection to unrestricted-use or blocked. Those postings create new transfer requirements, so the warehouse can physically move the material after the decision. Mismatches between inventory management stock and bin stock are the main support issue.

EWM and the Quality Inspection Engine

EWM includes an inspection process driven by inspection rules, which decide what to inspect by product, partner or other criteria. The Quality Inspection Engine can run inside EWM or connect to SAP QM, so you choose between a light, warehouse-only inspection and full QM with plans and characteristics.

In the QM-connected design, SAP QM remains the owner of inspection planning, results and usage decision, while EWM owns physical stock and tasks. Configuration includes the inspection rule, the object type for the inbound delivery, stock type mapping and the determination of the follow-up warehouse process.

Common configuration traps

Mismatched stock categories between QM and the warehouse, no putaway strategy for inspection stock, and usage decision codes that post to a stock type the warehouse does not know are the usual issues.

Another is partial inspection: a lot split across several bins or deliveries. Test it. Also test returns, batches, serial numbers and quantities posted before the usage decision, since each can change the posting rules.

Try it here, free

SAP WM to EWM Migration Object Mapping Worksheet

Open full tool

Editable worksheet to map each SAP WM object to its EWM equivalent and track owner, decision and effort for a WM to EWM migration.

Common pitfalls

  • !Activating QM for a material but not for the plant, so no lot is created.
  • !Leaving inspection stock in the same bins as unrestricted stock.
  • !Making the usage decision before the goods are physically in the right area.
  • !Assuming WM and EWM use the same inspection control logic.
  • !Skipping tests with batch-managed or serial-numbered stock.

How an ERP-grounded AI assistant handles this

On premises, a private AI layer can read inspection lots, stock and warehouse tasks together and explain why material is stuck in quality inspection or not yet put away. It does not replace QM or EWM, it answers questions across both read-only so planners stop switching screens.

Frequently asked questions

When is the inspection lot created in a WM warehouse?

At goods receipt, when QM is active for the plant and the material has an inspection type for goods receipt. Stock is posted to quality inspection and the warehouse moves it using transfer requirements and orders.

How does EWM decide what to inspect?

Through inspection rules and the Quality Inspection Engine. The rule uses product, partner and other attributes to create an inspection document for the inbound delivery, which can be handled in EWM or connected to SAP QM.

What happens after the usage decision?

QM posts the stock from quality inspection to unrestricted, blocked or scrap. The warehouse side then moves the goods with transfer orders in WM or warehouse tasks in EWM.

Can I use QM without EWM or WM?

Yes. QM works with plain inventory management by storage location. WM and EWM add bin-level handling on top, and the integration points are about keeping stock and tasks aligned.

Related

Error fix

SAP QM: Inspection Lot Not Created at Goods Receipt

An inspection lot is created only when QM is active for the plant, the material has an active inspection type for the goods movement, and the material carries a QM control key. Check the Quality Management view in MM02, confirm inspection type 01 (purchase order) or 04 (production order) is active, then check QM activation in the plant and the goods movement used.

How-to

SAP QA11 Usage Decision: Make It and Post Stock Correctly

The usage decision (UD) in QA11 closes an inspection lot, assigns a quality score and a UD code such as accepted or rejected, and posts the lot quantity from quality inspection stock to unrestricted use, blocked stock, scrap or return to vendor. The UD is blocked until required inspection characteristics are closed and results are recorded.

How-to

How to Cancel a Usage Decision in SAP QM

SAP QM does not delete a usage decision, you change or reset it. Open QA12 (Change Usage Decision) for the inspection lot, and use the reset or change function if your release and authorization allow it. Stock already posted by the original decision is adjusted by the system, but only if the stock is still where the posting put it.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

Error fix

SAP Short Dump TIME_OUT: Maximum Runtime Exceeded

A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.

AI for ERP

AI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting

AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.

AI for ERP

AI for SAP S/4HANA, Running On-Prem or in Your Private Cloud

Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.

Stuck on SAP ERP / S/4HANA?

Talk to engineers who work inside SAP ERP / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Software