SAP QM QM in Procurement Interview Questions

Origin 01 identifies inspection lots created automatically at goods receipt for a purchase order, driven by the inspection type activated in the material's QM view. It links the lot to the PO, material, plant and vendor batch, triggers stock posting to quality inspection status, and determines which inspection plan or master inspection characteristics apply for results recording and usage decision.

A quality info record is maintained per vendor-material combination and stores procurement-specific quality settings such as inspection stock indicator, skip-lot status, and release without inspection. The inspection type (e.g., 01 goods receipt inspection) defined in the material's QM view determines whether an inspection lot is created at all. The QI record then modifies that behavior for the specific vendor, allowing skip-lot or mandatory inspection overrides without changing the inspection type setup itself.

Inspection lot origin (field HERKUNFT) classifies how and why an inspection lot was created, e.g. 01 for goods receipt against a purchase order, 04 for goods receipt from other origins, 05 for stock transfer, 89 for manual creation. It drives which control key, default inspection type, and follow-up actions (stock posting, UD requirement) apply, and links the lot to the originating procurement document like the PO or material document.

An inspection type (e.g., 01, 04, 08) defines the business context for which an inspection lot is created and links material master QM view, inspection plan, and the relevant business transaction (goods receipt, in-process, stock transfer). It controls lot creation, sampling relevance, results recording requirements, and usage decision defaults, enabling automatic inspection lot generation when configured in the material's QM view per plant.

Use notification type Q1 (Quality Notification - Vendor/Problem with vendor) or a client-specific variant of it, linked to catalog profile and origin indicator for vendor complaints. Maintain the QM Info Record (vendor/material) with QM procurement active and inspection type 01 assigned. On usage decision rejection at goods receipt, the system can propose a notification via inspection lot follow-up action, pulling vendor, PO, and material data automatically if the info record and catalog assignment are correctly linked.

Quality info record status and inspection-relevant settings are evaluated primarily at inspection lot creation time, which for source inspection is often tied to the purchase order or goods receipt processing point, not retroactively applied to POs already released before the status change. If the info record change is saved with a future validity or the existing PO already carries inspection-relevant data determined earlier, the new blocked status will only apply to lots created after the change is fully effective and any dependent PO data is refreshed. I would check the info record's validity dates, change log, and whether the affected POs need re-determination.

The QI record's control indicators for the material-vendor combination decide the outcome: setting inspection active with a percentage or fixed sample forces a lot; enabling the skip lot flag with a defined quality level and validity period lets the system bypass inspection based on switching rules; setting the delivery block indicator prevents goods receipt entirely regardless of inspection settings. Validity dates and release status also matter, since an expired or blocked QI record can unexpectedly force full inspection or stop receipt.

A quality info record (vendor/material combination) determines whether goods receipt inspection is active for a vendor-material pair, sets the certificate type requirement, and can trigger release without inspection or skip logic based on vendor quality rating. Configuration decisions include control key settings (inspection active flag), release strategy linkage, and whether the info record overrides plant-level inspection type settings. It must be maintained in QM01/QM02 and synchronized with purchasing info records.

First verify the inspection setup for material/plant/inspection type 01 is active and flagged for GR inspection; if inactive, no inspection lot is created and stock posts unrestricted by default. Check the QM view in the material master and the inspection type's stock posting indicator. In EWM, confirm the quality inspection process is mapped so putaway rules route to a QI storage type/bin based on the inspection lot status transferred from ERP. Also validate movement type 101 configuration isn't overriding stock type via user exit or batch-specific override.

I would sequence cutover validation by first confirming country-specific master data (plants, chart of accounts assignments, vendor evaluation criteria) is fully migrated and active, then run the BTP extension against a subset of test plants per country before full activation. Validation checkpoints would include confirming API connectivity per country instance, verifying scorecard calculations against known historical data, and gating go-live sign-off per country rather than assuming a single global validation covers all local configurations.

In both cases, once the batch's inspection validity date lapses, the stock is flagged for re-inspection and typically moved to a blocked or quality stock category upon next relevant movement. With EWM, this is handled through EWM's own quality inspection engine and physical stock status in the EWM warehouse, requiring synchronization between ERP/S4 QM master data and EWM QIE configuration. With standard WM, the same ERP inspection lot and stock category directly drive WM transfer orders without a separate inspection engine, making the process more tightly coupled to core QM.

