SAP QM Results Recording Interview Questions

Results Recording is a standard block in SAP QM interviews. It is rarely asked as a definition; it is asked as a situation you have to talk your way through.

Results Recording is the core QM transaction activity where inspectors capture measured, valuated or Boolean quality characteristics against an inspection lot, feed defect/notification data, and drive the Usage Decision that releases or blocks stock. This part covers the business purpose and manual recording workflow for beginners, then moves into configuration of characteristic control keys, sampling, single vs. summarized recording, and inspection points for intermediate consultants, including ECC vs S/4HANA differences.

This page carries 29 reviewed SAP QM results recording interview questions, each with a complete written answer and no sign-in required. The set breaks down into 3 foundational, 20 mid-level and 6 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.

Treat the answers as a starting structure, not a script. Interviewers in SAP QM rounds follow up on whatever you sound least certain about, so the value is in being able to keep going after the first answer.

29 Results Recording questions with answers

easyResults Recording

1. What is a selected set in SAP QM catalog configuration, and why would you use one instead of assigning the full code group to a usage?

A selected set is a restricted subset of codes taken from a code group within a QM catalog, defined for a specific usage (e.g., defect recording, usage decision). Instead of exposing every code in a large code group, the selected set limits what users see for a particular inspection type, plant, or material context, improving data entry accuracy and preventing irrelevant or outdated codes from being chosen during results recording or defect logging.

easyResults Recording

2. In QM catalog configuration, what is the purpose of a selected set, and how does it change what users see during results recording or defect recording compared to using the full code group list?

A selected set is a subset of code groups from a catalog that is explicitly grouped together and assigned to an object such as an inspection type, task list, or defect recording usage. Instead of exposing every code group in the catalog, the selected set limits the dropdown to only the relevant, pre-approved codes for that business context, reducing user error, speeding data entry, and keeping global catalogs reusable across plants while still context-specific.

easyResults Recording

3. In batch-managed materials, why might a single inspection lot require recording results against multiple specifications, and how does the system determine which specification version applies?

A material can have multiple valid specifications (master inspection characteristics or specs) tied to different batch attributes, customer requirements, or validity periods, especially in process industries. The system selects the applicable specification based on the batch classification, the material's inspection type, and validity dates maintained in the specification database. Inspectors record results against the version linked to the batch's characteristic values, ensuring the correct acceptance criteria are applied per batch.

mediumResults Recording

4. When configuring results recording for a delivery inspection integrated with EWM, what configuration steps ensure characteristics are correctly transferred and recorded?

The inspection plan must be assigned to the material with characteristics linked to master inspection characteristics; sampling procedures determine sample size. For EWM-integrated scenarios, the inspection type must support decentralized WM processing, and the QIE (Quality Inspection Engine) or classic RFC integration must be configured so inspection lots created in EWM synchronize characteristic results back to ERP QM tables like QASE. Control indicators on the inspection plan operation determine whether results recording is mandatory before usage decision.

mediumResults Recording

5. When results recording for delivery-based inspection lots is executed through an EWM-managed warehouse, what configuration steps ensure results entered by warehouse personnel are correctly transferred back to the ERP inspection lot?

You must configure the quality inspection engine in EWM to reference the ERP inspection type and characteristics via the sampling procedure and QIE integration, ensure the material master's QM view has EWM-relevant inspection setup active, and confirm the RFC/queue-based communication (or CIF-like distribution for decentralized EWM) synchronizes characteristic results and usage decision status. Mapping of EWM quality inspection document fields to ERP results recording table QASE must be validated, and confirmation of the warehouse task should trigger the ERP UD update.

mediumResults Recording

6. During results recording for a goods receipt inspection lot, the warehouse team needs the WM/EWM transfer order to remain blocked in the quality inspection area until characteristic results are valuated. What integration points ensure this synchronization?

The inspection lot's stock is held in quality inspection stock type, and the WM/EWM transfer order for putaway is generated referencing that stock type so goods physically remain in a QI storage area/bin. Results recording (QE01/QE51N) captures characteristic values, but the stock only changes to unrestricted after usage decision with a valid stock posting follow-up action; the WM/EWM transfer order for final putaway to bulk storage is only released once the UD updates stock status, ensuring physical movement aligns with quality release.

mediumResults Recording

7. During in-process inspection at a PP operation, results recording shows several characteristics failing but the operator wants to continue production without stopping the order. What configuration and process options address this?

