C_TS414_2023 SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Quality Management Free Practice Exam Questions (2025 Updated)

To enable multiple results recording for the same inspection characteristic within one operation in SAP S/4HANA QM (e.g., transaction QE51N), specific sampling procedures are used:

Using Sampling Procedure with Independent Multiple Samples (C): This sampling type (configured in transaction QDV1) allows recording multiple independent results for a characteristic (e.g., 5 separate measurements), each valuated individually. It’s ideal for detailed analysis within an operation (SPRO > QM > Quality Inspection > Sample Management).

Using Sampling Procedure with Inspection Points (D): Inspection points (set in the inspection plan header, transaction QP01, and linked to a sampling procedure) enable multiple recordings over time or events (e.g., per shift), supporting repeated results for the same characteristic.

Using Sampling Procedure with Sampling Scheme (A): Sampling schemes (e.g., ISO 2859) define sample sizes but don’t inherently allow multiple results per characteristic.

Using Conditional Inspection Characteristics (B): Conditional characteristics depend on other results but don’t facilitate multiple recordings of the same characteristic.

Thus, "Using sampling procedure with independent multiple samples" and "Using sampling procedure with inspection points" are the correct answers.References: SAP Help Portal - "Multiple Results Recording in QM"; SAP S/4HANA QM User Guide - "Sampling Procedures".

Creating a new inspection type in SAP QM (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types) requires:

Assign a Task List Type to the New Inspection Type (A): The inspection type (e.g., custom Z01) must be linked to a task list type (e.g., Q for inspection plans) to define the inspection scope, a mandatory step.

Assign the New Inspection Type to a Predefined Inspection Lot Origin (C): The type must be assigned to an inspection lot origin (e.g., 01 for GR) to determine when lots are created, a required configuration.

Assign the New Inspection Type to a Number Range (B): Number ranges are assigned to origins, not directly to types, so this is optional.

Define Default Values for the New Inspection Type (D): Defaults (e.g., UD settings) are optional enhancements, not mandatory.

Thus, "Assign a task list type to the new inspection type" and "Assign the new inspection type to a predefined inspection lot origin" are the correct answers.References: SAP Help Portal - "Customizing Inspection Types"; SAP S/4HANA QM Customizing Guide - "Inspection Lot Creation".

In SAP S/4HANA QM, the item of a quality notification (transaction QM01) can reference specific objects:

Material (A): Materials are a standard object category, linking the notification to a specific material number (e.g., in the "Reference Object" section).

Batch (C): Batches (LO-BM) can be assigned to track batch-specific issues, a common QM feature.

Serial Number (E): Serial numbers (e.g., for equipment or materials) are supported to pinpoint individual units, especially in industries like electronics.

Delivery Item (B): Delivery items are referenced in SD notifications but not directly assigned as objects in the item structure in standard QM.

Purchase Order Item (D): POs are reference documents, not directly assignable objects in the notification item.

Thus, "Material," "Batch," and "Serial number" are the correct answers.References: SAP Help Portal - "Reference Objects in Quality Notifications"; SAP S/4HANA QM User Guide - "Notification Items".

The Document Management System (DMS) in SAP S/4HANA allows users to link documents (e.g., PDFs, drawings, or instructions) to various objects to provide additional context or instructions. In Quality Management, certain basic data objects support this integration natively:

Inspection Methods (A): Inspection methods define how an inspection is performed (e.g., a test procedure). You can assign DMS documents to inspection methods to provide detailed instructions or reference materials (e.g., a calibration guide). This is configured in the inspection method master data (transaction QK01/QK02) where a document link field is available.

Master Inspection Characteristics (D): Master inspection characteristics (MICs) define what is being inspected (e.g., length, weight). DMS documents can be assigned to MICs to include specifications, diagrams, or tolerances directly in the master data (transaction QS21/QS23). This is a standard feature to enhance inspection planning and execution.

Codes from Code Groups (B): Codes and code groups are used for qualitative valuations (e.g., defect types). They do not have a direct field for DMS document assignment in their master data (transaction QS41/QS51), making this option incorrect.

Sampling Procedures (C): Sampling procedures determine how samples are drawn (e.g., fixed sample size). While critical to inspection planning, they do not support direct DMS document assignment in standard SAP configuration (transaction QDV1/QDV2).

Thus, the correct answers are "Inspection methods" and "Master inspection characteristics," as both support DMS integration without additional customization.References: SAP Help Portal - "Document Management in QM"; SAP S/4HANA QM Configuration Guide - "Basic Data for Quality Management".

The requirement for a supplier to provide a quality certificate and its type is configured in:

