Free Practice Questions for SAP C_TS414_2023 Exam

To automatically create a quality notification (e.g., QN01) when an inspection characteristic is rejected in SAP S/4HANA QM, specific settings in the master inspection characteristic (MIC, transaction QS23) are required:

Defects Recording Automatically Called Up (A): In the MIC’s control indicators, the "Defects Recording" checkbox must be activated with the "Automatic" option. This triggers defect recording and, if linked to a notification type in Customizing (SPRO > QM > Quality Inspection > Defects Recording), creates a notification upon rejection.

Documentation Required if Rejected (B): Setting "Documentation Required" for rejection ensures that a defect or notification is initiated when the characteristic fails, supporting the automatic process (found in the MIC’s "Inspection Characteristic" tab).

Assignment of Defect Codes for Rejection (C): Defect codes are selected during recording, not pre-assigned in the MIC for automatic notification creation.

Assignment of an Inspection Method (D): Inspection methods guide execution but don’t drive notification automation.

Thus, "Defects recording automatically called up" and "Documentation required if rejected" are the correct answers.References: SAP Help Portal - "Automatic Notification Creation in QM"; SAP S/4HANA QM User Guide - "Defects Recording".

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.References: SAP Help Portal - "Digital Signatures in QM"; SAP S/4HANA QM Customizing Guide - "Signature Strategy".

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

Source inspections (inspection type 0101) occur at the supplier’s site before GR:

Quality Info Record: Procurement (B): In the quality info record (transaction QI01), you activate source inspection by selecting the "Source Inspection" indicator and linking it to inspection type 0101 (predefined in Customizing). This triggers an inspection lot before delivery (SPRO > QM > Quality Inspection > Source Inspection).

Business Partner (A): Supplier data doesn’t control inspection location.

Purchase Order Item (C): POs can trigger the lot but don’t activate source inspection settings.

Material Master (D): The QM view activates inspection types (e.g., 0101), but the supplier-specific setting is in the quality info record.

Thus, "Quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Source Inspection in QM"; SAP S/4HANA QM Customizing Guide - "Inspection Types".