Free SAP C_TS414_2023 Practice Exam with Questions & Answers

In SAP S/4HANA QM, the Document Management System (DMS) supports linking document types to master data objects for reference:

Quality Assurance Agreements to Quality Info Records: Procurement (A): In the quality info record (transaction QI01), you can assign a DMS document type (e.g., QAA) for quality assurance agreements with suppliers. This is standard for procurement QM (SPRO > QM > Environment > Document Management).

Technical Delivery Terms to Materials (C): Technical delivery terms (e.g., shipping instructions) can be linked to the material master via DMS (transaction MM01/MM02), typically in the Basic Data or QM view, as a standard feature.

Quality Assurance Agreements to Materials (B): QA agreements are supplier-specific and linked to quality info records, not directly to materials in standard SAP.

Technical Delivery Terms to Quality Info Records: Procurement (D): Delivery terms are material-specific, not typically assigned to quality info records in standard configuration.

Thus, "A" and "C" are the correct answers, reflecting SAP standard assignments.References: SAP Help Portal - "DMS in Quality Management"; SAP S/4HANA QM Configuration Guide - "Document Types".

The response profile (transaction QMSM) in QM notifications defines automatic tasks via the "Determine Tasks" function:

Task Code Group (A): Specifies the group (e.g., from catalog type 2) containing task codes, defining the task category (SPRO > QM > Quality Notifications > Response Profile).

Task Code (C): The specific code within the group (e.g., "Investigate") is defined, detailing the task to be created.

Cause Code (B): Cause codes (catalog type 5) are for problem analysis, not task definition.

Notification Type (D): The type is set at the notification level, not in the response profile.

Thus, "Task code group" and "Task code" are the correct answers.References: SAP Help Portal - "Response Profiles in QM"; SAP S/4HANA QM User Guide - "Notification Tasks".

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

Status profiles in SAP QM (defined in SPRO > QM > Quality Notifications > Status Management) control the lifecycle of notification elements:

Header (B): The notification header (e.g., transaction QM01) can have a status profile assigned to manage overall statuses (e.g., "Open," "Completed").

Tasks (D): Tasks within the notification (e.g., "Investigate") can have their own status profile to track individual task progress (e.g., "Released," "Completed").

Activities (A): Activities log events but don’t support status profiles directly.

Items (C): Items (defect details) use catalog types, not status profiles.

Thus, "Header" and "Tasks" are the correct answers.References: SAP Help Portal - "Status Profiles in QM Notifications"; SAP S/4HANA QM User Guide - "Notification Status".

Task lists (e.g., routings) for production orders in SAP integrate QM master data to enable inspections:

Material Specifications (A): Material specs (transaction QS61) can be referenced in routings (transaction CA01) to define inspection requirements for a material, integrating QM into production.

Master Inspection Characteristics (C): MICs (transaction QS21) are directly assigned to operations in routings or inspection plans, specifying what to inspect during production.

Classifications (B): Classifications (transaction CL01) are batch or material attributes, not directly integrated into task lists for production orders.

Control Indicators (D): These are settings within characteristics or plans, not standalone master data for integration.

Thus, "Material specifications" and "Master inspection characteristics" are the correct answers (assuming a multiple-choice intent, though only two are clearly correct based on standard SAP).References: SAP Help Portal - "QM Integration with PP"; SAP S/4HANA QM User Guide - "Task Lists".

In SAP S/4HANA QM, an inspection plan group contains multiple inspection plans, each identified by a unique group counter. When an inspection lot is created (e.g., for goods receipt or production), the system must select the appropriate plan from the group:

Lot Size (D): The lot size of the inspection lot is the primary determinant for selecting an inspection plan. In the inspection plan header (transaction QP01/QP02), you define a "usage" and "lot size range" for each plan within the group. The system matches the inspection lot’s size to the applicable lot size range in the plan, ensuring the correct plan is chosen. This is standard behavior in QM (e.g., for inspection lot origin 01 or 03).

Sample Size (A): Sample size is determined by the sampling procedure within the inspection plan, not the other way around. It doesn’t select the plan.

Material Type (B): Material type influences material master settings but does not directlydetermine the inspection plan selection within a group.

Procurement Type of the Material (C): Procurement type (e.g., in-house vs. external) might influence the inspection type, but it doesn’t select between plans in a group.

Thus, "Lot size" is the correct answer, as it aligns with SAP’s logic for task list selection.References: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide - "Inspection Lot Creation".

A sampling procedure in SAP S/4HANA QM (transaction QDV1) defines how samples are calculated and valuated for an inspection lot. Mandatory assignments ensure the system can determine and process the sample:

Sampling Type (C): This is a required field in the sampling procedure header. It specifies how the sample size is determined (e.g., fixed sample, percentage, sampling scheme). Without it, the system cannot calculate the sample size (e.g., "100% inspection" or "Attribute sampling").

Valuation Mode (D): Also mandatory, this defines how inspection results are evaluated (e.g., "Manual valuation," "Attribute inspection nonconforming units"). It’s assigned in the sampling procedure and ensures consistent acceptance/rejection rules.

Inspection Severity (A): This is optional and applies only to sampling schemes (e.g., normal, tightened), not all sampling types.

Unit of Measure (B): The unit of measure is inherited from the material or characteristic, not a mandatory assignment in the sampling procedure itself.

Thus, "Sampling type" and "Valuation mode" are the correct answers, as they are essential components of every sampling procedure.References: SAP Help Portal - "Sampling Procedures in QM"; SAP S/4HANA QM Customizing Guide - "Sample Management".

When a quality certificate is mandatory (set in the quality info record, transaction QI01) but no GR inspection lot is created (inspection type 01 inactive in the material master), the system handles the missing certificate as follows:

The Goods Receipt is Posted to Blocked Stock (B): If the certificate is required (e.g., "Certificate Check" active in QI01) and not received (transaction QC55), the GR (transaction MIGO) posts the material to blocked stock (movement type 103/105 process). This is standard behavior to prevent unrestricted use until the certificate is confirmed, even without an inspection lot (SPRO > QM > Quality Certificates > Procurement > DefineControl Keys).

Unrestricted Use Stock (A): This would occur only if no certificate check was enforced, contradicting the premise.

Quality Notification Created Automatically (C): Notifications require manual creation or specific Customizing (e.g., defect recording), not automatic generation here.

Missing Certificate Escalated (D): Escalation is not a standard SAP term or process in this context; it implies custom workflow not present in standard QM.

Thus, "The goods receipt is posted to blocked stock" is the correct answer.References: SAP Help Portal - "Certificate Processing at Goods Receipt"; SAP S/4HANA QM User Guide - "Stock Posting".

Control charts in SAP QM (e.g., during results recording, transaction QGC1) monitor characteristic values against statistical limits. Rejection is based on:

Action Limit (D): The action limit (upper/lower control limit, UCL/LCL) is the threshold beyond which a characteristic is rejected, indicating a process is out of control. In Customizing (SPRO > Quality Management > Quality Inspection > SPC > Define Control Charts), exceeding this limit triggers rejection or further action (e.g., defect recording).

Warning Limit (A): Warning limits (e.g., 2-sigma) signal potential issues but don’t automatically reject the characteristic; they prompt monitoring, not rejection.

Moving Average Line (B): This tracks trends but isn’t a rejection threshold.

Center Line (C): The center line (mean) is a reference, not a limit for rejection.

Thus, "Action limit" is the correct answer, aligning with SPC rejection rules.References: SAP Help Portal - "Statistical Process Control in QM"; SAP S/4HANA QM User Guide - "Control Charts".

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