SAP QM Interview Questions

Validate that the inspection lot origin (e.g., 05 for stock transfer or 89 for other goods movement tied to returns) triggers a corresponding EWM warehouse task; confirm the ERP-EWM integration model includes the relevant movement types, that the quality inspection storage type/process is mapped correctly in EWM, and that the usage decision posting in ERP synchronizes with EWM's inbound quality inspection process (QIE) to release the handling unit for putaway.

First check whether task deadline monitoring is active in the notification type configuration and whether the deadline monitoring program (via a background job) is scheduled to run and trigger workflow events. Verify that the workflow linkage for the deadline-exceeded event is bound to a workflow template that notifies the responsible buyer via the partner determination. Also confirm that partner functions on the notification actually resolve to a valid buyer with an active workflow inbox; a common root cause is unresolved or blank partner assignments blocking notification delivery.

Define region-specific dynamic modification rules as separate master data objects rather than a single global rule, each with tailored switching logic and tracked history keys (material, plant, vendor) aligned to regional regulatory needs. Assign these rules at the inspection characteristic or sampling procedure level within region-specific inspection plan versions, keeping the base plan structure global but allowing regional plan versions or alternative task lists to reference the appropriate rule, preserving template consistency while satisfying local compliance.

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.

In classic WM, a usage decision in QM does not automatically move physical stock between storage types; it only changes the inventory management stock category (quality inspection to unrestricted). A separate transfer order (TO) must be created, either manually or via automatic TO creation configured in the inspection type/stock posting settings or via a follow-up action linked to the usage decision code. If automatic TO creation is not configured (e.g., missing movement type assignment in the QM stock posting rules or WM movement type control), the stock stays in the quality storage type until the TO is processed.

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.