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

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

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

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

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 clean core integrations in SAP S/4HANA (minimizing custom code):

SOAP (A): SAP recommends SOAP APIs for robust, secure integrations (e.g., enterprise services), supporting clean core by leveraging standard interfaces.

OData (D): OData is the preferred RESTful API type for S/4HANA, enabling flexible, standard integrations (e.g., via SAP Gateway), a cornerstone of clean core.

RFC (B): Remote Function Calls are legacy and less favored for clean core due to tight coupling.

IDoc (C): IDocs are traditional EDI-focused, not prioritized for modern clean core integrations.

Thus, "SOAP" and "OData" are the correct answers.References: SAP Help Portal - "Integration APIs in S/4HANA"; SAP S/4HANA Developer Guide - "Clean Core APIs".

The clean core dashboard in SAP S/4HANA monitors system adherence to clean core principles:

Customers Can Use the Dashboard in the Dev, Test, and Production Tenants (B): The dashboard is available across all system tenants (development, test, production) to assess clean core status universally.

It Can Be Accessed by Using SAP For Me (C): SAP For Me (customer portal) provides access to the clean core dashboard, a standard entry point as of 2025.

Customers Can Grant Access to Partners (A): Partner access isn’t a standard feature; it’s customer-controlled.

It Can Be Used in All SAP S/4HANA Cloud Editions (D): Primarily for Cloud Private Edition and Public Cloud, not guaranteed for all editions (e.g., on-premise specifics vary).

Thus, "Customers can use the dashboard in the dev, test, and production tenants" and "It can be accessed by using SAP For Me" are the correct answers.References: SAP Help Portal - "Clean Core Dashboard"; SAP S/4HANA Cloud User Guide - "SAP For Me".

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

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

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

Configuring a quality department release for supplier-material purchasing is managed in:

Quality Info Record: Procurement (D): The quality info record (transaction QI01) includes a "Release Required" indicator and status profile settings, allowing the quality department to approve or block purchasing from a supplier for a material. This is the standard object for supplier-specific QM controls (SPRO > QM > Quality Inspection > Quality Info Record).

Business Partner (A): Manages supplier data but not QM release requirements.

Material Master (B): Defines inspection types but not supplier-specific release by the quality department.

Inspection Plan (C): Specifies inspection details, not release processes.

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

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

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

For a quality notification with origin "Customer Complaint" (e.g., type Q1, transaction QM01):

Sold-to Party (B): The sold-to party (customer) is mandatory because it identifies who raised the complaint, a key field in the notification header linked to SD data (SPRO > QM > Quality Notifications > Notification Creation > Define Notification Types). Without this, the notification cannot be saved.

Interested Party (A): Optional, used for additional stakeholders.

Contact Person (C): Optional, specifies a customer contact but isn’t required.

Author (D): The creator (system user) is auto-filled, not a mandatory partner function.

Thus, "Sold-to party" is the correct answer.References: SAP Help Portal - "Customer Complaint Notifications"; SAP S/4HANA QM User Guide - "Partner Functions".

Certificate profiles for outgoing certificates (transaction QC01) define certificate content:

The Print Sequence of Characteristics (A): In the certificate profile, you set the order of characteristics (e.g., MICs or class characteristics) to appear on the certificate (SPRO > QM > Quality Certificates > Outgoing > Define Certificate Profiles).

The Print Layout (C): The profile links to a form (e.g., via SAPscript or Smart Forms), defining the layout of the printed certificate.

The Characteristics to be Inspected (B): Characteristics are selected, not inspected, within the profile; inspection occurs in lots.

The Inspection Operations to be Executed (D): Operations are part of plans, not certificate profiles.

Thus, "The print sequence of characteristics" and "The print layout" are the correct answers.References: SAP Help Portal - "Certificate Profiles for Outgoing Certificates"; SAP S/4HANA QM User Guide - "Quality Certificates".

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

The Engineering Workbench (EWB) in SAP S/4HANA is a powerful tool for managing task lists, including inspection plans, in a structured and efficient way. Working areas in the EWB define the focus or scope of what users can edit or view during inspection planning. These settings are mandatory to streamline workflows and ensure the correct level of detail is maintained:

Header (A): The header level refers to the overall inspection plan (e.g., plan group and group counter). A working area focused on the header allows users to manage high-level attributes like validity dates or usage. This is a standard focus in EWB (transaction CEWB).

Operation (B): Operations within an inspection plan define the steps or activities (e.g., "Measure dimension"). A working area focused on operations allows detailed planning at this level, including assigning control keys or work centers. This is another standard focus in EWB.

Inspection Characteristic (C): While inspection characteristics (e.g., specific measurements) are part of an operation, they are not a standalone focus for a working area inEWB. They are managed within the operation context, not as a separate working area.

Classification (D): Classification is used for categorizing objects (e.g., materials) but is not a focus for working areas in inspection planning within EWB. It’s unrelated to this context.

Thus, "Header" and "Operation" are the correct focuses, aligning with EWB’s structure for inspection planning.References: SAP Help Portal - "Engineering Workbench in QM"; SAP S/4HANA QM User Guide - "Inspection Planning with EWB".

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

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

Number of Samples (B): Defines how many samples (e.g., 5 units) are drawn per item, a key field in the item details.

Sample Categories (D): Specifies the type (e.g., primary, reserve, pooled) for each sample-drawing item, a mandatory attribute.

Confirmation of Sample Drawing (A): Confirmation occurs in sample management (e.g., QPR2), not stored in the procedure item.

Sample Drawing Based on Number of Containers (C): This is a rule in the procedure header, not an item-specific detail.

Thus, "Number of samples" and "Sample categories" are the correct answers.References: SAP Help Portal - "Sample-Drawing Procedure"; SAP S/4HANA QM User Guide - "Sample Management".

In SAP S/4HANA QM, quality notifications (e.g., transaction QM01) use catalog types to classify data in specific structure elements:

Defect Locations (A): Catalog type "A" (Defect Location) can be assigned to specify where a defect occurred (e.g., "Surface"), configured in the notification item (SPRO > QM > Quality Notifications > Catalogs).

Defect Types (D): Catalog type "9" (Defect Type) is assigned to classify the nature of the defect (e.g., "Scratch"), a standard field in the notification item.

Tasks (E): Catalog type "2" (Tasks) is used to define actions (e.g., "Repair") in the tasks tab of the notification.

Assigned Objects (B): Objects (e.g., material, batch) are referenced but don’t use catalog types directly.

Defect Causers (C): Causers (e.g., "Machine") use catalog type "5" (Causes), but this isn’t listed as "Defect causers" in standard terms; it’s typically "Causes."

Thus, "Defect locations," "Defect types," and "Tasks" are the correct answers based on standard structure elements.References: SAP Help Portal - "Catalogs in Quality Notifications"; SAP S/4HANA QM User Guide - "Notification Structure".

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

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

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