344349321EWM/SCWM/POST/SCWM/MONbeginner

EWM Posting Changes: Blocking, Re-inspection, Release and Scrapping in the Bin

Stock in an EWM bin changes status without moving: damaged units are blocked, sent to quality, partly released and partly scrapped. Every change is made in EWM, which posts the matching movement types (344, 349, 321, 553) to inventory management.

Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.

Docsnone yet

Demo data

01Damage found in the bin

10 EA in RACK-01-03 have dented housings. They must not be picked.

Business scenario

During a pick, a worker notices 10 EA of RM-1000 in bin RACK-01-03 with dented housings. They are blocked at once; quality checks them; 6 are fine, 4 are scrapped.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

01
Damage found in the bin open in twin
10 EA in RACK-01-03 have dented housings. They must not be picked.
The fastest safe reaction is to change its stock type so picking strategies ignore it.
02
Where to block it? open in twin
The storage location is EWM-managed. Where should the block be posted?
Inventory management only knows totals; EWM knows which bin and which units.
03
Two systems disagree open in twin
A stock-type change posted only in inventory management does not tell EWM which bin or units are blocked. Typically such postings are refused for EWM-managed storage locations.
Changes to EWM-managed stock start in EWM, which then posts to inventory management.
04
Posting change: available → blocked (344) open in twin
10 EA change to blocked in RACK-01-03. Inventory management posts 344.
Picking strategies only take available stock.
05
Send to quality (349) open in twin
Quality takes over: blocked → quality inspection (349). The units stay in the bin.
Quality stock signals that a decision is pending, not that the goods are lost.
06
Release the good ones (321) open in twin
6 EA are only scuffed and released to available stock.
The units can be picked again.
07
Scrap the rest (553) open in twin
4 EA are beyond repair and scrapped from quality stock: ₹4,000 expensed.
Only scrapping changes value — the status changes before it did not.
08
Bin cleaned up open in twin
RACK-01-03: 96 EA available. Four posting changes, one value posting.
Compare with the MM stock type changes process, where MIGO posts the same movement types directly.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

Step	Plant / SLoc	Stock type	MvT	Change
Posting change: available → blocked (344)	1000 / AFS · RACK-01-03	Unrestricted use	344	−10 EA
Posting change: available → blocked (344)	1000 / AFS · RACK-01-03	Blocked	344	+10 EA
Send to quality (349)	1000 / AFS · RACK-01-03	Blocked	349	−10 EA
Send to quality (349)	1000 / AFS · RACK-01-03	Quality inspection	349	+10 EA
Release the good ones (321)	1000 / AFS · RACK-01-03	Quality inspection	321	−6 EA
Release the good ones (321)	1000 / AFS · RACK-01-03	Unrestricted use	321	+6 EA
Scrap the rest (553)	1000 / AFS · RACK-01-03	Quality inspection	553	−4 EA

Accounting impact

Scrapping from quality inspection stock

Typical

Scrap the rest (553)

Dr Expense — scrapping (GBB/VNG)₹4,000
Cr Inventory — raw materials (BSX)₹4,000

Scrapping takes the value out of inventory into a scrapping expense (transaction key GBB, modification VNG, typical).

Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.

Movement type

344Unrestricted → blocked
349Blocked → qualityReversal: 350
321Quality → unrestrictedReversal: 322
553Scrapping from quality stockReversal: 554

Changes the status of warehouse stock in place — blocked, quality, available — and scraps what cannot be used, keeping EWM and inventory management in step.

Transactions & Fiori apps

/SCWM/POST — Make Posting Change for Product
/SCWM/MON — Warehouse Monitor

Warehouse Monitor

Differences by SAP version

Classic WM: transfer postings in IM created transfer requirements for WM.

Configuration

Stock type mapping (F1/F2, Q1/Q2, B1/B2 — typical)
Configuration dependent
Which EWM stock types correspond to unrestricted, blocked and quality in each storage location.
Posting change in place vs with a task
Configuration dependent
Some storage types require the stock to move (e.g. to a blocked area) when its type changes.

Prerequisites

Stock types mapped between EWM and inventory management
Warehouse process type for posting changes

Master data

Storage bins: Whether the bin's storage type allows the new stock type.

Organizational structure

Warehouse EW01
Storage location AFS

Tables

Table	Description
/SCWM/AQUA	Quants with stock type per bin
MATDOC	Mirrored postings in inventory management

Integration

MMEach EWM posting change posts the corresponding movement type.
QMQuality decisions can trigger the changes.

Common errors

“Stock-type change refused in MIGO”
Likely causes: Storage location is EWM-managed
Where to look: Warehouse assignment of the storage location

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

CHECK 1
Posting change
- Is the storage location EWM-managed?
- Does the bin allow the target stock type?

Interview questions

How are stock-type changes made for EWM-managed stock?
As posting changes in EWM (/SCWM/POST or follow-up actions from inspection). EWM changes the quant's stock type, optionally with a warehouse task if the bin does not allow the new type, and posts the corresponding movement type to inventory management.

Quiz

Q1 · Multiple choice

Where do you block stock in an EWM-managed storage location?

In EWM (posting change)In MIGOIn the material master

Q2 · Identify the movement type

Which movement type scraps from quality inspection stock?

553551555

References

SAP SE — SAP Help Portal: Posting Changes in EWM (source)
SAP SE — SAP Help Portal: Stock Types in EWM (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history

Version	Change
1.0.0	Initial version.