ERPClimb logoERPClimb

SAP QM Inspection Planning Interview Questions

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

Inspection Planning in SAP QM covers how organizations define what to inspect, how to inspect it, and under what conditions inspection lots are created and evaluated. It spans inspection types, material master QM views, inspection plans, characteristics, sampling procedures, and their integration with procurement, production, sales, and plant maintenance processes across ECC and S/4HANA.

This page carries 79 reviewed SAP QM inspection planning interview questions, each with a complete written answer and no sign-in required. The set breaks down into 9 foundational, 40 mid-level and 30 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.

79 Inspection Planning questions with answers

easyInspection Planning

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

A selected set is a restricted, reusable subset of codes taken from a catalog code group, assigned for a specific usage such as a defect type list on a particular inspection plan, material, or plant. Instead of exposing every code in a large code group during result recording or usage decision, the selected set limits users to a relevant, controlled list, improving data quality and reducing input errors across different business areas sharing the same catalog.
easyInspection Planning

2. What is the purpose of a quality work center in SAP QM, and how does it relate to inspection operations and characteristics assigned in an inspection plan?

A quality work center defines where an inspection operation is performed, including capacity, responsible person or group, and default values like standard text or formulas. It is assigned at the operation level in the inspection plan (routing) and can default valuation rules, sampling procedures, or result recording settings for characteristics performed there, streamlining plan maintenance and ensuring consistent execution across similar inspection tasks.
easyInspection Planning

3. How does a material's inspection plan derive multiple specifications (e.g., customer-specific or country-specific) at the batch level, and what governs which specification is used when generating results for a given batch?

Batch-specific specifications are derived via the material's inspection plan usage combined with catalog/characteristic assignment, often tied to customer or sales-area-specific master inspection characteristics. The system selects the applicable specification based on inspection type, task list usage, and sometimes a customer-material-info-record link. Configuration must ensure valuation and specification selection logic (via QM order/inspection type control key) consistently ties to the correct batch attributes to avoid ambiguous derivation across plants.
easyInspection Planning

4. In a sell-to-quality scenario with a final inspection lot at goods receipt from an inspection stock transfer or return, how is dynamic modification rule configured to automatically tighten or relax inspection severity based on the vendor or customer quality history?

Dynamic modification is set in the inspection plan or material master inspection type via QM control key, linking to a dynamic modification rule (transaction QDR1) defined per material/vendor combination. The rule references sampling procedures tied to quality levels maintained in QM (dynamic modification level, e.g., skip lot or tightened inspection) based on historical usage decisions, driving automatic sample size or inspection stage changes at next lot creation.
easyInspection Planning

5. Why is the inspection type considered a foundational compliance control point in SAP QM, and what does it govern beyond simply triggering an inspection lot?

The inspection type is the compliance anchor because it determines whether stock is posted to quality inspection stock, links the material to a specific business transaction (goods receipt, in-process, stock transfer), and activates the QM view settings like control indicators for automatic usage decisions and lot creation. Without an active inspection type in the material's QM view, no inspection lot, sample, or usage decision history exists, breaking traceability and audit evidence for that transaction.
easyInspection Planning

6. What is the purpose of a dynamic modification rule in QM, and how does it affect incoming inspection lots?

A dynamic modification rule automatically adjusts the inspection scope (normal, tightened, reduced, or skip) for a material/vendor combination based on accumulated quality history from prior lots. It is assigned at the inspection characteristic or inspection type level in the material's inspection plan/control key, and evaluated during lot creation so that repeatedly compliant vendors can move to reduced sampling while poor quality triggers tightened inspection automatically.
easyInspection Planning

7. What is the purpose of an inspection type in SAP QM, and how does it relate to a material's quality management view?

An inspection type defines the business scenario for which inspection is triggered, such as goods receipt (01), in-process (03), or goods issue (04) inspection. It determines whether inspection lots are generated automatically, links to the QM view of the material master, and controls whether a stock posting is blocked pending usage decision. Multiple inspection types can be active per material, each with its own control parameters and inspection plan assignment.
easyInspection Planning

8. In SAP QM Stability Studies, how is a stability study structured to trigger periodic inspections at defined storage conditions and time intervals, and how does this link to PM if chamber monitoring is required?

A stability study is created with reference to a material and recipe, defining storage conditions (temperature/humidity) and a schedule of inspection intervals using the standard stability study functionality, which generates inspection lots automatically per interval via the study scheduling. Each condition can be tied to a storage chamber master; if chambers are monitored via PM equipment records, chamber readings or maintenance notifications can be cross-referenced, though native automatic PM integration for study triggering is limited and usually handled through custom enhancements or manual coordination.
easyInspection Planning

9. What is dynamic modification in QM inspection processing, and how does it change the inspection scope for incoming inspection lots?

Dynamic modification (skip/tightened/normal/reduced sampling) automatically adjusts inspection severity for a material-vendor or material-plant combination based on historical quality performance stored in the quality info record or dynamic modification rule. Good results over consecutive lots trigger reduced inspection or skip; poor results trigger tightened inspection. It's configured via inspection type control (QM in procurement) linking a sampling procedure to a dynamic modification rule and level, reducing manual effort for reliable suppliers.
mediumInspection Planning

10. You are designing the architecture for inspection plan migration to S/4HANA Public Cloud, where Fiori role design and PM integration for maintenance-triggered inspections are both in scope. What architecture decisions would you prioritize?

I would prioritize mapping legacy inspection plan groups and versions to a standardized structure compatible with Public Cloud's predefined migration templates, then design Fiori business roles that align inspection plan maintenance access with PM-triggered inspection lot processing, ensuring maintenance planners and quality engineers have appropriately scoped access. Integration with PM would be validated through inspection type configuration for maintenance orders, and role testing would confirm that Fiori catalog assignments don't expose extended configuration apps unavailable in Public Cloud.
mediumInspection Planning

11. During quality planning for a newly onboarded vendor-material combination, the quality planner needs usage decisions to clearly distinguish lots that passed under skip-lot inspection from lots that underwent full inspection, so management reporting can track skip-lot program effectiveness separately. How would you design the catalog and code group structure to support this in the quality info record setup?