Use characteristic-level valuation with defect recording rather than immediate lot rejection, allowing partial results recording while the inspection lot stays open; configure the inspection point completion or sample-based partial lot confirmation so PP confirmation isn't blocked. Enable defects recording (QM03/QA32) to log nonconformances against the operation and route to a follow-up action like rework, without triggering an automatic stop unless the inspection type or control key mandates milestone confirmation dependency.

mediumResults Recording

8. When results recording for delivery-based inspection lots is executed in an SAP EWM-managed warehouse, what configuration must be aligned between ERP QM and EWM to ensure results flow back correctly?

You must synchronize the inspection type/origin mapping so EWM creates quality inspection documents linked to the ERP inspection lot, align master inspection characteristics and sampling procedures via CIF or embedded distribution, and configure the QIE (Quality Inspection Engine) inspection rule in EWM to match ERP catalogs and code groups. Results recorded in EWM's inspection document must post back to update the ERP inspection lot's characteristic results and usage decision status.

mediumResults Recording

9. In an EWM-integrated inventory quality control scenario, what configuration ensures that results recording and usage decision correctly trigger the appropriate stock posting and warehouse task in EWM?

The inspection type must have stock posting parameters configured (QM movement types linking to inspection stock), and the material master QM view must activate inspection for the relevant inspection origin (e.g., 09 or 10 for inventory checks). On the EWM side, the warehouse product/storage type must recognize QM-relevant stock status, and the QM-EWM integration (via the inspection-relevant indicator and quality inspection storage type) ensures usage decision postings generate the correct EWM warehouse task to move stock from quality to unrestricted or blocked areas.

mediumResults Recording

10. A delivery inspection lot (origin 10) is created in ERP QM for outbound goods, and the warehouse operates in a decentralized EWM system where the physical quality check is performed. What configuration ensures the results recorded during the EWM quality inspection task are correctly transferred back and posted into ERP results recording without duplication?

Configure the inspection lot origin and inspection type mapping so QM creates the lot in ERP while EWM generates a corresponding quality inspection document linked via the delivery/warehouse task. Ensure characteristic transfer via the QM-EWM interface (CIF or embedded integration for S/4) is consistent between inspection plan characteristics and EWM inspection rule characteristics, and that results are posted back once via the confirmation, preventing double results recording by locking ERP entry during EWM task execution.

mediumResults Recording

11. During a stability study, a batch's test results at a mid-point time interval are missing due to a lab system interface failure with DMS-attached protocols. How would you troubleshoot and remediate the compliance gap?

Check the stability study inspection plan (recurring inspection schedule) to confirm the mid-point lot was created and dispatched correctly; review interface logs between the results system and QM (via IDoc or API) for the failed transfer. Verify the DMS document info record link wasn't broken, causing missing protocol attachment. Remediate by manually re-entering verified lab results with justification, documenting the interface failure and corrective action in the quality notification, and assessing impact on the overall study conclusion and regulatory submission.

mediumResults Recording

12. In an in-process inspection scenario integrated with Warehouse Management, results recording for a process order is delayed and the WM system has already confirmed putaway of finished goods into a fixed storage bin. What integration risks arise and how should this be managed?

The main risk is that finished goods physically reach storage before the inspection lot's usage decision is made, meaning the WM stock status may not reflect actual quality status, creating a possible mismatch between inventory availability and quality release. This should be managed by ensuring the inspection type is configured to keep stock in quality inspection status until UD, so WM putaway strategies respect the QI stock category and route to a blocked or quarantine storage type rather than allowing picking-relevant bins.

mediumResults Recording

13. During an audit, control chart evaluation results shown in an inspection lot cannot be traced back to the underlying raw measurement data files stored in DMS, even though the control chart itself displays as in-control. How would you troubleshoot this traceability gap?

Check whether the DMS document info records used to store raw measurement files are correctly linked to the specific inspection lot and characteristic result records, not just generically to the material or inspection plan. Verify the document status and version referenced matches the timeframe of the control chart evaluation, and confirm the interface or manual process that uploads raw data files runs before or with the results recording step. Also check if multiple document versions exist and the wrong version is linked, breaking the audit trail.

mediumResults Recording

14. How is stock held under inspection quality status managed and released when results recording confirms conformance, particularly where Warehouse Management is active?

Stock is posted to quality inspection stock (unrestricted-use blocked category) at goods receipt or delivery-related movement, keeping it non-issuable for other uses. Once results recording confirms conformance and usage decision is made, the stock category is updated (typically to unrestricted) triggering a follow-up movement in WM to relocate the material from a quarantine storage type/bin to normal storage. Configuration links the inspection type's stock posting settings with WM movement types to ensure physical and system stock stay synchronized.

mediumResults Recording

