ERPClimb logoERPClimb

SAP QM Inspection Lots Interview Questions

Inspection Lots 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.

Inspection Lots are the central document object in SAP QM used to plan, execute, and document quality inspections triggered by logistics processes such as goods receipt, production order confirmation, and delivery. This topic covers lot structure, origin-driven creation, control keys, integration with MM/PP/SD/PM, results recording, usage decisions, and how behavior differs across ECC and S/4HANA deployments.

This page carries 56 reviewed SAP QM inspection lots interview questions, each with a complete written answer and no sign-in required. The set breaks down into 13 foundational, 22 mid-level and 21 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 inspection lots.

56 Inspection Lots questions with answers

easyInspection Lots

1. What is a QM worklist, and how does it help inventory quality control teams manage open inspection lots across procurement receipts?

A QM worklist (e.g., via QA07 or similar list transactions) is a filtered list of open inspection lots requiring action—results recording, usage decision, or stock posting. It lets quality controllers group lots by plant, material, inspection type, or origin, prioritize overdue lots, and process usage decisions in bulk. For inventory quality control tied to procurement, it prevents stock from sitting indefinitely in quality inspection status by surfacing lots that need attention, improving throughput and reducing GR-to-stock cycle time.
easyInspection Lots

2. How is skip-lot (skip testing) inspection configured for goods receipt inspection lots, and what happens to the inspection lot and stock posting when a lot is skipped?

Skip lot is driven by the dynamic modification rule assigned to the inspection type/plan combination in the material master QM view, together with a quality level record that tracks the sequence of accepted lots. Once the quality level reaches the skip stage, the system still creates an inspection lot for the goods receipt but automatically triggers usage decision without requiring results recording, releasing stock to unrestricted use directly. Sampling procedure and dynamic modification must both be flagged active in the inspection plan.
easyInspection Lots

3. What role does dynamic modification play in sales and delivery-based inspection lots, and how does it adjust inspection severity for repeat business with the same customer?

Dynamic modification uses quality level records tied to material/customer combinations to track inspection history. Based on accepted or rejected lots, the system automatically escalates (tightening) or relaxes (skip-lot/reduced sampling) severity for future delivery inspections, per the rule assigned in the inspection plan's sampling procedure. This reduces unnecessary inspection effort for consistently compliant customer-material combinations while ensuring problem areas get tighter scrutiny.
easyInspection Lots

4. What is a skip lot and how does the dynamic modification rule enable skip-lot inspection for incoming goods in QM?

A skip lot is an inspection lot that is automatically set to 'skip' (no inspection required, stock posted directly to unrestricted use) based on a dynamic modification rule tied to a quality level. The rule tracks consecutive accepted lots for a material-vendor combination and switches inspection severity (normal, tightened, reduced, skip) using QDR/quality level records maintained in the material's inspection setup, reducing inspection effort for consistently reliable suppliers.
easyInspection Lots

5. What determines the inspection lot origin for a goods receipt against a purchase order, and why is this configuration significant?

Inspection lot origin (e.g., 01 for GR against PO) is derived from the inspection type assigned in the material master QM view combined with the movement type used. It drives which QM control key, inspection lot creation logic, and stock posting rules apply, linking MM movement to QM inspection processing. Origin 01 differs from origin 04 (goods issue) or 05 (delivery), each triggering distinct lot creation and follow-up logic in inventory management.
easyInspection Lots

6. What authorization objects and role design considerations govern a quality inspector's access to Fiori quality apps when inspection lots are triggered from PP production and process orders?

Access is controlled through PFCG business catalogs/roles assigned to Fiori launchpad groups, backed by classic authorization objects such as Q_LOSKAT (inspection lot), Q_TASK, and plant-level org value restrictions. For PP-triggered lots, roles must also include authorization for the underlying order type and plant so inspectors see only relevant lots. Role design should map catalog-to-role assignments consistently with backend authorization to avoid apps showing empty worklists despite valid backend access.
easyInspection Lots

7. What triggers the automatic creation of an inspection lot during a goods receipt against a purchase order, and how does the inspection type configuration determine this?

An inspection lot is created automatically when the material master has an active inspection type (e.g., 01 for goods receipt from purchasing) assigned in the QM view, and inspection setup is maintained for that material/plant combination. During MIGO goods receipt, the system checks the inspection type control indicators (lot-relevant, GR posting to stock in QI) and generates the lot with status linked to the material document, blocking stock in quality inspection status until usage decision.
easyInspection Lots