Create a dedicated code group within the usage decision catalog specifically for skip-lot outcomes, distinct from the standard full-inspection code group, and assign a selected set at the inspection type or plant level so inspectors see only the relevant codes for that lot's inspection path. Ensure the quality info record's skip-lot flag is visible in reporting fields so lots can be filtered by inspection path alongside the usage decision code for accurate program effectiveness metrics.
mediumInspection Planning

12. During in-process inspection on a production order, dynamic modification rules are configured to reduce sampling after consecutive accepted lots, but the plant also requires that a quality certificate still be generated for every batch produced, including those with reduced sampling. How would you design this so reduced sampling and full certificate coverage coexist?

Dynamic modification only governs sample size and inspection severity per the quality level history; it does not affect whether a usage decision or characteristic result exists for a lot. Configure the inspection plan so mandatory characteristics tied to certificate content always have at least a minimal sample even under reduced sampling, and set certificate profile selection to pull whatever characteristics were actually recorded for that specific lot. This way the certificate accurately reflects reduced sampling results without misrepresenting untested characteristics, and the certificate is still generated at usage decision regardless of sampling level.
mediumInspection Planning

13. A quality team wants to link FMEA risk analysis outputs to inspection plan characteristics so that high-risk failure modes automatically drive tighter sampling in production inspection. How would you approach designing this integration in SAP QM?

SAP QM does not natively enforce automatic sampling adjustment purely from FMEA risk priority numbers without custom logic; typically FMEA is managed in a separate quality management application or module and results are used manually to inform inspection plan design. Approach involves reviewing FMEA output offline or via integrated tools, then manually or via governed change process updating master inspection characteristics with appropriate sampling procedures for characteristics tied to high-risk failure modes, documenting rationale for audit traceability.
mediumInspection Planning

14. A stable production line has an in-process inspection point eligible for skip lot to reduce results recording effort, but every batch confirmed in the PP order must still carry a printed quality certificate referencing actual measured values. How would you design the skip lot and certificate configuration to satisfy both requirements?

Configure the dynamic modification rule with a skip stage on the in-process inspection plan so eligible lots automatically receive an accept-type usage decision without full results recording, while still generating an inspection lot record and batch record for traceability. Since the certificate profile requires actual measured values, either exclude this characteristic set from skip eligibility or configure a reduced sampling stage (not full skip) so at least representative results are captured; then link the certificate profile to pull whatever values exist, clearly marking skipped characteristics as 'not tested' rather than fabricating data.
mediumInspection Planning

15. A shared master inspection characteristic is used in inspection plans at two plants, but Plant A applies a fixed sample size while Plant B applies a percentage-based sampling procedure for the same characteristic. Is this a design flaw, and how would you validate it?

This is not automatically a flaw because sampling procedure is typically assigned at the inspection plan characteristic level, not inherited as a fixed attribute of the master inspection characteristic itself, so plants can legitimately override it. Validate by checking whether the MIC default sampling procedure was intentionally left blank to allow local override, confirming both plants' choices align with their AQL or regulatory requirements, and ensuring the divergence is documented in the template governance log rather than being an unintended local deviation.
mediumInspection Planning

16. During in-process inspection for a PP production order, an operator records a characteristic value outside tolerance but the system does not stop the confirmation. What could explain this, and how would you address it?

Likely the inspection characteristic is not defined as a required characteristic controlling confirmation, or the inspection point/completion isn't linked to a milestone confirmation control key that blocks further processing until UD is set. Check the routing's control key settings and inspection type for in-process inspection, and verify the characteristic's control indicator for 'stop confirmation on rejection' or milestone inspection point usage; if missing, production confirmation proceeds independent of the out-of-spec result, requiring reconfiguration of the control key or inspection point to enforce a hold.
mediumInspection Planning

17. A material uses classification with class characteristics to drive variant-specific inspection requirements, but the sampling scheme applied at goods receipt seems identical regardless of the variant selected. What should you check to determine whether class characteristics are correctly influencing sampling?

Class characteristics in classification typically drive characteristic value inheritance and variant selection, not the sampling procedure itself; sampling scheme selection comes from the inspection plan's control key or dynamic modification rule tied to quality history, independent of classification data. Check whether the inspection plan actually differentiates by variant (e.g., through separate plans or usage keys per material variant) rather than assuming classification alone changes sample size, since classification and sampling configuration are managed in separate structures.
mediumInspection Planning

18. What configuration determines whether an inspection lot is automatically created and released when a production order is created or released, and how does this interact with PP order confirmation?

Automatic inspection lot creation for production origins (03/04) is controlled by the inspection type settings assigned in the material master QM view, specifically the trigger point—order creation, order release, or goods receipt confirmation—and whether inspection stock posting is active. The inspection type control key determines skip-processing, sample calculation timing, and whether lot creation blocks order confirmation until inspection setup completes. If PP order confirmation is configured to require inspection completion, incomplete inspection lot setup can hold up confirmation postings.
mediumInspection Planning

19. A quality engineer new to FMEA wants to link failure modes identified in an FMEA analysis for a critical purchased component to specific inspection plan characteristics, to ensure incoming inspection covers known risk areas. What is a practical approach using standard SAP QM master data, and what are its limitations without dedicated PLM/FMEA tooling?

Map each high-risk failure mode from the FMEA to a corresponding master inspection characteristic, ensuring the characteristic description and long text reference the failure mode for traceability, then assign these characteristics to the inspection plan operation for the component with an appropriate sampling procedure reflecting risk priority. Standard QM has no native FMEA object, so the link is maintained manually through documentation and naming conventions rather than a system-enforced relationship; without SAP PLM FMEA or a dedicated risk tool, there's no automated update if failure mode risk changes, requiring manual governance to keep inspection plans aligned.
mediumInspection Planning

20. A regulated manufacturer notices that SPC control charts for the same specification show inconsistent capability indices across batches, and root-cause analysis points to batch derivation rules assigning different classification characteristics inconsistently before results are pushed to analytics. How would you diagnose and correct this?

Check the batch derivation rule (batch classification via class/characteristics inheritance) to confirm consistent characteristic values are propagated from the material or component batch to the derived batch. Verify inspection plan sampling procedure and control chart configuration reference the same characteristic master, not duplicated variants with different tolerances. Reconcile ACDOCA-independent QM tables (QAMV, QASE) feeding analytics against batch classification data, and correct derivation rule sequencing or timing so control chart inputs are standardized before extraction.
mediumInspection Planning

