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

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

The SAP Fiori app "Record Inspection Results" (App ID: F2170) supports:

Add Unplanned Inspection Characteristics (B): Users can add unplanned characteristics (e.g., as complete or incomplete copies) to an operation during recording, enhancing flexibility.

Add Remarks to an Inspection Characteristic (C): The app allows adding comments or notes to characteristics, supporting documentation (visible in the characteristic details).

Assign Documents and Links to an Inspection Characteristic (D): Documents (e.g., via DMS) or links can be attached to characteristics in the app for reference.

Add Unplanned Inspection Operations (A): Operations are predefined in the plan; the app doesn’t support adding new operations.

Add Inspection Method to an Inspection Characteristic (E): Methods are assigned in planning, not dynamically in the app.

Thus, "Add unplanned inspection characteristics," "Add remarks to an inspection characteristic," and "Assign documents and links to an inspection characteristic" are the correct answers.References: SAP Help Portal - "Record Inspection Results Fiori App"; SAP S/4HANA QM User Guide - "Fiori Apps".

In SAP S/4HANA QM, an inspection plan group contains multiple inspection plans, each identified by a unique group counter. When an inspection lot is created (e.g., for goods receipt or production), the system must select the appropriate plan from the group:

Lot Size (D): The lot size of the inspection lot is the primary determinant for selecting an inspection plan. In the inspection plan header (transaction QP01/QP02), you define a "usage" and "lot size range" for each plan within the group. The system matches the inspection lot’s size to the applicable lot size range in the plan, ensuring the correct plan is chosen. This is standard behavior in QM (e.g., for inspection lot origin 01 or 03).

Sample Size (A): Sample size is determined by the sampling procedure within the inspection plan, not the other way around. It doesn’t select the plan.

Material Type (B): Material type influences material master settings but does not directlydetermine the inspection plan selection within a group.

Procurement Type of the Material (C): Procurement type (e.g., in-house vs. external) might influence the inspection type, but it doesn’t select between plans in a group.

Thus, "Lot size" is the correct answer, as it aligns with SAP’s logic for task list selection.References: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide - "Inspection Lot Creation".

In SAP S/4HANA QM, the action box in quality notifications (e.g., transaction QM02) triggersfollow-up actions, which can be documented as:

As Task (C): Activities from the action box (e.g., "Send email") can be created as tasks in the notification’s task tab, using catalog type 2 (Tasks). This is a standard option for actionable steps (SPRO > QM > Quality Notifications > Define Action Box).

As Activity (D): Activities can be logged in the activities tab (catalog type 8) to record completed actions (e.g., "Email sent"), documenting the execution of the action box entry.

As Cause (A): Causes (catalog type 5) describe why an issue occurred, not action box outcomes.

As Item (B): Items detail defects or problems, not action documentation.

Thus, "As task" and "As activity" are the correct answers.References: SAP Help Portal - "Action Box in Quality Notifications"; SAP S/4HANA QM User Guide - "Notification Processing".

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

Transferring inspection results to a batch characteristic in SAP QM (e.g., during results recording) requires linking QM and batch management (LO-BM). The prerequisite in inspection planning is:

Assignment of a Class Characteristic to a Master Inspection Characteristic (B): To transfer results, the MIC (transaction QS21) must be linked to a class characteristic (transaction CT04) used in the batch class (transaction CL01). This is configured in the MIC by assigning the class characteristic, enabling the system to update batch values (e.g., potency) from inspection results. This is a standard prerequisite (SPRO > Quality Management > Inspection Planning > Basic Data > MIC).

Assignment of a Class Characteristic to the Inspection Specification (A): Inspection specifications (e.g., material specs) don’t directly link to class characteristics for this purpose; the link is via MICs.

Assignment of an Inspection Characteristic to the Inspection Specification (C): This refers to planning setup but doesn’t address batch transfer specifically.

Assignment of an Inspection Method to the Inspection Characteristic (D): Methods guide execution, not batch value transfer.