8. Which Fiori apps replace the classic SAP GUI transactions for day-to-day quality inspection processing in S/4HANA, and how do they integrate with MM goods receipt inspections?

Manage Inspection Lots (F1670) and Record Usage Decision (F2232) replace QA32/QE01 workflows for lot processing and UD entry. When a goods receipt is posted in MM against a material with QM active in the material master and inspection setup, an inspection lot is auto-created via QM-MM integration, triggering these apps for results recording and UD, which then release or block the stock in inventory.
easyInspection Lots

9. What is a stock transfer inspection in SAP QM, and when would inspection type 08 (or 04 depending on configuration) be triggered during a plant-to-plant stock transfer?

A stock transfer inspection generates an inspection lot when material moves between plants or storage locations under quality management control, typically via movement type 301/303 with QM active for stock transfer at the receiving plant. Inspection type 08 (goods receipt for stock transfer) or a customized type is activated in the QM view of the material master, ensuring incoming stock is held in quality inspection status until a usage decision is made before it becomes unrestricted.
easyInspection Lots

10. In an S/4HANA environment with EWM-managed storage locations, what Fiori-based configuration steps ensure that quality inspection lots created at goods receipt are correctly visible and actionable to warehouse quality staff?

Ensure the storage location is EWM-managed with QM inspection type 04/89 activated in the material master, and that the EWM quality inspection engine (QIE) is configured to trigger inspection documents synchronized with the S/4HANA inspection lot. Assign warehouse quality staff the Manage Inspection Lots and Record Results Fiori apps with plant/storage-location-restricted authorizations, and verify IDoc/queue-based replication (QINSPTYPE, QMAT) between EWM and S/4HANA is active.
easyInspection Lots

11. What is an inspection lot in SAP QM, and specifically how does inspection lot origin '01' link the goods receipt posting in MM to the creation and processing of the inspection lot?

An inspection lot is the QM object that controls and documents inspection activities for a material quantity. Origin '01' is triggered by inspection setup in the material master QM view (inspection type 01 active) combined with the movement type control for goods receipt against a purchase order. MIGO posting creates the lot automatically, stock initially posts to quality inspection stock (blocked for use), and the lot references the material, plant, vendor, batch, and purchase order document for traceability until usage decision is made.
easyInspection Lots

12. When stock is placed in quality inspection status during goods receipt, what determines whether that stock is batch-managed, and how does inspection status interact with batch classification?

Batch management is activated at material master level (batch management indicator plus batch level configuration), independent of inspection type. When an inspection lot is created, the goods receipt stock posts to quality inspection stock category tied to the batch. The batch classification (characteristics) can be updated during results recording, but the restricted usage status itself is controlled by MM stock status, not batch classification directly.
easyInspection Lots

13. What is an inspection lot origin in SAP QM, and why does the origin value (e.g., 01, 04, 05) matter for how the lot is created and processed?

Inspection lot origin is a key that identifies the business transaction that triggered lot creation, such as 01 for goods receipt against a PO, 04 for in-process/production, 05 for delivery inspection with QM in SD, or 89 for manual lots. It determines which inspection type is proposed, control key defaults, follow-up actions on usage decision (like stock posting or delivery block), and which source document fields populate the lot.
mediumInspection Lots

14. During a stock transfer between plants where the receiving plant requires inspection, what is the stock posting behavior in QM, and how does this integrate with EWM when the receiving location is warehouse-managed?

On goods receipt into the receiving plant with an active inspection type (e.g., 05 or 08), stock posts to quality inspection stock, blocking it from unrestricted use. An inspection lot is created referencing the stock transfer document. If the storage location is EWM-managed, the inspection stock status triggers a putaway strategy to a quality inspection storage type, and the usage decision in QM later triggers a warehouse task to move stock to a final storage bin only after release.
mediumInspection Lots

15. During a quality data migration for a company entering S/4HANA with localized inspection lot statuses, the business reports that Fiori quality apps show incomplete analytics tiles for certain plants after go-live. How would you diagnose and resolve this?

Check if role assignments (business catalogs/PFCG roles) for the affected plants' users include the correct Fiori launchpad spaces and analytical query authorizations; verify that migrated inspection lot data populated CDS view-relevant fields (e.g., plant, inspection type) correctly. Confirm analytical query filters aren't restricting by an organizational value missing in migrated records, then re-run migration reconciliation reports comparing legacy counts to ACDOCA-linked inspection results before republishing the tiles.
mediumInspection Lots

