Stock Type Changes: Quality Release (321), Blocking (344/343) and Re-inspection (349)
The same pallets change status without moving an inch: quality inspection stock is released to unrestricted use (321), damaged goods are blocked (344) and sent back to inspection (349). None of these postings changes the stock's value.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01Goods waiting in quality inspection
50 EA of RM-1000 sit in quality inspection stock. They are valuated but cannot be used.
Business scenario
50 EA of RM-1000 were received into quality inspection. The inspector accepts them. Later a forklift damages 10 EA in the store, which are blocked and then sent for re-inspection.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
Goods waiting in quality inspection open in twin
50 EA of RM-1000 sit in quality inspection stock. They are valuated but cannot be used.
It keeps goods out of production and sales until someone has checked them.
- 02
The inspector accepts the goods open in twin
The goods passed inspection. Which movement type releases them?
The movement type records exactly which status changed, which matters for audit and reporting.
- 03
Wrong source stock type open in twin
343 takes stock from blocked. There is no blocked stock, so SAP refuses: the quantity is not available in that stock type.
The posting checks the source stock type, so choosing the wrong pair fails with a deficit error.
- 04
Release from quality (321) open in twin
Quality → unrestricted: 50 EA. Unrestricted 500 → 550 EA. No accounting document.
The goods may now be issued to production or sold.
- 05
Damaged goods are blocked (344) open in twin
A forklift damages 10 EA. They are blocked so nobody uses them: unrestricted → blocked.
Blocking stops the damaged units being picked or consumed while their fate is decided.
- 06
Send for re-inspection (349) open in twin
Quality wants to check whether the 10 EA can be repaired: blocked → quality inspection.
The goods are now formally under inspection; the next step is 321 (release) or a scrapping (555 from blocked, 553 from quality).
- 07
Same pallets, different status open in twin
Unrestricted 540, quality 10, blocked 0. Total stock and total value never changed.
Stock types control what stock may be used for. Value only changes when ownership, material or valuation area changes.
SAP documents
Stock impact
| Step | Plant / SLoc | Stock type | MvT | Change |
|---|---|---|---|---|
| Release from quality (321) | 1000 / 0001 | Quality inspection | 321 | −50 EA |
| Release from quality (321) | 1000 / 0001 | Unrestricted use | 321 | +50 EA |
| Damaged goods are blocked (344) | 1000 / 0001 | Unrestricted use | 344 | −10 EA |
| Damaged goods are blocked (344) | 1000 / 0001 | Blocked | 344 | +10 EA |
| Send for re-inspection (349) | 1000 / 0001 | Blocked | 349 | −10 EA |
| Send for re-inspection (349) | 1000 / 0001 | Quality inspection | 349 | +10 EA |
Accounting impact
No accounting impact in the steps shown.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
- 321Quality inspection → unrestrictedReversal: 322
- 343Blocked → unrestrictedReversal: 344
- 349Blocked → quality inspectionReversal: 350
Controls what stock may be used for — consumed, sold, or held back — without moving it or changing its value.
Transactions & Fiori apps
- MIGO — Transfer posting
- MMBE — Stock overview by stock type
- QA11 — Record usage decision (QM)
- Transfer Stock — In-PlantAvailability depends on release and scope
- Stock — Single Material
Differences by SAP version
MB1B and MIGO post transfer postings; MB1B is not available in S/4HANA.
MIGO or Fiori apps; stock types are stored in MATDOC and read through compatibility views.
Fiori apps such as Transfer Stock — In-Plant.
Configuration
QM active in procurement
Configuration dependentDecides whether quality stock is released through usage decisions or MIGO.
Stock type in the material master / PO
Configuration dependentPost to inspection stock indicator decides whether receipts land in quality inspection.
Prerequisites
- Stock in the source stock type
- For QM-managed materials, an inspection lot and usage decision
Master data
- Material master (purchasing / QM views)
- Post-to-inspection indicator and inspection setup.
Organizational structure
- Plant 1000
- Storage location 0001
Tables
| Table | Description |
|---|---|
| MARD | Storage location stock per stock type (compatibility view in S/4HANA) |
| MATDOC | The transfer postings |
Integration
- QMUsage decisions post 321 (or scrapping/blocking) automatically.
Common errors
“Deficit of quality inspection stock”
Likely causes: Wrong source stock type chosen; Stock already released
Where to look: MMBE stock types · Material documents
“321 not allowed in MIGO”
Likely causes: Material is QM-managed with an open inspection lot
Where to look: Inspection lot (QA32) · QM view of the material
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
Transfer fails
- Is there stock in the source stock type?
- Is the material QM-managed?
Interview questions
Do stock type changes create accounting documents?
No, not within one plant and material: quality, blocked and unrestricted stock are all valuated own stock, so moving between them changes status but not value. Only changes of material, valuation area or ownership post accounting documents.
Name the movement types between unrestricted, quality and blocked stock.
321/322 quality ↔ unrestricted; 343/344 blocked ↔ unrestricted; 349/350 blocked ↔ quality inspection. The second number of each pair reverses the first.
Quiz
References
- SAP SE — SAP Help Portal: Transfer Postings — Stock Type Changes (source)
- SAP SE — SAP Help Portal: Quality Inspection Stock (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. |