SAP C_TS414_2023 SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Quality Management Exam Practice Test

Answer : A, C

In SAP S/4HANA Quality Management, catalogs are used to manage predefined codes for qualitative data recording, and selected sets are subsets of code groups used in specific contexts (e.g., inspection plans). Valuation of codes (assigning values like 'Accepted' or 'Rejected') is mandatory for certain catalog types to ensure consistent processing:

Usage Decisions (A): Catalog type '3' (Usage Decisions) requires valuation in the selected set because the usage decision (UD) determines the stock posting and quality score. In Customizing (SPRO > Quality Management > Quality Inspection > Usage Decision > Define Selected Sets), codes like 'A' (Accepted) or 'R' (Rejected) must be valuated to trigger specific system actions (e.g., goods movement). This is mandatory for inspection lot completion.

Defect Types (C): Catalog type '9' (Defects) requires valuation in the selected set when used in defect recording (e.g., transaction QS51). Defect codes (e.g., 'Scratch,' 'Dent') need valuation to classify severity or trigger follow-up actions like notifications, making it mandatory in quality processes.

Characteristic Attributes (B): Catalog type '1' (Characteristic Attributes) is used for qualitative MICs. Valuation is optional and depends on the characteristic's settings (e.g., 'Good/Bad'), not mandatory in the selected set itself.

Activities (QM) (D): Catalog type '5' (Activities) is used for tasks or follow-ups in notifications. Valuation is not mandatory in the selected set, as activities are typically descriptive rather than evaluative.

Thus, 'Usage decisions' and 'Defect types' are the correct answers, as valuation is a required step in their respective processes.

Answer : B

To explore released APIs in SAP S/4HANA:

SAP Business Accelerator Hub (B): Formerly SAP API Business Hub, this is the official platform (https://api.sap.com) to explore, test, and access released APIs for SAP S/4HANA, including QM-related APIs (e.g., Inspection Lot API). It's the standard tool as of 2025.

SAP Application Interface Framework (A): AIF is for monitoring and managing interfaces, not exploring APIs.

SAP Integration Suite (C): This is for building integrations, not a primary API exploration tool.

Thus, 'SAP Business Accelerator Hub' is the correct answer (single-choice context assumed).

Answer : A

The quality score in SAP S/4HANA Quality Management reflects the quality performance of an inspection lot, calculated at the usage decision (UD) stage. This score can influence subsequent processes, such as supplier evaluation. The procedure for its calculation is defined as follows:

Usage Decision Code (A): The quality score calculation procedure is assigned to the usage decision codes in Customizing (SPRO > Quality Management > Quality Inspection > Usage Decision > Define Quality Score Procedure). Each UD code (e.g., 'Accepted,' 'Rejected') can have a specific score or formula linked to it, determining how the system computes the score based on inspection results. This is the correct and standard location for this setting.

Procurement Data in the Quality Management View of the Material Master (B): This area (transaction MM02, QM view) contains settings like inspection type or control keys but does not define the quality score calculation procedure.

Quality Info Record: Procurement (C): The quality info record (transaction QI01/QI02) manages supplier-specific QM settings (e.g., release status), but it does not configure the quality score calculation procedure.

Inspection Type Settings in the Material Master (D): Inspection type settings (e.g., 01 for goods receipt) in the material master activate QM processes but do not define the score calculation logic.

Thus, 'Usage decision code' is the correct answer, as it directly ties the score calculation to the UD process.

Answer : A, C, E

In SAP S/4HANA QM, the item of a quality notification (transaction QM01) can reference specific objects:

Material (A): Materials are a standard object category, linking the notification to a specific material number (e.g., in the 'Reference Object' section).

Batch (C): Batches (LO-BM) can be assigned to track batch-specific issues, a common QM feature.

Serial Number (E): Serial numbers (e.g., for equipment or materials) are supported to pinpoint individual units, especially in industries like electronics.

Delivery Item (B): Delivery items are referenced in SD notifications but not directly assigned as objects in the item structure in standard QM.

Purchase Order Item (D): POs are reference documents, not directly assignable objects in the notification item.

Thus, 'Material,' 'Batch,' and 'Serial number' are the correct answers.

Answer : A, B, E

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.

Answer : A, B, D

Sample-drawing items in the sample-drawing procedure (transaction QPV2) define sample categories:

Reserve Sample (A): A standard category for samples retained for future testing (e.g., stability), maintained in the procedure.

Pooled Sample (B): Represents combined samples for collective testing, a defined category in sample management.

Primary Sample (D): The initial sample taken for immediate inspection, a core category in the procedure.

Initial Sample (C): Not a distinct category; overlaps with 'Primary sample.'

Sample for Storage Condition (E): Not a standard category; storage conditions are attributes, not sample types.

Thus, 'Reserve sample,' 'Pooled sample,' and 'Primary sample' are the correct answers.

Answer : D

Automatic goods movement during usage decision (UD, transaction QA11) for stock-relevant lots (e.g., type 01) is configured in:

In the Inspection Type (D): In Customizing (SPRO > QM > Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), the inspection type (e.g., 01) has a 'Automatic UD' and 'Stock Posting' setting. Activating this links UD codes to movement types (e.g., 321 for quality to unrestricted), enabling automatic stock updates.

Codes in the Selected Set (A): Selected sets (transaction QS51) define UD codes but don't control movements.

Codes in the Code Group (B): Code groups (transaction QS41) are for catalog organization, not stock movement settings.

Movement Type (C): Movement types (e.g., 321) are used but assigned via inspection type settings, not directly configured there.

Thus, 'In the inspection type' is the correct answer.