ERPClimb logoERPClimb

SAP QM Defect Recording Interview Questions

Defect Recording comes up in SAP QM interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

This page carries 24 reviewed SAP QM defect recording interview questions, each with a complete written answer and no sign-in required. The set breaks down into 2 foundational, 17 mid-level and 5 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for defect recording.

24 Defect Recording questions with answers

easyDefect Recording

1. During incoming inspection (lot origin 01) a goods receipt is inspected and defects are found on several sample units. What is the standard SAP QM process for recording these defects at the inspection lot level, and how do defects relate to the results recording of the associated inspection characteristics?

Defects are recorded via QM02/QE51N against the inspection lot, referencing a defect catalog (code group/code), defect class, and optionally linking to the failed inspection characteristic and sample unit. Defects can be assigned a priority and cause code and are stored independently from but can be tied to specific characteristic results, feeding downstream analysis (Pareto, defect rate reporting) and optionally triggering follow-up actions like quality notifications.
easyDefect Recording

2. In incoming inspection (lot origin 01), what is a QM defect record, and how does it relate to catalogs, defect types/codes, and the results recording of inspection characteristics?

A defect record documents a nonconformance found during inspection, linked to a catalog (e.g., defect type, defect location, cause) configured in QM catalog maintenance. Defects can be recorded at the lot level or tied to a specific inspection characteristic's results recording, capturing quantity affected, severity, and responsible object. This data feeds usage decision evaluation, vendor evaluation, and quality notifications, giving traceability from the MM goods receipt through to corrective action.
mediumDefect Recording

3. In a delivery inspection scenario integrated with EWM, defects are recorded during results recording but the warehouse team reports they cannot see defect details on the physical inventory or quality inspection document in EWM. How do you address this integration gap?

Confirm that defect data recorded in ERP/S4 QM (QE51N) is mapped and transferred through the quality inspection engine interface to EWM's quality inspection document; not all defect fields synchronize by default, only those configured in the interface's field mapping. Check whether EWM is using its own inspection engine (for EWM-driven QIE) versus ERP-managed inspection, since defect visibility depends on which system is system of record. Validate the interface monitor for transfer errors and confirm EWM quality inspection document status reflects the ERP UD/defect update.
mediumDefect Recording

4. During in-process inspection of a semi-finished product, an operator records a defect indicating a dimensional out-of-tolerance condition, and the material is later required to be shipped with a quality certificate referencing the batch's inspection results. How should defect recording and certificate generation be coordinated to ensure the certificate accurately reflects the nonconformance?

The defect should be recorded against the specific inspection characteristic and lot with appropriate defect class/priority; if the usage decision still allows conditional release (e.g., use with deviation), this should be reflected via a UD code that ties to the certificate profile so the certificate reporting includes the actual recorded result and any deviation note, not a sanitized value. The certificate profile must be configured to pull the true characteristic result and UD status, and any deviation/rework should be documented in the inspection lot before certificate issuance.
mediumDefect Recording

5. During a rollout, business users report that the same defect type catalog is showing irrelevant codes for both incoming inspection notifications and customer complaint notifications. How would catalog profiles be restructured to fix this cross-contamination?

Catalog profiles link specific code groups and catalogs to a notification type/item combination, so separate catalog profiles should be created for incoming inspection versus customer complaint notification types, each referencing only the relevant code groups within the shared master catalogs. Rather than duplicating catalogs, restrict visible code groups per profile so business context stays clean, then assign the correct profile in the notification type configuration so the item detail screen only offers applicable defect codes.
mediumDefect Recording

6. A quality organization is consolidating defect catalogs after a merger and finds overlapping code groups with slightly different meanings for the same defect type across legacy systems. How would you approach redesigning the catalog and code group structure to support consistent reporting?

Perform a catalog harmonization workshop mapping legacy defect codes to a unified taxonomy, grouping semantically equivalent codes under standardized code groups within the merged catalog structure, and retiring duplicates through catalog status changes rather than deletion to preserve historical lot traceability. Define new code groups aligned to the combined organization's reporting categories (e.g., by defect origin or severity), migrate open usage decisions cautiously, and communicate the mapping table to inspectors and quality engineers before cutover to avoid miscoding after go-live.
mediumDefect Recording

