Free Practice Questions for SAP C_TS414_2023 Exam

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.References: SAP Help Portal - "Catalog Profiles in QM"; SAP S/4HANA QM Customizing Guide -"Catalog Management".

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 thecharacteristic 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.References: SAP Help Portal - "Defects Recording in QM"; SAP S/4HANA QM User Guide - "Defect Management".

In SAP S/4HANA QM, outgoing quality certificates are generated for outbound deliveries (e.g., inspection type 10 or 11) to provide quality data to customers:

Delivery Item Level (C): Certificates are created at the delivery item level (transaction QC20) because each item in a delivery (VL01N) can have unique materials, batches, and inspection results requiring specific certificate data. The certificate profile (transaction QC01) is assigned to material/customer combinations, and the system generates certificates per item based on this linkage (SPRO > QM > Quality Certificates > Outgoing).

Material Level (A): Certificates aren’t created at the material master level; they’re tied to specific delivery transactions.

Shipping Point Level (B): Shipping points manage logistics, not certificate granularity.

Delivery Header Level (D): While the delivery header exists, certificates are item-specific to reflect individual material quality.

Thus, "Delivery item level" is the correct answer.References: SAP Help Portal - "Outgoing Quality Certificates"; SAP S/4HANA QM User Guide - "Certificate Creation".

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.References: SAP Help Portal - "Reference Documents for Supplier Complaints"; SAP S/4HANA QM User Guide - "Notification Creation".

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.References: SAP Help Portal - "Dynamic Modification in QM"; SAP S/4HANA QM Customizing Guide - "Dynamic Modification Rules".

The requirement for a supplier to provide a quality certificate and its type is configured in:

Quality Info Record: Procurement (D): In the quality info record (transaction QI01), you set the "Certificate Required" indicator and specify the "Certificate Type" (e.g., "ISO 9001") under the "Certificate Data" section. This links the requirement to a specific material-supplier combination, enforced during GR (SPRO > QM > Quality Inspection > Quality Info Record).

Purchase Order (A): POs inherit certificate settings from the quality info record, not define them.

Material Master (B): The QM view defines inspection types, not certificate requirements or types.

Business Partner (C): Supplier master data lacks QM-specific certificate settings.

Thus, "Quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Quality Info Record in QM"; SAP S/4HANA QM User Guide - "Certificate Management".

Automatic usage decision (UD) in SAP QM (configured via transaction QA16) requires:

No Inspection Characteristic Was Rejected (A): All characteristics must be accepted (e.g., valuation "A") for the system to proceed automatically (SPRO > QM > Quality Inspection > Usage Decision > Define Automatic UD).

All Required Inspection Characteristics Were Confirmed and Completed (B): Required characteristics (marked in the plan) must have results recorded and valuated (status RREC).

There Are No Defect Records for the Inspection Lot (E): Open defects block automatic UD, ensuring quality issues are resolved first.

Activity Recording Finished for All Operations (C): Activity confirmation (e.g., time) is optional and not a prerequisite.

All Inspection Operations Completed (D): Operations completion isn’t mandatory; characteristic completion is sufficient.

Thus, "A, B, E" are the correct answers.References: SAP Help Portal - "Automatic Usage Decision"; SAP S/4HANA QM User Guide - "UD Processing".

SAP Fiori apps in QM support usage decisions (UD):

Manage Usage Decisions (A): App ID F2171 is specifically designed for recording and managing usage decisions for inspection lots, a direct tool for this task.

Quality Technician Overview (B): App ID F2173 provides an overview and includes options to perform UD, supporting technicians in lot processing.

Quality Engineer Overview (C): App ID F2174 focuses on analytics and planning, not direct UD execution.

Manage Quality Level (D): App ID F2172 manages quality levels (e.g., skip lots), not UD itself.

Thus, "Manage Usage Decisions" and "Quality Technician Overview" are the correct answers.References: SAP Help Portal - "Fiori Apps for QM"; SAP S/4HANA QM User Guide - "Usage Decision Apps".

In SAP S/4HANA QM, inspection lots for production (inspection lot origin 03 or 04) are triggered by specific events in the production process:

Production Order Release (A): Releasing a production order (transaction CO02, status REL) can create an inspection lot of origin 03 for in-process inspections if QM is active in the material master (inspection type 03) and the routing includes QM operations. This is a standard trigger in discrete manufacturing.

Goods Movements for Production Order (D): Goods receipt from a production order (e.g., transaction MIGO, movement type 101) triggers an inspection lot of origin 04 if inspection type 04 is active in the material master. This is common for post-production quality checks.

Production Order Creation (B): Creating an order (status CRTD) does not typically trigger an inspection lot; it requires release or goods movement to activate QM.

Available-to-Promise (ATP) Check (C): ATP checks availability in sales or production planning but is unrelated to QM inspection lot creation.

Thus, "Production order release" and "Goods movements for production order" are the correct answers.References: SAP Help Portal - "Inspection Lot Origins 03 and 04"; SAP S/4HANA QM User Guide - "Production Integration".