Thus, "Assignment of a class characteristic to a master inspection characteristic" is the correct answer.References: SAP Help Portal - "Batch Management Integration with QM"; SAP S/4HANA QM User Guide - "Results Recording".

SAP Fiori apps in QM support usage decisions (UD):

Manage Usage Decisions (A): App ID F2171 is specifically designed for recording and managing usage decisions for inspection lots, a direct tool for this task.

Quality Technician Overview (B): App ID F2173 provides an overview and includes options to perform UD, supporting technicians in lot processing.

Quality Engineer Overview (C): App ID F2174 focuses on analytics and planning, not direct UD execution.

Manage Quality Level (D): App ID F2172 manages quality levels (e.g., skip lots), not UD itself.

Thus, "Manage Usage Decisions" and "Quality Technician Overview" are the correct answers.References: SAP Help Portal - "Fiori Apps for QM"; SAP S/4HANA QM User Guide - "Usage Decision Apps".

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

The catalog profile in the material master determines the set of codes available for quality processes like defect recording or usage decisions. Its assignment occurs at a specific organizational level:

Plant Level (D): In the material master (transaction MM01/MM02), the catalog profile is assigned in the Quality Management view under the "Inspection Setup" section (field QMAT-PROF). This is done at the plant level because QM processes (e.g., inspections) are plant-specific, and the catalog profile must align with the plant’s quality requirements. This is standard SAP behavior, ensuring flexibility across different plants for the same material.

Company Code Level (A): QM settings are not managed at the company code level, as this is a financial organizational unit unrelated to inspection processes.

Client Level (B): Client-level settings are too broad and apply globally, whereas catalog profiles need plant-specific granularity.

Business Area Level (C): Business areas are used for financial reporting, not QM organizational assignments.

Thus, "Plant level" is the correct answer, reflecting SAP’s organizational structure for QM data.References: SAP Help Portal - "Material Master in QM"; SAP S/4HANA QM User Guide - "QM View in Material Master".

Dependent characteristic specifications in SAP QM allow characteristics in an inspection plan to inherit values (e.g., tolerances) from a reference object. This is configured in the inspection plan (transaction QP01) under characteristic details:

Material and Customer (C): Used in sales-related inspections (e.g., inspection type 10), this reference allows characteristics to be tailored to customer-specific materialrequirements, pulling data from the material master or customer info records.

Material and Supplier (D): Common in procurement (e.g., inspection type 01), this reference links to quality info records or material master data, enabling supplier-specific specs for a material.

Material (E): The material alone can serve as a reference, pulling general specifications from the material master (e.g., QM view) or material specifications (transaction QS61), applicable across scenarios.

Material and Control Key (A): Control keys define operation behavior, not characteristic specifications, so this is not a valid reference.

Material and Work Center (B): Work centers are operation-specific and don’t store characteristic specs for reference in standard SAP.

Thus, "Material and customer," "Material and supplier," and "Material" are the correct answers.References: SAP Help Portal - "Dependent Characteristic Specifications"; SAP S/4HANA QM User Guide - "Inspection Planning".

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

Inspection points in SAP QM (configured in the inspection plan header, transaction QP01) allow multiple recordings within an inspection lot. Standard types include:

Inspection Point for Sample (A): Used for physical samples (e.g., per sample drawn), defined via inspection point type "1" (sample-based) in Customizing (SPRO > QM > Quality Planning > Inspection Planning > Define Inspection Point Types). Common in goods receipt or production.

Inspection Point for Functional Location (C): Type "3" supports inspections tied to functional locations (Plant Maintenance integration), used for equipment or facility checks within QM.

Inspection Point for Equipment (E): Type "2" links to equipment master records (PM), enabling equipment-specific inspection points in QM processes.

Inspection Point for Incoming Certificates (B): Certificates are managed separately (e.g., quality certificates in procurement), not as an inspection point type.

Inspection Point for Defects Recording (D): Defects are recorded within inspection points, but this is not a distinct type; it’s a function of existing types.