21. During goods receipt, a material with active inspection type 01 is posted, and stock is expected to land in quality inspection stock. The warehouse team reports the stock appeared directly in unrestricted use instead. What would you check to diagnose this?

First verify the inspection type control indicators in QM02/QM03 to confirm the GR posting to stock in QI is activated for that inspection type. Check inspection setup at material/plant level to ensure the inspection type is not deactivated with a deletion flag or end date. Also review the movement type used in MIGO, since some movement types can bypass QI stock posting. Finally check if the lot was auto-completed via a skip rule before GR, allowing direct unrestricted posting.
mediumInspection Planning

22. In a quality organization where MM purchasing users should be able to view but not modify sampling procedures linked to inspection plans, while QM specialists must maintain them, how would you design the authorization approach, and how does this separation interact with goods receipt inspection processing in MM?

Restrict change authorization for sampling procedures and inspection plan maintenance using authorization objects like Q_TASK_LST and C_TCODE checks on QP01/02/03, granting purchasing users only display access (QP03) or reporting views. Purchasing continues to trigger goods receipt normally via MIGO; the sampling logic executes automatically based on the inspection plan/quality info record without requiring purchasing to touch QM configuration. Document the segregation in the authorization concept and test that purchasing cannot accidentally alter sample size during GR processing.
mediumInspection Planning

23. Materials configured for skip-lot inspection under a dynamic modification rule are still generating full inspection lots at goods receipt in an EWM-integrated plant. What are the likely root causes and how would you troubleshoot this?

Check whether the dynamic modification rule and quality level are correctly maintained for the specific material/vendor combination and whether the quality level status has actually reached the skip stage based on accumulated acceptance history; a new vendor-material combination starts at normal/tightened by default. Also verify the inspection type configuration allows skip (the 'skip lot allowed' indicator must be set), and confirm EWM inbound processing isn't forcing inspection creation independent of the ERP dynamic modification result due to a separate quality inspection engine setting in EWM. Review quality level master records for stale or reset status.
mediumInspection Planning

24. How do reference operation sets support standardization of incoming inspection plans across multiple materials from the same vendor, and how do they interact with quality info records?

A reference operation set defines a standard group of inspection operations and characteristics that can be inserted into multiple inspection plans, avoiding duplicate maintenance for similar incoming inspection steps. When a vendor supplies many materials requiring the same core checks, each material's plan references the same operation set while the quality info record for that vendor-material combination still governs whether source inspection, skip lot, or delivery release without inspection applies, keeping standardization and vendor-specific control separate but complementary.
mediumInspection Planning

25. A skip-lot strategy is being introduced for a stable in-process inspection point on a long-running production line, but quality certificates are still required for every batch shipped to a regulated customer. How should this be configured?

Keep the dynamic modification rule active for the in-process inspection point so lots can skip detailed results recording when quality levels are favorable, but decouple certificate generation from the inspection lot's skip status by configuring the certificate profile to pull from batch-level characteristic values already stored (from prior inspections or specification data) rather than requiring a completed results recording on the skipped lot. This ensures regulatory certificates are still issued using available batch quality data even when the routine inspection step is skipped.
mediumInspection Planning

26. A material uses a classification system characteristic shared with other modules, and this same characteristic must feed sampling-relevant quality inspection results. What design considerations apply when reusing class characteristics inside QM inspection plans?

When a classification characteristic from CT04/CL02 is reused in an inspection plan, you must confirm its value type, unit of measure, and value range align with QM requirements, since QM enforces sampling and tolerance checks that generic classification characteristics may not support natively. You typically link it through a master inspection characteristic that references the classification characteristic for value consistency, while sampling procedure and control indicators are still defined at the QM master characteristic level, ensuring inspection-specific behavior isn't lost through pure classification reuse.
mediumInspection Planning

27. A production plant wants to reduce sampling frequency for a stable in-process inspection characteristic on a PP order without changing the underlying inspection plan. How would you leverage dynamic modification to achieve this, and what risks should be communicated to quality management?

Configure a dynamic modification rule at the master inspection characteristic level tied to the material/inspection type so that after a defined number of consecutive successful lots, the sampling scheme automatically moves to reduced or skip stage without altering the inspection plan itself. Communicate the risk that reduced sampling lowers detection probability for emerging process drift, and recommend periodic reset criteria or supervisory review of quality level history to ensure the rule doesn't mask a gradual quality decline; also flag that skip stages still require periodic re-verification lots to reset if quality level lapses.
mediumInspection Planning

28. A production plant configures inspection type 03 (in-process inspection) on a material's QM view as active but sets it to not automatically create inspection lots, expecting operators to manually trigger inspection during production order confirmation. Confirmations proceed without any inspection lot ever being created, and quality has no visibility into in-process results. What is happening, and how would you correct the setup?

With automatic lot creation disabled, the system will not spawn an inspection lot from the production order itself; a lot must be manually created, typically via QA01 referencing the order, or the inspection type must be reconfigured to auto-create lots at order release or goods receipt from production. Since no manual trigger exists in the confirmation process and PP confirmation does not call QM automatically, no lot is ever created. Correcting this requires either enabling automatic lot creation for inspection type 03 or adding a manual step/authorization check before confirmation to force lot creation.
mediumInspection Planning

29. A production planner notices that sample sizes calculated for in-process inspection lots vary inconsistently across production orders for the same material, even though the same inspection plan and sampling procedure are assigned. How would you investigate and correct this integration issue with PP?

Sample size is derived from the sampling procedure linked to the inspection characteristic, which may reference a dynamic sampling scheme dependent on lot size, quality level, or dynamic modification rule status from prior inspection history. Since production order quantities (and thus inspection lot quantities) vary, and dynamic modification tracks acceptance history per material/vendor or material/plant combination, the sample size legitimately fluctuates. Investigate the sampling procedure type (fixed sample size vs. sampling scheme like ISO 2859), check dynamic modification rule status in QM, and confirm order quantity is correctly passed from PP to the inspection lot.
mediumInspection Planning

30. A plant uses inspection type 03 (in-process inspection) tied to production orders. Quality wants a defect logged during in-process inspection to automatically prevent further order confirmation until the usage decision is made, without blocking unrelated production orders. How would you use inspection type configuration together with catalog/code group design to support this, and what are the integration limitations with PP?