16. During cutover, EWM-managed storage locations show inspection lot quantities that don't match the quality stock displayed in the Manage Inspection Lots Fiori app. How would you troubleshoot this discrepancy?

I would first verify whether the affected storage locations are EWM-managed and check the queue for QM-relevant IDocs or API messages between S/4HANA and the decentralized or embedded EWM instance, since inspection lot quantity updates depend on timely stock posting confirmations from EWM. I would compare inspection lot quantities in the backend against EWM warehouse stock, check for failed or delayed quality inspection engine (QIE) or handling unit confirmations, and reprocess any stuck queue entries before validating the Fiori app refresh.
mediumInspection Lots

17. A production shift reports that inspection lots created from a process order via PP-QM integration are not appearing in the expected Fiori worklist app, even though the lots exist in the backend. How would you troubleshoot this in an S/4HANA Public Cloud environment?

I would first confirm the inspection lot origin and status match the filter criteria configured for the Fiori worklist app, since apps like Manage Inspection Lots often filter by origin, plant, or inspection type defaults. Next, I'd check whether the user's authorization roles restrict visibility to certain plants or inspection lot origins, and verify the underlying CDS view isn't excluding lots due to a status combination (e.g., lot created but not yet released). If APIs were used to check lot existence, I'd compare API results against app filters to isolate a UI-layer versus data-layer issue.
mediumInspection Lots

18. For a delivery inspection scenario using skip lot functionality with EWM warehouse integration, how do you ensure skipped lots are still auditable while reducing manual results recording effort?

Skip lot functionality is driven by the dynamic modification rule with a skip stage in the quality level, which automatically sets the usage decision without requiring manual results recording for that lot. To maintain auditability, the system still creates the inspection lot record and logs the automatic UD with the applicable code, and the quality level history table retains the skip decision context. In EWM-integrated scenarios, I'd confirm the skipped lot status is properly communicated back to the warehouse task so putaway or goods issue is not blocked.
mediumInspection Lots

19. During cutover, MDG-replicated material master data is arriving in batches, and inspection lot creation via Fiori apps is significantly slower than expected for newly onboarded plants. What would you investigate to resolve this performance issue?

Check whether MDG replication is delivering material and inspection setup data (inspection types, control keys) in a sequence that causes lock waits or repeated retries during lot creation. Review batch job scheduling for replication versus inspection lot creation timing, examine ST05/ST22 traces for lock contention on material master tables, and confirm the Fiori app isn't repeatedly polling incomplete master data. Stagger replication batches by plant and validate completeness before enabling inspection lot creation to avoid race conditions.
mediumInspection Lots

20. In-process inspection lots generated from partial confirmations of a production order are each receiving full inspection severity, even though the material's quality level history at that plant should qualify it for skip-lot treatment under dynamic modification. How does the PP confirmation-to-inspection-lot integration explain this, and what would you check?

Each partial confirmation can generate a separate inspection lot, and dynamic modification evaluates the quality level record tied to material/plant/inspection type combination at lot creation time — if the quality level hasn't been updated yet because the usage decision for the prior partial lot is still pending, the next lot inherits the unadjusted (full inspection) level. Check the quality level table update timing, confirm the inspection type's dynamic modification rule is active, and verify the sampling procedure at the operation is actually linked to the quality level rather than a fixed scheme.
mediumInspection Lots

21. You are migrating historical inspection results tied to PP production orders into S/4HANA to feed a new quality analytics dashboard. What integration design must you validate to ensure PP order references remain intact post-migration?

I would validate that migrated inspection lots retain correct linkage to their originating production/process order numbers, operation, and confirmation data, since analytics dashboards typically join inspection results to PP order master data via these keys. This requires confirming the migration object sequencing loads PP orders before or alongside dependent inspection lots, and reconciling a sample set of migrated lots against source system order references before analytics extraction is enabled for reporting.
mediumInspection Lots

22. A warehouse using EWM wants to implement skip lot inspection for a fast-moving material during delivery-based inspection to reduce inspection workload. What integration considerations must be addressed between ERP QM dynamic modification and EWM processing?

Skip lot logic is driven by dynamic modification rules and quality level records in ERP QM; EWM must respect the resulting inspection type/skip status distributed to it, meaning the inspection lot may still be created but automatically closed with a system-set usage decision. Confirm the EWM QIE rule recognizes skipped lots so no physical inspection task is generated in the warehouse, and ensure exception handling exists for cases where skip status changes mid-cycle, since EWM tasks may already be released.
mediumInspection Lots

