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

Control charts in SAP QM (e.g., during results recording, transaction QGC1) monitor characteristic values against statistical limits. Rejection is based on:

Action Limit (D): The action limit (upper/lower control limit, UCL/LCL) is the threshold beyond which a characteristic is rejected, indicating a process is out of control. In Customizing (SPRO > Quality Management > Quality Inspection > SPC > Define Control Charts), exceeding this limit triggers rejection or further action (e.g., defect recording).

Warning Limit (A): Warning limits (e.g., 2-sigma) signal potential issues but don’t automatically reject the characteristic; they prompt monitoring, not rejection.

Moving Average Line (B): This tracks trends but isn’t a rejection threshold.

Center Line (C): The center line (mean) is a reference, not a limit for rejection.

Thus, "Action limit" is the correct answer, aligning with SPC rejection rules.References: SAP Help Portal - "Statistical Process Control in QM"; SAP S/4HANA QM User Guide - "Control Charts".

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

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

Dependent characteristic specifications in SAP QM allow characteristics in an inspection plan to inherit values (e.g., tolerances) from a reference object. This is configured in the inspection plan (transaction QP01) under characteristic details:

Material and Customer (C): Used in sales-related inspections (e.g., inspection type 10), this reference allows characteristics to be tailored to customer-specific materialrequirements, pulling data from the material master or customer info records.

Material and Supplier (D): Common in procurement (e.g., inspection type 01), this reference links to quality info records or material master data, enabling supplier-specific specs for a material.

Material (E): The material alone can serve as a reference, pulling general specifications from the material master (e.g., QM view) or material specifications (transaction QS61), applicable across scenarios.

Material and Control Key (A): Control keys define operation behavior, not characteristic specifications, so this is not a valid reference.

Material and Work Center (B): Work centers are operation-specific and don’t store characteristic specs for reference in standard SAP.

Thus, "Material and customer," "Material and supplier," and "Material" are the correct answers.References: SAP Help Portal - "Dependent Characteristic Specifications"; SAP S/4HANA QM User Guide - "Inspection Planning".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Valuation modes (set in the sampling procedure, transaction QDV1) for qualitative characteristics include:

Attributive Inspection Nonconforming Units (A): Used for qualitative characteristics (e.g., pass/fail), counting nonconforming units against a sample to determine acceptance (e.g., ANSI/ASQ Z1.4).

Manual Valuation (C): Allows manual acceptance/rejection of qualitative results (e.g., "Good" or "Bad"), a flexible option for subjective assessments.

Variable Inspection s-Method (B): Applies to quantitative characteristics using statistical variance, not qualitative ones.

Mean Value Within Tolerance Range (D): Specific to quantitative data, not applicable to qualitative characteristics.

Thus, "Attributive inspection nonconforming units" and "Manual valuation" are the correct answers.References: SAP Help Portal - "Valuation Modes for Qualitative Characteristics"; SAP S/4HANA QM User Guide - "Sampling Procedures".