Configure inspection type 03 with lot creation at order release or confirmation, mark it as triggering a quality inspection stock/block via QM-PP link, and use a code group in catalog 2 (usage decisions) with a 'Reject/Blocked' decision code that has follow-up action settings blocking goods movement postings. However, standard SAP does not natively halt order confirmation itself purely from a UD code; blocking is achieved through inspection lot status control on stock movements, not order confirmation logic, so a workflow or custom status check may still be needed for full order-level blocking.
mediumInspection Planning

31. You are rolling out SPC control charts across multiple plants that share the same material master but have different process capabilities. How would you design the control chart and inspection plan strategy to avoid false out-of-control signals?

Design plant-specific inspection plans (or plant-specific control indicators) rather than reusing one global plan, since process capability differences mean shared control limits will misrepresent stable plants as out-of-control. Configure separate control charts per plant/work center with locally calculated control limits based on that plant's historical data, and use sampling procedures appropriate to each plant's lot sizes. Centralize SPC monitoring through a common reporting layer while keeping limit calculation localized, and periodically recalculate limits after process changes.
mediumInspection Planning

32. How can reference operations be leveraged in inspection plan design to avoid duplicating the same set of quality checks across many similar inspection plans, and what integration consideration applies when these operations are shared with production routings?

Reference operation sets defined centrally can be inserted into multiple inspection plans, carrying a standard sequence of operations and characteristics so common checks like weight or dimension verification aren't recreated per plan. When shared with production routings that reference the same operation set, changes to the reference operation propagate to both quality and production task lists, so any modification must be assessed for impact across both process areas before release, since routing scheduling and inspection triggering both depend on it.
mediumInspection Planning

33. During in-process inspection for a production order, results recording shows measurements trending toward the tolerance limit, and dynamic modification rules should tighten the sampling scope for the next lot. How would you design this using dynamic modification and confirm the effect on subsequent inspection lots?

Configure a dynamic modification rule linked to the inspection type/material combination, using quality level records that track acceptance/rejection history; when results trend toward failing, the quality level status downgrades (e.g., from reduced to normal or tightened inspection), automatically increasing sample size or characteristics inspected on the next lot. Verify via the quality level record (QDQL/quality info record equivalent) that the switch actually occurred and cross-check that the inspection plan's dynamic modification rule is assigned correctly at the operation or characteristic level.
mediumInspection Planning

34. In a delivery inspection scenario using EWM, dynamic modification rules are supposed to reduce sample size based on quality level history, but the ERP-generated inspection characteristics passed to EWM always show full sample sizes regardless of quality level status. How would you troubleshoot the integration?

Confirm the quality level record in ERP (QM master data) actually reflects reduced status for the material/customer combination before the inspection lot is created, since dynamic modification evaluates at lot creation, not at EWM confirmation. Check that the EWM inspection plan replication and characteristic transfer via the quality inspection document correctly carries the sampling procedure determined in ERP, and verify no separate sampling override exists in EWM's quality inspection engine configuration.
mediumInspection Planning

35. A production line uses control charts to monitor a critical dimension across multiple work centers feeding a common assembly. How would you architect the SPC configuration to detect cross-work-center process drift?

Define the characteristic as SPC-relevant in the inspection plan with sampling procedure and control chart type (X-bar/R or individual/moving range) assigned per operation. Use a shared characteristic master so results across work centers roll into a common control chart view via QGC1/MSP1, but retain work-center subgroup identifiers to allow stratified analysis. Configure control limits from historical process capability, and use quality notifications triggered by out-of-control rules to alert on drift before it propagates downstream.
mediumInspection Planning

36. A material is produced at three plants, each supplying different customers with slightly different specification limits, but all plants feed a single centralized SPC analytics dashboard. Analysts report the control chart trends look artificially unstable even though each plant's process is actually stable within its own specification. How would you redesign the SPC and specification setup to fix this?

The likely root cause is that the analytics layer is aggregating control chart data across plants using a single specification limit set rather than plant- or customer-specific limits, causing false out-of-control signals. I would ensure each plant/material combination has its own inspection plan and control chart characteristic linked to its correct specification, tag control chart data with plant and specification context in the extraction, and configure analytics to segment or normalize by specification before trending, rather than pooling raw values across differing limit sets.
mediumInspection Planning

37. A production plant wants to reduce inspection effort for a mature material with a consistently strong quality history during in-process inspection, while still generating a certificate of analysis for each production lot. How would you design a skip-lot approach that satisfies both requirements?

Configure dynamic modification with skip-lot logic so qualifying lots receive an automatic usage decision without full results recording, based on consecutive accepted lots in the quality info record or material master. However, since a certificate is still required, configure the certificate profile to trigger from the inspection lot/batch regardless of skip status, using stored historical or last-recorded values, or force minimal results recording for characteristics feeding the certificate. Document this exception in the inspection plan control indicators.
mediumInspection Planning

38. A pharmaceutical client discovers mid-way through a multi-year stability study that the acceptance specification for a critical characteristic must change due to a regulatory update, and the change must not invalidate already-recorded interval results or affect batches already released to inventory in MM. How would you architect a change control approach for this?

Create a new specification version with an effective validity date rather than overwriting the existing one, preserving historical results tied to the original specification for audit purposes. Use master inspection characteristic versioning and inspection plan change numbers so future stability pull points reference the updated specification, while already-recorded results remain evaluated against the specification valid at recording time. Coordinate with MM so batch status and valuation of already-released batches are unaffected; only new inspection lots and future stability intervals adopt the revised limits, with change documentation retained for regulatory traceability.
mediumInspection Planning

39. A quality engineer complains they cannot change the sampling procedure on an active inspection plan characteristic, while a QM master data administrator can. What authorization and integration factors typically explain this difference?

Sampling procedure changes on inspection plan characteristics are usually authorization-object controlled (such as authorization for plan maintenance transactions and specific activity types like create, change, display), often combined with plant-level authorization checks. Administrators frequently hold broader roles including change access to released or active plans, while engineers may only have display or restricted change authorization pending change management workflow. Also check if the plan status locks changes requiring a new revision level.
mediumInspection Planning

40. A master inspection characteristic used across 200 inspection plans needs its sampling procedure changed from fixed sample size to a skip-lot approach due to consistently good supplier quality. What impact analysis and rollout steps would you perform?

