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

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 : A, D

Defects recording for inspection lots (e.g., transaction QE51N) requires specific Customizing:

Assign a Notification Type to an Inspection Type (A): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), linking a notification type (e.g., Q3) to an inspection type (e.g., 01) enables automatic or manual notification creation for defects, a mandatory step for integration.

Define the Report Type (D): The report type (SPRO > QM > Quality Inspection > Defects Recording > Define Report Types) must be defined to determine the defect recording layout and process, a required setting.

Activate the Workflow Template (B): Workflow is optional for notifications, not mandatory for defect recording.

Activate Reference to Existing Notifications (C): This is an optional enhancement, not a requirement.

Thus, 'Assign a notification type to an inspection type' and 'Define the report type' 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.

Answer : A, C, E

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.

Answer : B

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.

Answer : D

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.

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.