SAP Updated C_TS414_2023 Exam Questions and Answers by dulcie

The SAP Fiori app "Record Inspection Results" (App ID: F2170) in SAP S/4HANA QM supports specific result recording types for inspection lots:

Recording of Single Inspection Results (B): This allows entering individual values for quantitative or qualitative characteristics (e.g., one value per sample), a standard feature in the app for detailed recording.

Summarized Inspection Results Recording (D): The app supports entering a single aggregated value (e.g., average) for a characteristic, ideal for summarized quantitative data, as configured in the MIC control indicators.

Classed Inspection Results Recording (A): Classed recording (grouping results into ranges) is supported in classic transactions (e.g., QE51N) but not explicitly in the standard Fiori app’s functionality.

Results Recording for Inspection Points (C): While inspection points are supported in QM, the Fiori app focuses on lot-level recording and doesn’t emphasize point-specific recording in its standard scope.

Thus, "Recording of single inspection results" and "Summarized inspection results recording" are the correct answers.References: SAP Help Portal - "Record Inspection Results Fiori App"; SAP S/4HANA QM User Guide - "Fiori Apps in QM".

When creating an operation in an inspection plan (transaction QP01/QP02), certain fields aremandatory to define the operation’s purpose and execution in SAP S/4HANA QM:

Control Key (B): The control key is a mandatory field in the inspection plan operation. It determines the operation’s behavior, such as whether inspection characteristics are required, whether it’s a milestone, or if it triggers specific actions (e.g., QM01 for quality inspection). Defined in Customizing (SPRO > Quality Management > Quality Planning > Inspection Planning > Define Control Keys), it ensures the system knows how to process the operation. Without it, the operation cannot be saved.

Activity Type (A): This is relevant for cost accounting (e.g., in Production Planning or QM orders) but is not mandatory in the inspection plan operation itself.

Work Center (C): The work center (e.g., a test station) is optional in QM inspection plans unless specified by the control key. It’s common but not universally required.

Standard Text Key (D): This provides predefined descriptions for operations but is optional and not required to create an operation.

Thus, "Control key" is the correct answer, as it’s the only mandatory assignment in standard SAP QM for inspection plan operations.References: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide - "Operations in Inspection Plans".

When inspection lots are created automatically for delivery items (inspection type 10) and the sample size isn’t calculated (status CRTD):

The System Cancels the Lot (B): If the delivery item is removed (e.g., via VL02N), the associated inspection lot is canceled automatically because its reference (the delivery item) no longer exists. The system updates the lot status to "CANC" (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Follow-Up Actions). This is standard behavior to maintain data consistency.

Posts a Usage Decision (A): UD (transaction QA11) requires sample calculation and results, which hasn’t occurred here.

Marks the Lot for Cancellation (C): The lot is fully canceled, not just marked, in this scenario.

Sends a Workflow Message (D): Workflow notifications require custom configuration andaren’t standard here.

Thus, "The system cancels the lot" is the correct answer.References: SAP Help Portal - "Inspection Lot Processing for Deliveries"; SAP S/4HANA QM User Guide - "Lot Cancellation".

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