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

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

Activity recording (e.g., time or cost) for inspection lots of origin 01 (Goods Receipt) requires:

Inspection Operations with Work Centers (B): Operations in the inspection plan (transaction QP01) must have work centers assigned, as these link to activity types (e.g., labor) for recording effort or costs during inspection (SPRO > QM > Quality Planning > Inspection Planning).

Inspection Lot with a QM Order (D): A QM order (e.g., created via Customizing or lot assignment) is required to capture activity data (e.g., via transaction QE51N or CO11N), linking costs to the inspection lot (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Inspection Types).

Inspection Specifications with Master Inspection Characteristics (A): MICs define what’s inspected but aren’t prerequisites for activity recording.

Inspection Specifications with Inspection Methods (C): Methods guide execution, not activity recording setup.

Thus, "Inspection operations with work centers" and "Inspection lot with a QM order" are the correct answers.References: SAP Help Portal - "Activity Recording in QM"; SAP S/4HANA QM User Guide - "Cost Management".

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

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

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

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

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

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

Certificate profiles in SAP QM (transaction QC01) define the data included in outgoing quality certificates. The characteristic categories allowed are:

Master Inspection Characteristic (A): MICs (transaction QS21) are used in inspection plans and material specs, and their results can be included in certificate profiles to report quality data (e.g., measured values).

Class Characteristic (B): Class characteristics (from the Classification System, transaction CT04) are linked to batches or materials and can be included in certificate profiles to display classification data (e.g., batch properties).

Inspection Characteristic (C): This term refers to characteristics in an inspection lot/plan but is not a distinct category; it’s covered by MICs, so it’s not separately selectable.

Process Instruction Characteristic (D): Used in Process Industries (PI) for production, not applicable to QM certificate profiles in standard SAP.

Thus, "Master inspection characteristic" and "Class characteristic" are the correct answers.References: SAP Help Portal - "Quality Certificates - Certificate Profiles"; SAP S/4HANA QM User Guide - "Outgoing Certificates".

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

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

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

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

In SAP S/4HANA QM, an inspection plan group contains multiple inspection plans, each identified by a unique group counter. When an inspection lot is created (e.g., for goods receipt or production), the system must select the appropriate plan from the group:

Lot Size (D): The lot size of the inspection lot is the primary determinant for selecting an inspection plan. In the inspection plan header (transaction QP01/QP02), you define a "usage" and "lot size range" for each plan within the group. The system matches the inspection lot’s size to the applicable lot size range in the plan, ensuring the correct plan is chosen. This is standard behavior in QM (e.g., for inspection lot origin 01 or 03).

Sample Size (A): Sample size is determined by the sampling procedure within the inspection plan, not the other way around. It doesn’t select the plan.

Material Type (B): Material type influences material master settings but does not directlydetermine the inspection plan selection within a group.

Procurement Type of the Material (C): Procurement type (e.g., in-house vs. external) might influence the inspection type, but it doesn’t select between plans in a group.

Thus, "Lot size" is the correct answer, as it aligns with SAP’s logic for task list selection.References: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide - "Inspection Lot Creation".

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

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

When inspection lots are created automatically for delivery items (inspection type 10) and the sample size isn’t calculated (status CRTD):

The System Cancels the Lot (B): If the delivery item is removed (e.g., via VL02N), the associated inspection lot is canceled automatically because its reference (the delivery item) no longer exists. The system updates the lot status to "CANC" (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Follow-Up Actions). This is standard behavior to maintain data consistency.

Posts a Usage Decision (A): UD (transaction QA11) requires sample calculation and results, which hasn’t occurred here.

Marks the Lot for Cancellation (C): The lot is fully canceled, not just marked, in this scenario.

Sends a Workflow Message (D): Workflow notifications require custom configuration andaren’t standard here.

Thus, "The system cancels the lot" is the correct answer.References: SAP Help Portal - "Inspection Lot Processing for Deliveries"; SAP S/4HANA QM User Guide - "Lot Cancellation".

Dynamic modification levels in SAP QM determine the granularity at which inspection scope changes (e.g., reduced to full inspection) are applied in an inspection plan (transaction QP01):

Characteristic Level (A): Modification can occur at the individual characteristic level within an operation, allowing specific MICs to skip or intensify based on their quality history.

Inspection Lot Level (C): The entire inspection lot can be modified (e.g., skipped), based on the quality level for the material or combination (e.g., material/supplier).

Operation Level (D): Modification can apply to an operation, adjusting all characteristics within it based on performance (e.g., operation-specific skip).

Inspection Type Level (B): Inspection types define the process (e.g., 01 for GR), but dynamic modification is not set at this level; it’s tied to plans or lots.

Work Center (E): Work centers are execution locations, not a level for dynamic modification in QM.

Thus, "Characteristic level," "Inspection lot level," and "Operation level" are the correct answers.References: SAP Help Portal - "Dynamic Modification in Inspection Planning"; SAP S/4HANA QM Customizing Guide - "Dynamic Modification".

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

Blocking purchasing from a supplier for quality reasons is managed in:

Quality Info Record: Procurement (C): In the quality info record (transaction QI01), you can set the "Block" indicator or use a status profile (e.g., "Blocked") to prevent purchasing from a supplier for a specific material. This is the standard QM object for supplier-material quality control (SPRO > QM > Quality Inspection > Quality Info Record > Define Status).

Material (A): The material master can block overall procurement but not supplier-specific QM issues.

Business Partner (B): Blocking a supplier globally is possible (e.g., via MM06), but notmaterial-specific for quality reasons in QM.

Purchase Order Item (D): POs can’t enforce a quality block; they reflect existing restrictions.

Thus, "Quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Blocking Suppliers in QM"; SAP S/4HANA QM User Guide - "Quality Info Record".