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

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, inspection lots for production (inspection lot origin 03 or 04) are triggered by specific events in the production process:

Production Order Release (A): Releasing a production order (transaction CO02, status REL) can create an inspection lot of origin 03 for in-process inspections if QM is active in the material master (inspection type 03) and the routing includes QM operations. This is a standard trigger in discrete manufacturing.

Goods Movements for Production Order (D): Goods receipt from a production order (e.g., transaction MIGO, movement type 101) triggers an inspection lot of origin 04 if inspection type 04 is active in the material master. This is common for post-production quality checks.

Production Order Creation (B): Creating an order (status CRTD) does not typically trigger an inspection lot; it requires release or goods movement to activate QM.

Available-to-Promise (ATP) Check (C): ATP checks availability in sales or production planning but is unrelated to QM inspection lot creation.

Thus, "Production order release" and "Goods movements for production order" are the correct answers.References: SAP Help Portal - "Inspection Lot Origins 03 and 04"; SAP S/4HANA QM User Guide - "Production Integration".

In SAP S/4HANA Quality Management, catalogs are used to manage predefined codes for qualitative data recording, and selected sets are subsets of code groups used in specific contexts (e.g., inspection plans). Valuation of codes (assigning values like "Accepted" or "Rejected") is mandatory for certain catalog types to ensure consistent processing:

Usage Decisions (A): Catalog type "3" (Usage Decisions) requires valuation in the selected set because the usage decision (UD) determines the stock posting and quality score. In Customizing (SPRO > Quality Management > Quality Inspection > Usage Decision > Define Selected Sets), codes like "A" (Accepted) or "R" (Rejected) must be valuated to trigger specific system actions (e.g., goods movement). This is mandatory for inspection lot completion.

Defect Types (C): Catalog type "9" (Defects) requires valuation in the selected set when used in defect recording (e.g., transaction QS51). Defect codes (e.g., "Scratch," "Dent") need valuation to classify severity or trigger follow-up actions like notifications, making it mandatory in quality processes.

Characteristic Attributes (B): Catalog type "1" (Characteristic Attributes) is used for qualitative MICs. Valuation is optional and depends on the characteristic’s settings (e.g., "Good/Bad"), not mandatory in the selected set itself.

Activities (QM) (D): Catalog type "5" (Activities) is used for tasks or follow-ups in notifications. Valuation is not mandatory in the selected set, as activities are typically descriptive rather than evaluative.

Thus, "Usage decisions" and "Defect types" are the correct answers, as valuation is a required step in their respective processes.References: SAP Help Portal - "Catalogs and Selected Sets in QM"; SAP S/4HANA QM Customizing Guide - "Catalog Management".

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

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

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

In SAP S/4HANA QM, the Document Management System (DMS) supports linking document types to master data objects for reference:

Quality Assurance Agreements to Quality Info Records: Procurement (A): In the quality info record (transaction QI01), you can assign a DMS document type (e.g., QAA) for quality assurance agreements with suppliers. This is standard for procurement QM (SPRO > QM > Environment > Document Management).

Technical Delivery Terms to Materials (C): Technical delivery terms (e.g., shipping instructions) can be linked to the material master via DMS (transaction MM01/MM02), typically in the Basic Data or QM view, as a standard feature.

Quality Assurance Agreements to Materials (B): QA agreements are supplier-specific and linked to quality info records, not directly to materials in standard SAP.

Technical Delivery Terms to Quality Info Records: Procurement (D): Delivery terms are material-specific, not typically assigned to quality info records in standard configuration.

Thus, "A" and "C" are the correct answers, reflecting SAP standard assignments.References: SAP Help Portal - "DMS in Quality Management"; SAP S/4HANA QM Configuration Guide - "Document Types".

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

Source inspections (inspection type 0101) occur at the supplier’s site before GR:

Quality Info Record: Procurement (B): In the quality info record (transaction QI01), you activate source inspection by selecting the "Source Inspection" indicator and linking it to inspection type 0101 (predefined in Customizing). This triggers an inspection lot before delivery (SPRO > QM > Quality Inspection > Source Inspection).

Business Partner (A): Supplier data doesn’t control inspection location.

Purchase Order Item (C): POs can trigger the lot but don’t activate source inspection settings.

Material Master (D): The QM view activates inspection types (e.g., 0101), but the supplier-specific setting is in the quality info record.

Thus, "Quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Source Inspection in QM"; SAP S/4HANA QM Customizing Guide - "Inspection Types".

To explore released APIs in SAP S/4HANA:

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

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

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

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

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

Material specifications in SAP QM (transaction QS61) define inspection requirements directly in the material master, independent of task lists. They integrate specific QM basic data:

Master Inspection Characteristics (A): MICs are the core of material specifications, defining what is inspected (e.g., length, pH). They are assigned to the material spec to set tolerances or qualitative codes.

Sampling Procedures (C): These determine the sample size for the material spec’s characteristics (e.g., fixed sample of 5). They are assigned to MICs within the material specification.

Inspection Methods (E): Inspection methods (e.g., "Visual check") can be linked to MICs in the material spec to specify how the inspection is performed.

Dynamic Modification Rule (B): This governs inspection scope changes (e.g., skip lots) and is assigned to inspection types or plans, not material specs directly.

Selected Set (D): Selected sets are used for qualitative valuations (e.g., UD codes) but are not directly assigned to material specs; they link via MICs instead.

Thus, "Master inspection characteristics," "Sampling procedures," and "Inspection methods" are the correct answers.References: SAP Help Portal - "Material Specifications in QM"; SAP S/4HANA QM User Guide - "Basic Data".

Outbound quality inspections (e.g., inspection type 10) in Sales and Distribution (SD) occur for deliveries:

The Inspection is Skipped (A): If no inspection type (e.g., 10) is active in the material master or quality info record: SD, the inspection can be skipped, a valid option in standard SAP.

The Inspection Occurs Before the Goods Issue is Posted (D): For inspection type 10, the inspection lot is created with the delivery (before goods issue, transaction VL02N), allowing inspection before stock is moved (standard process).

After Release of the Sales Order (B): Inspections are tied to deliveries, not sales order release.

After Creation of the Sales Order (C): Inspection lots are not created at SO creation; they require a delivery.

Thus, "The inspection is skipped" and "The inspection occurs before the goods issue is posted" are the correct answers.References: SAP Help Portal - "Outbound Inspections in QM"; SAP S/4HANA QM User Guide - "SD Integration".

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

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

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

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

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

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

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

Standard SAP Fiori apps (e.g., "Record Defects," App ID F2175) support defect categories tied to QM processes:

Supplier Defect (A): Linked to procurement (e.g., inspection type 01), recordable via apps for supplier-related issues.

Production Defect (B): Tied to production lots (e.g., type 03/04), a standard category in Fiori defect recording.

Customer Defect (D): Associated with customer complaints (e.g., notification type Q1), supported in apps.

Generic Defect (C): Not a specific standard category; defects are context-specific.

Warehouse Defect (E): Typically stock-related (type 08), not a distinct Fiori category.

Thus, "Supplier defect," "Production defect," and "Customer defect" are the correct answers.References: SAP Help Portal - "Defect Recording Fiori Apps"; SAP S/4HANA QM User Guide - "Defect Categories".

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

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

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