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

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.

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.

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 the characteristic 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.

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.

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.

Automatic goods movement during usage decision (UD, transaction QA11) for stock-relevant lots (e.g., type 01) is configured in:

In the Inspection Type (D): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), the inspection type (e.g., 01) has a 'Automatic UD' and 'Stock Posting' setting. Activating this links UD codes to movement types (e.g., 321 for quality to unrestricted), enabling automatic stock updates.

Codes in the Selected Set (A): Selected sets (transaction QS51) define UD codes but don't control movements.

Codes in the Code Group (B): Code groups (transaction QS41) are for catalog organization, not stock movement settings.

Movement Type (C): Movement types (e.g., 321) are used but assigned via inspection type settings, not directly configured there.

Thus, 'In the inspection type' is the correct answer.

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 and aren't standard here.

Thus, 'The system cancels the lot' is the correct answer.

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.

Inspection lots with origin 03 (Production) in SAP QM are triggered during production processes (e.g., order release or goods receipt). The task list types used are:

Routing (B): In production (PP), routings (transaction CA01) define operations and can include QM-relevant operations with inspection characteristics. For inspection lot origin 03, the system uses routings when QM is integrated with PP, especially for in-process inspections.

Inspection Plan (D): The inspection plan (transaction QP01) is the primary QM task list for origin 03, defining detailed inspection steps (e.g., characteristics, sampling) for production-related lots, such as goods receipt from production.

Master Recipe (A): Used in Process Industries (PP-PI) for recipes (transaction C201), not standard for discrete manufacturing origin 03 lots.

Equipment Task List (C): Relevant for Plant Maintenance (PM), not production QM lots.

Thus, 'Routing' and 'Inspection plan' are the correct answers for origin 03.

In SAP S/4HANA QM, the item of a quality notification (transaction QM01) can reference specific objects:

Material (A): Materials are a standard object category, linking the notification to a specific material number (e.g., in the 'Reference Object' section).

Batch (C): Batches (LO-BM) can be assigned to track batch-specific issues, a common QM feature.

Serial Number (E): Serial numbers (e.g., for equipment or materials) are supported to pinpoint individual units, especially in industries like electronics.

Delivery Item (B): Delivery items are referenced in SD notifications but not directly assigned as objects in the item structure in standard QM.

Purchase Order Item (D): POs are reference documents, not directly assignable objects in the notification item.

Thus, 'Material,' 'Batch,' and 'Serial number' are the correct answers.