Quality Info Record: Procurement (D): In the quality info record (transaction QI01), you set the "Certificate Required" indicator and specify the "Certificate Type" (e.g., "ISO 9001") under the "Certificate Data" section. This links the requirement to a specific material-supplier combination, enforced during GR (SPRO > QM > Quality Inspection > Quality Info Record).

Purchase Order (A): POs inherit certificate settings from the quality info record, not define them.

Material Master (B): The QM view defines inspection types, not certificate requirements or types.

Business Partner (C): Supplier master data lacks QM-specific certificate settings.

Thus, "Quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Quality Info Record in QM"; SAP S/4HANA QM User Guide - "Certificate Management".

Task lists (e.g., routings) for production orders in SAP integrate QM master data to enable inspections:

Material Specifications (A): Material specs (transaction QS61) can be referenced in routings (transaction CA01) to define inspection requirements for a material, integrating QM into production.

Master Inspection Characteristics (C): MICs (transaction QS21) are directly assigned to operations in routings or inspection plans, specifying what to inspect during production.

Classifications (B): Classifications (transaction CL01) are batch or material attributes, not directly integrated into task lists for production orders.

Control Indicators (D): These are settings within characteristics or plans, not standalone master data for integration.

Thus, "Material specifications" and "Master inspection characteristics" are the correct answers (assuming a multiple-choice intent, though only two are clearly correct based on standard SAP).References: SAP Help Portal - "QM Integration with PP"; SAP S/4HANA QM User Guide - "Task Lists".

In SAP S/4HANA Quality Management, catalogs are used to manage predefined codes for qualitative data recording, and selected sets are subsets of code groups used in specific contexts (e.g., inspection plans). Valuation of codes (assigning values like "Accepted" or "Rejected") is mandatory for certain catalog types to ensure consistent processing:

Usage Decisions (A): Catalog type "3" (Usage Decisions) requires valuation in the selected set because the usage decision (UD) determines the stock posting and quality score. In Customizing (SPRO > Quality Management > Quality Inspection > Usage Decision > Define Selected Sets), codes like "A" (Accepted) or "R" (Rejected) must be valuated to trigger specific system actions (e.g., goods movement). This is mandatory for inspection lot completion.

Defect Types (C): Catalog type "9" (Defects) requires valuation in the selected set when used in defect recording (e.g., transaction QS51). Defect codes (e.g., "Scratch," "Dent") need valuation to classify severity or trigger follow-up actions like notifications, making it mandatory in quality processes.

Characteristic Attributes (B): Catalog type "1" (Characteristic Attributes) is used for qualitative MICs. Valuation is optional and depends on the characteristic’s settings (e.g., "Good/Bad"), not mandatory in the selected set itself.

Activities (QM) (D): Catalog type "5" (Activities) is used for tasks or follow-ups in notifications. Valuation is not mandatory in the selected set, as activities are typically descriptive rather than evaluative.

Thus, "Usage decisions" and "Defect types" are the correct answers, as valuation is a required step in their respective processes.References: SAP Help Portal - "Catalogs and Selected Sets in QM"; SAP S/4HANA QM Customizing Guide - "Catalog Management".

Entering a priority (e.g., "High") in a quality notification (transaction QM01):

Calculate the Notification Start and Finish Dates (C): The priority (set in Customizing, SPRO > QM > Quality Notifications > Define Priorities) triggers the system to calculate required start and end dates based on response times linked to the priority (e.g., 24 hours for "High"). This is standard behavior for time-sensitive notifications.

Create Activities Automatically (A): Activities are logged manually or via action boxes, not priority.

Create Tasks Automatically (B): Tasks require a response profile, not just priority.

Calculate Malfunction Dates (D): Malfunction dates are specific to equipment notifications (e.g., F2), not driven by priority alone.

Thus, "Calculate the notification start and finish dates" is the correct answer.References: SAP Help Portal - "Priorities in QM Notifications"; SAP S/4HANA QM User Guide - "Notification Processing".

During results recording (e.g., transaction QE51N), additional characteristics can be added to an operation:

Master Inspection Characteristics as Complete Copy Model (B): MICs (transaction QS21) can be added as a complete copy, inheriting all attributes (e.g., tolerances, sampling) for immediate use in the lot.

Master Inspection Characteristics as Incomplete Copy Model (C): MICs can be added as an incomplete copy, allowing customization (e.g., adjusting tolerances) during recording, a flexible option in SAP QM.

Master Inspection Characteristics as Reference Characteristic (A): Reference MICs are linked for reuse but not added anew during recording; they’re predefined in the plan.

Class Characteristics from the Classification System (D): Class characteristics (transaction CT04) are for batch classification, not inspection recording.

