SAP C_TS414_2023 Exam Questions

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.

Dynamic modification in SAP S/4HANA QM allows the system to adjust inspection scopes (e.g., skip lots, reduced inspection) based on quality performance. These criteria are defined in the inspection plan (transaction QP01) or Quality Level settings and determine when modification occurs:

Material and Supplier (A): This is a standard dynamic modification criterion (e.g., for inspection type 01 - Goods Receipt). It tracks quality history for a material-supplier combination, commonly used in procurement scenarios (SPRO > Quality Management > Quality Inspection > Dynamic Modification).

Material and Customer (D): Used in sales or production scenarios (e.g., inspection type 10 - Delivery), this criterion adjusts inspections based on material-customer quality history, ensuring customer-specific requirements are met.

Material (E): A standalone material criterion is valid across multiple inspection types (e.g., 03 - Production), allowing modification based solely on the material's quality history, regardless of supplier or customer.

Material and Work Center (B): Work centers are linked to operations, not directly to dynamic modification criteria in standard SAP QM. This is not a predefined option.

Material and Equipment (C): Equipment is relevant for plant maintenance (PM), not a standard QM dynamic modification criterion for inspection plans.

Thus, 'Material and supplier,' 'Material and customer,' and 'Material' are the correct answers, reflecting standard SAP functionality.

In SAP S/4HANA QM, quality notifications (e.g., transaction QM01) use catalog types to classify data in specific structure elements:

Defect Locations (A): Catalog type 'A' (Defect Location) can be assigned to specify where a defect occurred (e.g., 'Surface'), configured in the notification item (SPRO > QM > Quality Notifications > Catalogs).

Defect Types (D): Catalog type '9' (Defect Type) is assigned to classify the nature of the defect (e.g., 'Scratch'), a standard field in the notification item.

Tasks (E): Catalog type '2' (Tasks) is used to define actions (e.g., 'Repair') in the tasks tab of the notification.

Assigned Objects (B): Objects (e.g., material, batch) are referenced but don't use catalog types directly.

Defect Causers (C): Causers (e.g., 'Machine') use catalog type '5' (Causes), but this isn't listed as 'Defect causers' in standard terms; it's typically 'Causes.'

Thus, 'Defect locations,' 'Defect types,' and 'Tasks' are the correct answers based on standard structure elements.

In SAP S/4HANA QM, combining code groups from multiple catalog types (e.g., defects, causes) into a single object is necessary for processes like defect recording or notifications:

Catalog Profile (A): The catalog profile (maintained via transaction QPCD or Customizing) is designed to group code groups from different catalog types (e.g., defect types, causes, activities) into a single entity. It's assigned to objects like material masters or notification types, enabling consistent use of codes across processes like defect recording (e.g., in inspection lots) or notification processing (e.g., QN01). This is the standard object for this purpose.

Report Type (B): Report types (SPRO > QM > Quality Inspection > Define Report Types) define the layout of defect recording but do not combine code groups from catalogs; they reference catalog profiles instead.

Selected Set (C): A selected set (transaction QS51) is a subset of codes from one catalog type, not a combination across multiple types.

Confirmation Profile (D): Confirmation profiles are used in production (e.g., PP) for operation confirmations, not QM catalog management.

Thus, 'Catalog profile' is the correct answer, as it's the dedicated object for combining codes from multiple catalogs.

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.