C_TS414_2023 SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Quality Management Questions and Answers

The quality info record: Procurement (transaction QI01/QI02) manages supplier-material relationships and can impose release restrictions:

To a Quantity, by Entering a Release Quantity (A): In the quality info record, you can set a "Release Quantity" field to limit the approved purchase quantity (e.g., 100 units). Once exceeded, further approval is needed, a standard feature.

Until the Supplier Has Provided a Quality Certificate, by Entering a Certificate Type (B): You can specify a certificate type (e.g., "ISO 9001") in the "Certificate" field, blocking release until the supplier provides it, verified during goods receipt.

To a Period of Time, by Supplying a Release Date (C): While validity dates exist, they define the record’s lifespan, not a specific release restriction mechanism.

Until the Supplier Quality Score is Better Than a Threshold (D): Quality scores influence supplier evaluation but aren’t directly set as a release condition in the info record.

Thus, "A" and "B" are the correct answers, reflecting standard SAP QM functionality.References: SAP Help Portal - "Quality Info Record: Procurement"; SAP S/4HANA QM User Guide - "Supplier Release".

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".

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".

Certificate profiles in SAP QM (transaction QC01) define the data included in outgoing quality certificates. The characteristic categories allowed are:

Master Inspection Characteristic (A): MICs (transaction QS21) are used in inspection plans and material specs, and their results can be included in certificate profiles to report quality data (e.g., measured values).

Class Characteristic (B): Class characteristics (from the Classification System, transaction CT04) are linked to batches or materials and can be included in certificate profiles to display classification data (e.g., batch properties).

Inspection Characteristic (C): This term refers to characteristics in an inspection lot/plan but is not a distinct category; it’s covered by MICs, so it’s not separately selectable.

Process Instruction Characteristic (D): Used in Process Industries (PI) for production, not applicable to QM certificate profiles in standard SAP.

Thus, "Master inspection characteristic" and "Class characteristic" are the correct answers.References: SAP Help Portal - "Quality Certificates - Certificate Profiles"; SAP S/4HANA QM User Guide - "Outgoing Certificates".

Partner determination in QM notifications (e.g., transaction QM01) assigns partners (e.g., responsible person) via:

Assignment to the Notification Type (D): The partner determination procedure is assigned in Customizing (SPRO > QM > Quality Notifications > Notification Creation > Define Notification Types), linking specific partner roles (e.g., coordinator) to a notification type (e.g., Q1 for customer complaints). This is the standard approach.

Notification Origin (A): Origins (e.g., 01 for GR) don’t directly assign partner procedures.

Material Type (B): Material types are MM settings, not linked to QM partner determination.

Material Master (C): Material master doesn’t store partner procedures for notifications.

Thus, "Assignment to the notification type" is the correct answer.References: SAP Help Portal - "Partner Determination in QM Notifications"; SAP S/4HANA QM Customizing Guide - "Notification Types".

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".

Dynamic modification levels in SAP QM determine the granularity at which inspection scope changes (e.g., reduced to full inspection) are applied in an inspection plan (transaction QP01):

Characteristic Level (A): Modification can occur at the individual characteristic level within an operation, allowing specific MICs to skip or intensify based on their quality history.

Inspection Lot Level (C): The entire inspection lot can be modified (e.g., skipped), based on the quality level for the material or combination (e.g., material/supplier).

Operation Level (D): Modification can apply to an operation, adjusting all characteristics within it based on performance (e.g., operation-specific skip).

Inspection Type Level (B): Inspection types define the process (e.g., 01 for GR), but dynamic modification is not set at this level; it’s tied to plans or lots.

Work Center (E): Work centers are execution locations, not a level for dynamic modification in QM.

Thus, "Characteristic level," "Inspection lot level," and "Operation level" are the correct answers.References: SAP Help Portal - "Dynamic Modification in Inspection Planning"; SAP S/4HANA QM Customizing Guide - "Dynamic Modification".

Blocking purchasing from a supplier for quality reasons is managed in:

Quality Info Record: Procurement (C): In the quality info record (transaction QI01), you can set the "Block" indicator or use a status profile (e.g., "Blocked") to prevent purchasing from a supplier for a specific material. This is the standard QM object for supplier-material quality control (SPRO > QM > Quality Inspection > Quality Info Record > Define Status).

