🔬 What is SAP QM (Quality Management)?
In SAP QM (Quality Management) is an joined module within SAP ECC 6.0 ERP and S/4HANA that supports all quality-related processes across the supply chain. It enables companies to plan, execute, and document quality inspections for incoming materials, during production, and on outgoing deliveries. QM JOINED with MM, PP, SD, PM, and FI modules and supports industry standards like ISO 9001, GMP, FDA 21 CFR Part 11, and automotive standards such as IATF 16949.
Inspection Planning
Inspection plans, task lists, control keys, sampling procedures, and master inspection characteristics.
Quality Inspection
Inspection lots, results recording, defects recording, usage decisions, and stock postings.
Quality Control & Reporting
Quality notifications, CAPA, SPC, audit management, certificates, and QM in procurement/production/sales.
Interview Strategy: Always structure QM answers as: Definition → Where it fits in the process → Transaction code → Real example. QM interviewers always ask about inspection lot flow, usage decision, and how QM links to stock management - prepare these thoroughly.
🔴 Top 50 Advanced SAP QM Interview Questions
These 50 questions cover the hidden and most tested areas of SAP QM - from inspection lot creation and control keys to SPC, audit management, QM in procurement, S/4HANA changes, and troubleshooting. Each answer includes a real-world examples.
An Inspection Plan is the quality master data that defines how a material should be inspected. It contains: Operations (inspection steps), Inspection Characteristics (what to measure - dimensions, visual checks), Control Keys (what the system does - results recording, defects required), Sampling Procedure (how many samples to take), and Work Centre (where inspection is done). Created via QP01.
Example: Material SHAFT-100 has inspection plan QP-SHAFT: Operation 0010 "Dimensional Check" with characteristics - Diameter (spec: 50±0.5 mm), Length (200±1 mm), Surface Finish (Ra ≤ 1.6). Control key QM01 (results recording required). Sampling procedure S-05 (5 samples per lot). When a GR is posted for SHAFT-100, this plan is used to create the inspection lot automatically.
A Control Key is a configuration object assigned to each inspection characteristic in the inspection plan. It controls whether: results recording is required or optional, defects recording is required, the characteristic is relevant for SPC, whether a specification must be maintained, whether the characteristic is qualitative (pass/fail) or quantitative (measured value), and whether skip inspection applies.
Example: Control key QM01: Results recording = required, defects recording = optional, SPC relevant = yes, quantitative = yes. Used for critical dimensions. Control key QM02: Results recording = optional, qualitative only. Used for visual checks like packaging appearance. Wrong control key assignment means results can be skipped - a serious quality gap for regulated industries.
An Inspection Lot is the central QM document that triggers and tracks a quality inspection for a specific quantity of material. It is created automatically based on inspection lot origin - e.g., origin 01 (GR from PO), 03 (Production GR), 10 (Delivery to customer), 04 (In-process inspection). Can also be created manually via QA01. Each lot links to the relevant inspection plan and records all results.
Example: Vendor delivers 500 kg of Chemical CHEM-200. GR posted via MIGO → SAP auto-creates Inspection Lot 1000001 (origin 01) for 500 kg in quality stock. QA team opens QA32, records pH value = 7.2 (spec 7.0–7.5 ✓), density = 1.05 (spec 1.04–1.06 ✓). Makes usage decision ACCEPT → stock moves from quality stock to unrestricted.
The Usage Decision (UD) is the QA team's final verdict on an inspection lot - it determines the disposition of the inspected material. Made via QA11. Common UD codes: A = Accept (stock moves to unrestricted), R = Reject (stock moves to blocked), RE = Return to vendor, RA = Restricted Use (conditional release). UD triggers automatic stock posting in MM.
Example: Inspection lot for 1,000 tablets: 950 pass all tests, 50 show coating defects. UD = Partial Acceptance: 950 units → unrestricted stock (movement type 321), 50 units → blocked stock (movement type 344). Defect notification automatically created for the 50 rejected units. Vendor gets debit memo for the rejected quantity via QM–MM integration.
Key inspection lot origins: 01 - GR from Purchase Order (incoming inspection), 03 - GR from Production Order (final inspection), 04 - In-process inspection during production, 05 - GR from PM order, 06 - Audit inspection (manual), 08 - Recurring inspection (shelf life), 09 - Source inspection at vendor, 10 - Delivery to customer (outgoing), 11 - General task (manual). Activated per material in the material master QM view.
Example: Pharmaceutical company activates inspection types 01 (vendor GR), 03 (production finish), 08 (shelf life retest), and 10 (customer delivery) in the QM view of material master for each API. Every material movement of the correct type triggers an automatic inspection lot - ensuring no batch reaches the next stage without QA clearance.
A Master Inspection Characteristic (MIC) is a reusable quality parameter defined centrally in QS21. It stores: characteristic name, short text, unit of measure, inspection method, control key, and whether it is quantitative or qualitative. MICs are referenced in inspection plans - updating the MIC centrally updates all plans using it. This ensures consistency across hundreds of plans.
Example: Company tests "Tensile Strength" for 200 different metal parts. MIC TENS-STR defined once: unit = N/mm², control key QM01, quantitative. All 200 inspection plans reference TENS-STR. When the test method changes from ISO 6892-1 to ASTM E8, the inspection method is updated in QS21 once - all 200 plans automatically use the new method. No need to update each plan individually.
A Sampling Procedure defines how many samples to draw from an inspection lot and what acceptance criteria apply. Types: Fixed sample (always take N samples), Percentage sample (x% of lot), AQL-based (Acceptable Quality Level per ISO 2859 - sample size depends on lot size and AQL level). Configured via QDV1 and assigned to inspection plan characteristics.
Example: GR of 5,000 PCBs. Sampling procedure uses AQL 1.0, Inspection Level II. SAP looks up ISO 2859 table: lot size 5,000 → Sample letter L → sample size = 200. Accept if ≤ 5 defectives, reject if ≥ 6. Instead of checking all 5,000 boards, QA inspects 200. If 4 defects found → accept. If 7 defects found → reject the entire lot and raise defect notification.
Results Recording is the entry of actual measured values or pass/fail decisions for each inspection characteristic in a lot. Done via QE01 (individual) or QA32 (lot worklist). For quantitative characteristics: enter actual value → SAP compares to upper/lower tolerance limits → auto-evaluates pass/fail. For qualitative: select from catalogue (accepted/rejected/not tested). Results can also be entered for individual samples or mean values.
Example: Inspection lot for steel rods. QA opens QA32, selects lot 1000045. Characteristic "Diameter": spec 20.00 ± 0.05 mm. Enters 5 measured values: 20.02, 19.98, 20.03, 20.01, 19.97 → all within tolerance → auto ACCEPTED. Characteristic "Surface Cracks": qualitative → selects "No Cracks Found" from catalogue. All characteristics accepted → UD can be made.
Defects Recording captures the type, location, and number of defects found during inspection. It uses a defect catalogue (code groups for defect types - scratches, cracks, wrong dimensions) configured in QS41. Defects are recorded via QF01 or directly from results recording. Defects data feeds into quality notifications, SPC charts, and defect statistics reports.
Example: Inspection of 500 injection-moulded parts. QA finds: 12 parts with "Sink Marks" (defect code A1), 5 parts with "Flash" (defect code A2), 3 parts with "Short Shot" (defect code A3). Defects recorded in QF01 with quantities and locations. Pareto chart from QM information system shows Sink Marks = 60% of all defects → process team investigates moulding temperature as root cause.
A Quality Notification is a document to report, investigate, and track quality problems. Types: Q1 - Customer complaint (from SD), Q2 - Complaint to vendor (from MM), Q3 - Internal quality notification. Each notification has: problem description, defect codes, tasks (corrective actions), activities (work done), causes, and status. Managed via QM01 (create), QM02 (change).
Example: Customer calls about cracked gear housings in delivery. AR team creates Q1 notification QN-10045: describes crack defect, references customer PO and delivery. QA manager adds Task: "Collect samples from customer" (deadline 5 days). Root cause analysis finds insufficient cooling time. Corrective action: increase cooling from 30s to 45s. 8D report generated from notification. Notification closed after verification.
QM in procurement is activated by setting the QM procurement key in the material master QM view. When activated, every GR against a PO for that material creates an inspection lot (origin 01) automatically. The material goes into quality inspection stock - it cannot be used until a UD is made. The QM procurement key also controls vendor evaluation, release procedures, and Q-Info records.
Example: Material API-500 has QM procurement active (inspection type 01 checked in QM view). Vendor delivers 200 kg → MIGO GR posts 200 kg to quality stock. The 200 kg is visible in MMBE under "Quality Inspection" - unreachable for production. Only after QA records results and makes UD = Accept does SAP auto-post to unrestricted stock (mvt 321). If UD = Reject → stock moves to blocked (mvt 344) and vendor notification Q2 is created.
The Quality Info Record (QIR) stores the quality agreement between a company and a specific vendor for a specific material. It controls: whether inspection is required or skipped (skip set), release status of the vendor (blocked/released/conditional), certificate requirement, and skip inspection rules based on vendor quality history. Created via QI01.
Example: Vendor V-1001 has been supplying bolts for 2 years with zero defects. Q-Info Record updated: skip = active (skip lot rule: if 10 consecutive lots accepted, skip next inspection). GR of next lot → inspection lot created but immediately set to "skip" status → no QA testing required → lot auto-accepted. If vendor fails once, skip resets and full inspection resumes from the next delivery.
Skip inspection (dynamic modification) allows trusted vendors or stable processes to bypass detailed inspection based on quality history. Configured via Dynamic Modification Rule in the sampling procedure + Q-Info Record. The rule defines: how many consecutive accepted lots trigger a skip, and how many skips are allowed before full inspection resumes. Uses Stage concept (Stage 1 = full, Stage 2 = reduced, Stage 3 = skip).
Example: Dynamic modification rule: 5 consecutive accepted lots → move to Stage 2 (reduced sample). 5 more accepted lots → Stage 3 (skip). One rejection at any stage → return to Stage 1 (full inspection). Vendor V-500 ships 10 perfect lots → reaches skip stage. QA team inspects 0 samples for next 3 deliveries (time saved ≈ 15 hours). On lot 14, one defect found → reset to Stage 1 immediately.
In-process inspection (type 04) creates inspection lots during production - triggered by milestones in the routing (PP work centre operations). The inspection plan operation is linked to a PP routing operation. When the production order reaches that routing step, the inspection lot is created. In-process checks ensure quality is maintained during manufacturing - not just at the end.
Example: Production routing for Gear Shaft: Operation 0020 "Turning" → Operation 0030 "In-Process Check" (linked to QM type 04). When production order reaches op 0030, inspection lot created. QA checks: diameter, runout, surface finish. If all OK → UD = Accept → production order proceeds to op 0040 "Grinding". If rejected → production STOPPED, defect notification created, operator notified to adjust CNC parameters.
Inspection type 10 triggers an inspection lot when an outgoing delivery is created in SD. The goods issue (GI) is blocked until the UD is made - ensuring only quality-approved goods leave the warehouse. The inspection plan for type 10 defines the final pre-shipment checks (packaging, labelling, functional tests). Linked to delivery via SD delivery document.
Example: Sales order for 1,000 automotive parts. Delivery created in VL01N → Inspection Lot 2000088 (type 10) auto-created. QA checks: packaging integrity, label correctness, random functional test (10 pcs). All pass → UD = Accept in QA11. GI now allowed → VL02N post GI → goods shipped. If QA finds wrong labels → UD = Reject → GI blocked → production team re-labels before shipment.
When batch management is active, each inspection lot is linked to a specific batch. The UD updates the batch status (unrestricted/restricted/blocked) and can write QM results as batch classification values (e.g., pH value, purity % stored as batch characteristics). This enables batch traceability and automatic batch determination based on quality results in SD/PP.
Example: Pharmaceutical batch B-20250301 of API. QM inspection records: Assay = 99.2%, Moisture = 0.3%, pH = 6.8. UD = Accept → batch status set to "unrestricted". Results written to batch classification: CHAR_ASSAY = 99.2, CHAR_MOISTURE = 0.3. In SD, batch determination automatically selects batches where CHAR_ASSAY ≥ 99.0 for premium orders - quality data drives supply chain decisions.
A Quality Certificate (Certificate of Analysis - CoA) is a document sent with goods that confirms the material meets quality specifications. In SAP, certificates are created and printed via QC11 for outgoing deliveries or QC41 for incoming. The certificate profile defines which inspection results, batch characteristics, and layout to use. Triggered automatically at goods issue or delivery creation.
Example: Customer requires a CoA with every chemical delivery. Certificate profile CP-CHEM linked to material and customer. On GI posting, SAP auto-generates the CoA showing: Batch number, test results (Purity 99.5%, Water content 0.1%, Heavy metals: ND), QA manager signature, and ISO standard reference. CoA sent with delivery documents - customer can scan batch QR code to verify the certificate on the portal.
SPC (Statistical Process Control) in SAP QM monitors process stability using control charts. When a characteristic has SPC relevant = yes in the control key, measured values are used to plot X-bar/R charts, X-bar/S charts, or attribute charts. SAP calculates control limits (UCL/LCL) and alerts when process goes out of control. Run via QGC1. Supports Cp, Cpk process capability indices.
Example: Automotive press tool stamping 10,000 parts/day. Diameter measured every hour (5 samples). SAP plots X-bar chart: UCL = 50.08 mm, LCL = 49.92 mm, target = 50.00 mm. On day 3, chart shows 7 consecutive points above centreline (Nelson rule 2) → SAP alert "Process shift detected". Maintenance team inspects die → finds wear → replaced. Process returns to centre. Cpk = 1.45 (capable process).
SAP QM supports Audit Management for internal and external audits (ISO 9001, supplier audits, process audits). An audit is a type of quality notification with a structured question catalogue. Auditors record findings, non-conformances (NC), observations, and recommendations. NCs generate corrective actions tracked as tasks. Audit results feed into the quality score and vendor evaluation.
Example: Annual ISO 9001 surveillance audit. SAP Audit Management creates audit plan with 45 questions across clauses 4–10. Auditor records: 2 major NCs (calibration records missing, SOP not updated), 5 minor NCs, 8 observations. Each NC auto-creates a corrective action task with owner and deadline. 30-day follow-up audit scheduled. Closure recorded when evidence uploaded. Audit history maintained for 10 years.
CAPA in SAP QM is managed through the Tasks and Activities section of quality notifications. Corrective actions address existing defects; preventive actions stop recurrence. Each task has: description, responsible person, planned completion date, and status. Tasks can require signatures (electronic sign-off). Effectiveness verification is a follow-up task. Escalation is automatic on overdue tasks.
Example: Q3 notification for 15 warped panels (corrective action): Task 1 - Sort and scrap 15 panels (owner: warehouse, due 2 days). Task 2 - Adjust oven temperature from 180°C to 175°C (owner: production, due 1 day). Preventive action: Task 3 - Update SOP and retrain operators (owner: QA, due 10 days). Task 4 - Verify 3 production runs at new setting (effectiveness check, due 30 days). All tasks tracked in QM02 with status updates.
SAP MM Vendor Evaluation scores vendors across criteria including Quality (automatic score from QM), Price, Delivery, and Service. QM automatically calculates the quality score based on: inspection lot results (acceptance rate), number of quality notifications raised, and UD history. Score calculated via ME61. Low quality score can trigger vendor block in Q-Info Record.
Example: Vendor V-200 (rubber gaskets): 12 lots received, 10 accepted (83%), 3 quality notifications raised in 6 months. QM auto-calculates quality score = 72/100. Overall vendor score = Quality 72 (weight 40%) + Delivery 85 (weight 30%) + Price 90 (weight 30%) = 83.3. Score below 70 would trigger purchasing review. Quarterly report shared with vendor - gasket defect rate reduced from 5% to 1.5% after vendor corrective action.
Source inspection (type 09) is an inspection performed at the vendor's premises before the goods are shipped. An inspection lot is created from the purchase order (before GR). The QA inspector travels to the vendor, records results, and makes the UD in SAP. If accepted, a release label is printed at the vendor. On GR, the incoming lot can be skipped if source inspection was passed.
Example: Large custom forging ordered from Vendor V-300 (PO value ₹15L, 6-month lead time). On PO creation, source inspection lot 3000001 auto-created. QA engineer visits vendor plant, measures all critical dimensions on the forging before shipment. All pass → UD = Accept in SAP (mobile app on-site). Vendor ships with release label. GR at factory → inspection type 01 lot auto-skipped (source inspection passed) → material directly to unrestricted stock.
Shelf life management in SAP QM uses inspection type 08 (recurring inspection) to re-test materials before expiry. When a batch reaches its next inspection date, SAP automatically creates a new inspection lot for re-testing. If retested and approved, the expiry date is extended. If failed, the batch is blocked. Managed together with batch management and the SLED (Shelf Life Expiration Date) field.
Example: Chemical solvent batch B-200 has SLED = 31-Dec-2025. Recurring inspection set every 6 months. On 30-Jun-2025, SAP auto-creates inspection lot 4000010 for batch B-200. QA retests stability parameters: purity 99.1% (pass), colour clear (pass), viscosity 42 cP (pass). UD = Accept → SLED extended to 30-Jun-2026. Without retesting, batch would be automatically blocked after 31-Dec-2025 and could not be issued to production.
Catalogues in SAP QM are lists of codes used for qualitative inspection results, defect types, defect locations, and causes. They are organised as Catalogue Type → Code Group → Codes. Standard catalogue types: 1 = defect types, 2 = defect locations, 3 = causes, 9 = Usage decision codes. Configured via QS41. Catalogues ensure consistent recording and enable statistical analysis.
Example: Catalogue type 1 (defects): Code group SURFACE → codes: S1 Scratch, S2 Dent, S3 Corrosion, S4 Discolouration. Code group DIMENSION → codes: D1 Oversized, D2 Undersized, D3 Wrong angle. When QA records defects for metal parts, they select from this catalogue - no free text. Pareto analysis of all S1/S2/S3/S4 codes over 6 months → S1 (Scratch) = 45% of all defects → investigation of packaging and handling.
A QM Order (internal order type QM) is linked to an inspection lot to collect the costs of quality inspection - labour hours, consumables, lab reagents, test equipment usage. The QM order is a CO object - costs post to it via confirmations or activity allocations. Enables management accounting of quality costs (cost of quality = prevention + appraisal + failure costs).
Example: Incoming inspection lot for steel coils. QM Order QMO-5001 linked to lot. QA technician confirms 4 hours (activity type QA-TECH at ₹400/hr = ₹1,600). Lab uses 3 test specimens ₹200 each = ₹600. Hardness tester usage 2 hrs at ₹300/hr = ₹600. Total QM Order cost = ₹2,800. Monthly report: total incoming inspection costs = ₹1.2L. Vendor improvement programme target: reduce to ₹0.6L by enabling skip inspection for top vendors.
An Inspection Plan is material-specific - it defines quality parameters for a specific material or material-plant combination. A General Task List (type Q) in QM is not material-specific - it defines generic inspection steps for equipment, processes, or recurring checks (e.g., lab equipment calibration procedure, environmental monitoring). General task lists are referenced in maintenance plans (PM) or QM notifications.
Example: Inspection Plan QP-SHAFT: specific to material SHAFT-100, defines dimensional checks with tolerances. General Task List GTL-CALIB: defines the calibration procedure for vernier callipers - 5 steps, reference standards, acceptance criteria. GTL-CALIB is referenced in a PM maintenance plan that schedules calibration every 3 months for all 50 callipers. One general task list, 50 maintenance orders generated automatically.
SAP QM quality notifications support the 8D problem-solving methodology widely used in automotive (IATF 16949). The notification structure maps to 8D disciplines: D1 (Team), D2 (Problem description), D3 (Containment actions), D4 (Root cause - fishbone), D5 (Chosen corrective action), D6 (Implementation), D7 (Preventive actions), D8 (Team recognition). Notification activities, tasks, and long texts capture all 8 disciplines. The 8D report is printed via QM smartform.
Example: Customer complaint Q1-2025-087 for noise in gearbox. D1: Cross-functional team formed. D2: Noise level 72 dB (limit 65 dB) in 3rd gear. D3: Immediate - 100% test all gearboxes in warehouse. D4: Root cause - gear hobbing tool worn beyond limit. D5: Replace tool every 5,000 cuts instead of 8,000. D6: New tool installed, first 10 gearboxes retested OK. D7: Add tool wear monitoring to PM plan. D8: Team recognised in company newsletter. 8D report auto-generated from notification fields.
The QM Information System (QMIS) provides standard analytical reports on quality data. Key reports: MCXA - Inspection Lot Analysis (acceptance rate by material/vendor), MCXB - Defects analysis (Pareto by defect type), MCXC - Characteristics analysis (Cp/Cpk trends), MCXD - Notification analysis (open/closed, by type), QM15 - Quality level per vendor. All accessible from the QM information system menu.
Example: Monthly QM review: MCXA shows vendor V-300 rejection rate = 8.5% (benchmark 2%) → procurement team notified. MCXB Pareto: defect "Dimension out of tolerance" = 62% of all defects → engineering reviews drawing tolerances. MCXC for critical characteristic Hardness: Cpk = 0.95 (below 1.33 target) → process improvement project initiated. All data from QMIS exported to management dashboard automatically.
QM integrates with PM for test equipment management and calibration. Test equipment (e.g., callipers, gauges, thermometers) is managed as PM equipment. A calibration inspection plan (QM) is linked to the equipment. PM generates maintenance orders for calibration at scheduled intervals. QM creates the inspection lot, records calibration results, and makes the UD. Equipment is blocked from use if calibration inspection lot is open (not yet calibrated).
Example: Pressure gauge EQ-5012 must be calibrated every 6 months (regulatory requirement). PM maintenance plan generates calibration work order on 1-Apr and 1-Oct. When work order released, QM inspection lot created automatically. Calibration technician records 5 test point readings against certified standards. UD = Accept → gauge receives "Calibrated" sticker + next calibration date. UD = Reject → gauge tagged "OUT OF SERVICE", all measurements taken with this gauge in the period flagged for review.
An Inspection Point allows recording of multiple sets of results within a single inspection lot - used for continuous production monitoring where the same characteristics are checked at regular intervals (every hour, every 100 pieces). Each inspection point represents one time-stamped measurement event. Results at each point are recorded independently. Used mainly for in-process inspection (type 04) in continuous manufacturing.
Example: Tablet press running continuously for 8 hours. One inspection lot for the production order. Inspection points created every 30 minutes (16 inspection points). At each point: 10 tablets weighed, 10 tablet hardness measured, 10 disintegration times recorded. If inspection point 8 (4-hour mark) shows weight drift → operator adjusts fill depth → next inspection point confirms correction. All 16 inspection points documented for batch record - FDA audit ready.
A Partial Lot splits an inspection lot into multiple sub-lots (e.g., by shift, machine, operator) where each sub-lot gets its own UD - the overall lot can have mixed decisions. An Inspection Point records multiple measurements within one lot without splitting. Partial lots allow different stock postings per sub-lot; inspection points are for statistical monitoring only within one lot.
Example: GR of 3,000 units from vendor - 3 different production shifts. Inspection lot split into 3 partial lots: Shift A 1,000 units (all pass → released), Shift B 1,000 units (all pass → released), Shift C 1,000 units (8 defects found → UD = Reject → blocked stock). Without partial lots, one defect in Shift C would force all 3,000 units to quality decision - partial lots prevent over-rejection and improve efficiency.
Customer complaint flow: 1) Q1 Quality Notification created (QM01), 2) Returns order created in SD (VA01 order type RE), 3) Return delivery created (VL01N), 4) GR of returned goods creates inspection lot (origin 06 or 01), 5) QA inspects returned goods, 6) UD determines final disposition - scrap, rework, or return to stock, 7) Credit memo issued to customer (SD), 8) Root cause analysis and CAPA in notification, 9) Notification closed.
Example: Customer returns 200 pumps claiming bearing noise. Q1 notification QN-2025-120 created. Returns order RE-50001 raised. 200 pumps received back → inspection lot created, QA disassembles 10 units: bearing clearance 0.08 mm (spec ≤ 0.05 mm) - confirmed defect. UD: 200 units → rework. After rework, new inspection lot → all pass → returned to stock. Credit memo issued for 200 pumps. Corrective action: tighten bearing clearance inspection in production from 0.06 to 0.04 mm max.
Key QM configuration steps: 1) Activate QM in plant parameters (SPRO → QM → Basic Settings), 2) Define control keys, 3) Define sampling procedures, 4) Define inspection types, 5) Define catalogue types and codes, 6) Define notification types and partners, 7) Assign QM procurement keys, 8) Activate inspection lot origins per plant. Each plant can have different QM settings - allows phased rollout.
Example: New plant Plant 0003 being added. IMG configuration: activate QM for plant 0003, define that inspection types 01, 03, 10 are active. Assign control keys QM01 and QM02 to plant 0003. Map plant 0003 to the same catalogue types as plants 0001 and 0002. Create Q-Info Records for the top 20 vendors in plant 0003. Go-live: all incoming GRs at plant 0003 now auto-create inspection lots - QM is live in 4 weeks.
Cp (Process Capability Index) = (USL – LSL) / (6σ) - measures how wide the tolerance is vs process spread. Cpk (Process Capability Index centred) = min[(USL–μ)/3σ, (μ–LSL)/3σ] - accounts for process centring. Cp ≥ 1.33 (automotive minimum), Cpk ≥ 1.33. SAP QM calculates Cp/Cpk automatically from results data when SPC is active. Viewed in characteristic statistics report MCXC.
Example: Shaft diameter: USL=50.05, LSL=49.95 (tolerance = 0.10 mm). Process σ=0.012 mm. Cp = 0.10/(6×0.012) = 1.39 (capable). Process mean = 50.02 (slightly off-centre). Cpk = min[(50.05–50.02)/(3×0.012), (50.02–49.95)/(3×0.012)] = min[0.83, 1.94] = 0.83. Cpk below 1.33 → process not centred → engineer adjusts CNC offset to bring mean to 50.00 → new Cpk = 1.39 (both Cp and Cpk equal = perfectly centred).
The QM view of the material master (maintained via MM02) contains: Inspection type activation (01, 03, 04, 10 etc.), QM procurement key (activates quality stock), Post to inspection stock indicator, Certificate required flag, Technical delivery terms, Tolerance level for batch classification, and Inspection interval for recurring inspections. These settings drive the entire QM behaviour for the material.
Example: Material API-PARACETAMOL (pharmaceutical raw material). QM view: Inspection type 01 ✓ (incoming), Inspection type 08 ✓ (recurring, every 12 months), Post to inspection stock ✓ (GR goes to quality stock), Certificate required ✓ (vendor must provide CoA), QM procurement key 0001 (full inspection required). This single material master setup ensures complete quality control from every GR to recurring shelf-life retesting - with zero manual intervention to trigger inspections.
A Quality Notification is the broader document - it covers customer complaints (Q1), vendor complaints (Q2), and internal issues (Q3). A Defect is a specific finding within an inspection lot (recorded via QF01 during results recording). Defects can automatically generate quality notifications (if configured in the inspection plan). They are related but distinct - defects are inspection findings; notifications are the action management workflow.
Example: Inspection lot for castings: QA records 5 defects - 3 porosity (D1), 2 cracks (D2). Defect recording in QF01. Since cracks (D2) is a "critical defect" class in the catalogue, SAP auto-creates Q3 notification QN-3045 with defect details pre-filled. Q3 notification triggers: stop shipment, engineering review, supplier 8D request. Porosity defects alone would not auto-create a notification (minor defect class - just recorded statistically).
SAP QM can automatically transfer inspection results to batch classification characteristics when the UD is made. Configuration: link MIC to batch classification characteristic in the inspection plan. On UD, the mean or last value of the measured characteristic is written to the batch class. This enables batch-level quality traceability and smart batch determination in SD/PP based on quality values.
Example: Textile batch B-505: Colour Strength (MIC CS-001) linked to batch class characteristic COLOUR_STRENGTH. QA measures 5 samples: 98.2, 97.8, 98.5, 98.0, 98.3 → mean = 98.16. On UD = Accept, COLOUR_STRENGTH = 98.16 written to batch B-505. Premium customer orders require COLOUR_STRENGTH ≥ 98.0 → batch determination in SD automatically selects batch B-505 (98.16 ≥ 98.0). Standard orders use any batch ≥ 95.0.
Quantitative characteristics have measured numerical values with upper/lower specification limits (e.g., diameter, weight, pH). SAP auto-evaluates pass/fail by comparing to tolerance limits. Supports SPC, Cp/Cpk, histograms. Qualitative characteristics are attribute-based - pass/fail or selection from a catalogue (e.g., colour correct/incorrect, surface condition good/bad). No numerical processing - only frequency analysis of codes.
Example: PCB inspection. Quantitative: Track width = 0.15 mm ± 0.01 mm → measured with microscope, SPC chart maintained, Cpk calculated. Qualitative: Solder joint appearance → QA selects from catalogue: "IPC-A-610 Class 3 Acceptable" / "Defect – Insufficient Solder" / "Defect – Solder Bridge". Quantitative gives statistical insight; qualitative gives pass/fail and defect frequency data. Both types coexist in the same inspection plan.
Physical Sample Management in SAP QM tracks the physical location and status of retained samples. When samples are drawn from an inspection lot, physical sample records are created with unique identifiers, storage location, quantity, and retention period. Samples can be sent to external labs. Results recorded against physical sample IDs. Critical for pharmaceutical, food, and chemical industries where regulatory retention is mandatory.
Example: GMP batch of drug substance. 5 physical samples drawn from inspection lot: Sample PS-001 to PS-005 (each 10g). PS-001 and PS-002 sent to internal QC lab for immediate testing. PS-003 sent to external accredited lab for compendial testing. PS-004 and PS-005 placed in retention storage (2°C–8°C) for 2 years. SAP tracks each sample's chain of custody. Lab results linked back to original inspection lot. Retention samples retrievable for regulatory inspection at any time.
The QM procurement key (set in material master QM view) activates quality stock posting on GR. When combined with the Q-Info Record, it controls the vendor release status: Released (normal procurement), Blocked (no PO creation allowed), Conditional Release (allowed with warning). A vendor can be automatically blocked via a quality notification task or manually in QI02. Blocked vendors cannot receive new POs in MM.
Example: Vendor V-400 delivers contaminated chemical (3rd rejection in 6 months). QA manager opens Q-Info Record QI02 for V-400 / CHEM-300 / Plant 0001 → sets status = BLOCKED. Any buyer trying to create PO for CHEM-300 from V-400 gets hard error: "Vendor V-400 is blocked for material CHEM-300 - contact QA." Purchasing must find alternative vendor. Block lifted only after V-400 submits CAPA and 3 consecutive accepted deliveries from V-400's other plant.
SAP QM supports FDA 21 CFR Part 11 via the Digital Signature framework. Configured transactions (e.g., UD, results recording) require users to authenticate (user ID + password) and provide a reason/comment before the action is saved. The signature is logged in the change document and digital signature log - meeting Part 11 requirements for audit trail, access control, and electronic signatures. Used in pharma, med device, and biotech.
Example: QA analyst enters results for API batch. On saving, system prompts: "Digital Signature Required - Enter User ID: [jane.doe] Password: [***] Reason: [Results entry verified against lab notebook]." Entry logged with timestamp, user ID, and reason in the audit trail. QA manager then makes UD - second signature required: "Reviewed and approved by [qa.manager]." FDA inspector can see complete chain of who did what and when - without any paper records.
SAP QM integrates with the Document Management System (DMS) - inspection plans, characteristics, and notifications can link to Document Info Records (DIR) containing drawings, specifications, SOPs, and test methods. When the inspection lot is processed, the linked documents (e.g., engineering drawing, test method SOP) are accessible directly from QA32. Ensures inspectors always use the current approved version.
Example: Inspection plan for VALVE-500 links to DIR DOC-2025-081 (Engineering Drawing Rev.C) and DIR DOC-2025-144 (Test Method SOP-QA-012). When QA opens inspection lot in QA32, they click the document link icon → drawing opens as a PDF showing the exact dimension to check. If drawing is revised to Rev.D, QM planner updates the DIR link in QP02 - all future lots automatically show Rev.D. No printed drawings required (paperless QA).
SAP QM inspection plans support versioning via Change Numbers (Engineering Change Management). When a specification changes, a new version of the inspection plan is created with a validity date. Historical inspection lots reference the plan version that was valid at the time - full traceability. The change number records who changed what and when. This is essential for regulatory compliance and product change control.
Example: Customer requests shaft tolerance tightened from ±0.5 to ±0.3 mm effective 01-Apr-2025. Change number CN-2025-015 created (approved by engineering, QA, customer sign-off). QP02: inspection plan updated - characteristic "Diameter" USL/LSL changed to 50.30/49.70. Valid from 01-Apr-2025. All lots created before 01-Apr → use old tolerance. All lots from 01-Apr → use new ±0.3. Audit trail: change number CN-2025-015 links to customer approval email in DMS.
Key SAP QM database tables: QMEL - Quality notifications header, QMFE - Notification items/defects, QMMA - Notification tasks, QALS - Inspection lot header, QASR - Inspection lot short results, QAMV - Inspection specifications (characteristics in lot), QAVE - Inspection results (single values), QAPP - Inspection plan assignment to material, PLPO - Inspection plan operations, QINF - Q-Info record header.
Example: ABAP report to find all rejected inspection lots in 2025: SELECT from QALS WHERE PRUEFLOS_STATUS = '3' (rejected) AND ERDAT BETWEEN '20250101' AND '20251231'. Join QALS.PRUEFLOS → QASR.PRUEFLOS for characteristic results. Join QALS.MATNR → MARA for material description. Export to Excel for monthly quality KPI report. QALS is the central table - always start here for any inspection lot query.
SAP QM allows inspection plans to be copied from a reference plan during creation (QP01 → Extras → Copy from). The copied plan inherits all operations, characteristics, and sampling procedures. A Reference Operation Set (task list type R) stores standard operations/characteristics reusable across multiple inspection plans - any change to the reference set propagates to all plans using it (when the update is executed).
Example: Company introduces 30 new valve variants (different sizes, same test methodology). Reference Operation Set ROS-VALVE contains standard 8 operations: dimensional check, pressure test, leak test, visual. Each new valve's inspection plan is created in QP01 by copying from ROS-VALVE - all 8 operations pre-loaded. Only material-specific tolerances need to be updated. 30 plans created in 2 hours instead of 2 days. Future test method update: change ROS-VALVE once → all 30 plans updated.
Key S/4HANA QM changes: Fiori apps replace most QM GUI transactions (QA32 → "Record Inspection Results" Fiori app). Quality Issue Management (SAP QIM) provides enhanced notification workflow. Inspection lot worklist in Fiori with real-time analytics. Digital signature framework enhanced. QM integration with SAP IBP for quality-aware supply chain planning. Batch management fully integrated with ACDOCA for financial traceability.
Example: ECC QA team used QA32 (GUI). In S/4HANA, QA inspector opens Fiori Launchpad on tablet → "Record Inspection Results" app → scan inspection lot barcode → characteristics displayed with spec limits → enters values → real-time pass/fail indicator → swipe to next characteristic → save. Usage Decision in "Make Usage Decision" app - one tap, done. Mobile-enabled QA reduces paperwork by 80%. Real-time dashboards replace monthly Excel reports.
A Q2 notification is a complaint raised against a vendor for defective supplied material. Created manually or auto-triggered by a rejection UD. The Q2 notification links to: the original PO, GR document, inspection lot, defect details. It drives: 8D report request from vendor, debit memo (MM returns processing - MIGO return delivery + credit memo in MIRO), and vendor quality score update. Vendor must respond to the notification with corrective actions.
Example: 200 rubber seals rejected (hardness 45 Shore A, spec 55–65). Q2 notification QN-2025-V-088 created: links to PO 4500001234, references inspection lot, defect = "Hardness Out of Spec". Notification emailed to vendor V-200 with 8D request (deadline 10 days). MM returns: return delivery created → 200 seals returned to vendor. Credit memo for 200 seals ₹24,000 posted in MIRO. Vendor submits 8D → root cause = wrong compound batch. Corrective action verified → Q2 notification closed.
The QM Work Centre (created via IR01, category Q) represents the QA lab, inspection station, or team. Assigned to inspection plan operations. Used for: scheduling inspection capacity, calculating inspection costs (activity type × rate), and routing the inspection lot to the correct team. Work centre capacity can be planned and monitored to prevent QA bottlenecks.
Example: QM Work Centre WC-LAB has 3 QA technicians, capacity 8 hrs/day each = 24 hrs/day. Inspection plan for CHEM-500 uses WC-LAB, estimated 2 hrs per lot. Maximum 12 lots per day. During peak procurement month, 15 lots/day arriving → WC-LAB at 125% capacity → bottleneck visible in capacity report. QA manager temporarily assigns 2 additional technicians from WC-LAB2 to handle the overload.
Checklist for missing inspection lot on GR: 1) Is inspection type 01 activated in material master QM view for the plant? 2) Is the "Post to inspection stock" indicator set? 3) Does a valid inspection plan exist for the material-plant combination in status "Released"? 4) Is the Q-Info Record status "Released" (not blocked)? 5) Is the plant QM active (SPRO)? 6) Is there a valid assignment of inspection plan to the material (QA08)? 7) Check the inspection lot creation log in QA08.
Example: New material BOLT-500 added. GR posted but no inspection lot. Checklist: MM02 QM view → inspection type 01 NOT checked (root cause found). Fix: activate type 01 in MM02, set "Post to QI stock" flag. Re-run assignment via QA08 to ensure plan is linked. Test GR of 10 units → inspection lot 5000001 created and 10 units in quality stock. Issue: always check QM material master view when setting up new materials. Missing one checkbox = entire QM process bypassed silently.
Complete inspection lot lifecycle: 1) Trigger - GR/production/delivery creates lot automatically. 2) Status: Created - lot in "Queue" (inspection not started). 3) Sample Drawing - QA draws samples, updates sample quantity. 4) Status: Released - lot moved to "In Processing". 5) Results Recording - actual values entered in QE01/QA32. 6) Defects Recording - defects captured in QF01. 7) Usage Decision - UD made in QA11 → stock posting triggered. 8) Status: Completed - lot closed, data available for QMIS reporting.
Example - Complete flow: GR 500 kg Sugar (01) → Lot 9000001 created, 500 kg in quality stock. QA draws 5 samples (1 kg each). Results: Sucrose content 99.8% (pass), Moisture 0.05% (pass), Colour ICUMSA 25 (pass), Particle size 0.4 mm (pass). No defects recorded. UD = Accept (code A). Stock posting: 500 kg → unrestricted (mvt 321). Certificate of Analysis auto-printed. Lot status = Completed. QMIS updated. Batch B-SU-050 status = unrestricted. Total cycle time: 4 hours from GR to release. Production can now use Sugar batch.
🗄️ Important SAP QM Database Tables
Every SAP QM consultant should know these core tables for ABAP reporting, data extraction, and troubleshooting quality data.
| Table | Description | Key Fields |
|---|---|---|
| QALS | Inspection Lot Header - one row per inspection lot | PRUEFLOS |
| QAMV | Inspection Specifications - characteristics in a lot | PRUEFLOS + VORGLFNR + MERKLFNR |
| QAVE | Inspection Results - actual measured values per characteristic | PRUEFLOS + VORGLFNR + MERKLFNR |
| QASR | Inspection Lot Short Results (summary per characteristic) | PRUEFLOS + VORGLFNR + MERKLFNR |
| QMEL | Quality Notification Header | QMNUM |
| QMFE | Notification Items / Defects | QMNUM + POSNR |
| QMMA | Notification Tasks (CAPA actions) | QMNUM + MANUM |
| QINF | Q-Info Record Header (vendor-material QM agreement) | LIFNR + MATNR + WERKS |
| QAPP | Inspection Plan Assignment to Material | MATNR + WERKS + PLNTY + PLNNR |
| PLKO | Inspection Plan Header (Task List Header) | PLNTY + PLNNR + PLNAL |
| PLPO | Inspection Plan Operations | PLNTY + PLNNR + PLNAL + PLNKN |
| QPAM | Inspection Characteristics in Plan (MIC assignments) | PLNTY + PLNNR + PLNAL + VORGLFNR + MERKLFNR |
Tip: Always start QM queries from QALS (inspection lot header). Join QALS.PRUEFLOS to QASR for results summary or QAVE for individual sample values. For notifications, QMEL is the starting table - join to QMFE for defect items and QMMA for tasks. Use QA32 for day-to-day work; SE16N on QALS for batch data extraction.
⚡ Key SAP QM Transactions
| Transaction | Description | Area |
|---|---|---|
| QP01 | Create Inspection Plan | Inspection Planning |
| QP02 / QP03 | Change / Display Inspection Plan | Inspection Planning |
| QS21 | Create Master Inspection Characteristic (MIC) | Master Data |
| QS41 | Maintain Inspection Catalogues (defect codes) | Master Data |
| QDV1 | Create Sampling Procedure | Master Data |
| QI01 / QI02 | Create / Change Q-Info Record | Master Data |
| QA01 | Create Inspection Lot (manual) | Inspection Execution |
| QA32 | Change Inspection Lot (worklist - results + UD) | Inspection Execution |
| QE01 | Record Results for Inspection Characteristics | Results Recording |
| QF01 | Record Defects for Inspection Lot | Defects Recording |
| QA11 | Make Usage Decision | Usage Decision |
| QM01 / QM02 | Create / Change Quality Notification | Quality Notifications |
| QC11 | Create / Print Quality Certificate | Certificates |
| QGC1 | Display Control Chart (SPC) | SPC |
| MCXA | Inspection Lot Analysis (QMIS) | Reporting |
| MCXB | Defect Analysis / Pareto Chart | Reporting |
| MCXC | Characteristic Analysis (Cp/Cpk) | Reporting / SPC |
| QA08 | Assign Inspection Plans to Materials | Plan Assignment |
| ME61 | Vendor Evaluation (quality score contribution) | Vendor Quality |
Interview Ready?
Master the end-to-end inspection lot flow (Q03, Q08, Q04 combined), explain the Usage Decision and stock postings confidently, and always be ready to discuss QM in Procurement vs Production vs Sales integration. These three areas appear in 90% of QM interviews.
📘 Related SAP Tutorials
SAP FICO Interview Questions
Top 50 advanced SAP FICO interview questions covering GL, AP, AR, Asset Accounting, CO-PA with examples.
Read TutorialWhat Are SAP OSS Notes
What Are SAP OSS Notes? Complete Guide for Beginners.
Read Tutorial