23. In S/4HANA Public Cloud, how does data archiving strategy for closed inspection lots differ architecturally from an on-premise deployment, and what governance considerations does this introduce when integrating with BTP-based extensions?

Public Cloud restricts direct archiving object customization; archiving runs through SAP-delivered standard archiving objects with limited extensibility, and residence/retention rules are typically configured via released Fiori apps rather than custom ABAP archiving programs. BTP extensions consuming inspection lot data (via released APIs/CDS) must account for archived data no longer being available through standard OData services, requiring extension-side caching or historical reporting layers, and governance must ensure extension teams are informed of retention policy changes before implementation.
mediumInspection Lots

24. A global template rollout requires local plants to consume inspection lot data through APIs for a third-party lab system hosted on BTP. What integration design would you recommend?

Use released OData/API_INSPECTIONLOT-type APIs (where available in the target release) exposed through SAP API Business Hub, consumed via an integration flow in BTP Integration Suite that maps lab results to the standard result recording APIs or usage decision APIs. Apply an API management layer for throttling and monitoring, and template the integration flow so each rollout country only adjusts endpoint/plant-specific parameters, preserving global template consistency while allowing local system connections.
mediumInspection Lots

25. During a technical cutover from ECC to S/4HANA, a large number of inspection lots remain open with partial results recorded but no usage decision. What cutover strategy would you recommend for handling these open lots, and how does this affect Fiori role assignment planning?

I would recommend closing out or forcing usage decisions on lots wherever business-feasible before cutover, since migrating open lots with partial results into new data structures carries reconciliation risk. For lots that must remain open, I would migrate them via the standard inspection lot migration object with careful mapping of result and sample data, and ensure Fiori business roles for Manage Inspection Lots and Record Usage Decision are assigned to relevant users before go-live so they can complete UDs immediately post-cutover without gaps in access.
mediumInspection Lots

26. During hypercare of a PM-integrated S/4HANA rollout, business users complain the Migration Cockpit-loaded inspection lots aren't visible in their assigned Fiori launchpad roles. What role and Fiori configuration would you check?

Check whether the migrated business roles include the correct PFCG catalog/group assignments for QM Fiori apps (e.g., Manage Inspection Lots) and whether the business catalogs were assigned to the same role used pre-cutover. Validate that the technical user used by Migration Cockpit didn't accidentally overwrite authorization defaults, and confirm the launchpad content roles match the target org structure post-migration, especially if PM and QM share overlapping plant-level authorizations.
mediumInspection Lots

27. During cutover, production planners need to use Fiori apps to process inspection lots for PP process orders immediately after go-live, but role assignments were not yet validated against the new app catalog. How would you handle this cutover risk?

I would run a pre-cutover dry-run assigning planned roles to a test user group and validate access to key apps like Manage Inspection Lots and Record Usage Decision against real process order scenarios. Any gaps found would be corrected in the role catalog before go-live weekend. During cutover itself, I'd have a rapid-response team monitoring first PP-triggered inspection lots and role-based app visibility, with a fallback to temporary emergency access if critical gaps surface.
mediumInspection Lots

28. During a global template rollout, a subsidiary reports that inspection lots created via Manage Inspection Lots are not appearing in the corporate analytics dashboard, while other subsidiaries' lots appear correctly. How would you investigate and resolve this governance gap?

I would first check whether the subsidiary's plant is included in the analytics scope (CDS view filters or authorization restrictions by plant/company code). Next verify inspection lot origin and status profile consistency with the template, since analytics often filter on specific lot status combinations. I would also confirm the subsidiary uses the same inspection type numbering and characteristic catalog as the template, since deviations break cross-plant aggregation in embedded analytics.
mediumInspection Lots

29. How would you configure skip lot functionality for delivery inspection where lots are managed and confirmed through EWM?

Skip lot processing is realized through the dynamic modification rule's skip stage: once the quality level reaches skip criteria, the system generates the inspection lot but sets it to a usage decision that bypasses results recording, often with automatic UD via a control key/inspection setup marked 'skip.' In an EWM-integrated delivery inspection, the QM inspection type still creates the lot in ERP/S4, but the skip flag prevents work item creation in EWM quality inspection engine (QIE), so goods movement proceeds without physical sampling while quality history is still updated for future re-evaluation.
mediumInspection Lots