First, determine whether the sampling procedure is maintained at the MIC level or overridden at the plan/operation level, since local overrides won't inherit the change automatically. Analyze which plans use the MIC without local override versus those with characteristic-specific sampling assigned directly. Test the skip-lot logic (dynamic modification rule) in a sandbox to confirm switch-over criteria based on historical results, then release the change during a low-volume period, monitor initial lots closely, and communicate to quality inspectors about revised sample sizes.
mediumInspection Planning

41. How is dynamic modification configured to influence sample size determination for delivery inspections integrated with EWM?

Dynamic modification rules are configured in the inspection plan/control plan via a dynamic modification rule linked to a sampling procedure; the rule tracks the acceptance history (e.g., accepted lots counter) at the combination of material, plant, and inspection type, adjusting sample size or skipping inspection based on tightened/reduced/normal inspection levels. When EWM handles the physical warehouse task for delivery inspection, the quality result and dynamic modification level are still driven by the ERP-side inspection plan, and EWM only executes storage-bin level tasks after QM confirms the inspection type is relevant.
mediumInspection Planning

42. A compliance team requires a defensible audit trail showing which sampling scheme quality level was active when each goods receipt inspection lot was created, to support regulatory audits of a skip-lot program. How do sampling schemes assigned through inspection plans interact with quality info record settings at goods receipt, and what data supports this traceability?

The sampling scheme's quality level and switching rule, referenced via the inspection plan's sampling procedure, determine sample size at lot creation, while the quality info record can enable or block skip-lot inspection for that vendor-material combination. Each inspection lot stores the sampling procedure and quality level used at creation time, and the vendor's quality level history is tracked in the sampling scheme's usage data, giving an auditable link between PO receipt, QI record status, and applied sampling logic.
mediumInspection Planning

43. A discrete manufacturer wants full traceability from a supplier-delivered raw material batch, through the control plan characteristics evaluated at receiving inspection, to the final component consumption recorded against production orders, spanning QM and MM batch records. How would you architect this control-plan traceability solution?

Link the control plan (inspection plan) to the material so every receiving inspection lot records characteristic results against the specific vendor batch via batch classification. Use goods movement history and batch where-used functionality to trace the vendor batch into production order component consumption. Store inspection results (QALS/QAVE) referencing the batch, and ensure batch classification values are propagated so a single traceability report can join vendor batch, inspection results, and consuming production orders across QM and MM tables.
mediumInspection Planning

44. A plant wants to reduce sample size for a stable quality characteristic without changing the inspection plan structure. What master data change would you recommend and why?

Modify the sampling procedure linked to the master inspection characteristic's inspection characteristic assignment, or update the sample size/scheme referenced at the operation-characteristic level, rather than altering the inspection plan header. If a fixed sample size procedure is used, adjust the sample size value directly; if using a sampling scheme with AQL, consider switching inspection severity via dynamic modification rules instead of a one-off manual change, preserving statistical validity.
mediumInspection Planning

45. During a project, procurement wants inspection severity to automatically tighten for a material after two consecutive rejected lots and relax back to normal after five consecutive accepted lots, integrated with existing inspection plans. How would you configure this using sampling schemes and inspection plan assignment?

Configure a dynamic modification rule that references usage decision history and links to a sampling scheme with defined inspection severities (reduced, normal, tightened), setting the switching rule thresholds to two consecutive rejections for tightening and five consecutive acceptances for relaxation. Assign this dynamic modification rule to the relevant inspection characteristic or lot-level control in the inspection plan, and ensure the sampling scheme includes sample size definitions per severity level. Test with historical lot data before production cutover since switching logic depends on inspection history stored in the system.
mediumInspection Planning

46. A production order's in-process inspection lot is unexpectedly moving to tightened inspection after several good lots. What dynamic modification factors would you review to explain this behavior?

Review the dynamic modification rule's evaluation basis, since tightened inspection can trigger from factors beyond the immediate lot, such as a rolling window of prior lots including one with a rejected UD or overdue results recording counted as a failure. Check the quality level record for the material-plant combination to see recent history and locked/blocked status, and confirm whether a manual override or a linked notification/complaint auto-adjusted the quality level, since these can force tightened inspection independent of the current lot's own results.
mediumInspection Planning

47. How does a sampling scheme's quality level and switching rule interact with goods receipt inspection to reduce inspection frequency over time for a reliable vendor?

The sampling scheme, tied to a dynamic modification rule, tracks lot acceptance history and applies switching rules (normal, tightened, reduced inspection) based on consecutive accepted or rejected lots, consistent with AQL-based statistical sampling concepts. As a vendor consistently passes GR inspections, the switching rule can move inspection severity from normal to reduced, lowering sample size on subsequent inspection lots automatically without manual plan changes, as long as the material-vendor combination remains within the dynamic modification rule's defined tracking scope.
mediumInspection Planning

48. A plant wants certain inspection plan operations to require documented measurements while others should only serve as process checkpoints without blocking the inspection lot. How would you use control keys to design this?

You assign a control key at each operation level that determines whether the operation is inspection-relevant, whether characteristics trigger a mandatory result recording and usage decision, and whether the operation contributes to lot scope calculation. For checkpoints that should not block progress, you use a control key flagged as non-inspection-relevant or informational, while operations requiring formal documentation get a control key with mandatory inspection and required characteristics, ensuring the usage decision only depends on the critical operations.
mediumInspection Planning

49. What configuration steps ensure dynamic modification rules correctly adjust the sample size used for results recording on delivery inspection lots processed in an EWM-managed warehouse?

Dynamic modification rules are assigned in the inspection plan/material specification via QM quality level (QM06) linked to the sampling procedure. For EWM integration, the sample size determined in ERP QM at results recording must match the quantity confirmed in the EWM quality inspection task; this requires the sampling procedure's dynamic modification level (tightened/normal/reduced) to be evaluated before the EWM task is generated, and the EWM inspection specification transfer must reference the same characteristic and sample data so the physical count aligns. Quality level history (acceptance/rejection) drives level changes for subsequent lots.
hardInspection Planning

50. You are designing a global QM template where dynamic modification rules must apply differently per region due to varying regulatory audit requirements. What architecture would you propose?

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.
hardInspection Planning

51. Inspectors report that sample sizes calculated for a fixed-percentage sampling procedure vary inconsistently across identical lot sizes at different plants using the same inspection plan. As the architect, how do you diagnose the root cause?

