SAP C_TS414_2023 SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Quality Management Exam Practice Test

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

Automatic goods movement during usage decision (UD, transaction QA11) for stock-relevant lots (e.g., type 01) is configured in:

In the Inspection Type (D): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), the inspection type (e.g., 01) has a "Automatic UD" and "Stock Posting" setting. Activating this links UD codes to movement types (e.g., 321 for quality to unrestricted), enabling automatic stock updates.

Codes in the Selected Set (A): Selected sets (transaction QS51) define UD codes but don’t control movements.

Codes in the Code Group (B): Code groups (transaction QS41) are for catalog organization, not stock movement settings.

Movement Type (C): Movement types (e.g., 321) are used but assigned via inspection type settings, not directly configured there.

Thus, "In the inspection type" is the correct answer.References: SAP Help Portal - "Automatic Stock Posting in QM"; SAP S/4HANA QM Customizing Guide - "Inspection Types".

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

To record quality certificate receipt independently from goods receipt (GR) in SAP S/4HANA QM, the system must decouple these processes:

Control of Certificate Receipt in the Quality Info Record: Procurement (B): In the quality info record (transaction QI01), the "Certificate Control" settings (e.g., "Certificate Required" and "Check at GR" unchecked) allow certificate receipt to be recorded separately (e.g., via transaction QC55) before or after GR. This is the standard setting to achieve independence, ensuring the GR posts to blocked stock or proceeds without certificate enforcement at that step (SPRO > QM > Quality Certificates > Procurement).

Assignment of a Status Profile in the Certificate Profiles (A): Certificate profiles (transaction QC01) define outgoing certificates, not incoming certificate receipt processes.

Indicator for Enhanced Certificate Processing in the Certificate Type (C): The certificate type (SPRO > QM > Quality Certificates > Define Certificate Types) has an "Enhanced Processing" indicator, but it relates to certificate creation, not independent receipt recording.

Assignment of a Status Profile in the Certificate Type (D): Status profiles in certificate types manage certificate statuses, not GR independence.

Thus, "Control of certificate receipt in the quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Certificate Receipt in Procurement"; SAP S/4HANA QM Customizing Guide - "Quality Certificates".

In SAP S/4HANA QM, combining code groups from multiple catalog types (e.g., defects, causes) into a single object is necessary for processes like defect recording or notifications:

Catalog Profile (A): The catalog profile (maintained via transaction QPCD or Customizing) is designed to group code groups from different catalog types (e.g., defect types, causes, activities) into a single entity. It’s assigned to objects like material masters or notification types, enabling consistent use of codes across processes like defect recording (e.g., in inspection lots) or notification processing (e.g., QN01). This is the standard object for this purpose.

Report Type (B): Report types (SPRO > QM > Quality Inspection > Define Report Types) define the layout of defect recording but do not combine code groups from catalogs; they reference catalog profiles instead.

Selected Set (C): A selected set (transaction QS51) is a subset of codes from one catalog type, not a combination across multiple types.

Confirmation Profile (D): Confirmation profiles are used in production (e.g., PP) for operation confirmations, not QM catalog management.

Thus, "Catalog profile" is the correct answer, as it’s the dedicated object for combining codes from multiple catalogs.References: SAP Help Portal - "Catalog Profiles in QM"; SAP S/4HANA QM Customizing Guide -"Catalog Management".

For inspection type 01 (Goods Receipt) with a missing mandatory certificate (set in the quality info record, transaction QI01):

Recording of Inspection Results (B): The inspection lot is created (status CRTD), and you can record results (transaction QE51N) even without the certificate, as this step precedes the usage decision (UD).

Recording of Defects (D): Defects can be recorded (e.g., via QE51N or QF01) during inspection, regardless of certificate status, to document issues found.

Confirmation of Certificate Receipt After Usage Decision (A): Certificate receipt must be confirmed before UD if mandatory (controlled by the "Certificate Check" setting); this option is not possible post-UD.

Posting of the Usage Decision (C): UD (transaction QA11) is blocked if the certificate is mandatory and missing, as the system sets a status (e.g., CCRQ) until resolved.

Thus, "Recording of inspection results" and "Recording of defects" are the correct answers.References: SAP Help Portal - "Certificate Processing in Procurement"; SAP S/4HANA QM User Guide - "Inspection Lot Processing".

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

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

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

The response profile (transaction QMSM) in QM notifications defines automatic tasks via the "Determine Tasks" function:

Task Code Group (A): Specifies the group (e.g., from catalog type 2) containing task codes, defining the task category (SPRO > QM > Quality Notifications > Response Profile).

Task Code (C): The specific code within the group (e.g., "Investigate") is defined, detailing the task to be created.

Cause Code (B): Cause codes (catalog type 5) are for problem analysis, not task definition.

Notification Type (D): The type is set at the notification level, not in the response profile.

Thus, "Task code group" and "Task code" are the correct answers.References: SAP Help Portal - "Response Profiles in QM"; SAP S/4HANA QM User Guide - "Notification Tasks".

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

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

Defects recording in SAP QM (e.g., transaction QE51N) during production inspections uses specific elements to define its layout and behavior:

Report Type (A): Defined in Customizing (SPRO > QM > Quality Inspection > Defects Recording > Define Report Types), the report type determines the structure and fields available for defect entry (e.g., simplified or detailed layout).

Confirmation Profile (C): This governs how defects are confirmed or structured during recording, especially in production-integrated scenarios (e.g., operation confirmation), influencing the defect entry screen.

Catalog Profile (D): Assigned to the material or inspection type, the catalog profile (transaction QPCD) specifies the code groups and codes available for defect classification, shaping the recording layout.

Partner Profile (B): Used in EDI or external integrations, not for defect recording layout in QM.