30. How do you configure skip lot processing for delivery inspection lots feeding an EWM-managed warehouse, and what precautions apply to the interface handoff?

Configure skip lots via dynamic modification rule linked to the inspection type in the material's QM view, with the skip level set in the sampling procedure so lots meeting the criteria auto-generate a usage decision without manual results recording. In EWM integration, the skip decision must post back through the inbound delivery quality inspection engine (QIE) or standard QM-EWM interface before the warehouse task releases putaway, otherwise stock is blocked awaiting a UD that never arrives manually.
mediumInspection Lots

31. During cutover, several PP-related production orders have open inspection lots at time of go-live. What approach should be taken to handle these open inspection lots during migration to avoid disrupting production confirmations?

Open inspection lots tied to in-process production orders typically should not be migrated as new objects but rather kept in the legacy system until closed, or the production order itself should be completed/closed before cutover if feasible. Where lots must carry over, ensure the production order status, batch, and inspection lot linkage are migrated consistently so PP confirmation and usage decision processes aren't blocked by inconsistent lot status or missing characteristic results.
mediumInspection Lots

32. During hypercare after a QM go-live, users report they cannot release inspection lots through Fiori apps despite having correct backend authorization roles. How would you investigate whether this is a BTP-related authorization issue?

Check if the Fiori launchpad and identity provisioning are federated through BTP/Identity Authentication service; verify the user's business role assignment in the Identity Provisioning or Cloud Identity Services synced correctly to the backend PFCG role. Confirm scopes/authorizations for the OData service used by the inspection lot app are activated and that communication arrangement/destination between BTP and backend is functioning. Review trace logs in both BTP cockpit and backend ST22/SU53 to isolate the failure point.
mediumInspection Lots

33. A delivery inspection lot (origin 10) is created in ERP QM for an outbound delivery processed through a decentralized EWM warehouse. Results recording is expected to be entered in EWM via mobile devices and reflected back in the ERP inspection lot. What configuration must be aligned between ERP QM and EWM to ensure characteristics and results synchronize correctly, and where does the final usage decision reside?

Inspection characteristics and sampling procedure must be replicated from the ERP inspection plan to EWM via the quality inspection engine (QIE) or CIF/replication depending on release, ensuring the EWM quality inspection document mirrors the ERP characteristic structure. Results entered in EWM via RF/mobile confirmation are transmitted back to ERP through the integration model, updating the ERP inspection lot's results recording. The usage decision itself is always finalized in ERP QM (QA32/QE01), not in EWM, since EWM only executes and confirms the inspection task.
mediumInspection Lots

34. After go-live, integration monitoring shows delayed inspection lot creation for production orders in PP, with Fiori apps showing stale statuses. How would you troubleshoot this integration issue?

Check the integration monitoring dashboard for queued or failed IDocs/BAPI calls between PP order confirmation and inspection lot creation, verifying whether the delay is in the backend job scheduling (e.g., batch job for automatic lot creation) or in Fiori OData service caching. Review application logs (SLG1) for inspection lot creation errors, confirm inspection type control settings for the material trigger automatic lot creation correctly, and check if Fiori app data refresh intervals or gateway cache settings cause the stale status display.
mediumInspection Lots

35. In a decentralized EWM warehouse, a delivery inspection lot (origin 10) generates a quality inspection document, but the warehouse team confirms the inspection task in EWM before the ERP inspection lot characteristics have been fully created. What integration risks does this create and how should the process be designed to avoid them?

If EWM confirms results before ERP characteristics are fully generated, the synchronization may fail or post incomplete/mismatched results, leaving the ERP inspection lot inconsistent with EWM's task status. The process should ensure the ERP inspection lot and its characteristics are created and released before the EWM quality inspection document is made available for confirmation, using proper timing in the outbound delivery/goods issue trigger and monitoring queues (SMQ1/SMQ2) for synchronization errors.
hardInspection Lots

36. In a global QM template rollout across multiple company codes and plants, what design considerations govern number range configuration for inspection lots and how do they affect data migration and reporting?

Number ranges for inspection lots are defined centrally in QM customizing and are typically plant-independent unless business requires separate ranges per plant for traceability or legal reasons. In a global template, you must decide whether one internal number range spans all plants or if external number ranges are needed for specific origins like customer returns. Poor planning causes range exhaustion, gaps disrupting audit trails, or collisions during data migration when legacy lot numbers must be preserved.
hardInspection Lots