Material (A): The material master can block overall procurement but not supplier-specific QM issues.

Business Partner (B): Blocking a supplier globally is possible (e.g., via MM06), but notmaterial-specific for quality reasons in QM.

Purchase Order Item (D): POs can’t enforce a quality block; they reflect existing restrictions.

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

Valuation modes (set in the sampling procedure, transaction QDV1) for qualitative characteristics include:

Attributive Inspection Nonconforming Units (A): Used for qualitative characteristics (e.g., pass/fail), counting nonconforming units against a sample to determine acceptance (e.g., ANSI/ASQ Z1.4).

Manual Valuation (C): Allows manual acceptance/rejection of qualitative results (e.g., "Good" or "Bad"), a flexible option for subjective assessments.

Variable Inspection s-Method (B): Applies to quantitative characteristics using statistical variance, not qualitative ones.

Mean Value Within Tolerance Range (D): Specific to quantitative data, not applicable to qualitative characteristics.

Thus, "Attributive inspection nonconforming units" and "Manual valuation" are the correct answers.References: SAP Help Portal - "Valuation Modes for Qualitative Characteristics"; SAP S/4HANA QM User Guide - "Sampling Procedures".

For an existing inspection lot tied to a delivery item (e.g., inspection type 10) with no results recorded:

Change the Actual Lot Quantity of the Current Inspection Lot (A): If the delivery item quantity changes (VL02N), the system updates the inspection lot’s quantity to match (status CRTD or INSP), as long as no results are recorded. This maintains synchronization without creating a new lot (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Inspection Lot Update).

Cancel and Create a New One (B): Cancellation and recreation occur only if the item is deleted, not just quantity-changed.

Create a New Inspection Lot (C): A new lot isn’t created for a quantity change; the existing lot adjusts.

Block the Current Inspection Lot (D): Blocking isn’t triggered by quantity changes in this scenario.

Thus, "Change the actual lot quantity of the current inspection lot" is the correct answer.References: SAP Help Portal - "Inspection Lot Updates"; SAP S/4HANA QM User Guide - "Delivery Integration".

Defects recording for inspection lots (e.g., transaction QE51N) requires specific Customizing:

Assign a Notification Type to an Inspection Type (A): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), linking a notification type (e.g., Q3) to an inspection type (e.g., 01) enables automatic or manual notification creation for defects, a mandatory step for integration.

Define the Report Type (D): The report type (SPRO > QM > Quality Inspection > Defects Recording > Define Report Types) must be defined to determine the defect recording layout and process, a required setting.

Activate the Workflow Template (B): Workflow is optional for notifications, not mandatory for defect recording.

Activate Reference to Existing Notifications (C): This is an optional enhancement, not a requirement.

Thus, "Assign a notification type to an inspection type" and "Define the report type" are the correct answers.References: SAP Help Portal - "Defects Recording Customizing"; SAP S/4HANA QM Customizing Guide - "Inspection Types".

The quality score in SAP S/4HANA Quality Management reflects the quality performance of an inspection lot, calculated at the usage decision (UD) stage. This score can influence subsequent processes, such as supplier evaluation. The procedure for its calculation is defined as follows:

Usage Decision Code (A): The quality score calculation procedure is assigned to the usage decision codes in Customizing (SPRO > Quality Management > Quality Inspection > Usage Decision > Define Quality Score Procedure). Each UD code (e.g., "Accepted," "Rejected") can have a specific score or formula linked to it, determining how the system computes the score based on inspection results. This is the correct and standard location for this setting.

Procurement Data in the Quality Management View of the Material Master (B): This area (transaction MM02, QM view) contains settings like inspection type or control keys but does not define the quality score calculation procedure.

Quality Info Record: Procurement (C): The quality info record (transaction QI01/QI02) manages supplier-specific QM settings (e.g., release status), but it does not configure the quality score calculation procedure.

Inspection Type Settings in the Material Master (D): Inspection type settings (e.g., 01 for goods receipt) in the material master activate QM processes but do not define the score calculation logic.

Thus, "Usage decision code" is the correct answer, as it directly ties the score calculation to the UD process.References: SAP Help Portal - "Quality Score and Usage Decision"; SAP S/4HANA QM Customizing Guide - "Usage Decision".

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".