Because the inspection was completed at the vendor's site with a usage decision recorded there (often via a source inspection lot or supplier self-certification), the receiving goods receipt in the EWM-integrated plant typically posts directly toward unrestricted-use stock rather than generating a new full inspection lot, assuming the inspection type is configured for skip or reduced inspection based on prior vendor decision. Validation must confirm that the QM-EWM interface correctly maps the inbound delivery's inspection-relevant status, that the EWM warehouse task doesn't route stock to a quality inspection storage type inconsistent with the vendor's already-completed decision, and that any residual inspection type at the receiving plant is properly configured for reduced sampling.

The QI record controls whether an inspection lot is created at goods receipt for a vendor/material/plant combination, whether a certificate is required, and supports skip-lot logic through release status and block indicators tied to vendor quality history. It does not define the sampling procedure or sample size itself; that comes from the inspection plan's control key or the material's inspection type settings, which the system pulls in when the inspection lot is generated.

A quality info record (vendor-material combination) determines whether goods receipt inspection is skipped in favor of source inspection at the vendor, and can define whether a certificate is required. It works alongside inspection type 01 activation in the material QM view; if the info record indicates skip delivery, GR inspection lots are suppressed even though the QM view is active. Configuration requires activating QM in procurement, maintaining the info record via QI02/QI06, and aligning with vendor evaluation criteria.

The QINF (QM01/QM02) holds fields like inspection type control, delivery release without inspection, block flags, and skip/dynamic modification parameters. If skip lot is active, the system checks the dynamic modification rule tied to inspection history to decide whether a lot is skipped, reduced, or fully sampled. Source inspection at the vendor's site is flagged separately and, combined with certificate requirements, determines whether goods receipt inspection or sampling per the assigned inspection plan is triggered at all.

Blocked quality info record status typically controls procurement blocking (source list or purchasing block), not inspection lot creation directly, which is driven by the material master inspection type and control key settings. Check whether inspection type 01 is active in the material master QM view and whether the info record block was intended to stop purchasing rather than inspection. Resolve by aligning info record purpose with actual business intent, using purchasing block fields if procurement should stop.

The quality info record (QI06/QI02) governs the QM-relevant relationship between a vendor and material at plant level, controlling whether goods receipt inspection is active, source inspection requirements, certificate types needed, and release status. When skip inspection is activated with valid statistics (e.g., a defined number of good deliveries), the system can suppress inspection lot creation at goods receipt, posting stock directly to unrestricted use, while still tracking delivery history so skip status can be revoked if quality deteriorates.

First check the material master QM view to confirm inspection type 01 (GR inspection) is active and the inspection plan/task list is released and assigned correctly to the material, plant, and usage. Verify the control key itself is flagged as inspection-relevant and not overridden by a quality info record set to skip inspection or by a source inspection agreement diverting the check to the vendor. Also confirm the task list status, validity dates, and that the correct inspection type was triggered by the movement type used at goods receipt.

Check the QM view of the material master (inspection type 01 active, plant-specific), then verify whether the movement type used for each PO document type actually triggers inspection (QM control key/inspection setup at movement type level in OMJJ or MM inspection type customizing). Also check the purchasing info record's QM control data, source list flags, and whether one PO category (e.g., stock transport order or subcontracting) bypasses standard GR inspection logic. Confirm via table QALS whether lots exist but were auto-UD'd, versus never generated.

Centralize specifications in PLM and distribute them to QM as material specifications/characteristics via standard PLM-QM integration, ensuring plant-specific inspection plans reference the same master specification to avoid divergence. For calibration, define plant-specific maintenance strategies per equipment category while keeping a global equipment classification standard so audits can compare compliance across plants. Supplier quality scores should aggregate inspection lot results and complaint data (QM notifications) per vendor across plants using a central reporting layer, since native transaction data is plant-siloed.

Dynamic modification uses the quality score history stored against the material/vendor/inspection type combination to move between inspection stages: normal, reduced, tightened, and skip. For source inspection, results recorded at the supplier location feed the same inspection lot completion logic; passing results improve quality score and can shift the material to reduced or skip inspection for subsequent lots, while repeated rejections tighten inspection or force full sampling until stability is demonstrated again.

I would first check whether the corrective action task actually invoked the correct follow-up function to set a quality info record block or source list block, since corrective actions in QM do not automatically restrict procurement unless explicitly linked to QI info record maintenance or vendor evaluation blocking. I would trace the task completion log, verify the function module assigned to the task code, and confirm the QI info record (material/vendor) block indicator was updated; if the link is missing, I would build a follow-up action or workflow step that calls the QI info record maintenance transaction and validate MRP/PO release strategy honors that block.