37. Explain how skip lot inspection is set up for final inspection lots feeding into SD delivery processing, and what risk controls should be maintained.

Skip lot logic is achieved through a dynamic modification rule with a 'skip' inspection level, tied to a sampling procedure that has demonstrated sustained quality acceptance; when the level reaches skip, the system auto-generates the inspection lot but sets it to a status allowing immediate usage decision without results recording, often via automatic UD settings in QM03/QM04. For SD-linked final inspection, controls must include periodic re-triggering of full inspection (tightened level fallback on any rejection), audit trail retention, and validation that automatic UD codes still post correct stock movements to avoid unflagged nonconforming goods reaching delivery.
hardInspection Lots

38. A serialized material inspected during sales returns shows inconsistent dynamic modification behavior—some serial numbers get skip-lot treatment while others don't, despite identical inspection history. How would you diagnose this?

Dynamic modification rules are typically evaluated at the inspection lot or material/vendor level, not per serial number, so inconsistency suggests the dynamic modification rule's underlying quality level record is being reset or recalculated between lots, or that serial numbers are split across different inspection lots with different quality level history. I'd check the quality level per material/customer combination, review QM sample determination logic, and confirm serial number profile settings aren't causing lot splits that reset historical counters.
hardInspection Lots

39. During a global template rollout to a new country using MDG-driven master data replication, inspection lots are not being generated automatically for goods receipt at the new plant despite correct inspection setup at the template level. How do you troubleshoot this?

I would first verify that the material master's inspection type and QM control key were correctly replicated by MDG to the new plant-level material master, since replication failures or incomplete distribution models often drop plant-specific extensions. Next, check the inspection setup for the plant (QM view activation, inspection type 01/04 settings) and confirm inspection lot origin configuration is active for that plant. Finally, review replication monitoring logs in MDG for errors before assuming a QM configuration issue.
hardInspection Lots

40. You are architecting a skip-lot strategy for final inspection lots that feed directly into SD delivery creation for a high-volume finished goods line, where skipped lots must still be traceable in usage decision history for audit purposes. What design would you implement to balance efficiency with auditability and delivery-blocking control?

Configure the dynamic modification rule with a skip-lot quality level so eligible lots auto-generate with a UD proposal (often via automatic usage decision) rather than bypassing lot creation entirely, ensuring an inspection lot and UD record always exist for audit trail. Set the UD code used for skipped lots to carry the same stock posting and SD delivery-release logic as manually decided lots, so delivery blocking logic in SD remains consistent. Periodically force full inspection lots via the quality level's skip interval to validate ongoing conformance.
hardInspection Lots

41. An architect is troubleshooting why incoming inspection lots for a specific vendor/material combination are consistently generated with the wrong sampling procedure despite correct inspection plan assignment. What systematic approach would you take?

Start by checking whether a dynamic modification rule is overriding the plan-defined sampling procedure based on the current quality level for that vendor/material combination—this is the most common cause of unexpected sample size changes. Verify the inspection plan version validity and usage 10 (incoming inspection) is correctly selected at lot creation, check if a QM info record or source inspection agreement exists overriding standard sampling, and review whether the material's inspection setup (QM view) references a different inspection plan group than expected. Confirm via lot origin and inspection specification display which sampling procedure was actually applied and trace it back to its determination logic.
hardInspection Lots

42. During hypercare after a large QM migration, several users report they cannot release inspection lots migrated from legacy, even though functional testing during migration validation passed. As the architect, how would you investigate whether this is an authorization gap versus a migration data issue?

Compare the affected users' PFCG roles against the migration project's test user roles to see if productive roles lack the QM release authorization object (e.g., inspection lot release activity). Check SU53/trace logs for the failed authorization check. Simultaneously verify migrated inspection lot status sequences are valid (no skipped/duplicate status records) using status management reports. If authorization trace shows no failure, focus on migration object consistency in status tables; if trace shows failure, it's an authorization gap requiring role correction via MDG-driven role governance.
hardInspection Lots

43. A client wants to add a custom field to the inspection lot to capture a regulatory attribute, and insists on modifying the standard inspection lot table structure directly in a Public Cloud environment. As the architect, how do you respond and what clean core-compliant alternative do you propose?

