Get SAP C_TS414_2023 Exam Practice Questions - Real and Updated

Answer : A, C, E

Material specifications in SAP QM (transaction QS61) define inspection requirements directly in the material master, independent of task lists. They integrate specific QM basic data:

Master Inspection Characteristics (A): MICs are the core of material specifications, defining what is inspected (e.g., length, pH). They are assigned to the material spec to set tolerances or qualitative codes.

Sampling Procedures (C): These determine the sample size for the material spec's characteristics (e.g., fixed sample of 5). They are assigned to MICs within the material specification.

Inspection Methods (E): Inspection methods (e.g., 'Visual check') can be linked to MICs in the material spec to specify how the inspection is performed.

Dynamic Modification Rule (B): This governs inspection scope changes (e.g., skip lots) and is assigned to inspection types or plans, not material specs directly.

Selected Set (D): Selected sets are used for qualitative valuations (e.g., UD codes) but are not directly assigned to material specs; they link via MICs instead.

Thus, 'Master inspection characteristics,' 'Sampling procedures,' and 'Inspection methods' are the correct answers.

Answer : B

For a quality notification with origin 'Customer Complaint' (e.g., type Q1, transaction QM01):

Sold-to Party (B): The sold-to party (customer) is mandatory because it identifies who raised the complaint, a key field in the notification header linked to SD data (SPRO > QM > Quality Notifications > Notification Creation > Define Notification Types). Without this, the notification cannot be saved.

Interested Party (A): Optional, used for additional stakeholders.

Contact Person (C): Optional, specifies a customer contact but isn't required.

Author (D): The creator (system user) is auto-filled, not a mandatory partner function.

Thus, 'Sold-to party' is the correct answer.

Answer : B, C, D

The SAP Fiori app 'Record Inspection Results' (App ID: F2170) supports:

Add Unplanned Inspection Characteristics (B): Users can add unplanned characteristics (e.g., as complete or incomplete copies) to an operation during recording, enhancing flexibility.

Add Remarks to an Inspection Characteristic (C): The app allows adding comments or notes to characteristics, supporting documentation (visible in the characteristic details).

Assign Documents and Links to an Inspection Characteristic (D): Documents (e.g., via DMS) or links can be attached to characteristics in the app for reference.

Add Unplanned Inspection Operations (A): Operations are predefined in the plan; the app doesn't support adding new operations.

Add Inspection Method to an Inspection Characteristic (E): Methods are assigned in planning, not dynamically in the app.

Thus, 'Add unplanned inspection characteristics,' 'Add remarks to an inspection characteristic,' and 'Assign documents and links to an inspection characteristic' are the correct answers.

Answer : A, B

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.

Answer : A, D

Defects recording for inspection lots (e.g., transaction QE51N) requires specific Customizing:

Assign a Notification Type to an Inspection Type (A): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), linking a notification type (e.g., Q3) to an inspection type (e.g., 01) enables automatic or manual notification creation for defects, a mandatory step for integration.

Define the Report Type (D): The report type (SPRO > QM > Quality Inspection > Defects Recording > Define Report Types) must be defined to determine the defect recording layout and process, a required setting.

Activate the Workflow Template (B): Workflow is optional for notifications, not mandatory for defect recording.

Activate Reference to Existing Notifications (C): This is an optional enhancement, not a requirement.

Thus, 'Assign a notification type to an inspection type' and 'Define the report type' are the correct answers.