7. During in-process inspection at a production order's final operation, an operator records a defect for a minor cosmetic nonconformance, but the certificate of analysis for the batch still needs to be generated and shipped with the product since the defect does not affect functional specifications. How would you configure defect and certificate handling to support this?

Configure the defect catalog to distinguish severity (critical/major/minor) so minor cosmetic defects don't automatically block usage decision acceptance or certificate generation. Set the usage decision code to allow acceptance with recorded defects visible in the quality notification, while the certificate profile pulls only the relevant functional characteristics' results, optionally noting defect disposition separately. Ensure PP confirmation and certificate print aren't gated by defect existence, only by UD status.
mediumDefect Recording

8. A quality manager wants to introduce a new defect classification scheme for customer complaints without disrupting existing usage decision codes and historical reporting. How would you approach catalog and code group design?

Create a new code group under an appropriate existing catalog type (e.g., catalog type 9 for defect types or a dedicated complaint catalog type) rather than modifying existing usage decision code groups, keeping usage decision catalogs untouched to preserve historical UD reporting integrity. Assign the new code group to relevant selection sets used in complaint/notification processing (QM notifications), and validate that existing catalogs referenced in closed inspection lots remain unaffected since codes are typically not deleted, only deactivated when obsolete.
mediumDefect Recording

9. Supplier quality analytics show that a large percentage of notifications are being closed with a generic 'other' defect code, making root-cause trend reporting meaningless. How would you diagnose and correct this at a configuration level?

Review the catalog profile assigned to the relevant notification type and check whether the defect/cause catalogs have too few specific codes or if 'other' was set as a default/first-selectable value, encouraging shortcut entries. Check if catalog fields are optional rather than mandatory at the relevant status transition, and whether users have training or UI guidance. Correct by refining catalog structure with more granular codes, making cause/defect entry mandatory before completion via status control, and reviewing catalog code group ownership so codes stay current for the supplier population.
mediumDefect Recording

10. After a catalog profile change was deployed, quality analysts report that when creating new complaint notifications, the defect code fields on the item are now blank/unavailable, breaking their analytics extracts. What would you check to diagnose and resolve this?

Check whether the catalog profile assigned to the complaint notification type still references the correct catalog type and code group for the item/defect (QMFE) usage, since a profile change can inadvertently remove or reassign the code group. Also verify that the code group's validity period hasn't expired and that the catalog is still flagged as usable for that notification type's inspection type or QM order type combination. Compare the transport for unintended deletions versus additions in the catalog profile customizing table.
mediumDefect Recording

11. A production nonconformance notification must classify a defect by defect location, defect type, cause, and action taken. How should the catalog structure be designed to support this?

Define separate catalog types for defect location, defect class/type, cause, and action, each containing code groups and codes grouped logically by product family or process step. Assign a catalog profile to the notification type that references the relevant catalogs for item, cause, and task coding blocks. Codes should be reusable across notification types where applicable, and selected sets can be used to restrict the list shown to users for a specific plant or material group, keeping data entry consistent and analyzable.
mediumDefect Recording

12. When configuring defect recording for delivery inspections integrated with EWM, what configuration decisions must be made to ensure defects captured during results recording are properly linked to the inspection lot and visible for corrective action tracking?

You must assign a catalog profile with defect, cause and corrective action catalogs to the inspection type/plan, activate defect recording in the inspection characteristic or as a general defect at the operation level, and configure the catalog selected sets so EWM quality inspection documents can pass defect data back via the QIE or embedded EWM-QM interface. Ensure code groups and codes are synchronized between ERP/S4 QM and the EWM system to avoid mapping failures during results transfer.
mediumDefect Recording

13. During in-process inspection of a PP order, an operator records results for a sub-lot but the follow-up action for defect recording is not triggering the expected quality notification. Walk through how you would diagnose this in the inspection lot.