Direct modification of standard structures is not permitted in Public Cloud under the clean core model, and would jeopardize upgradeability and support. I would propose using the in-app Custom Fields and Logic tool to add the field to the inspection lot business context, exposing it through Fiori and CDS extension views without touching standard objects. If deeper logic is needed, I'd design a side-by-side extension on BTP using released APIs, keeping the core untouched and ensuring the extension is upgrade-safe.
hardInspection Lots

44. Incoming inspection lots for a critical raw material are being created automatically at goods receipt, but purchasing reports that some GRs post directly to unrestricted stock without any inspection lot appearing. How would you diagnose the root cause?

First check the material master QM view inspection setup (inspection type 01 active and QM active indicator flagged) and the QM control key/inspection type-plant assignment; if these are missing or deactivated for that plant, no lot is created. Next verify the purchasing info record or PO doesn't have a source inspection override, check whether a released inspection plan or master inspection characteristic exists forcing plan-based lot creation, and review whether the movement type used bypasses QM (e.g., non-105/101 movements or stock transfer postings not configured for inspection). Finally check batch job/change logs for recent removal of the QM inspection type from the material master.
hardInspection Lots

45. What is the process for designing and maintaining number range objects for inspection lots across multiple company codes in a global template, and why do gaps or overlaps in these ranges create compliance risk?

You define number range intervals for the inspection lot object, typically decided by whether lots need to be distinguishable by plant, inspection type, or origin for traceability and audit purposes. Ranges are usually client-wide but interval segmentation by year or plant group is common to keep lot numbers meaningful and to avoid collisions during data migration from legacy systems. Buffering number ranges for performance can create gaps after system restarts, which auditors may flag, so buffering should be disabled or carefully justified for regulated industries where sequential lot traceability is scrutinized.
hardInspection Lots

46. During a QM transformation project, historical inspection lots migrated into S/4HANA reference material and vendor records that are only partially replicated from an MDG hub, causing broken characteristic value links after load. How would you troubleshoot and remediate this?

I would first verify MDG replication status for the referenced materials/vendors to confirm whether records are fully active in S/4HANA before migration load. If gaps exist, I'd sequence migration to run only after MDG replication completes for dependent objects, using replication monitor logs to identify blocked records. For already-loaded lots with broken links, I'd run targeted corrections via the Migration Cockpit's error handling, re-triggering characteristic value linkage after the missing master data is confirmed active.
hardInspection Lots

47. As lead architect for a global template rollout involving quality data migration with EWM-managed warehouses, what controls would you put in place to ensure inspection lot and quality data consistency between S/4HANA and EWM during cutover?

I would establish reconciliation controls comparing inspection lot counts and status between S/4HANA QM and EWM quality inspection documents before and after migration, using migration object load logs and custom validation reports. Key controls include freezing master data (inspection types, sampling procedures) before extraction, sequencing migration objects so material master and inspection setup data load before inspection lots, and running parallel dual-maintenance checks during a defined cutover window with sign-off gates per country in the template rollout.
hardInspection Lots

48. During hypercare, production supervisors report that inspection lots generated from PP process order confirmations exist in the backend but do not appear in their Fiori worklist app for several hours after creation. As lead architect, how would you diagnose and resolve this delay?

First check whether the delay is CDS view refresh latency, a queued IDoc/BAdI trigger backlog in the PP-QM interface, or a Fiori OData service cache issue. Review application logs (SLG1) for QM inspection lot creation BAdIs, check background job scheduling for any batch-triggered lot creation, and verify the Fiori app's underlying CDS view isn't delta-dependent on a delayed job. Correlate timestamps across BKPF-equivalent QM tables and the Fiori worklist refresh cycle to isolate whether it's a data latency, replication, or UI caching problem.
hardInspection Lots

49. A global manufacturing rollout requires production order-based inspection lots (origin 03/04) across plants with differing legacy inspection setups inherited from an ECC-to-S/4HANA conversion. What design considerations ensure consistent inspection lot origin behavior post-migration?

Validate that inspection types linked to origin 03 (in-process, production order) and 04 (goods receipt from other origins, e.g. process order) are consistently activated in material masters across plants, since legacy ECC configurations often diverge by plant due to historical local customization. Confirm control keys, sampling procedures, and follow-up actions are harmonized centrally, ideally through a template-driven material master extension process, and validate that any custom logic (user exits, BAdIs) for automatic lot creation tied to order confirmation was carried forward and retested in S/4HANA, since some legacy enhancements may not trigger correctly under the Universal Journal-integrated order confirmation flow.
hardInspection Lots

