- Home
- Modules
- SAP QM
SAP QM: the module that decides if stock can be used
Quality Management, explained for users and for consultants from other modules.
010000004711Barley malt · Origin 01 · Goods receiptPO 450001234525,000 KGRELRRECQE51N- Moisture
4.3 %· max 5.0Accepted - Protein
10.9 %· 9.5–11.5Accepted - Foreign matter
0.3 %· max 0.5Accepted - Germination · 3-day testOpen
Overview
What QM is, if you have never worked with it
SAP QM, Quality Management, is the part of SAP that checks whether materials and products meet their specifications, records what was found and decides whether the stock can be used. It plans the inspections, creates an inspection lot when goods arrive or are produced, records the results, handles complaints in quality notifications and closes each lot with a usage decision that moves the stock.
This page is for the people who work around QM without being QM consultants: key users in the warehouse, purchasing, production and the lab, and FI, CO, MM or SD consultants who keep meeting inspection lots and stock that nobody can use. It follows one inspection lot from the goods receipt to the stock posting, shows what each step posts in the books and lists the transactions worth knowing.
- SAP ECC 6
- SAP S/4HANA
- SAP S/4HANA Cloud
QA32QE51NQA11Use the User | Consultant switch at the top of the page to show or hide the technical layer: Customizing, tables and the settings behind each step.
Quality at every step of the chain
Lots can start at a goods receipt, during production, at a stock transfer, at a delivery to a customer, in plant maintenance or on a timer for stored batches. SAP predefines these triggers, called inspection lot origins.
Source: SAP Help, inspection typeStock that waits, already on the books
Goods under inspection sit in quality inspection stock: valuated, so they are already in inventory, but not available for withdrawals in the standard system. What lets them out is the usage decision.
Source: SAP Help, stock categoryQuality has a price
ASQ says many organizations have quality-related costs as high as 15 to 20 percent of sales revenue. QM records the inspections, defects and decisions behind those costs, and QM orders can collect them in CO.
Source: ASQ, cost of quality
Who QM talks to
QM rarely works alone. An inspection lot is born from another module’s document and its decision lands in another module’s stock, invoice or report, which is why a “quality problem” so often reaches the MM, FI or CO desk.
- MMProcurement and stockGoods receipts create lots; quality info records control suppliers; stock waits in quality inspection.
- PP / PP-PIProductionIn-process inspection (origin 03) and goods receipt from production (origin 04).
- SDCustomersDelivery inspections (origins 10, 11), certificates of analysis and customer complaints (Q1).
- PMMaintenanceCalibration orders for test equipment create inspection lots when they are released.
- EWMWarehouseEWM inspections (origin 17) and warehouse defects that can block stock in storage bins.
- FI-APSupplier invoicesPayment block I while the goods receipt inspection is not OK.
- COCost of qualityQM orders collect inspection costs and nonconformity costs such as rework and scrap.
- Batch managementBatchesRecurring inspections (origin 09) and batch characteristics updated by the usage decision.
Master data
What must exist before the first inspection lot
An inspection only happens if the material is set up for it, and it only checks what the planning data says. Read the chain from the top: the QM view switches inspection on, the inspection type says how, the plan or specification says what, and the sampling rules say how much. Pick an object to see what it does and why people outside QM should care.
Material master
QM view and inspection setup
The QM view is kept per plant and says whether, when and how a material is inspected. Its inspection setup lists the inspection types for the material; a type only creates lots once it is both assigned and active. The same view holds the QM in procurement indicator and its control key, which apply to the whole client.
Example: Barley malt, plant 1000: inspection type 01 active, post to inspection stock, inspect with task list.
Why it matters outside QM
This is where stock is decided at the goods receipt: with an active, stock-relevant inspection type, the receipt goes to quality inspection stock instead of unrestricted-use stock. Same value in inventory, but nobody can consume it.
WhereMM02QA08QI05
The transactions for each object are in the Consultant view.
Customizing
Inspection lot origin and inspection type
The origin is fixed by SAP and says what triggered the lot: 01 goods receipt for a purchase order, 04 goods receipt from production, 08 stock transfer, 09 recurring inspection and so on. Inspection types are defined in Customizing and assigned to an origin; one origin can have several, such as 01 for regular receipts and 0101 for a model (first-article) inspection.
Example: Origin 01 → inspection types 01, 0101 and 0130 (external processing).
Why it matters outside QM
Only origins 01, 04, 05, 08 and, under conditions, 09 are stock-relevant, so only their lots hold stock in quality inspection. Manually created lots never are.
WhereQCC0
The transactions for each object are in the Consultant view.
Quality planning
Inspection plan or material specification
An inspection plan lists operations and characteristics for one plant and one lot-size range, with work centers, inspection methods and dynamic modification. A material specification holds only characteristics and is valid in every plant. Both can be active; when a characteristic is in both, the specification wins, but SAP recommends choosing one per inspection.
Example: Plan for barley malt in plant 1000: one laboratory operation with four characteristics.
Why it matters outside QM
Only inspection plans can capture QM costs and use work centers. When no valid plan exists for the plant and lot size, the lot waits in status PREQ.
WhereQP01QP02QP03QS61
The transactions for each object are in the Consultant view.
Quality planning
Master inspection characteristic
What is checked. A quantitative characteristic, such as density or moisture, has tolerance limits; a qualitative one, such as color, is judged by its attribute and can use a catalog of codes. It is defined once, reused in many plans and specifications, and each result is valuated as accepted or rejected.
Example: MOISTURE: upper limit 5.0 %, recorded with one decimal.
Why it matters outside QM
Characteristics gate the usage decision: every required characteristic must be finished (status 0, 4 or 5) before anyone can accept or reject the lot and release the stock.
WhereQS21QS26QS27
The transactions for each object are in the Consultant view.
Quality planning
Sampling procedure
How much of the lot is inspected and how it is judged: a fixed sample, a percentage, 100 percent or a sampling scheme. Its valuation mode decides whether a characteristic is judged by nonconforming units or defects, by its attribute or by the mean value within tolerance.
Example: Fixed sample of 5 units, valuated by nonconforming units.
Why it matters outside QM
Bigger samples mean more destructive testing, and destructive samples leave stock with movement type 331, an expense in FI.
WhereQDV1
The transactions for each object are in the Consultant view.
Quality planning
Dynamic modification and quality level
Rules that change the inspection scope with the history: normal, reduced, tightened or skip. The quality level keeps the stage reached for a material and supplier (or customer, or manufacturer) and decides the sample of the next lot. A skip stage has a maximum duration in days; after that, the next lot is inspected again.
Example: Four accepted lots: normal → reduced. One rejection: back to normal.
Why it matters outside QM
This is how QM cuts appraisal costs: good suppliers earn fewer inspections, poor ones get tighter checks.
WhereQDR1QDR2QDR3
The transactions for each object are in the Consultant view.
Catalogs
Catalogs and code groups
Standard codes that keep defects and decisions comparable: defect types (catalog type 9), defect locations (E), causes (5), tasks (2), actions (8) and usage decisions (3). Codes sit in code groups, and selected sets offer users only the allowed ones.
Example: Defect type “too long” in code group LENGTH.
Why it matters outside QM
Coded defects and causes can be counted and ranked, so quality costs can be traced to causes and suppliers instead of free text.
WhereQS41QS51
The transactions for each object are in the Consultant view.
Procurement
Quality info record
One record per plant, supplier and material. It can release a supplier only up to a date or a quantity, block it after quality problems, model release stages such as first article and series supply, and switch to source inspection at the supplier. Certified suppliers can skip the goods receipt inspection.
Example: Supplier 300145: released until 31.12.2026, series supply.
Why it matters outside QM
With QM in procurement, purchase orders are refused when the release is exceeded, and the control key can block the supplier’s invoice for payment while the goods receipt inspection is not OK.
WhereQI01Manage Quality Info Records
The transactions for each object are in the Consultant view.
Sources: SAP Learning, describing the required master data, enhancing the material master, implementing quality control in procurement, setting up dynamic modification and configuring quality notifications; SAP Help, inspection type and inspection characteristic.
The QM process
Follow one inspection lot from the goods receipt to the stock
Eight steps of the classic goods receipt inspection, the most common QM flow; production and delivery inspections follow the same pattern. Pick a step to see what happens, where you see it, what it posts in the books and, in the Consultant view, what sits under the hood.
Step 1 of 8 · What happens
A goods movement or a job triggers the lot
Most lots start with a goods receipt for a purchase order, but production orders, stock transfers, deliveries, customer returns and the recurring-inspection job for batches start them too. If the material has an active inspection type for that origin, SAP creates the inspection lot by itself.
Who: Warehouse clerk, or a background job
Where you see it
The goods receipt looks normal; the stock lands in quality inspection and the lot appears in the inspection lot lists.
MIGOQA32
Under the hood
The lot origin plus the active inspection type in the QM view decide the processing. For stock transfers the movement type must be QM-relevant in Customizing; for recurring inspection an inspection interval sets each batch’s next inspection date.
QCC0QA08QA07
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: The goods receipt posts inventory against GR/IR as usual, even though the stock lands in quality inspection: that stock is valuated.
Sources: SAP Help, inspection type and stock category; SAP Learning, enhancing the material master, executing stock transfers and recurring inspections.
Step 2 of 8 · What happens
The inspection lot is created
The lot records what is inspected, how much and why. SAP assigns the inspection plan or specification and calculates the sample, and the lot moves from CRTD to REL. Without a valid plan it waits in PREQ.
Who: The system, or the quality planner when plans are assigned by hand
Where you see it
Lot header with origin, quantity, plan, sample size and status.
QA03QA32
Under the hood
Lot header in table QALS, characteristic specifications in QAMV. With no plan or specification, the inspection percentage or the 100% indicator in the QM view sets the sample. QAC3 resets a sample calculation.
QALSQAMVQAC3
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting.
Sources: SAP Learning, lifecycle of an inspection lot and performing result recording; SAP Community, inspection lot statuses; Tutorialspoint and dvw analytics, QM tables.
Step 3 of 8 · What happens
A sample is drawn and inspected
Only the sample is inspected, not the whole lot, unless the plan asks for 100 percent. Its size comes from the sampling procedure and, where dynamic modification is used, from the quality level: in a skip stage there may be nothing to inspect at all.
Who: Quality technician or laboratory
Where you see it
Sample size on the lot; sample-drawing instructions can be printed, set per inspection type.
QA03
Under the hood
Sampling procedure, dynamic modification rule and quality level by material, supplier, manufacturer or customer. Characteristics skipped by dynamic modification get status 4.
QDV1QDR1
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting yet. Destructive samples leave stock later, at the usage decision, with movement type 331.
Sources: SAP Learning, setting up dynamic modification and performing result recording; SAP Help, inspection type; SAP Community, usage decision stock postings.
Step 4 of 8 · What happens
Results are recorded and valuated
For each characteristic the technician enters measured values or codes, and SAP valuates them as accepted or rejected, automatically from the sampling procedure or by hand. Long-term characteristics, such as a test that takes days, can stay open and receive results after the usage decision.
Who: Quality technician
Where you see it
Results recording worklist: lots, operations and characteristics in one tree. Once results exist, the lot shows RREC.
QE51NQE01QE72
Under the hood
Results per characteristic in QAMR and per sample unit in QASE. Characteristic status 1 = must be processed, 5 = completed, 6 = sent to a subsystem through QM-IDI. BAdI BADI_QEEM_CLOSE_ECHARACTERISTIC can separate entering a result from validating it.
QAMRQASEQEDS
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting.
Sources: SAP Learning, performing result recording; TestingBrain, QM-IM transactions; Guru99, quality notifications (RREC); Tutorialspoint, QM tables.
Step 5 of 8 · What happens
Defects go into a notification or a defect
When something fails, the technician records defects with catalog codes. In classic QM they land in a quality notification, such as F2 for a supplier-related defect; in SAP S/4HANA they can also live as defects with quality tasks, and move to a notification or an 8D process only when needed.
Who: Quality technician, then the quality engineer
Where you see it
Defects on the lot; notifications with items, causes, tasks and actions.
QF11QM02QM10
Under the hood
The inspection type names the default notification type for defects. Catalog types: defect 9, location E, cause 5, task 2, action 8. Notification status goes from OSNO (outstanding) to NOPR (in process) to NOCO (completed).
QS41QM01
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No FI posting. Nonconformity costs such as rework hours or scrap values can be collected on a QM order assigned to the notification.
Sources: SAP Learning, configuring quality notifications and using defects and quality tasks; Guru99, quality notifications; saponlinetutorials, QM transactions.
Step 6 of 8 · What happens
The usage decision closes the lot
The usage decision says, for the whole lot, whether it can be used: a code from the catalog, valuated as accepted or rejected, plus a quality score from 1 to 100. Follow-up actions tied to the code can update batch characteristics, print a report or trigger more steps.
Who: Quality engineer
Where you see it
Usage decision with tabs for characteristics, defects and stock; collective decisions for lots with nothing rejected.
QA11QA32QA16
Under the hood
Stored in table QAVE. Lots with completed characteristics and no defects can get a quick, collective or automatic UD (QA10, scheduled with QA17). In SAP S/4HANA the UD codes (catalog type 3) are Customizing and can no longer be maintained in QS41 or QS51.
QAVEQA10QA17
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: The usage decision itself posts nothing. Only the stock posting that comes with it can.
Sources: SAP Learning, performing usage decisions; TestingBrain, QM-IM transactions; Tutorialspoint, QM tables.
Step 7 of 8 · What happens
Stock leaves quality inspection
The lot quantity is posted out of quality inspection stock: to unrestricted use if it passed; to blocked stock, scrap, sample usage, another material or back to the supplier if not; or split across several. When all of it is posted, the lot shows SPCO.
Who: Quality engineer, on the stock tab of the usage decision
Where you see it
Stock posting tab of the usage decision; the list of lots still holding stock.
QA11QVM2
Under the hood
Movement types 321, 350, 553, 331, 309 and 122, linked to the lot in table QAMB. Postings can run automatically with the UD or be proposed for confirmation, which SAP Learning warns can leave stock stuck; Customizing can block the UD until the stock is posted.
QAMBOBYC
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: 321 and 350 only change the stock type, so no journal entry. 331 (sample), 553 (scrap) and 122 (return to supplier) take value out of inventory and create one.
Sources: SAP Community, UD stock postings and movement types 350 and 322; SAP Learning, lifecycle of an inspection lot; SAP Help, account groupings VQP and VNG; dvw analytics, QAMB.
Step 8 of 8 · What happens
Suppliers, invoices and customers feel it
The quality score feeds the supplier evaluation, the quality level sets the next inspection stage, and a rejected lot can lead to a complaint or a replacement order. If the control key blocks invoices, accounts payable can release the supplier’s invoice once the goods are accepted; for outgoing goods, results can go to the customer as a certificate.
Who: Purchasing, accounts payable, quality engineer
Where you see it
Blocked invoices, supplier complaints and delivery certificates.
MRBRQM01QC20
Under the hood
Vendor evaluation averages the quality scores of the supplier’s lots in the period (goods receipt, main criterion quality). Certificates use a certificate profile (QC01), its assignment (QC15) and output type LQCB.
QC01QC15
Customizing, tables and the settings behind this step are in the Consultant view.
Invoice releaseIn the books: Payment block I, set when the goods receipt inspection is not OK, can be released in MRBR once the lot is accepted.
Sources: SAP Help, vendor evaluation (goods receipt, quality) and invoice block when the inspection is not OK; SAP Community, payment block for quality reasons and certificate of analysis step by step; SAP Learning, performing usage decisions.
The three stock types every QM user should know
Most “I can’t use my material” calls end at one of these. All three are the company’s own stock in the same plant; what changes is who may touch it.
- Free to useUnrestricted-use stockValuated and available for consumption, sales and transfers. Accepted lots end up here, with movement type 321.
- Waiting for a decisionQuality inspection stockValuated, so it is already in inventory, but not available for withdrawals in the standard system. Only the usage decision, or an early posting, lets it out.
- Not to be usedBlocked stockOwn stock that should not be used. Rejected goods often wait here (350) for a return or scrapping; 343 moves them back if they turn out fine.
Sources: SAP Help, stock category and stock types; SAP Community, usage decision stock postings.
Try it
From the usage decision to the journal entry
This is the part FI and CO people ask about most: what does a quality decision do to inventory and to the P&L? The answer depends on where the stock goes. Change the decision below and watch the stock posting tab, the journal entries and the inventory value move together.
The decision
Example: 500 KG rejected, to blocked stock, 10 KG sample used up.
Lot of 10,000 KG received on a purchase order, standard price 0.50 per KG, equal to the PO price. Examples only.
The stock posting tab, line by line
| Mvt | Posting | Quantity | Value | Journal entry |
|---|---|---|---|---|
321 | Quality inspection → unrestricted use | 9,490 KG | 4,745.00 | None |
331 | Sample usage from quality inspection | 10 KG | 5.00 | Yes |
350 | Quality inspection → blocked stock | 500 KG | 250.00 | None |
553 | Scrap from quality inspection | 0 KG | 0.00 | Yes |
122 | Return delivery to the supplier | 0 KG | 0.00 | Yes |
Usage decision: accepted in part. The code you pick says whether the lot counts as accepted or rejected.
Journal entries created
| Account | Key | Debit | Credit |
|---|---|---|---|
| Sample consumption | GBB-VQP | 5.00 | |
| Inventory | BSX | 5.00 | |
| Scrapping expense | GBB-VNG | 0.00 | |
| Inventory | BSX | 0.00 | |
| Offset on the purchase order | — | 0.00 | |
| Inventory | BSX | 0.00 | |
| Total | 5.00 | 5.00 |
Debits equal credits. Accounts come from MM account determination (OBYC).
None. 321 and 350 only change the stock type of the same material in the same plant, so there is nothing to post in FI: just a material document.
Where the 10,000 KG ended up
Inventory, before and after
Before: in quality inspection5,000.00
After: still in inventory4,995.00
Expensed (samples, scrap)5.00
Back to the supplier0.00
Supplier invoiceDepends on the UD code
The stock was in inventory from the moment of the goods receipt. The quality decision only moves it, expenses it or sends it back.
Movement types as proposed on the usage decision’s stock tab in a standard setup; your plant may offer fewer or different options. Account groupings VQP (sample withdrawals) and VNG (scrapping) are SAP’s standard offsetting entries for transaction GBB; which G/L accounts they reach depends on your OBYC settings. The return takes the value out of inventory against the purchase order; the offsetting account depends on your settings and, with a price difference, on how the goods receipt was valued. Sources: SAP Community, usage decision stock postings and movement types 350 and 322; SAP Help, account groupings for offsetting entries, stock category and invoice block when the inspection is not OK.
Quick test
Why is my stock stuck in quality?
Ten calls every QM support team knows by heart. Guess the cause first, then open the card to see it, the fix and who acts.
- Master data
- Results
- Stock posting
- Procurement
- Accounting
- Batch
The goods receipt went straight to unrestricted stock.Show the answer
Master dataNo inspection type for that origin is active in the material’s QM view in this plant, or it does not post to inspection stock. Activate it in the QM view or with QA08 for future receipts. Certified suppliers can also skip the inspection on purpose.
Who acts: Quality planner or QM consultant
The usage decision is made, but the stock is still in quality inspection.Show the answer
Stock postingThe UD and the stock posting are separate events. The lot shows SPRQ: open the stock tab in QA11 or QA32 and post it. QVM2 lists the lots still holding stock.
Who acts: Quality engineer
MIGO won’t move the stock from quality inspection to unrestricted.Show the answer
Stock postingOnce an inspection lot exists, that stock is managed by QM: release it through the usage decision. To send it to another storage location or plant while it waits, use Move Inspection Stock in Manage Inspection Lots.
Who acts: Quality engineer
I can’t make the usage decision.Show the answer
ResultsRequired characteristics are still open: all must be in status 0, 4 or 5. Finish them, or force completion, which needs special authorization. A user or system status can also lock the UD.
Who acts: Quality technician, then the quality engineer
The lot is stuck in PREQ.Show the answer
Master dataNo inspection plan or specification was found. Plans are valid for one plant and a lot-size range, so check those, then assign the plan in QA02 or the Change Inspection Lot app.
Who acts: Quality planner
There is nothing to record results against.Show the answer
Master data“Inspect characteristics” was off in the inspection setup when the lot was created. Re-assigning a plan won’t fix it: cancel the goods receipt, correct the setup and post the receipt again.
Who acts: QM consultant, warehouse
Purchasing can’t order this material from this supplier.Show the answer
ProcurementThe quality info record’s release date or quantity is exceeded, it carries a quality block, or the supplier’s QM system does not match the one the material requires.
Who acts: Quality planner, purchasing
The supplier’s invoice is blocked for payment.Show the answer
AccountingThe QM control key blocks invoices: payment block I while the goods receipt inspection is not OK, that is, no usage decision yet or a rejected lot. After an accepted UD, accounts payable releases it in MRBR.
Who acts: Accounts payable, quality engineer
The goods receipt was cancelled, but the lot is still open in MD04.Show the answer
Stock postingA documented inconsistency: SAP Note 2186161 makes the cancellation set the lot to LTCA, and the correction report from SAP Note 48815 fixes lots that are already open.
Who acts: QM consultant
A batch suddenly became restricted.Show the answer
BatchThe recurring inspection report (QA07) found its best-before date in the past and changed its status. Batches due for re-inspection move to quality inspection stock with an origin 09 lot instead.
Who acts: Quality engineer, warehouse
Sources: SAP Learning, enhancing the material master, executing stock transfers, performing result recording, performing usage decisions, implementing quality control in procurement and recurring inspections; SAP Help, invoice block when the inspection is not OK; SAP Community, stock still in inspection after the usage decision and payment block for quality reasons; SAP blog on GR cancellation leaving the lot open (SAP Notes 2186161 and 48815); TestingBrain, QA07.
Speak QM
The codes QM people use without explaining them
“It’s an 01 lot in RREC, waiting for the UD, then 321 to unrestricted.” These are the standard codes you will hear in meetings and see on every QM screen. Your company may add its own, often starting with Z.
How it works: origins are predefined by SAP. Customizing assigns one or more inspection types to each, and the material’s QM view activates them. Lots for origins 10 to 14 and 17 cannot be created by hand. Sources: SAP Help, inspection type; SAP Learning, lifecycle of an inspection lot.
How to read them: system statuses on the lot header, set by SAP as the lot moves on. A user status profile, set per inspection type, can add your own and block steps. Sources: SAP Community, inspection lot statuses and stock still in inspection after the UD; SAP KBA 2493861; SAP Learning, result recording and usage decisions; Guru99; SAP blog on GR cancellation.
Where you see them: on the stock tab of the usage decision. Which options appear depends on the plant’s configuration. Sources: SAP Community, UD stock postings and movement types 350 and 322; SAP Help, account groupings for offsetting entries.
How they start: Qx notifications are created by hand, for example from a customer call; Fx notifications are created when defects are recorded in an inspection. Sources: SAP Learning, configuring quality notifications; Guru99, quality notifications.
How they fit: catalogs hold the codes, code groups organise them and selected sets offer the allowed ones. Tasks have deadlines and a status; actions only document what was done. Sources: SAP Learning, configuring quality notifications and performing usage decisions.
01Goods receipt for a POPurchased goods arriving; types 01, 0101 (model inspection) and 0130 (external processing).02Goods issueInspection when goods are issued.03In-process inspectionInspection during a production order.04Goods receipt from productionGoods delivered by a production order.05Other goods receiptReceipts without a purchase or production order.06Customer returnGoods coming back from a customer.07AuditAudit inspections.08Stock transferTransfers within or between plants; type 0800 creates lots when QM is activated for existing stock.09Recurring inspectionStored batches inspected again on their next inspection date.10Delivery with sales orderInspection of a delivery to a customer.11Delivery without sales orderDelivery to a customer with no order behind it.12General deliveryInspection for a general delivery.13Repetitive manufacturingIn-process inspection in repetitive manufacturing.14Plant maintenanceInspections that come from plant maintenance.15Physical samplesInspection of physical samples.17EWM inspectionInspection in Extended Warehouse Management.89MiscellaneousOther inspections, often created by hand.CRTDCreatedThe lot exists but is not yet released for results.PREQPlan requiredNo inspection plan or specification assigned yet.RELReleasedReady for results recording.CHCRCharacteristics requiredCharacteristics need results.RRECResults recordedResults exist; defects can now be recorded in QA32.ICCOInspection completedNo more results can be recorded.UDUsage decision madeThe lot has its decision.SPRQStock posting requiredStock still to be posted after the UD.SPCOStock posting completedNo stock left in the lot.UDREUsage decision resetReset in the Manage Usage Decisions app.LTCALot cancelledFor example, cancelled together with its goods receipt.STUPStatistics updatedResults written to the QM statistics.321Inspection → unrestrictedAccepted quantity becomes usable. No journal entry.350Inspection → blockedRejected goods wait for a decision. No journal entry.553Scrap from inspectionDestroyed goods; expense through GBB-VNG.331Sample usageDestructive samples; expense through GBB-VQP.309To new materialThe quantity moves to another material number.122Return deliveryBack to the supplier, against the purchase order.322Unrestricted → inspectionReverses 321.343Blocked → unrestrictedWhen blocked goods turn out acceptable.Q1Customer complaintReference: customer, sales order, delivery.Q2Complaint against supplierReference: supplier, purchase order, inspection lot.Q3Internal problemReference: material, production order, plant.F1Customer-related defectFrom defect recording.F2Supplier-related defectFrom defect recording at incoming inspection.F3Material-related defectFrom defect recording in production.OSNOOutstandingCreated, processing not started.NOPRIn processSet when the notification is released.NOCOCompletedClosed, with a completion date.9Defect typesWhat is wrong, such as “too long”.EDefect locationsWhere on the item the defect is.5CausesThe root cause of a defect.2TasksWork to be done, with a processor and a deadline.8ActionsWhat was already done, for the record.3Usage decisionsUD codes; Customizing in SAP S/4HANA.
Saving the usage decision and posting the stock are two separate events. A lot can show UD and still hold its stock in quality inspection, with status SPRQ, until someone posts it; QVM2 lists such lots, and Customizing can stop a UD until the stock is posted. Source: SAP Community
Reference
The QM transactions people actually use
QM transactions follow a pattern: QA for inspection lots and usage decisions, QE for results, QM for notifications, QS for master data, QP for inspection plans, QD for sampling, QI for quality info records and QC for certificates. Start here shows the ones worth bookmarking; FI/CO bridge collects what accounting and controlling touch; the last column says where each one exists. Type a code or a word to search all of them.
| Code or app | For | What it does | Who opens it | ECC / S/4HANA |
|---|---|---|---|---|
QA32 | User | Inspection lot selection: the daily worklist to change lots and reach results, defects and usage decisions. | Quality technicians and engineers | ECC + S/4HANA |
QA33 | User | Display inspection lots, with the same selection as QA32. | Everyone | ECC + S/4HANA |
QA01 | User | Create an inspection lot by hand; QA02 changes and QA03 displays it. | Quality team | ECC + S/4HANA |
QE51N | User | Results recording worklist. | Quality technicians | ECC + S/4HANA |
QE01 | User | Record characteristic results; QE02 changes and QE03 displays them. | Quality technicians | ECC + S/4HANA |
QE72 | User | Tabular results recording for several inspection lots. | Laboratory | ECC + S/4HANA |
QE71 | User | Tabular results recording for inspection points. | Production quality | ECC + S/4HANA |
QF11 | User | Record defects for an inspection lot. | Quality technicians | ECC + S/4HANA |
QA11 | User | Record the usage decision and post the stock. | Quality engineers | ECC + S/4HANA |
QA12 | User | Change a usage decision with history; QA14 changes it without history and QA13 displays it. | Quality engineers | ECC + S/4HANA |
QA16 | User | Collective usage decision for accepted lots. | Quality engineers | ECC + S/4HANA |
QVM2 | User | Inspection lots that still hold stock: where stuck stock shows up. | Quality engineers, warehouse | ECC + S/4HANA |
QAC2 | User | Transfer stock to an inspection lot. | Quality engineers | ECC + S/4HANA |
QAC3 | User | Reset the sample calculation of a lot. | Quality planners | ECC + S/4HANA |
QM01 | User | Create a quality notification: customer complaint, supplier complaint or internal problem. | Quality, customer service, purchasing | ECC + S/4HANA |
QM02 | User | Change a notification: release it, add causes, tasks and actions, complete it. QM03 displays it. | Quality engineers | ECC + S/4HANA |
QM10 | User | List of quality notifications in change mode; QM11 in display mode. | Quality engineers | ECC + S/4HANA |
QM12 | User | List of notification tasks. | Task processors | ECC + S/4HANA |
QC20 | User | Create the quality certificate for a delivery (certificate of analysis). | Quality, shipping | ECC + S/4HANA |
MB5M | User | Shelf life list: batches by best-before date. | Warehouse, quality | ECC + S/4HANA |
QCC0 | Consultant | Direct access to QM Customizing: inspection types, lot origins and their defaults. | QM consultants | ECC + S/4HANA |
QS21 | Consultant | Create a master inspection characteristic. | Quality planners | ECC + S/4HANA |
QS26 | Consultant | Where-used list of an inspection characteristic; QS27 replaces it. | Quality planners | ECC + S/4HANA |
QS31 | Consultant | Create an inspection method. | Quality planners | ECC + S/4HANA |
QS41 | Consultant | Maintain catalogs: code groups and codes. | Quality planners | ECC + S/4HANA |
QS51 | Consultant | Edit selected sets, the codes offered to users. | Quality planners | ECC + S/4HANA |
QS61 | Consultant | Maintain a material specification. | Quality planners | ECC + S/4HANA |
QDV1 | Consultant | Create a sampling procedure. | Quality planners | ECC + S/4HANA |
QDR1 | Consultant | Create a dynamic modification rule; QDR2 changes and QDR3 displays it. | Quality planners | ECC + S/4HANA |
QP01 | Consultant | Create an inspection plan; QP02 changes and QP03 displays it. | Quality planners | ECC + S/4HANA |
QA08 | Consultant | Collective processing of the inspection setup: activate inspection types for many materials. | QM consultants | ECC + S/4HANA |
QI01 | Consultant | Create a quality info record for procurement (material, supplier, plant). | Quality planners, purchasing | ECC + S/4HANA |
QI05 | Consultant | Mass maintenance of the QM in procurement control key in material masters. | QM consultants | ECC + S/4HANA |
QA07 | Consultant | Trigger for recurring inspection of batches (report RQAAAS10). | QM consultants, background job | ECC + S/4HANA |
QA10 | Consultant | Trigger automatic usage decisions; QA17 schedules the job. | QM consultants | ECC + S/4HANA |
QA09 | Consultant | Number ranges for inspection lots. | QM consultants | ECC + S/4HANA |
QC01 | Consultant | Create a certificate profile; QC15 assigns it. | QM consultants | ECC + S/4HANA |
OQI4 | Consultant | Customize the lot selection of QA32 and QA33. | QM consultants | ECC + S/4HANA |
QCC5 | Consultant | Business Add-Ins (BAdIs) in Quality Management. | QM consultants, developers | ECC + S/4HANA |
MRBR | FI/CO bridge | Release blocked invoices; QM’s payment block I shows here. | Accounts payable | ECC + S/4HANA |
OBYC | FI/CO bridge | MM account determination behind UD postings: inventory (BSX), samples (GBB-VQP), scrapping (GBB-VNG). | FI and MM consultants | ECC + S/4HANA |
QK01 | FI/CO bridge | Assign a QM order to materials, to collect inspection (appraisal) costs; QK02 displays the assignment. | Controlling, QM consultants | ECC + S/4HANA |
QK04 | FI/CO bridge | Create QM orders. | Controlling, QM consultants | ECC + S/4HANA |
MIGO | FI/CO bridge | The goods receipt that creates the lot and posts inventory against GR/IR; also return deliveries (122). | Warehouse, MM | ECC + S/4HANA |
| Manage Inspection Lots | Fiori app | Find and change lots; Move Inspection Stock sends a whole lot to another storage location or plant. | Quality engineers | S/4HANA |
| Change Inspection Lot | Fiori app | Assign a plan and calculate the sample by hand. | Quality planners | S/4HANA |
| Record Inspection Results | Fiori app | Results for one or many lots, operations or characteristics, with defect creation. | Quality technicians | S/4HANA |
| Hierarchical Results Recording Worklist | Fiori app | Tree of lots, operations and characteristics, with configurable layouts. | Quality technicians | S/4HANA |
| Record Inspection Results in Table Form | Fiori app | One table for a few characteristics across many lots. | Laboratory | S/4HANA |
| Manage Usage Decisions | Fiori app | Quick or detailed usage decisions, stock splits, and resetting a UD. | Quality engineers | S/4HANA |
| Record Usage Decision | Fiori app | Tabbed UD covering defects, characteristics, stock, inspection points, samples and equipment. | Quality engineers | S/4HANA |
| Quality Engineer Overview | Fiori app | Lots ready for a decision, with quick UD. | Quality engineers | S/4HANA |
| Manage Quality Levels | Fiori app | Quality level history and the next inspection stage. | Quality planners | S/4HANA |
| Inspection Lot Analytics | Fiori app | QM statistics from inspection lots. | Quality managers | S/4HANA |
| Manage Quality Info Records | Fiori app | Create and manage quality info records for procurement. | Quality planners | S/4HANA |
| Change QM Inspection Setup - Collective Processing | Fiori app | The app counterpart of QA08. | QM consultants | S/4HANA |
| Manage Defects | Fiori app | Work on defects, add quality tasks, transfer to a notification or start problem solving. | Quality engineers | S/4HANA |
| Record Production Defects | Fiori app | Record a defect against a production order, operation or work center. | Production | S/4HANA |
| Resolve Internal Problems | Fiori app | 8D problem solving for internal problems. | Quality engineers | S/4HANA |
QALS | Table | Inspection lot record, one row per lot. | Consultants, analysts | ECC + S/4HANA |
QAMV | Table | Characteristic specifications of the lot, with tolerances. | Consultants | ECC + S/4HANA |
QAMR | Table | Results per inspection characteristic. | Consultants, analysts | ECC + S/4HANA |
QASE | Table | Results per sample unit. | Consultants | ECC + S/4HANA |
QAVE | Table | Usage decision. | Consultants, analysts | ECC + S/4HANA |
QAMB | Table | Link between inspection lot and material document (MATDOC in SAP S/4HANA). | FI, MM and QM consultants | ECC + S/4HANA |
QMEL | Table | Quality notification header. | Consultants, analysts | ECC + S/4HANA |
QMFE | Table | Notification defect items. | Analysts | ECC + S/4HANA |
QMSM | Table | Notification tasks. | Analysts | ECC + S/4HANA |
QMMA | Table | Notification activities. | Analysts | ECC + S/4HANA |
QPMK | Table | Master inspection characteristics. | Consultants | ECC + S/4HANA |
QINF | Table | Quality info record for material and supplier. | Consultants | ECC + S/4HANA |
QDQL | Table | Quality levels. | Consultants | ECC + S/4HANA |
PLKO | Table | Inspection plan header; PLMK holds its characteristics and MAPL the material assignment. | Consultants | ECC + S/4HANA |
Nothing matches. Try another word, or pick All.
Codes cross-checked with the TestingBrain and saponlinetutorials QM lists, SAPSTACK, ERPLingo, Guru99, SAP Learning and the SAP Community; Fiori app names follow SAP Learning; tables follow Tutorialspoint and dvw analytics. Projects can hide transactions or rename apps, so check your own system before you write them into a manual.
ECC to S/4HANA
What changed in QM with SAP S/4HANA
The inspection lot, the results and the usage decision work as in SAP ECC, and the classic transactions are still there. What changed is around them: Fiori apps by role, defects without notifications, structured problem solving and a few objects that moved into Customizing. If your company is moving from ECC, these are the cards to read.
Usage decision codes
ECCMaintained with the catalogs in QS41 and QS51 (catalog type 3).
S/4HANACustomizing objects maintained by application consultants; QS41 and QS51 no longer edit catalog type 3.
Codes are still plant-specific and valuated as accepted or rejected.
Source: SAP Learning, performing usage decisionsCorrecting a usage decision
ECCChange it with history (QA12) or without (QA14).
S/4HANAManage Usage Decisions can reset it: code, score and follow-up actions are cleared and the lot moves from UD to UDRE.
Reset is allowed per plant and inspection type, and it never reverses stock postings.
Source: SAP Learning, performing usage decisionsResults recording
ECCQE51N worklist, QE01 for one lot, QE71 to QE73 for tables.
S/4HANARecord Inspection Results, the Hierarchical Results Recording Worklist and the table form app, all able to create defects.
The hierarchical worklist is extended with a BAdI that still carries the old name: BADI_QE_TREE_QE51N.
Source: SAP Learning, performing result recordingUsage decision
ECCQA11 or QA32, with QA16 for collective decisions.
S/4HANAManage Usage Decisions, Record Usage Decision and the Quality Engineer Overview with quick UD.
Record Usage Decision still covers inspection points, samples and calibration, which Manage Usage Decisions does not.
Source: SAP Learning, performing usage decisionsDefects
ECCRecorded defects create quality notifications (F1, F2, F3).
S/4HANADefects of their own (production, warehouse, generic) with quality tasks, moved to a notification only when needed.
Manage Defects offers Transfer Defects to Notification and Start Problem-Solving Process.
Source: SAP Learning, defects and quality tasksProblem solving (8D)
ECC8D reports printed from notifications, or the method run outside SAP in e-mail and Excel.
S/4HANAAn 8D issue created from the defect and worked in the Resolve Internal Problems app.
Aimed at industries with formal requirements: automotive suppliers, aerospace and defense, medical devices.
Source: SAP Learning, defects and quality tasksMoving inspection stock
ECCStock postings from the usage decision’s stock tab.
S/4HANAManage Inspection Lots › Move Inspection Stock moves a whole lot to another storage location or plant, linked to the lot.
The lot quantity cannot be split in this move.
Source: SAP Learning, executing stock transfersWarehouse
ECCWM: the usage decision creates posting change notices and transfer requirements.
S/4HANAEWM inspections with their own lot origin (17), and warehouse defects that can block stock in storage bins.
Origin 17 lots cannot be created by hand.
Source: SAP Learning, lifecycle of an inspection lotQuality planning and suppliers
ECCFirst-article approvals and 8D often lived in e-mail and Excel.
S/4HANAFirst article approval (PPAP) in the quality info record, a Fiori-based FMEA and a new supplier evaluation with questionnaires.
Listed by the SAP partner Consilio among its reasons to use QM in SAP S/4HANA (April 2026).
Source: Consilio, ten reasons to use QM in S/4HANA (2026)Analytics
ECCQM information system (QMIS) and list transactions.
S/4HANAEmbedded analytics inside SAP S/4HANA, such as the Inspection Lot Analytics app.
Usage decisions feed the QM statistics automatically.
Source: SAP Learning, performing usage decisions
Why it matters
What poor quality costs, and where SAP sees it
ASQ, the American Society for Quality, says that many organizations have true quality-related costs as high as 15 to 20 percent of sales revenue. Pick a revenue to see what that upper range would mean, then see where each kind of cost leaves a trace in SAP.
ASQ’s figure is an upper range seen in many organizations, not an average: a well-run company can be far below it.
Quality-related cost at 15 to 20 percent
- PREVENTION
Stopping defects before they happen
In SAP: quality planning, such as inspection plans, characteristics, quality info records and, in S/4HANA, the Fiori FMEA.
- APPRAISAL
Checking the work
In SAP: the inspections themselves, lots, samples and lab time, collected on QM orders, and the scope that dynamic modification reduces.
- INTERNAL FAILURE
Defects caught at home
In SAP: scrap (553), rework on a QM order, internal problem notifications (Q3) and production defects.
- EXTERNAL FAILURE
Defects the customer finds
In SAP: customer complaints (Q1), customer returns (lot origin 06) and the credit memos that follow in SD.
Source for the figures and the four categories: ASQ, cost of quality. SAP objects from SAP Learning, SAP Help, Guru99 and Consilio, as linked elsewhere on this page. ASQ, cost of quality
Industries
Same module, three very different jobs
The inspection lot is the same everywhere, but what a company leans on depends on what it makes. These are the QM features each kind of plant usually asks for first.
- Food and beverage
Batches, best-before dates, certificates
Recurring inspections re-check stored batches on their next inspection date and restrict expired ones, usage decisions can update batch characteristics, and certificates of analysis go out with deliveries (QC20, output type LQCB).
Source: SAP Learning, recurring inspections - Pharma and life sciences
Signatures and four eyes
Digital signatures can be required on notifications and tasks, results recording has its own signature process (QEDS), and a BAdI can separate entering a result from validating it.
Source: SAP Learning, quality notifications - Automotive, aerospace, medical devices
8D and first-article approval
8D problem solving starts from a defect, and first-article inspections run as their own inspection type (0101) until the quality info record’s status releases the supplier for series supply.
Source: SAP Learning, defects and quality tasks
Documented, but little known
16 tips for users and consultants
Each tip comes from SAP Learning, SAP Help, the SAP Community or a published source, linked under the tip.
- 01Users
Post the stock with the usage decision, not before
Early postings out of quality inspection are possible, but SAP advises against them: defective material may already be consumed and sample stock may run short.
QA11
- 02Users
A changed UD does not undo the stock
Changing or resetting a usage decision does not reverse stock postings or other follow-up actions. Check the stock tab and post back by hand.
QA12QA14
- 03Users
Defects button greyed out in QA32?
The lot has not reached RREC. Record at least one result first and the button becomes available.
QA32
- 04Users
Hunt stuck stock with QVM2
Lots with a usage decision but no stock posting show SPRQ. QVM2 or QA32 find them so the stock can be posted.
QVM2QA32
- 05Users
Long tests don’t hold up the lot
Long-term characteristics can still receive results after the usage decision, so a three-day test need not block the stock.
QE51N
- 06Consultants
QA08 for existing stock, once
Activating a stock-relevant inspection type with QA08 creates lots for stock already in quality inspection, with the plant’s default type such as 0800. From then on, MIGO can no longer move that stock.
QA08
- 07Consultants
A missed indicator can’t be fixed on the lot
If “Inspect characteristics” was off when the lot was created, re-assigning a plan won’t help: cancel the goods receipt and post it again.
QA02
- 08Consultants
Specification or plan: choose one
Both can be active, and a characteristic in both is taken from the specification. SAP recommends one or the other per inspection.
QS61QP01
- 09Consultants
Give skip stages an end
A skip stage needs a maximum duration in days; if no lot arrives in that time, the next one is created for the next non-skip stage.
QDR1
- 10Consultants
Keep one plant out of QM in procurement
The setting applies to the whole client. Maintain control key 0000 in a plant’s QM view to exclude it; QI05 changes control keys in bulk.
QI05
- 11Consultants
Four eyes on results
BAdI BADI_QEEM_CLOSE_ECHARACTERISTIC can separate entering a result from validating it, for regulated plants.
QCC5
- 12Consultants
Steer the inspection type per supplier
Customer exit QAAT0001, or the status scheme of the quality info record, can choose the inspection type, for example a first-article type until the supplier is released for series.
QI01
- 13FI/CO
Find the accounts behind UD postings
Sample usage posts through account grouping VQP and scrapping through VNG, both offsetting entries of transaction GBB in OBYC, against inventory (BSX).
OBYC
- 14FI/CO
QM can hold supplier payments
With invoice blocking set in the material’s QM control key, an invoice is blocked with reason I while the goods receipt inspection is not OK. Accounts payable releases it in MRBR.
MRBR
- 15FI/CO
Put the cost of quality on QM orders
QM orders assigned to materials (QK01) collect inspection costs, and a QM order assigned to a notification collects rework hours or scrap values.
QK01QK04
- 16FI/CO
Quality inspection stock is in your inventory
Goods waiting for a decision are valuated, so month-end inventory already includes them even though nobody can use them.
Source: SAP Help, stock category
Myths
Things people get wrong about QM
Myth
Stock in quality inspection is not on the balance sheet yet.FactIt is. SAP Help says stock in quality inspection has been valuated but does not count as unrestricted-use stock; the goods receipt already posted inventory against GR/IR.
Myth
The usage decision posts the stock.FactNot necessarily. They are separate events: a lot can show UD and still hold stock, with status SPRQ, until the stock posting is done. Customizing can force the posting before the UD.
Myth
Changing the usage decision reverses the stock posting.FactIt does not. Changing or resetting a UD leaves stock postings and other follow-up actions as they were; reverse them yourself.
Myth
Moving stock from inspection to unrestricted creates a journal entry.FactNo. 321 and 350 are transfers between stock types, with no accounting impact. Scrap, samples and returns do create journal entries.
Myth
Every inspection needs an inspection plan.FactNo. A material specification can hold the characteristics, and without any specification the sample comes from the inspection percentage or the 100% indicator in the QM view.
Myth
QM is only for goods receipts.FactSAP predefines lot origins for production, stock transfers, deliveries, customer returns, recurring batch inspections, plant maintenance and EWM as well.
Myth
In a skip stage, no inspection lot is created.FactThe lot is still created and still needs a usage decision. Characteristics skipped by dynamic modification get status 4, so results are optional; collective (QA16) or automatic (QA10) decisions close such lots in bulk.
Myth
Every quality problem needs a quality notification.FactNot in SAP S/4HANA. Defects can be recorded and fixed with quality tasks without a notification header, and moved to a notification or an 8D process only when needed.
The questions people ask most
What is the difference between an inspection lot origin and an inspection type?
The origin is predefined by SAP and says what triggered the lot, such as 01 for a goods receipt for a purchase order or 04 for a goods receipt from production. The inspection type is defined in Customizing, assigned to an origin and activated per material in the QM view. One origin can have several types, for example 01 for regular receipts and 0101 for a model (first-article) inspection.
Why did my goods receipt not create an inspection lot?
Usually because no inspection type for that origin is active in the material’s QM view in that plant, or the type does not post to inspection stock. For stock transfers, the movement type must also be QM-relevant. A certified supplier can also skip the goods receipt inspection on purpose, sending the goods straight to unrestricted-use stock.
What is the difference between quality inspection stock and blocked stock?
Both are the company’s own stock that cannot be used freely. Quality inspection stock is waiting for a decision, and only the usage decision or an early posting releases it. Blocked stock should not be used at all; rejected goods often wait there for a return or scrapping. Moving goods from inspection to blocked (350) has no accounting impact.
Can stock in quality inspection be withdrawn or sold?
Not in the standard system: stock in quality inspection and blocked stock are not available for withdrawals, and only unrestricted-use stock is always usable. Customizing can change that, and whether planning and availability checks count inspection stock depends on your settings. The usage decision can also post all or part of a lot to unrestricted use early, although SAP advises against early postings.
How do I correct a usage decision?
In SAP GUI, QA12 changes it with history and QA14 without. In SAP S/4HANA, the Manage Usage Decisions app can reset it where the plant and inspection type allow, clearing the code and score and moving the lot from UD to UDRE. Either way, stock postings and other follow-up actions already done are not reversed; post them back yourself.
What is the quality score?
A number from 1 (lowest) to 100 (highest) given to the lot at the usage decision. Depending on the inspection type, it comes from the UD code, from the characteristics (weighted or worst case) or from the share of defects. Vendor evaluation averages the scores of a supplier’s lots for its quality criterion.
What is skip-lot, and is it safe?
Dynamic modification lets good history reduce inspection: after a run of accepted lots, normal can become reduced and then skip, and a rejection sends it back. A skip stage has a maximum duration in days, after which the next lot is inspected again. The quality level keeps the history per material and supplier, customer or manufacturer.
Why is the supplier’s invoice blocked for payment?
If invoice blocking is set in the material’s QM control key, SAP blocks the invoice with reason I while the goods receipt inspection is not OK, that is, when there is no usage decision yet or the lot was rejected. Accounts payable releases it in MRBR once quality has accepted the goods.
What is the difference between Q1, Q2 and Q3?
They are the standard quality notification types: Q1 for a customer complaint, Q2 for a complaint against a supplier and Q3 for an internal problem. They are created by hand; F1, F2 and F3 are their counterparts created from defects recorded during an inspection.
In SAP S/4HANA, should I record a defect or a quality notification?
A defect is the lighter object: production, warehouse or generic, fixed with quality tasks and without a notification header. When a problem needs more analysis, Manage Defects can transfer it to a notification, or start an 8D problem-solving process for industries with formal requirements.
What does QM post in FI?
Nothing by itself. The goods receipt posts as usual, even into inspection stock. At the usage decision, 321 (to unrestricted) and 350 (to blocked) only change the stock type, while sample usage (331), scrap (553) and a return to the supplier (122) take value out of inventory. Inspection and nonconformity costs can be collected on QM orders in CO.
Can I record results after the usage decision?
Only for long-term characteristics that were still open. Every other characteristic is closed by the usage decision, and a lot in ICCO accepts no more results unless inspection completion is reset.
Which tables hold QM data?
QALS for the inspection lot, QAMV and QAMR for characteristic specifications and results, QASE for results per sample unit, QAVE for the usage decision, QAMB for the link to material documents, and QMEL, QMFE, QMSM and QMMA for the notification header, defects, tasks and activities.
Related pages
References
Checked in November 2026. SAP knowledge base articles and SAP Notes need an SAP for Me login. Transaction lists from partner sites can lag behind your release; check names in your own system.
- Describing the required master datalearning.sap.com
- Enhancing the material masterlearning.sap.com
- Executing stock transferslearning.sap.com
- Explaining the lifecycle of an inspection lotlearning.sap.com
- Performing result recordinglearning.sap.com
- Performing usage decisionslearning.sap.com
- Configuring quality notificationslearning.sap.com
- Using defects and quality taskslearning.sap.com
- Implementing quality control in procurementlearning.sap.com
- Recurring inspections for batch-managed materialslearning.sap.com
- Setting up dynamic modificationlearning.sap.com
- Inspection type and inspection lot originshelp.sap.com
- Stock categoryhelp.sap.com
- Stock types in inventory managementhelp.sap.com
- Account groupings for offsetting entries (GBB)help.sap.com
- Invoice block when the goods receipt inspection is not OKhelp.sap.com
- Vendor evaluation: goods receipt (main criterion quality)help.sap.com
- Usage decision with Warehouse Managementhelp.sap.com
- Creation of a calibration orderhelp.sap.com
- Inspection characteristichelp.sap.com
- KBA 2493861: resetting inspection completion (ICCO)userapps.support.sap.com
- Usage decision stock postings and movement typesSAP Community
- Movement types 350 and 322SAP Community
- Payment block for quality reasonsSAP Community
- Usage decision made, stock still in inspectionSAP Community
- Inspection lot system statusesSAP Community
- Goods receipt cancellation leaves the inspection lot openblogs.sap.com
- Certificate of analysis, step by stepSAP Community
- Cost of qualityasq.org
- Ten reasons to use QM in SAP S/4HANA (2026)consilio-gmbh.de
- Quality notifications in SAP QMguru99.com
- SAP QM-IM transaction codestestingbrain.com
- QA07: trigger for recurring inspectiontestingbrain.com
- SAP QM transaction codessaponlinetutorials.com
- QA32: inspection lot selectionsapstack.com
- QDR1: create dynamic modification ruleerplingo.com
- SAP QM tablestutorialspoint.com
- Quality info recordstutorialspoint.com
- The most important SAP QM tablesdvwanalytics.com