First check the characteristic's control indicators (defect recording activated) and whether the sampling procedure's valuation rule triggers a notification on rejection. Verify the inspection lot's task list/plan has defect codes assigned and defects category linked to a quality notification type in configuration (QM-PP integration). Confirm in results recording that a defect was actually recorded, not just a rejected characteristic value, since notifications trigger off defects, not raw value failures. Also check user status/authorization blocking automatic notification creation.
mediumDefect Recording

14. During a sales returns inspection, an inspector records a defect against a characteristic but the defect data isn't showing up correctly linked to the returned batch when the warehouse team later checks the WM transfer order history. What could cause this disconnect and how would you fix it?

Likely causes include the defect being recorded at the inspection lot level without a batch reference if the return material isn't batch-managed at that inspection origin, or the WM transfer order was completed independently of the QM inspection lot without cross-referencing the batch/lot number in its history. Check whether the inspection type for returns (commonly origin 06 or a custom return origin) is batch-relevant, verify the defect recording includes the correct object reference (batch, material document), and confirm WM transfer order confirmation timing versus inspection lot creation to ensure proper linkage in the audit trail.
mediumDefect Recording

15. When defects are recorded during results recording for a delivery-based inspection lot integrated with EWM, what configuration decisions determine how defect data is structured and linked back to the inspection lot?

You configure a catalog profile for the inspection lot's material/plant assigning catalogs for defect type, location, cause and responsibility, and link this to the inspection plan or inspection type. Defects are recorded against inspection characteristics or independently, referencing the same lot number regardless of whether the physical quality check occurred in EWM. Key decisions include whether defects are entered in ERP QM after EWM confirmation, or captured via inspection results uploaded from EWM, and ensuring the catalog codes used are synchronized between systems so codes are meaningful and consistently interpreted.
mediumDefect Recording

16. A QM team wants inspectors recording results at goods receipt to see only a short, relevant list of defect codes for a given material category, while the full code group retains dozens of codes used across multiple material types shared with MM master data reporting. How would you use a selected set to solve this without duplicating the code group, and what MM reporting impact should you validate?

I would create a selected set referencing the existing code group but limiting the visible codes to the relevant subset for that material category, assigning the selected set at the catalog usage level tied to inspection type or material group rather than duplicating codes. This keeps a single source of truth for defect codes while narrowing the inspector's view. I would validate that MM-side reporting (e.g., quality notifications, vendor evaluation) still resolves against the full code group so historical and cross-material analytics remain intact.
mediumDefect Recording

17. During in-process inspection of a production order, an operator records a defect against a dimensional characteristic, and the batch must later be accompanied by a certificate that accurately reflects this nonconformance before the next PP confirmation step proceeds. How would you design this?

Configure the inspection plan characteristic to trigger defect recording (QM04-linked defect codes) when results fall outside tolerance, ensure the defect is linked to the specific inspection lot and characteristic via table QMFE, and configure the certificate profile to pull both results (QASE) and defect data into the certificate print program (QC20/QC21). The usage decision code should reflect the nonconformance status, and PP confirmation should be gated on UD completion using a status check or user exit so the next operation cannot proceed until the certificate accurately reflects recorded defects.
mediumDefect Recording

18. In QM catalog configuration, how would you use a selected set to restrict the damage/defect codes displayed when a shared catalog is used both for QM inspection results recording and for PM notification coding?

You would define a selected set that references a subset of codes from the full code group and assign that selected set to the specific usage (inspection type, task list, or notification type) needing it. For PM notifications sharing catalog 2 or catalog 3 codes, the selected set limits which damage codes appear to notification processors, while QM result/defect recording can reference a different selected set drawing from the same code group, avoiding maintaining duplicate catalogs while keeping each application's list relevant.
mediumDefect Recording

19. A customer complaint reveals that a defective batch shipped despite an EWM-managed delivery inspection reporting no defects. How would you investigate the integration gap between EWM quality checks and QM defect recording?