Thus, "Master inspection characteristics as complete copy model" and "Master inspection characteristics as incomplete copy model" are the correct answers.References: SAP Help Portal - "Adding Characteristics in Results Recording"; SAP S/4HANA QM User Guide - "Inspection Results".

To manage release stages (e.g., first-article, series) with different inspection plans in procurement, SAP QM uses:

By Assigning a Status Profile to the Quality Info Record: Procurement (B): In the quality info record (transaction QI01), you assign a status profile (defined in SPRO > QM > Environment > Status Management). This profile controls stages (e.g., "First Article," "Series") via statuses, and each status can link to a specific inspection plan via dynamic modification or inspection type settings. This is the standard approach for supplier-material-specific release processes.

Business Partner (A): Status profiles here are for partner management, not QM inspection stages.

Inspection Type Settings in Customizing (C): Inspection types (e.g., 01) don’t use status profiles directly in Customizing.

Inspection Type in Material Master (D): The material master’s QM view doesn’t supportstatus profiles for this purpose.

Thus, "By assigning a status profile to the quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Quality Info Record and Release Stages"; SAP S/4HANA QM Customizing Guide - "Status Profiles".

Status profiles in SAP QM (defined in SPRO > QM > Quality Notifications > Status Management) control the lifecycle of notification elements:

Header (B): The notification header (e.g., transaction QM01) can have a status profile assigned to manage overall statuses (e.g., "Open," "Completed").

Tasks (D): Tasks within the notification (e.g., "Investigate") can have their own status profile to track individual task progress (e.g., "Released," "Completed").

Activities (A): Activities log events but don’t support status profiles directly.

Items (C): Items (defect details) use catalog types, not status profiles.

Thus, "Header" and "Tasks" are the correct answers.References: SAP Help Portal - "Status Profiles in QM Notifications"; SAP S/4HANA QM User Guide - "Notification Status".

Material specifications in SAP QM (transaction QS61) define inspection requirements directly in the material master, independent of task lists. They integrate specific QM basic data:

Master Inspection Characteristics (A): MICs are the core of material specifications, defining what is inspected (e.g., length, pH). They are assigned to the material spec to set tolerances or qualitative codes.

Sampling Procedures (C): These determine the sample size for the material spec’s characteristics (e.g., fixed sample of 5). They are assigned to MICs within the material specification.

Inspection Methods (E): Inspection methods (e.g., "Visual check") can be linked to MICs in the material spec to specify how the inspection is performed.

Dynamic Modification Rule (B): This governs inspection scope changes (e.g., skip lots) and is assigned to inspection types or plans, not material specs directly.

Selected Set (D): Selected sets are used for qualitative valuations (e.g., UD codes) but are not directly assigned to material specs; they link via MICs instead.

Thus, "Master inspection characteristics," "Sampling procedures," and "Inspection methods" are the correct answers.References: SAP Help Portal - "Material Specifications in QM"; SAP S/4HANA QM User Guide - "Basic Data".

The SAP Fiori app "Record Inspection Results" (App ID: F2170) in SAP S/4HANA QM supports specific result recording types for inspection lots:

Recording of Single Inspection Results (B): This allows entering individual values for quantitative or qualitative characteristics (e.g., one value per sample), a standard feature in the app for detailed recording.

Summarized Inspection Results Recording (D): The app supports entering a single aggregated value (e.g., average) for a characteristic, ideal for summarized quantitative data, as configured in the MIC control indicators.

Classed Inspection Results Recording (A): Classed recording (grouping results into ranges) is supported in classic transactions (e.g., QE51N) but not explicitly in the standard Fiori app’s functionality.

Results Recording for Inspection Points (C): While inspection points are supported in QM, the Fiori app focuses on lot-level recording and doesn’t emphasize point-specific recording in its standard scope.

Thus, "Recording of single inspection results" and "Summarized inspection results recording" are the correct answers.References: SAP Help Portal - "Record Inspection Results Fiori App"; SAP S/4HANA QM User Guide - "Fiori Apps in QM".

For a "Complaint Against Supplier" notification (e.g., type Q2, transaction QM01):

Material Document (B): Material documents (e.g., goods receipt via MIGO) are standard references, linking the complaint to a specific receipt event (SPRO > QM > Quality Notifications > Notification Creation).

Purchasing Document (C): Purchase orders (e.g., from ME21N) are commonly referenced to tie the complaint to the supplier’s delivery or order.

WBS Element (A): Work Breakdown Structure elements are PS-related, not standard for supplier complaints.

QM Order (D): QM orders track costs but aren’t reference documents for notification creation.