To explore released APIs in SAP S/4HANA:

SAP Business Accelerator Hub (B): Formerly SAP API Business Hub, this is the official platform (https://api.sap.com ) to explore, test, and access released APIs for SAP S/4HANA, including QM-related APIs (e.g., Inspection Lot API). It’s the standard tool as of 2025.

SAP Application Interface Framework (A): AIF is for monitoring and managing interfaces, not exploring APIs.

SAP Integration Suite (C): This is for building integrations, not a primary API exploration tool.

Thus, "SAP Business Accelerator Hub" is the correct answer (single-choice context assumed).References: SAP Help Portal - "SAP Business Accelerator Hub"; SAP S/4HANA Developer Guide - "APIs".

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".

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".

Sample-drawing items in the sample-drawing procedure (transaction QPV2) define sample categories:

Reserve Sample (A): A standard category for samples retained for future testing (e.g., stability), maintained in the procedure.

Pooled Sample (B): Represents combined samples for collective testing, a defined category in sample management.

Primary Sample (D): The initial sample taken for immediate inspection, a core category in the procedure.

Initial Sample (C): Not a distinct category; overlaps with "Primary sample."

Sample for Storage Condition (E): Not a standard category; storage conditions are attributes, not sample types.

Thus, "Reserve sample," "Pooled sample," and "Primary sample" are the correct answers.References: SAP Help Portal - "Sample Management in QM"; SAP S/4HANA QM User Guide - "Sample-Drawing Procedure".

Completing a quality notification (e.g., transaction QM02, status NOCO) requires all dependent objects to be closed:

Open Tasks (B): Open tasks (e.g., "Investigate issue") prevent completion because they indicate unresolved actions. The system checks task status (e.g., TSOS) and blocks completion if any remain open (SPRO > QM > Quality Notifications > Define Status Profiles).

Open Defects (A): Defects are recorded in lots or notifications but don’t directly block completion unless tied to tasks.

Open Activities (C): Activities are logged events, not blockers unless configured as tasks.

Open Causes (D): Causes describe problems but don’t prevent completion unless linked to open tasks.

Thus, "Open tasks" is the correct answer.References: SAP Help Portal - "Notification Completion in QM"; SAP S/4HANA QM User Guide - "Status Management".

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".

The quality level in SAP QM tracks inspection history (e.g., for dynamic modification) and is updated at specific process steps:

Making the Usage Decision for an Inspection Lot (B): The usage decision (UD, transaction QA11) updates the quality level based on inspection results (e.g., accept/reject), determining future inspection scopes (e.g., skip or reduced). This is configured in SPRO > QM > Quality Inspection > Dynamic Modification.

Creating an Inspection Lot (C): Lot creation (e.g., for type 01 or 03) can update the quality level if it’s the first lot or if prior levels are reset, especially with dynamic modification rules active.

Creating a Quality Notification (A): Notifications document issues but don’t directly update the quality level unless tied to a UD.

Creating a Quality Certificate (D): Certificates report results but don’t influence the quality level.

Thus, "Making the usage decision for an inspection lot" and "Creating an inspection lot" are the correct answers.References: SAP Help Portal - "Quality Level in QM"; SAP S/4HANA QM User Guide - "Dynamic Modification".

Valuation modes in SAP QM (defined in the sampling procedure, transaction QDV1) determine how quantitative characteristics are evaluated:

Manual Valuation (B): Allows manual acceptance/rejection of quantitative results (e.g., based on measured values), a standard option for flexibility.

Attributive Inspection Number of Defects (D): Used for quantitative characteristics when counting defects (e.g., scratches), treating it as an attribute-like valuation for nonconformities.

Mean Value Within Tolerance Range (E): The system valuates based on whether the mean of recorded values falls within tolerances, a common quantitative mode.

Attributive Inspection Nonconforming Units (A): Specific to qualitative attributes, not quantitative measurements.

Valuation According to Characteristic Attribute Code (C): Applies to qualitative characteristics with predefined codes, not quantitative ones.

Thus, "Manual valuation," "Attributive inspection number of defects," and "Mean value within tolerance range" are the correct answers.References: SAP Help Portal - "Valuation Modes in QM"; SAP S/4HANA QM User Guide - "Sampling Procedures".