15. During results recording for an in-process production inspection lot in a WM-managed storage location, how does the system ensure that stock movements triggered by the inspection remain synchronized with the warehouse transfer requirement process, and what happens if results recording is delayed?

Stock postings from QM (e.g., to quality inspection stock or blocked stock) generate transfer requirements/orders in WM via the interim storage type linkage configured in the WM movement type control. If results recording is delayed, the material may sit in an interim area longer than expected, delaying putaway confirmation and potentially causing bin occupancy or picking conflicts. Coordination requires aligning inspection lot processing time with WM confirmation SLAs and using status-dependent stock types to prevent premature putaway.

mediumResults Recording

16. For delivery inspection lots (origin 10) processed in a decentralized EWM environment, what configuration is required so that results recording performed in ERP QM can be synchronized with the quality inspection task confirmed in EWM, and where does the usage decision ultimately get recorded?

The inspection setup uses origin 10 with an inspection type linked to the delivery process; EWM generates a quality inspection document (QIE) tied to the ERP inspection lot via the physical inspection group and CIF/queue integration. Sample results can be recorded in EWM RF or GUI and are transferred back to ERP characteristic results via the QM-EWM interface. The usage decision itself is always recorded in ERP QM against the inspection lot, not in EWM.

mediumResults Recording

17. For delivery inspection lots (origin 10) processed through an EWM-managed warehouse, what configuration ensures results recording performed against the ERP inspection lot aligns correctly with the usage decision, and where is the final usage decision recorded?

Configuration must align the inspection type and control key so ERP creates the inspection lot and quality info records/inspection plan drive the characteristics, while EWM's quality inspection engine (QIE) generates the corresponding warehouse task using the same sampling data via the ERP-EWM interface. Results entered in EWM (mobile RF or desktop) are transferred back to the ERP inspection lot's results recording tables; the usage decision itself is always finalized in ERP QM (QA11/QA12), not in EWM, since EWM only executes and confirms the inspection task.

mediumResults Recording

18. An operator recording results for an in-process inspection lot on a production order needs the resulting batch to carry a certificate showing measured values, but the PP confirmation for the next operation is scheduled to happen almost immediately after results are saved. How would you design the sequencing of results recording, usage decision, and certificate creation to avoid delaying production while still ensuring the certificate is accurate?

Configure results recording to auto-complete valuation when all characteristics are entered, then trigger the usage decision automatically via a follow-up action or workflow as soon as recording is saved, provided no manual review is required by quality rules. Certificate generation should be scheduled as a background job triggered by the UD rather than run synchronously with PP confirmation, so the operator's confirmation proceeds without waiting on print output. For characteristics requiring manual QM review, define a short-cycle approval step so it doesn't block production but still ensures certificate accuracy.

mediumResults Recording

19. A production line performs in-process inspection at a critical operation, and the customer requires a quality certificate that includes the actual recorded measurement values before the batch can proceed to the next PP operation. How would you design the sequencing of results recording, usage decision, and certificate creation to satisfy this without stalling the production schedule?

Configure the in-process inspection point to require results recording completion (RR indicator set for all mandatory characteristics) as a hard stop before the PP confirmation of that operation, using inspection-point-relevant control keys. Once results are recorded, set an automatic or immediate manual usage decision with a UD code linked to certificate creation (QC01/QC20 profile) so the certificate is generated referencing the batch and inspection lot data directly from results recording. To avoid delaying production, define the certificate profile to pull data automatically at UD save rather than requiring separate manual certificate creation, and route only exception cases (failed characteristics) for hold.

mediumResults Recording

20. An inspection lot created via stock transfer (origin 05) shows results recording locked/greyed out for certain characteristics, while a similarly configured GR-based lot (origin 01) allows full entry. What is likely causing this difference and how would you resolve it?

This usually points to inspection plan or task list assignment differences between origins; the stock transfer inspection type may reference a task list version with fewer or different characteristic control indicators (e.g., characteristic marked as 'not recordable' or inherited from a different usage). I'd compare the task list/inspection plan assigned to each origin via the material's inspection setup, check characteristic control indicators, and verify the correct inspection plan usage (e.g., usage 5 for goods movement) is assigned.

mediumResults Recording

21. A supplier quality team reports that control chart analytics dashboards show gaps and inconsistent trend lines for a material even though inspection lots were completed and results recorded on schedule, and the control charts appear correctly evaluated with DMS-attached chart images in the inspection lot. How would you troubleshoot this?

