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

Answer : A, C

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.

Answer : B, C

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.

Answer : B, D

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.

Answer : D

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 directly determine 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.

Answer : A, D

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.

Answer : B, C, D

The SAP Fiori app 'Record Inspection Results' (App ID: F2170) supports:

Add Unplanned Inspection Characteristics (B): Users can add unplanned characteristics (e.g., as complete or incomplete copies) to an operation during recording, enhancing flexibility.

Add Remarks to an Inspection Characteristic (C): The app allows adding comments or notes to characteristics, supporting documentation (visible in the characteristic details).

Assign Documents and Links to an Inspection Characteristic (D): Documents (e.g., via DMS) or links can be attached to characteristics in the app for reference.

Add Unplanned Inspection Operations (A): Operations are predefined in the plan; the app doesn't support adding new operations.

Add Inspection Method to an Inspection Characteristic (E): Methods are assigned in planning, not dynamically in the app.

Thus, 'Add unplanned inspection characteristics,' 'Add remarks to an inspection characteristic,' and 'Assign documents and links to an inspection characteristic' are the correct answers.

Answer : B, C, D

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.