C_TS414_2023 Practice Exam Questions with Answers SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Quality Management Certification

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

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

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

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

The quality info record: Procurement (transaction QI01/QI02) manages supplier-material relationships and can impose release restrictions:

To a Quantity, by Entering a Release Quantity (A): In the quality info record, you can set a "Release Quantity" field to limit the approved purchase quantity (e.g., 100 units). Once exceeded, further approval is needed, a standard feature.

Until the Supplier Has Provided a Quality Certificate, by Entering a Certificate Type (B): You can specify a certificate type (e.g., "ISO 9001") in the "Certificate" field, blocking release until the supplier provides it, verified during goods receipt.

To a Period of Time, by Supplying a Release Date (C): While validity dates exist, they define the record’s lifespan, not a specific release restriction mechanism.

Until the Supplier Quality Score is Better Than a Threshold (D): Quality scores influence supplier evaluation but aren’t directly set as a release condition in the info record.

Thus, "A" and "B" are the correct answers, reflecting standard SAP QM functionality.References: SAP Help Portal - "Quality Info Record: Procurement"; SAP S/4HANA QM User Guide - "Supplier Release".

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

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

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

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

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

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

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

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

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

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

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

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

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

When a quality certificate is mandatory (set in the quality info record, transaction QI01) but no GR inspection lot is created (inspection type 01 inactive in the material master), the system handles the missing certificate as follows:

The Goods Receipt is Posted to Blocked Stock (B): If the certificate is required (e.g., "Certificate Check" active in QI01) and not received (transaction QC55), the GR (transaction MIGO) posts the material to blocked stock (movement type 103/105 process). This is standard behavior to prevent unrestricted use until the certificate is confirmed, even without an inspection lot (SPRO > QM > Quality Certificates > Procurement > DefineControl Keys).

Unrestricted Use Stock (A): This would occur only if no certificate check was enforced, contradicting the premise.

Quality Notification Created Automatically (C): Notifications require manual creation or specific Customizing (e.g., defect recording), not automatic generation here.

Missing Certificate Escalated (D): Escalation is not a standard SAP term or process in this context; it implies custom workflow not present in standard QM.

Thus, "The goods receipt is posted to blocked stock" is the correct answer.References: SAP Help Portal - "Certificate Processing at Goods Receipt"; SAP S/4HANA QM User Guide - "Stock Posting".

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

The SAP Fiori app "Record Inspection Results" (App ID: F2170) in SAP S/4HANA QM supports specific result recording types for inspection lots:

Recording of Single Inspection Results (B): This allows entering individual values for quantitative or qualitative characteristics (e.g., one value per sample), a standard feature in the app for detailed recording.

Summarized Inspection Results Recording (D): The app supports entering a single aggregated value (e.g., average) for a characteristic, ideal for summarized quantitative data, as configured in the MIC control indicators.

Classed Inspection Results Recording (A): Classed recording (grouping results into ranges) is supported in classic transactions (e.g., QE51N) but not explicitly in the standard Fiori app’s functionality.

Results Recording for Inspection Points (C): While inspection points are supported in QM, the Fiori app focuses on lot-level recording and doesn’t emphasize point-specific recording in its standard scope.

Thus, "Recording of single inspection results" and "Summarized inspection results recording" are the correct answers.References: SAP Help Portal - "Record Inspection Results Fiori App"; SAP S/4HANA QM User Guide - "Fiori Apps in QM".

For clean core integrations in SAP S/4HANA (minimizing custom code):

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

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

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

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

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

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

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