C_TS414_2023 Exam Questions & Answers

For an inspection lot to be created for an outbound delivery item (e.g., inspection type 10):

An Inspection Lot Origin is Assigned to a Delivery Type in Customizing (B): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Lot Origins and Assign Inspection Types), the delivery type (e.g., LF for outbound) must be linked to an inspection lot origin (e.g., 10). This ensures the system triggers a lot during delivery creation (VL01N).

The Relevant Inspection Type is Active in the Material (C): Inspection type 10 must be activated in the material master's QM view (transaction MM01/MM02) for the plant, enabling QM for outbound deliveries.

QM is Active in the Relevant Movement Type (A): Movement types (e.g., 601 for goods issue) trigger stock postings, not inspection lots directly in outbound scenarios.

QM is Active in the Quality Info Record: SD (D): The quality info record: SD (transaction QVDM) defines inspection requirements but isn't a prerequisite for lot creation; it refines the process.

Thus, 'B' and 'C' are the correct answers.

The quality info record: SD (transaction QVDM) specifies QM requirements for outbound deliveries:

Customer and Sales Organization (A): This combination allows generic inspection settings for a customer across a sales organization, a valid standard option.

Customer, Material, and Sales Organization (B): This is the most specific combination, enabling material-specific inspection requirements for a customer within a sales org (SPRO > QM > Quality Inspection > Quality Info Record: SD).

Customer, Material, and Division (C): Division isn't a key field for the SD info record in standard SAP.

Customer, Material, and Distribution Channel (D): Distribution channel isn't part of the key; sales org is used instead.

Thus, 'A' and 'B' are the correct answers.

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.

Inspection points in SAP QM (configured in the inspection plan header, transaction QP01) allow multiple recordings within an inspection lot. Standard types include:

Inspection Point for Sample (A): Used for physical samples (e.g., per sample drawn), defined via inspection point type '1' (sample-based) in Customizing (SPRO > QM > Quality Planning > Inspection Planning > Define Inspection Point Types). Common in goods receipt or production.

Inspection Point for Functional Location (C): Type '3' supports inspections tied to functional locations (Plant Maintenance integration), used for equipment or facility checks within QM.

Inspection Point for Equipment (E): Type '2' links to equipment master records (PM), enabling equipment-specific inspection points in QM processes.

Inspection Point for Incoming Certificates (B): Certificates are managed separately (e.g., quality certificates in procurement), not as an inspection point type.

Inspection Point for Defects Recording (D): Defects are recorded within inspection points, but this is not a distinct type; it's a function of existing types.

Thus, 'Inspection point for sample,' 'Inspection point for functional location,' and 'Inspection point for equipment' are the correct answers.

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.