First confirm whether the analytics extraction relies on the DMS document objects or the underlying SPC result values in the quality management tables; if analytics pulls document metadata rather than characteristic values, missing or delayed DMS synchronization can create dashboard gaps even when charts display correctly in the transaction. Check whether sample results were transferred asynchronously from a lab system causing timing mismatches with the analytics extract cycle. Verify control chart evaluation rules and sampling procedure consistency across the affected lots, and confirm the analytics data source reflects the same characteristic and sampling scheme used for chart generation.

mediumResults Recording

22. During results recording for an inspection lot tied to a WM-managed storage location, what configuration ensures stock postings from usage decision correctly trigger transfer requirements in the warehouse?

The inspection type must be configured with stock posting activated (insp. w/ or w/o task list, movement type control), and the plant/storage location combination needs WM number assignment. Movement types used during usage decision (e.g., 321, 349) must have corresponding WM movement type entries in the WM movement type table so the system generates transfer requirements automatically when the goods movement posts.

mediumResults Recording

23. During in-process inspection on a production order, an operator records results but the system requires a certificate to accompany the batch once the order is confirmed. How should results recording, usage decision, and certificate generation be sequenced to satisfy this requirement without delaying production confirmation?

Results recording and usage decision on the in-process inspection lot should occur as close to real-time as possible, ideally before or immediately at order confirmation, so the certificate profile linked to the material/batch can pull finalized results. If confirmation must proceed before UD due to process timing, configure the certificate creation to trigger only after UD is set, holding certificate output separately from production confirmation, and use batch status management to prevent the batch from being used or shipped until both UD and certificate are complete.

hardResults Recording

24. For a batch-managed material undergoing results recording across multiple partial lots, how does SAP determine the usage decision status and stock posting at the batch level versus the inspection lot level, and what complexities arise when characteristics fail for only some batches?

Results recording occurs per inspection lot, and each lot is tied to a specific batch and quantity. When multiple partial lots exist for the same material batch (e.g., split GRs), each lot has an independent usage decision; a failed characteristic in one lot does not automatically propagate a rejection to other lots of the same batch unless batch status management or a batch-wide block is manually triggered. This creates complexity in ensuring consistent batch quality status, especially when batch characteristics (class) are updated only from specific inspection results, requiring manual reconciliation or custom logic via user exits.

hardResults Recording

25. Result recording for a characteristic is not showing the expected inspection method instructions, even though the method appears correctly assigned in the master characteristic. How would you investigate this as an architect responsible for global master data governance?

I would first check which method version is actually referenced by the specific inspection plan operation, since plans lock to a version at the time of assignment and do not automatically pick up later method changes. Next, verify the characteristic's method assignment validity dates and whether a newer method was released but not propagated to existing plans. I would also check if the material's inspection plan was regenerated after the method update, and review change documents on the method master to confirm when and by whom it was revised.

hardResults Recording

26. During hypercare after go-live, business users report that a custom quality characteristic field populated via MDG governance workflow is not appearing correctly in the S/4HANA quality inspection results screen, despite fit-to-standard workshops having accepted standard configuration. How would you troubleshoot and resolve this?

First verify whether the field is a genuine extension (custom Z-field) or a standard field misconfigured during fit-to-standard; check the extensibility layer (in-app extensibility via custom fields and logic) to confirm the field was correctly exposed on the inspection results UI and mapped to the underlying CDS view. Next validate the MDG replication/workflow output actually populates the correct backend table before UI rendering. If the field was added post-workshop without updating the Fiori app configuration or the extensibility scope, that's the likely root cause—requiring UI adaptation via key user extensibility and confirming ACDOCA/QM tables aren't the miscommunication point.

hardResults Recording

27. What data integrity controls should be architected to prevent PP work center results recording from proceeding when the measuring/test equipment assigned to an inspection characteristic has an invalid or overdue calibration status?

Link each measuring equipment record's usable/calibration status (set via user status profile driven by the last calibration inspection lot UD) to the inspection characteristic in the plan, then use a custom check (enhancement/BAdI) in QE51N results recording that validates equipment status before allowing entry, blocking or warning if calibration is overdue. Combine with mandatory equipment assignment fields on characteristics, restricted authorizations to bypass warnings, and periodic audit reports comparing equipment calibration due dates against result-recording timestamps to catch gaps.

hardResults Recording

28. For a regulated manufacturer using digital signatures to authorize inspection results recording and quality certificate release, how would you architect the electronic signature strategy so it satisfies 21 CFR Part 11-style requirements while integrating with PP order confirmation and usage decision steps?

Configure signature strategies in QM (via digital signature customizing) tied to specific activities: usage decision, results recording approval, and certificate release, each requiring authentication (password or higher assurance) with reason codes. Link signature-relevant steps so PP confirmations cannot proceed until the inspection lot usage decision is digitally signed, enforced through status management. Signatures are logged with user, timestamp, and meaning in the signature log table, providing an audit trail. Certificate printing programs should check signature completion status before allowing release, preventing bypass.