50. A customer complains about a finished goods shipment that passed final inspection, but the same characteristic failed in a prior lot for a different sales order of the same material. How would you investigate whether the inspection lot origin setup contributed to inconsistent inspection rigor between these two orders?

I would compare the inspection lot origin used for both lots (e.g., origin 10 for delivery-based inspection versus a manually created lot) and check whether the inspection plan or dynamic modification stage differed between the two sales orders. If the sales order used a different order type or shipping point mapped to a different inspection setup, sampling procedures could differ, leading to inconsistent characteristic evaluation. I would also review whether skip-lot logic reduced sampling for the passing lot based on recent quality score improvement.
hardInspection Lots

51. Users report that the Manage Inspection Lots Fiori app fails to display recently created lots in a newly onboarded Public Cloud MDG-integrated tenant, even though the lots exist in the backend. How would you diagnose this as a solution architect?

First check whether the master data (material, vendor) synced from MDG has consistent keys and status in the local system, since inconsistent MDG replication can cause OData service filters or authorization checks to silently exclude records. Verify the CDS view/OData service behind the app isn't filtering on a business partner or material status field that MDG hasn't fully activated. Also check role-based restrictions and check the app's value help configuration for missing master data links.
hardInspection Lots

52. During hypercare, Fiori quality apps are timing out for users processing high-volume goods-receipt inspection lots tied to MM postings. How would you diagnose and resolve this performance issue?

I would start with system performance traces (ST12/SAT equivalents) around the OData service calls behind the Fiori app, checking for expensive selects against inspection lot and results tables triggered by MM goods receipt volume. Common causes include missing indexes, unfiltered list reads, or synchronous batch-input style processing during peak GR periods. Resolution typically involves query optimization, adjusting Fiori list-report filters to reduce dataset size, and coordinating with Basis on OData throughput and gateway capacity during peak MM posting windows.
hardInspection Lots

53. Walk through how stock postings differ across inspection lot origins 01 (goods receipt), 04 (production), and 05 (in-process) and the implications for MM integration.

Origin 01 lots post GR stock to quality inspection blocked category via MIGO, tied to the purchase order; usage decision then triggers movement into unrestricted or return delivery via MM. Origin 04 lots for finished/semi-finished goods post stock at order confirmation, with UD driving GR to stock or scrap postings. Origin 05 (in-process) lots typically don't generate independent stock postings since they inspect intermediate steps within an order without a separate goods movement, relying instead on process confirmation.
hardInspection Lots

54. A batch is under multiple concurrent inspection lots from different origins (e.g., GR and stock transfer). How does the system manage batch status when usage decisions are made at different times for each lot?

Each inspection lot has its own stock category and quantity tied to it independently; the batch itself does not carry a single system-wide status but reflects aggregated stock quantities across categories (unrestricted, blocked, quality inspection). Usage decision on one lot only affects the quantity tied to that lot's movement, so a batch can simultaneously show quantities in different stock statuses until all open lots are decided.
hardInspection Lots

55. During cutover for an S/4HANA transformation, you have thousands of open inspection lots tied to SD delivery-based inspections at goods issue. What cutover strategy would you use to avoid disrupting shipments?

I would classify open inspection lots by criticality, closing or completing straightforward lots in the legacy system before cutover cutoff, and migrating only genuinely open, in-process lots with their current usage decision status intact. For SD-linked lots tied to open deliveries, I'd coordinate cutover timing with the logistics team to freeze new delivery creation briefly around cutover, ensuring lot-to-delivery linkage is preserved through the migration object, and run reconciliation to confirm delivery block statuses match pre-cutover.
hardInspection Lots

56. When migrating open inspection lots and their associated results from ECC to S/4HANA, what governance controls should be applied around the migration objects and APIs used, particularly where EWM-managed storage locations are involved?

Only migrate inspection lots that are genuinely open and required for business continuity; closed lots should be archived, not migrated, to avoid inflating ACDOCA-adjacent tables and inspection tables unnecessarily. Use the released migration objects/APIs for QM master and open transactional data, and coordinate timing with EWM so that quality inspection stock in EWM-managed locations is reconciled and not double-migrated through both ERP and EWM interfaces, preventing orphaned or duplicate quality stock records.

Related lesson

Enterprise Architecture and Governance for Inspection Lot Processes Across S/4HANA Landscapes

Related topics

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

Next practice step

Practice with Interview AITake a mock test