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

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

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

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

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

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

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

Inspection methods in SAP S/4HANA QM (transaction QK01) define how an inspection is performed and can be assigned to specific objects in inspection planning:

Master Inspection Characteristic (B): In the MIC master data (transaction QS21/QS23), you can assign an inspection method to specify the procedure (e.g., "Visual inspection"). This is a standard assignment to ensure consistency across plans.

Inspection Characteristic in an Operation of an Inspection Plan (D): Within an inspection plan (transaction QP01), you can assign an inspection method directly to a characteristic in an operation. This overrides or supplements the MIC’s method if needed, providing flexibility during planning.

Selected Set (A): Selected sets (transaction QS51) are for qualitative codes, not for assigning inspection methods.

Work Center (C): Work centers define where an inspection occurs but do not directly accept inspection method assignments in standard SAP QM.

Thus, "Master inspection characteristic" and "Inspection characteristic in an operation of an inspection plan" are the correct answers.References: SAP Help Portal - "Inspection Methods in QM"; SAP S/4HANA QM User Guide - "Inspection Planning".

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

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

A catalog profile in SAP S/4HANA QM defines a collection of code groups and codes from various catalog types (e.g., defects, usage decisions) for use in quality processes. It can be assigned at multiple levels:

In the Quality Management View of the Material Master (A): The catalog profile is assigned in the QM view of the material master (transaction MM01/MM02, field QMAT-PROF) at the plant level. This links it to inspection lots for that material, controlling defect recording or UD codes.

In the Customizing Settings for the Notification Type (B): In Customizing (SPRO > Quality Management > Quality Notifications > Notification Creation > Define Notification Types), you can assign a catalog profile to a notification type (e.g., Q1 for customer complaints). This determines the codes available during notification processing.

In the Customizing Settings for the Inspection Type (C): In Customizing (SPRO > Quality Management > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), a catalog profile can be linked to an inspection type (e.g., 01 for goods receipt). This governs the codes used in inspection lots of that type.

In the Master Inspection Characteristic (D): MICs (transaction QS21) use individual code groups or selected sets, not catalog profiles directly.

In the Customizing Settings for the Report Type (E): Report types (used in defect recording layouts) reference catalog profiles indirectly via other objects, not as a direct assignment.

Thus, the correct answers are "A, B, C," as these are the standard assignment points.References: SAP Help Portal - "Catalog Profiles in QM"; SAP S/4HANA QM Customizing Guide - "Notification and Inspection Types".

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

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

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

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

In SAP S/4HANA QM, outgoing quality certificates are generated for outbound deliveries (e.g., inspection type 10 or 11) to provide quality data to customers:

Delivery Item Level (C): Certificates are created at the delivery item level (transaction QC20) because each item in a delivery (VL01N) can have unique materials, batches, and inspection results requiring specific certificate data. The certificate profile (transaction QC01) is assigned to material/customer combinations, and the system generates certificates per item based on this linkage (SPRO > QM > Quality Certificates > Outgoing).

Material Level (A): Certificates aren’t created at the material master level; they’re tied to specific delivery transactions.

Shipping Point Level (B): Shipping points manage logistics, not certificate granularity.

Delivery Header Level (D): While the delivery header exists, certificates are item-specific to reflect individual material quality.

Thus, "Delivery item level" is the correct answer.References: SAP Help Portal - "Outgoing Quality Certificates"; SAP S/4HANA QM User Guide - "Certificate 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".

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

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

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

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

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

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

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

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

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

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

The 8D methodology in SAP QM is an internal problem-solving process triggered by quality issues:

Defects Recording for an Inspection Lot (A): Recording defects in an inspection lot (e.g., transaction QE51N) can initiate an 8D process via a linked notification (e.g., Q2), a standard starting point (SPRO > QM > Quality Notifications > 8D Methodology).

Item of a Quality Notification (C): The notification item (e.g., in QM01) directly supports 8D by documenting the problem (D1) and subsequent steps, a primary entry point.

Defect of Defect Category Generic Defect (B): "Generic Defect" isn’t a standard category; defect types are specific (e.g., production, supplier).

Defect of the Defect Category Production Defect (D): While relevant, it’s the act of recording (A) or notification (C) that starts 8D, not the category alone.

Thus, "Defects recording for an inspection lot" and "Item of a quality notification" are the correct answers.References: SAP Help Portal - "8D Methodology in QM"; SAP S/4HANA QM User Guide -"Problem Solving".