hardResults Recording

29. A goods receipt-driven incoming inspection lot exists in the system, but results recording shows no characteristics available to record even though the material has an active inspection plan. As the architect, how do you systematically root-cause this?

Check the inspection lot's inspection specifications tab to confirm a task list/plan was actually copied at lot creation, not just exists in master data; a plan status not released or usage key mismatch (e.g., plan for usage '5' vs lot requiring '1') prevents copying. Verify plan validity dates against the goods receipt date and that the material's inspection type is correctly configured to reference plans versus routing-based characteristics. Check whether characteristics were deactivated at the operation level or the sampling procedure has zero sample size, suppressing results recording fields entirely.

Next practice step

Practice with Interview AI Take a mock test

SAP QM Results Recording Interview Questions

29 Results Recording questions with answers

1. What is a selected set in SAP QM catalog configuration, and why would you use one instead of assigning the full code group to a usage?

2. In QM catalog configuration, what is the purpose of a selected set, and how does it change what users see during results recording or defect recording compared to using the full code group list?

3. In batch-managed materials, why might a single inspection lot require recording results against multiple specifications, and how does the system determine which specification version applies?

4. When configuring results recording for a delivery inspection integrated with EWM, what configuration steps ensure characteristics are correctly transferred and recorded?

5. When results recording for delivery-based inspection lots is executed through an EWM-managed warehouse, what configuration steps ensure results entered by warehouse personnel are correctly transferred back to the ERP inspection lot?

6. During results recording for a goods receipt inspection lot, the warehouse team needs the WM/EWM transfer order to remain blocked in the quality inspection area until characteristic results are valuated. What integration points ensure this synchronization?

7. During in-process inspection at a PP operation, results recording shows several characteristics failing but the operator wants to continue production without stopping the order. What configuration and process options address this?

8. When results recording for delivery-based inspection lots is executed in an SAP EWM-managed warehouse, what configuration must be aligned between ERP QM and EWM to ensure results flow back correctly?

9. In an EWM-integrated inventory quality control scenario, what configuration ensures that results recording and usage decision correctly trigger the appropriate stock posting and warehouse task in EWM?

11. During a stability study, a batch's test results at a mid-point time interval are missing due to a lab system interface failure with DMS-attached protocols. How would you troubleshoot and remediate the compliance gap?

12. In an in-process inspection scenario integrated with Warehouse Management, results recording for a process order is delayed and the WM system has already confirmed putaway of finished goods into a fixed storage bin. What integration risks arise and how should this be managed?

13. During an audit, control chart evaluation results shown in an inspection lot cannot be traced back to the underlying raw measurement data files stored in DMS, even though the control chart itself displays as in-control. How would you troubleshoot this traceability gap?

14. How is stock held under inspection quality status managed and released when results recording confirms conformance, particularly where Warehouse Management is active?

16. For delivery inspection lots (origin 10) processed in a decentralized EWM environment, what configuration is required so that results recording performed in ERP QM can be synchronized with the quality inspection task confirmed in EWM, and where does the usage decision ultimately get recorded?

17. For delivery inspection lots (origin 10) processed through an EWM-managed warehouse, what configuration ensures results recording performed against the ERP inspection lot aligns correctly with the usage decision, and where is the final usage decision recorded?

20. An inspection lot created via stock transfer (origin 05) shows results recording locked/greyed out for certain characteristics, while a similarly configured GR-based lot (origin 01) allows full entry. What is likely causing this difference and how would you resolve it?

22. During results recording for an inspection lot tied to a WM-managed storage location, what configuration ensures stock postings from usage decision correctly trigger transfer requirements in the warehouse?

24. For a batch-managed material undergoing results recording across multiple partial lots, how does SAP determine the usage decision status and stock posting at the batch level versus the inspection lot level, and what complexities arise when characteristics fail for only some batches?

25. Result recording for a characteristic is not showing the expected inspection method instructions, even though the method appears correctly assigned in the master characteristic. How would you investigate this as an architect responsible for global master data governance?

27. What data integrity controls should be architected to prevent PP work center results recording from proceeding when the measuring/test equipment assigned to an inspection characteristic has an invalid or overdue calibration status?

29. A goods receipt-driven incoming inspection lot exists in the system, but results recording shows no characteristics available to record even though the material has an active inspection plan. As the architect, how do you systematically root-cause this?

Related lesson

Related topics

Next practice step