I would first check whether the sampling procedure is truly identical across plants or if plant-specific inspection plan versions have diverging sampling scheme or rule assignments. Next, verify the sample-determination method configured in the sampling procedure (fixed sample, sample-based on AQL table, or percentage rule) since percentage-based rules can round differently based on lot size boundaries. Also inspect whether a dynamic modification rule at plant level is altering inspection scope (skip, reduced, tightened) based on local quality history, which would explain apparent inconsistency without an actual configuration error.
hardInspection Planning

52. A client reports that dynamic modification rules for incoming inspection are not tightening or reducing inspection scope as expected across multiple plants sharing the same material. How would you diagnose the root cause?

Dynamic modification rules are tied to the quality level record per material-plant-vendor combination, so I'd first check if quality levels exist and are correctly configured per plant, since a missing quality level defaults to normal inspection scope. I'd review the dynamic modification rule assigned to the inspection plan or material master and verify the switching rule logic, then examine the lot history in the quality level to confirm stages are advancing based on actual usage decisions rather than being reset by manual intervention or master data changes.
hardInspection Planning

53. A plant using skip lot inspection for incoming raw materials finds that inspection lots are being created for every goods receipt despite the material being flagged for skip-lot sampling. As the architect, how would you diagnose and resolve this?

First verify the skip-lot indicator and dynamic modification rule are actually assigned to the inspection type in the material master QM view, since skip lot is implemented through dynamic modification with a skip status, not a standalone flag. Check the quality level record to confirm it is in 'skip' status; if the vendor's quality performance recently degraded or a manual reset occurred, the level may have reverted to 'normal'. Also confirm the sampling procedure supports skip logic and that no manual override or inspection type setting forces 100% inspection regardless of quality level.
hardInspection Planning

54. You are migrating inspection plans as part of a Public Cloud QM rollout where sales orders drive inspection requirements via SD integration. What sequencing and dependency risks must you manage for the inspection plan migration object?

Inspection plans must be loaded after materials, work centers, and inspection characteristics are fully migrated, since the plan references these as dependent master data. Because SD-triggered inspections rely on the sales order item's material and inspection type setup, ensure the material's QM view activation and sales-order-related inspection type are consistent before plan activation, otherwise sales orders created post-cutover may fail to generate inspection lots or reference an inactive plan version.
hardInspection Planning

55. A material has two active inspection types, goods receipt and in-process, and quality leadership wants each inspection type's dynamic modification rule to track and switch quality levels independently so that a supplier quality issue in-process does not incorrectly tighten goods receipt sampling, and vice versa. How would you architect the dynamic modification rule and quality level structure to keep these tracks isolated?

Assign separate dynamic modification rules per inspection type rather than a single shared rule, and ensure the sampling scheme's quality level tracking is scoped by inspection type and material-plant combination rather than material alone. Verify the inspection plan for each inspection type references its own sampling procedure and DMR, and confirm quality level history in the sampling scheme usage data is not inadvertently shared across inspection types due to a common characteristic or plan reuse.
hardInspection Planning

56. An architect is designing a dynamic modification strategy for final inspection lots that feed SD order fulfillment across multiple plants with different customer quality expectations. What design considerations govern the rule and quality level structure?

Design separate quality level records per plant-material-customer combination where customer-specific rigor differs, using the material's inspection setup to reference plant-specific dynamic modification rules; ensure rule sets (VDAT/inspection severity sequences) reflect risk tolerance per customer segment, and centralize control via inspection plan usage per plant. Consider audit requirements so skip/reduced levels don't bypass customer-mandated inspections tied to sales order requirements, and maintain traceability of level switches for customer complaint investigations.
hardInspection Planning

57. A global rollout standardizes inspection characteristics across 15 plants using shared master characteristics and master inspection plans, but several plants legitimately need different specification limits for the same characteristic due to local regulatory or customer requirements. How would you architect the characteristic and inspection plan structure to allow plant-specific limit overrides without fragmenting the global template governance?

Keep the master characteristic (CT04/QS21) generic with no hardcoded limits, defining limits instead at the plan or plant-specific inspection characteristic level where the master characteristic is used in a task list or material specification. Use plant-specific task lists or group counters referencing the same master characteristic, or leverage material specifications to layer plant/customer-specific limits on top of a shared characteristic base, preserving one governed characteristic definition while allowing controlled local variance through change management.
hardInspection Planning

58. Walk through the end-to-end process of designing an inspection setup that leverages the material master QM view together with master inspection characteristics and inspection methods for reuse across multiple materials.

First, create reusable master inspection characteristics with their sampling and valuation rules, then link master inspection methods (measurement or test procedures) to those characteristics or leave them standalone for plan-level assignment. In the material master QM view, activate relevant inspection types and assign a catalog profile. Build the inspection plan referencing the master characteristics, pulling in the linked methods automatically or overriding at plan level. This structure lets multiple materials share the same characteristic/method logic while only the inspection plan and material assignment vary.
hardInspection Planning

59. You need to design dynamic modification rules for periodic inventory quality control inspection lots so they can skip based on quality level thresholds, while the same material is also subject to sales/delivery-based inspection lots for specific customers. How would you architect this to avoid conflicting skip decisions between the two inspection origins?

Since quality level records are typically keyed by material, plant, and inspection type, periodic stock-check lots and delivery-based lots usually maintain independent quality level histories even for the same material. Architect the solution by assigning distinct inspection types for each origin so skip-lot decisions don't cross-contaminate, but establish a governance process (or manual quality level override) to ensure a batch failing periodic inspection isn't shipped skip-lot to a customer. Document the risk that inventory-level skip-lot status does not guarantee sales-level quality assurance.
hardInspection Planning

60. You are designing a global change management process for master inspection characteristics and methods used across dozens of inspection plans worldwide. What architecture would you propose to control changes without breaking existing production inspection lots?

Use master inspection characteristics and methods maintained centrally with validity periods and change numbers tied to engineering change management, so new versions become effective only from a defined date without retroactively altering in-process lots. Existing open inspection lots continue referencing the characteristic version active at lot creation. Establish a governance board to approve changes, mandatory impact analysis across referencing plans, and staged rollout using change number-controlled activation rather than direct overwrite.
hardInspection Planning

