C_TS414_2023 Sample Questions Answers

Status profiles in SAP QM (defined in SPRO > QM > Quality Notifications > Status Management) control the lifecycle of notification elements:

Header (B): The notification header (e.g., transaction QM01) can have a status profile assigned to manage overall statuses (e.g., "Open," "Completed").

Tasks (D): Tasks within the notification (e.g., "Investigate") can have their own status profile to track individual task progress (e.g., "Released," "Completed").

Activities (A): Activities log events but don’t support status profiles directly.

Items (C): Items (defect details) use catalog types, not status profiles.

Thus, "Header" and "Tasks" are the correct answers.References: SAP Help Portal - "Status Profiles in QM Notifications"; SAP S/4HANA QM User Guide - "Notification Status".

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

Defect recording in SAP QM (e.g., transaction QF01 or QE51N) is tied to specific objects:

Inspection Lots (A): Defects are recorded directly against an inspection lot (e.g., during results recording), linking to the lot’s context (e.g., material, supplier).

Inspection Characteristics (B): Within an inspection lot, defects can be recorded at thecharacteristic level (e.g., a specific MIC fails), allowing detailed defect analysis.

Business Partners (C): Defects aren’t recorded against suppliers/customers directly; they’re tied to lots or notifications.

Quality Certificates (D): Certificates document results, not serve as objects for defect recording.

Thus, "Inspection lots" and "Inspection characteristics" are the correct answers.References: SAP Help Portal - "Defects Recording in QM"; SAP S/4HANA QM User Guide - "Defect Management".

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

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

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 level in SAP QM tracks inspection history (e.g., for dynamic modification) and is updated at specific process steps:

Making the Usage Decision for an Inspection Lot (B): The usage decision (UD, transaction QA11) updates the quality level based on inspection results (e.g., accept/reject), determining future inspection scopes (e.g., skip or reduced). This is configured in SPRO > QM > Quality Inspection > Dynamic Modification.

Creating an Inspection Lot (C): Lot creation (e.g., for type 01 or 03) can update the quality level if it’s the first lot or if prior levels are reset, especially with dynamic modification rules active.

Creating a Quality Notification (A): Notifications document issues but don’t directly update the quality level unless tied to a UD.

Creating a Quality Certificate (D): Certificates report results but don’t influence the quality level.

Thus, "Making the usage decision for an inspection lot" and "Creating an inspection lot" are the correct answers.References: SAP Help Portal - "Quality Level in QM"; SAP S/4HANA QM User Guide - "Dynamic Modification".

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

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 a customer complaint notification (type Q1, transaction QM01), standard reference documents include:

Delivery (A): Outbound delivery documents (e.g., from VL01N) are commonly referenced, linking the complaint to a shipped item (SPRO > QM > Quality Notifications > Notification Creation).

Sales Order (D): Sales orders (e.g., from VA01) can be referenced to trace the complaint back to the original customer order.

Quotation (B): Quotations are pre-sales documents and not standard references for QM notifications.

Material Document (C): Material documents (e.g., GR) are procurement-related, not typical for customer complaints.

Thus, "Delivery" and "Sales order" are the correct answers.References: SAP Help Portal - "Reference Documents in QM Notifications"; SAP S/4HANA QM User Guide - "Customer Complaints".

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

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

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

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

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

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

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

Inspection points in SAP QM (configured in the inspection plan, transaction QP01) allow multiple result recordings over time or events for a single lot:

Goods Receipt Inspections (A): For inspection type 01, inspection points (e.g., per container) can be used to record results for partial deliveries or batches, common in procurement.

Inspections with Samples (D): Inspection points support sample-based inspections (e.g., physical samples), allowing results per sample point, as defined in the sampling procedure.

In-process Inspections During Production (E): For inspection type 03, inspection points (e.g., per shift or operation) enable ongoing checks during production, a standard use case.

Inspections for Quality Notifications (B): Notifications (e.g., QN01) record defects or issues but don’t use inspection points, which are lot-specific.

Inspections for Warehouse Defects (C): Warehouse defects (e.g., stock quality issues) typically use stock transfer inspections (type 08), not inspection points.

Thus, "A, D, E" are the correct answers.References: SAP Help Portal - "Inspection Points in QM"; SAP S/4HANA QM User Guide - "Inspection Scenarios".

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

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

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

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

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

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

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

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