Thus, "Inspection point for sample," "Inspection point for functional location," and "Inspection point for equipment" are the correct answers.References: SAP Help Portal - "Inspection Points in QM"; SAP S/4HANA QM Customizing Guide - "Inspection Point Types".

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

Activity recording (e.g., time or cost) for inspection lots of origin 01 (Goods Receipt) requires:

Inspection Operations with Work Centers (B): Operations in the inspection plan (transaction QP01) must have work centers assigned, as these link to activity types (e.g., labor) for recording effort or costs during inspection (SPRO > QM > Quality Planning > Inspection Planning).

Inspection Lot with a QM Order (D): A QM order (e.g., created via Customizing or lot assignment) is required to capture activity data (e.g., via transaction QE51N or CO11N), linking costs to the inspection lot (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Inspection Types).

Inspection Specifications with Master Inspection Characteristics (A): MICs define what’s inspected but aren’t prerequisites for activity recording.

Inspection Specifications with Inspection Methods (C): Methods guide execution, not activity recording setup.

Thus, "Inspection operations with work centers" and "Inspection lot with a QM order" are the correct answers.References: SAP Help Portal - "Activity Recording in QM"; SAP S/4HANA QM User Guide - "Cost 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".

Inspection lots with origin 03 (Production) in SAP QM are triggered during production processes (e.g., order release or goods receipt). The task list types used are:

Routing (B): In production (PP), routings (transaction CA01) define operations and can include QM-relevant operations with inspection characteristics. For inspection lot origin 03, the system uses routings when QM is integrated with PP, especially for in-process inspections.

Inspection Plan (D): The inspection plan (transaction QP01) is the primary QM task list for origin 03, defining detailed inspection steps (e.g., characteristics, sampling) for production-related lots, such as goods receipt from production.

Master Recipe (A): Used in Process Industries (PP-PI) for recipes (transaction C201), not standard for discrete manufacturing origin 03 lots.

Equipment Task List (C): Relevant for Plant Maintenance (PM), not production QM lots.

Thus, "Routing" and "Inspection plan" are the correct answers for origin 03.References: SAP Help Portal - "Inspection Lot Origin 03"; SAP S/4HANA QM Customizing Guide - "Inspection Lot Creation".

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

SAP’s clean core principles (as per S/4HANA Cloud strategy) aim for a standardized, upgrade-friendly system:

Establish an Organizational Structure, Technical Foundation, and Transformation Methodology for Clean Core (A): This foundational principle ensures governance and methodology (e.g., SAP Activate) for clean core adoption.

Integrate Clean Core Practices in the End-to-End Value Process Chain (B): Embedding clean core into business processes ensures minimal customization and maximum standard use.

Establish Regular Housekeeping Tasks and Procedures (C): Ongoing maintenance (e.g.,data cleanup) keeps the system lean and standard-compliant.

Establish Release Management (D): While important, it’s a broader IT practice, not a core clean core principle.

Define Roles and Responsibilities as Part of a Process Transformation Office (E): Useful but not a primary SAP-defined clean core principle.

Thus, "A, B, C" are the correct answers.References: SAP Help Portal - "Clean Core Strategy"; SAP S/4HANA Cloud Best Practices - "Clean Core".

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

When inspection lots are created automatically for delivery items (inspection type 10) and the sample size isn’t calculated (status CRTD):

The System Cancels the Lot (B): If the delivery item is removed (e.g., via VL02N), the associated inspection lot is canceled automatically because its reference (the delivery item) no longer exists. The system updates the lot status to "CANC" (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Follow-Up Actions). This is standard behavior to maintain data consistency.

Posts a Usage Decision (A): UD (transaction QA11) requires sample calculation and results, which hasn’t occurred here.

Marks the Lot for Cancellation (C): The lot is fully canceled, not just marked, in this scenario.

Sends a Workflow Message (D): Workflow notifications require custom configuration andaren’t standard here.

Thus, "The system cancels the lot" is the correct answer.References: SAP Help Portal - "Inspection Lot Processing for Deliveries"; SAP S/4HANA QM User Guide - "Lot Cancellation".

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