61. A customer with a long-standing dynamic modification rule based on quality level history suddenly starts receiving recurring inspection lots at full sample size despite a strong recent quality track record. As the architect, how would you investigate and resolve this?

I'd first check whether the quality level record (QDR1/QDV1) was reset or expired, since quality levels have validity periods and lot counters that reset on rejection or manual intervention. I'd review recent usage decisions for rejections that reset the skip sequence, verify the dynamic modification rule's parameters (block size, minimum lots) still match business intent, and check if a material master or info record change (source of supply, vendor) invalidated the existing quality level linkage.
hardInspection Planning

62. A component sourced from a vendor undergoes source inspection at the supplier site (origin 05/07 configuration), but the same component also requires an in-process inspection once it enters production. How would you architect the inspection lot origin strategy to avoid duplicate or conflicting inspection results across procurement and production, and what MM integration risks exist?

Design separate inspection plans per origin (e.g., 05 for stock transfer/source inspection, 04 for production) with distinct characteristic sets so results don't overlap—source inspection validates vendor conformance, production inspection validates process/assembly conditions. Ensure inspection lot origin mapping in the material's QM view doesn't trigger redundant lots for the same goods movement, and confirm MM movement types correctly invoke only the intended inspection type via OMCT/QM info record settings. Risk: duplicate lots consuming inventory postings twice or blocking stock unnecessarily if both origins activate on the same movement.
hardInspection Planning

63. Describe the end-to-end process of setting up master inspection characteristics and methods so they can be correctly referenced by a material's QM view and inspection plan.

You first create master inspection characteristics in QS21 defining control indicators, value range/catalog assignment, and sampling relevance, then create methods in QS31 that define how the characteristic is measured. The material's QM view activates the inspection setup indicator and assigns the QM procurement key, but actual linkage happens in the inspection plan (QP01) where each operation references the master characteristic and method by version. Governance requires locking approved versions so plan usage remains stable even if the characteristic master is later revised.
hardInspection Planning

64. A custom quality characteristic field added via in-app extensibility on the inspection plan is not appearing in the replicated material master record in a connected MDG hub. How would you diagnose and resolve this in an S/4HANA architecture with distributed MDG?

First confirm the custom field is part of a released extension include and mapped in the replication model (e.g., via BAdI or field mapping in the distribution model), since MDG replication only carries fields explicitly included in the governed data model and BAPI structures. Check whether the field belongs to QM-specific inspection plan data, which is typically not part of standard material master replication, versus true material master extensibility fields, and extend the MDG data model and mapping accordingly if business-justified.
hardInspection Planning

65. In an S/4HANA Public Cloud implementation, what controls and extensibility constraints must an architect consider when migrating custom inspection plan characteristics and control indicators from an ECC on-premise system?

Public Cloud restricts direct table-level or classic transaction access, so custom characteristics and control indicators must be reviewed against the released extensibility scope for QM, using in-app extensibility fields rather than core enhancements. Architects must validate that master inspection characteristics referenced by plans exist as standard or extended fields in the Public Cloud key user extensibility framework, and that any custom logic embedded via user exits in ECC is redesigned using BAdIs or Business Add-Ins exposed for cloud extensibility, since classic ABAP modifications are not permitted.
hardInspection Planning

66. How would you architect a control plan solution combining inspection plans, certificate profiles, and PP integration for an automotive IATF-compliant client on S/4HANA?

Use the S/4HANA control plan capability (Manage Control Plans app) to map process steps to characteristics, control methods, and reaction plans, linking each control point to a routing/inspection plan operation. Certificate profiles are configured to auto-generate certificates of conformance referencing the same characteristics once usage decisions post. Integration with PP ensures the control plan characteristics are inherited into the production order/inspection lot at order release, keeping control plan, inspection plan, and routing operations synchronized as a single source of truth.
hardInspection Planning

67. A global rollout wants a single inspection method used consistently across five plants for a critical laboratory test, but each plant's lab uses slightly different equipment references and result units. How would you architect the inspection method setup to balance standardization with local flexibility?

Create a master inspection method centrally with the standardized test procedure text, default sampling, and result category, then let each plant's inspection plan or material task list list reference the same master method while overriding only equipment-specific fields at the operation/characteristic level, such as test equipment assignment or unit of measure conversion. Avoid plant-specific copies of the method itself; instead use plan-level overrides so the core test logic stays governed centrally while equipment details remain locally maintained.
hardInspection Planning

68. After a master inspection characteristic's sampling procedure is changed from a fixed sample size to a single sampling scheme with AQL, you notice that inspection lots created after the change use the new sampling logic for most vendors, but a subset of vendor-material combinations still generate lots with the old fixed sample size. As the architect responsible for master data governance, how would you diagnose the root cause?

Check whether quality info records for those vendor-material combinations carry a plant-specific sampling procedure override or skip-lot flag that takes precedence over the characteristic-level default. Also verify inspection plan version validity dates, whether the affected plans reference an older plan version still active, and whether change numbers were used so the new sampling procedure only applies from a specific effective date. Confirm the material's inspection type control and any dynamic modification rule quality-level history influencing scheme selection.
hardInspection Planning

69. In an EWM-integrated site, a storage-bin level inbound inspection triggered via the quality inspection engine (QIE) fails to create the corresponding inspection lot in ERP/S4 for a batch-managed material, even though the inspection plan and QM view configuration look correct. As the architect, how would you diagnose whether the issue lies in QIE inspection rule setup, master data replication, or the ERP inspection type configuration?

I would first confirm the QIE inspection rule and inspection plan assignment in EWM are correctly linked to the sample-relevant process code and material/plant. Then verify master data replication (material, batch, inspection plan) between ERP and EWM via CIF or S/4 embedded integration completed without errors. Check whether the ERP inspection type is flagged for the correct origin and whether inspection lot creation is expected in ERP versus handled entirely within EWM's QIE. Finally review interface logs and IDoc/queue monitors for failed transmissions.
hardInspection Planning

70. You need to design a change control architecture where updates to master inspection characteristics and methods go through a formal approval and versioning process before being propagated to inspection plans across multiple plants, ensuring open inspection lots and active MM quality info records are not disrupted. What architecture would you propose?

