C_TS414_2023 Questions and Answers

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

To record inspection results for an inspection lot (e.g., transaction QE51N):

The Sample Determination Has Been Performed for the Inspection Lot (A): The lot must have its sample size calculated (status "SAMP" or "INSP") based on the sampling procedure, a prerequisite for result entry (SPRO > QM > Quality Inspection > Sample Management).

The Inspection Operations Are Released for Inspection Results Recording (B): Operations in the inspection plan must be released (status REL) to allow result recording, ensuring the lot is ready (transaction QP01).

The Inspection Methods Are Part of the Inspection Specifications (C): Methods guide execution but aren’t a condition for recording.

The Inspection Specifications Have Been Assigned to the Inspection Lot (D): Specs (e.g., material specs) are linked implicitly via the plan, not a separate condition.

Thus, "The sample determination has been performed for the inspection lot" and "The inspection operations are released for inspection results recording" are the correct answers.References: SAP Help Portal - "Prerequisites for Results Recording"; SAP S/4HANA QM User Guide - "Inspection Lot 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 quantitative characteristics in results recording (transaction QE51N), control indicators in the MIC (transaction QS23) define how results are confirmed:

Summarized Recording (B): Records a single aggregated value (e.g., average) for the sample, a standard option for efficiency.

Classed Recording (C): Results are grouped into classes (e.g., ranges like 10-15 mm), common for statistical analysis.

Single Result (D): Each individual result is recorded separately, ideal for detailed tracking.

Mean Value and Standard Deviation (A): These are calculated outputs, not control indicators for recording type.

Mean Value (E): This is a result, not a control indicator for how data is entered.

Thus, "Summarized recording," "Classed recording," and "Single result" are the correct answers.References: SAP Help Portal - "Results Recording for Quantitative Characteristics"; SAP S/4HANA QM User Guide - "Control Indicators".

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

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

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

Digital signatures in SAP S/4HANA QM (configured via SPRO > Cross-Application Components > Digital Signature) ensure auditability and compliance in critical processes:

Recording the Usage Decision for an Inspection Lot (B): The usage decision (transaction QA11) can require a digital signature to confirm stock disposition, a common regulatory requirement (e.g., in pharmaceuticals).

Valuation of an Inspection Result (C): Valuating results (e.g., accept/reject in QE51N) can mandate a signature, especially for critical characteristics, as set in the MIC or inspection type settings.

Manual Confirmation of a Physical Sample Drawing (D): Confirming sample drawing (transaction QPR2) can require a signature to validate the physical process, configurable in sample management.

Assignment of Inspection Specification (A): Assigning specs (e.g., in QP01) is a planning step, not typically requiring a signature.

Defect Recording in Inspection Lot (E): Defect entry (e.g., QF01) may trigger notifications but doesn’t standardly require a signature unless custom-configured.

Thus, "B, C, D" are the correct answers.References: SAP Help Portal - "Digital Signatures in QM"; SAP S/4HANA QM Customizing Guide - "Signature Strategy".

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

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

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

During results recording (e.g., transaction QE51N), additional characteristics can be added to an operation:

Master Inspection Characteristics as Complete Copy Model (B): MICs (transaction QS21) can be added as a complete copy, inheriting all attributes (e.g., tolerances, sampling) for immediate use in the lot.

Master Inspection Characteristics as Incomplete Copy Model (C): MICs can be added as an incomplete copy, allowing customization (e.g., adjusting tolerances) during recording, a flexible option in SAP QM.

Master Inspection Characteristics as Reference Characteristic (A): Reference MICs are linked for reuse but not added anew during recording; they’re predefined in the plan.

Class Characteristics from the Classification System (D): Class characteristics (transaction CT04) are for batch classification, not inspection recording.

Thus, "Master inspection characteristics as complete copy model" and "Master inspection characteristics as incomplete copy model" are the correct answers.References: SAP Help Portal - "Adding Characteristics in Results Recording"; SAP S/4HANA QM User Guide - "Inspection Results".

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