Status Profile (E): Manages statuses (e.g., of notifications), not the defect recording interface.

Thus, "Report type," "Confirmation profile," and "Catalog profile" are the correct answers.References: SAP Help Portal - "Defects Recording in QM"; SAP S/4HANA QM User Guide - "Inspection Results".

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

Automatic usage decision (UD) in SAP QM (configured via transaction QA16) requires:

No Inspection Characteristic Was Rejected (A): All characteristics must be accepted (e.g., valuation "A") for the system to proceed automatically (SPRO > QM > Quality Inspection > Usage Decision > Define Automatic UD).

All Required Inspection Characteristics Were Confirmed and Completed (B): Required characteristics (marked in the plan) must have results recorded and valuated (status RREC).

There Are No Defect Records for the Inspection Lot (E): Open defects block automatic UD, ensuring quality issues are resolved first.

Activity Recording Finished for All Operations (C): Activity confirmation (e.g., time) is optional and not a prerequisite.

All Inspection Operations Completed (D): Operations completion isn’t mandatory; characteristic completion is sufficient.

Thus, "A, B, E" are the correct answers.References: SAP Help Portal - "Automatic Usage Decision"; SAP S/4HANA QM User Guide - "UD Processing".

A sampling procedure in SAP S/4HANA QM (transaction QDV1) defines how samples are calculated and valuated for an inspection lot. Mandatory assignments ensure the system can determine and process the sample:

Sampling Type (C): This is a required field in the sampling procedure header. It specifies how the sample size is determined (e.g., fixed sample, percentage, sampling scheme). Without it, the system cannot calculate the sample size (e.g., "100% inspection" or "Attribute sampling").

Valuation Mode (D): Also mandatory, this defines how inspection results are evaluated (e.g., "Manual valuation," "Attribute inspection nonconforming units"). It’s assigned in the sampling procedure and ensures consistent acceptance/rejection rules.

Inspection Severity (A): This is optional and applies only to sampling schemes (e.g., normal, tightened), not all sampling types.

Unit of Measure (B): The unit of measure is inherited from the material or characteristic, not a mandatory assignment in the sampling procedure itself.

Thus, "Sampling type" and "Valuation mode" are the correct answers, as they are essential components of every sampling procedure.References: SAP Help Portal - "Sampling Procedures in QM"; SAP S/4HANA QM Customizing Guide - "Sample Management".

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

When creating a supplier complaint notification (e.g., Q2) from a goods receipt material document (transaction QM01):

Purchasing Document Number and Item (A): The PO number and item are copied from the material document (linked via MIGO), providing the procurement context.

Material Number (B): The material number is transferred to identify the affected product.

Inspection Lot Number (C): If an inspection lot (e.g., type 01) was created during GR, its number is copied to link quality data (SPRO > QM > Quality Notifications > Integration with Inspection Lots).

Reference Quantity and Unit (D): Quantity is referenced but not automatically copied to the notification header/item in standard SAP.

Advanced Shipping Number (E): ASN is logistics-related (e.g., inbound delivery), not typically copied from a material document.

Thus, "Purchasing document number and item," "Material number," and "Inspection lot number" are the correct answers.References: SAP Help Portal - "Notification Creation from Goods Receipt"; SAP S/4HANA QM User Guide - "Supplier Complaints".

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

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

Dynamic modification in SAP S/4HANA QM allows the system to adjust inspection scopes (e.g., skip lots, reduced inspection) based on quality performance. These criteria are defined in the inspection plan (transaction QP01) or Quality Level settings and determine when modification occurs:

Material and Supplier (A): This is a standard dynamic modification criterion (e.g., for inspection type 01 - Goods Receipt). It tracks quality history for a material-supplier combination, commonly used in procurement scenarios (SPRO > Quality Management > Quality Inspection > Dynamic Modification).

Material and Customer (D): Used in sales or production scenarios (e.g., inspection type 10 - Delivery), this criterion adjusts inspections based on material-customer quality history, ensuring customer-specific requirements are met.

Material (E): A standalone material criterion is valid across multiple inspection types (e.g., 03 - Production), allowing modification based solely on the material’s quality history, regardless of supplier or customer.

Material and Work Center (B): Work centers are linked to operations, not directly to dynamic modification criteria in standard SAP QM. This is not a predefined option.

Material and Equipment (C): Equipment is relevant for plant maintenance (PM), not a standard QM dynamic modification criterion for inspection plans.

Thus, "Material and supplier," "Material and customer," and "Material" are the correct answers, reflecting standard SAP functionality.References: SAP Help Portal - "Dynamic Modification in QM"; SAP S/4HANA QM Customizing Guide - "Dynamic Modification Rules".

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

When creating an operation in an inspection plan (transaction QP01/QP02), certain fields aremandatory to define the operation’s purpose and execution in SAP S/4HANA QM:

Control Key (B): The control key is a mandatory field in the inspection plan operation. It determines the operation’s behavior, such as whether inspection characteristics are required, whether it’s a milestone, or if it triggers specific actions (e.g., QM01 for quality inspection). Defined in Customizing (SPRO > Quality Management > Quality Planning > Inspection Planning > Define Control Keys), it ensures the system knows how to process the operation. Without it, the operation cannot be saved.

Activity Type (A): This is relevant for cost accounting (e.g., in Production Planning or QM orders) but is not mandatory in the inspection plan operation itself.

Work Center (C): The work center (e.g., a test station) is optional in QM inspection plans unless specified by the control key. It’s common but not universally required.

Standard Text Key (D): This provides predefined descriptions for operations but is optional and not required to create an operation.

Thus, "Control key" is the correct answer, as it’s the only mandatory assignment in standard SAP QM for inspection plan operations.References: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide - "Operations in Inspection Plans".

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