Leverage the change number/status concept on master characteristics and methods so new versions carry a defined validity date and change status, allowing edits to occur in a 'locked' or 'in process' state before release. Maintain inspection plans with their own change number so plan updates only pick up the new characteristic version at the next valid-from date, leaving open inspection lots tied to the version active at lot creation. Coordinate with quality info records so skip/source inspection logic isn't invalidated mid-cycle, and run impact analysis (where-used) before releasing changes globally.
hardInspection Planning

71. Dynamic modification rules for a vendor's incoming inspection are configured to reduce sample size after a run of accepted lots, but you notice full inspection lots continue to be generated despite qualifying acceptance history. What are the likely root causes to investigate?

Check whether the dynamic modification rule is correctly assigned in the inspection plan and whether the quality level record (QM material-vendor combination) is being updated after each UD; a missing or reset quality level resets to normal inspection. Also verify the switch-over rule sequence, that the UD codes used actually count toward acceptance in the DMR, and that lot origin/inspection type combination is the one configured for dynamic modification - manual UD codes bypassing automatic determination can also block level progression.
hardInspection Planning

72. A global rollout requires that a customer's inspection severity be automatically relaxed to skip-lot status after a defined number of consecutive accepted deliveries, but tightened immediately upon any rejection, integrated with SD delivery-based inspections. How would you design this using dynamic modification, and what risks must be addressed at the architecture level?

Design a dynamic modification rule linked to the material/customer or material/sales-org combination, with quality levels defining tightened, normal, reduced, and skip stages based on consecutive accepted usage decisions; a single rejection resets the quality level to tightened per the rule's parameters. Ensure the dynamic modification rule is assigned to the inspection plan used for the SD-triggered inspection type and that quality level records (QM quality level master) are maintained at the correct combination granularity. Architecture risks include incorrect granularity causing cross-customer contamination of quality history, and skip-lot status inadvertently bypassing inspection for high-risk characteristics.
hardInspection Planning

73. Inspection lots for a critical material are being created with an incorrect sample size that doesn't match the expected AQL-based scheme. What is your root-cause investigation approach?

First verify which sampling procedure is assigned at the inspection characteristic level in the active inspection plan version, since multiple plan versions can exist with different validity dates. Check whether the sampling scheme (QS/quality level, AQL) referenced is correctly configured and whether dynamic modification rules have shifted severity due to recent lot history. Also confirm the inspection lot picked up the correct plan via task list usage and lot origin, since manual overrides at lot creation can bypass plan-defined sampling.
hardInspection Planning

74. An architect is designing a dynamic modification rule strategy for a multi-plant, multi-material rollout where some materials require strict regulatory-driven fixed inspection and others benefit from adaptive skip-lot logic. What architectural approach balances compliance rigidity with operational efficiency?

Segment materials into inspection categories based on regulatory risk classification, assigning fixed (non-switchable) inspection severity to regulated materials by omitting or restricting dynamic modification rule assignment, while applying skip-lot-enabled dynamic modification rules only to non-regulated, historically stable materials. Centralize dynamic modification rule definitions in a template but control activation through inspection plan assignment per material risk tier, and build governance so rule changes for regulated materials require compliance sign-off, preventing accidental skip-lot application to controlled items.
hardInspection Planning

75. Explain how dynamic modification rules influence inspection severity and sampling for final inspection lots across successive production orders, and what data drives the automatic tightening or reduction of inspection scope.

Dynamic modification rules track the quality history (accepted/rejected lots) per material-plant-inspection type combination using a dynamic modification record. Based on consecutive accepted lots, the system can automatically switch to a reduced sampling procedure; consecutive rejections trigger tightened inspection or skip-lot suspension. The rule links a sampling scheme, inspection severity levels (normal/tightened/reduced), and switching rules configured in the inspection plan or material master QM view, evaluated at lot creation.
hardInspection Planning

76. For a goods receipt inspection lot against a purchase order, the calculated sample size unexpectedly differs from what the inspection plan's sampling procedure specifies, even though the sampling scheme is fixed. As the architect, what would you investigate to explain the discrepancy?

Check whether the inspection lot quantity (base UoM) differs from the PO quantity due to unit-of-measure conversion between purchasing and inspection plan UoM. Verify the sampling procedure type isn't dynamic-modification-driven (varying with quality level), confirm partial deliveries or inspection points splitting the lot quantity, and check if the sample-determination indicator (fixed value, sampling scheme, percentage) is correctly assigned at the operation/characteristic level rather than overridden manually in the inspection lot.
hardInspection Planning

77. A plant has skip lot inspection active for a raw material via the dynamic modification rule, and quality levels show a consistent 'skip' status, yet incoming inspection lots continue to be created for every goods receipt against a specific vendor. As architect, how would you systematically isolate whether the issue is in the quality level, the material/vendor combination, or the inspection type setup?

Check whether the quality level record (QA32) actually exists and is active for the correct material-vendor-plant combination and inspection type, since skip lot requires a valid quality level, not just an active dynamic modification rule. Verify the inspection type control key allows skip lot and that no manual inspection setup or lot origin override forces a lot. Check the info record/source list for vendor-specific inspection settings and confirm QM-relevant flag consistency across material master, purchasing info record, and quality info record.
hardInspection Planning

78. Explain how dynamic modification rules influence inspection lot creation and inspection scope over time, and describe the design trade-offs when integrating this with a sales-driven quality requirement (e.g. customer-specific inspection).

Dynamic modification rules use quality level records tracking a vendor/material/plant combination's historical results to shift inspection severity (skip, reduce, normal, tighten) automatically at lot creation. For customer-driven SD scenarios, rules must weigh standardization against contractual inspection commitments, since a quality level built from general receipts may not reflect customer-specific criteria; architects often segment quality levels by customer or sales org combination, or override dynamic rules with fixed inspection for regulated customers, sacrificing automation for compliance certainty.
hardInspection Planning

79. During a global template rollout, how should catalogs be structured to support standardized inspection plans across multiple plants with local variations?

Design a global catalog structure (catalog types 1, 2, 9, etc.) with harmonized code groups and codes maintained centrally, then use plant-specific selected sets to restrict which codes are usable locally without duplicating catalog master data. Inspection plans reference master inspection characteristics that pull catalog codes; local variations are handled via plant-specific selected sets or supplementary code groups rather than forking the catalog itself, preserving reporting consistency in QM tables like QASE.

Related lesson

Why Inspection Planning Matters: Foundations and Master Data

Related topics

Quality NotificationsInspection LotsUsage 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