Investigate whether the EWM inspection was actually configured to synchronize defect data back to the ERP inspection lot's defect recording (QM03/results recording), since EWM's own quality inspection can be executed independently and may not always push detailed defects into the QM defects table unless the integration model and inspection type mapping are correctly set. Check the EWM-ERP inspection document link, confirm the inspection rule and characteristic mapping, and verify whether the usage decision in EWM was propagated correctly to the ERP lot, as a disconnect here can allow shipment despite unrecorded quality issues.
hardDefect Recording

20. During a catalog restructuring project, defect codes from a legacy selection set were merged into a new catalog code group, but historical usage decision reports now show inconsistent defect descriptions across inspection lots created before and after the change. How would you diagnose and prevent this?

Catalog codes are typically time-dependent but historical documents reference the code as it existed at recording time via internal keys, so descriptions can differ if code texts were changed rather than versioned properly. Diagnose by checking code validity dates and change history in catalog maintenance. Prevent recurrence by creating new codes for genuinely new meanings instead of renaming existing ones, and using validity periods to preserve historical text integrity for audit and trend reporting.
hardDefect Recording

21. Design a defects recording architecture for final inspection lots that must support root-cause analytics across multiple plants feeding a common SD delivery process, while avoiding master data duplication.

Establish a global catalog architecture using cross-plant catalog profiles referencing shared code groups/codes (defect type, defect location, cause) maintained centrally in QS41-QS42, then assign plant-specific defect recording profiles in the inspection plan referencing these global catalogs rather than creating plant-local codes. Enable Quality Notification (QM01) auto-creation from defects using notification type customizing linked to usage decision codes, and use QM information system (QM60xx reports) or embedded analytics on ACDOCA-equivalent QM tables (QMEL/QMFE) for root-cause aggregation across plants without duplicating catalogs.
hardDefect Recording

22. An architect is troubleshooting a recurring issue where defects recorded during incoming inspection are not appearing in the vendor evaluation score despite correct usage decisions. What root causes should be investigated?

Check whether defect recording is linked to the correct catalog and code group mapped to vendor evaluation criteria (QM subscore), whether the vendor evaluation automatic update indicator is active in the QM view of the purchasing info record or vendor master, and whether the UD code used actually triggers a vendor evaluation score update (some UD codes are configured as non-scoring). Also verify defects were saved before UD and that the info record/material combination used in evaluation matches the inspection lot's actual vendor-material link.
hardDefect Recording

23. During a customer complaint investigation, defects recorded against a sales-return inspection lot (origin 06) are not appearing in the QM defect analysis reports that procurement and production teams rely on for supplier and process quality metrics. As the architect, how would you diagnose and resolve this cross-functional visibility gap?

First verify that the sales-return inspection lot's catalog profile and defect recording configuration align with the same code groups/catalogs used for GR (origin 01) and production (origin 04) lots, since inconsistent catalog assignment fragments reporting. Check whether defects are being recorded at the item/characteristic level with proper defect type/code group linkage, and confirm QM information system (QM01-QM07) selection includes origin 06 in report variants. Root cause is often origin-specific catalog profiles or excluded inspection lot origins in report selection criteria, requiring catalog harmonization and report variant correction.
hardDefect Recording

24. Describe the end-to-end process of restructuring legacy flat defect catalogs into a hierarchical catalog and code group structure that supports multiple inspection plan groups across a global template, without breaking historical usage decision reporting.

Start by inventorying existing catalog types, code groups, and selected sets per legacy system, mapping overlapping defect meanings. Design a global catalog hierarchy with standardized code groups reused via selected sets per usage, keeping legacy codes inactive rather than deleted so historical inspection lots retain their original text. Migrate new inspection plans and MICs to reference the new selected sets, run parallel testing on new lots, then cut over by usage date rather than mass-updating closed lots, and validate reporting continuity by comparing pre- and post-cutover defect trend reports.

Related topics

Quality NotificationsInspection PlanningInspection LotsUsage DecisionQuality CertificatesResults RecordingQM in ProcurementCalibration InspectionS/4HANA Quality Management, Migration, Public Cloud and ArchitectureQM Master Data

Next practice step

Practice with Interview AITake a mock test