Thus, "Material document" and "Purchasing document" are the correct answers.References: SAP Help Portal - "Reference Documents for Supplier Complaints"; SAP S/4HANA QM User Guide - "Notification Creation".

Defect recording in SAP QM (e.g., transaction QF01 or QE51N) is tied to specific objects:

Inspection Lots (A): Defects are recorded directly against an inspection lot (e.g., during results recording), linking to the lot’s context (e.g., material, supplier).

Inspection Characteristics (B): Within an inspection lot, defects can be recorded at thecharacteristic level (e.g., a specific MIC fails), allowing detailed defect analysis.

Business Partners (C): Defects aren’t recorded against suppliers/customers directly; they’re tied to lots or notifications.

Quality Certificates (D): Certificates document results, not serve as objects for defect recording.

Thus, "Inspection lots" and "Inspection characteristics" are the correct answers.References: SAP Help Portal - "Defects Recording in QM"; SAP S/4HANA QM User Guide - "Defect Management".

When a quality certificate is mandatory (set in the quality info record, transaction QI01) but no GR inspection lot is created (inspection type 01 inactive in the material master), the system handles the missing certificate as follows:

The Goods Receipt is Posted to Blocked Stock (B): If the certificate is required (e.g., "Certificate Check" active in QI01) and not received (transaction QC55), the GR (transaction MIGO) posts the material to blocked stock (movement type 103/105 process). This is standard behavior to prevent unrestricted use until the certificate is confirmed, even without an inspection lot (SPRO > QM > Quality Certificates > Procurement > DefineControl Keys).

Unrestricted Use Stock (A): This would occur only if no certificate check was enforced, contradicting the premise.

Quality Notification Created Automatically (C): Notifications require manual creation or specific Customizing (e.g., defect recording), not automatic generation here.

Missing Certificate Escalated (D): Escalation is not a standard SAP term or process in this context; it implies custom workflow not present in standard QM.

Thus, "The goods receipt is posted to blocked stock" is the correct answer.References: SAP Help Portal - "Certificate Processing at Goods Receipt"; SAP S/4HANA QM User Guide - "Stock Posting".

For a customer complaint notification (type Q1, transaction QM01), standard reference documents include:

Delivery (A): Outbound delivery documents (e.g., from VL01N) are commonly referenced, linking the complaint to a shipped item (SPRO > QM > Quality Notifications > Notification Creation).

Sales Order (D): Sales orders (e.g., from VA01) can be referenced to trace the complaint back to the original customer order.

Quotation (B): Quotations are pre-sales documents and not standard references for QM notifications.

Material Document (C): Material documents (e.g., GR) are procurement-related, not typical for customer complaints.

Thus, "Delivery" and "Sales order" are the correct answers.References: SAP Help Portal - "Reference Documents in QM Notifications"; SAP S/4HANA QM User Guide - "Customer Complaints".

For an inspection lot to be created for an outbound delivery item (e.g., inspection type 10):

An Inspection Lot Origin is Assigned to a Delivery Type in Customizing (B): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Lot Origins and Assign Inspection Types), the delivery type (e.g., LF for outbound) must be linked to an inspection lot origin (e.g., 10). This ensures the system triggers a lot during delivery creation (VL01N).

The Relevant Inspection Type is Active in the Material (C): Inspection type 10 must be activated in the material master’s QM view (transaction MM01/MM02) for the plant, enabling QM for outbound deliveries.

QM is Active in the Relevant Movement Type (A): Movement types (e.g., 601 for goods issue) trigger stock postings, not inspection lots directly in outbound scenarios.

QM is Active in the Quality Info Record: SD (D): The quality info record: SD (transaction QVDM) defines inspection requirements but isn’t a prerequisite for lot creation; it refines the process.

Thus, "B" and "C" are the correct answers.References: SAP Help Portal - "Inspection Lots for Deliveries"; SAP S/4HANA QM Customizing Guide - "Inspection Lot Origins".

The quality info record: SD (transaction QVDM) specifies QM requirements for outbound deliveries:

Customer and Sales Organization (A): This combination allows generic inspection settings for a customer across a sales organization, a valid standard option.

Customer, Material, and Sales Organization (B): This is the most specific combination, enabling material-specific inspection requirements for a customer within a sales org (SPRO > QM > Quality Inspection > Quality Info Record: SD).

Customer, Material, and Division (C): Division isn’t a key field for the SD info record in standard SAP.

Customer, Material, and Distribution Channel (D): Distribution channel isn’t part of the key; sales org is used instead.

Thus, "A" and "B" are the correct answers.References: SAP Help Portal - "Quality Info Record: SD"; SAP S/4HANA QM User Guide - "SD Quality Management".