In SAP S/4HANA QM, quality notifications (e.g., transaction QM01) use catalog types to classify data in specific structure elements:

Defect Locations (A): Catalog type "A" (Defect Location) can be assigned to specify where a defect occurred (e.g., "Surface"), configured in the notification item (SPRO > QM > Quality Notifications > Catalogs).

Defect Types (D): Catalog type "9" (Defect Type) is assigned to classify the nature of the defect (e.g., "Scratch"), a standard field in the notification item.

Tasks (E): Catalog type "2" (Tasks) is used to define actions (e.g., "Repair") in the tasks tab of the notification.

Assigned Objects (B): Objects (e.g., material, batch) are referenced but don’t use catalog types directly.

Defect Causers (C): Causers (e.g., "Machine") use catalog type "5" (Causes), but this isn’t listed as "Defect causers" in standard terms; it’s typically "Causes."

Thus, "Defect locations," "Defect types," and "Tasks" are the correct answers based on standard structure elements.References: SAP Help Portal - "Catalogs in Quality Notifications"; SAP S/4HANA QM User Guide - "Notification Structure".

For an existing inspection lot tied to a delivery item (e.g., inspection type 10) with no results recorded:

Change the Actual Lot Quantity of the Current Inspection Lot (A): If the delivery item quantity changes (VL02N), the system updates the inspection lot’s quantity to match (status CRTD or INSP), as long as no results are recorded. This maintains synchronization without creating a new lot (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Inspection Lot Update).

Cancel and Create a New One (B): Cancellation and recreation occur only if the item is deleted, not just quantity-changed.

Create a New Inspection Lot (C): A new lot isn’t created for a quantity change; the existing lot adjusts.

Block the Current Inspection Lot (D): Blocking isn’t triggered by quantity changes in this scenario.

Thus, "Change the actual lot quantity of the current inspection lot" is the correct answer.References: SAP Help Portal - "Inspection Lot Updates"; SAP S/4HANA QM User Guide - "Delivery Integration".

Standard SAP Fiori apps (e.g., "Record Defects," App ID F2175) support defect categories tied to QM processes:

Supplier Defect (A): Linked to procurement (e.g., inspection type 01), recordable via apps for supplier-related issues.

Production Defect (B): Tied to production lots (e.g., type 03/04), a standard category in Fiori defect recording.

Customer Defect (D): Associated with customer complaints (e.g., notification type Q1), supported in apps.

Generic Defect (C): Not a specific standard category; defects are context-specific.

Warehouse Defect (E): Typically stock-related (type 08), not a distinct Fiori category.

Thus, "Supplier defect," "Production defect," and "Customer defect" are the correct answers.References: SAP Help Portal - "Defect Recording Fiori Apps"; SAP S/4HANA QM User Guide - "Defect Categories".

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

The catalog profile in the material master determines the set of codes available for quality processes like defect recording or usage decisions. Its assignment occurs at a specific organizational level:

Plant Level (D): In the material master (transaction MM01/MM02), the catalog profile is assigned in the Quality Management view under the "Inspection Setup" section (field QMAT-PROF). This is done at the plant level because QM processes (e.g., inspections) are plant-specific, and the catalog profile must align with the plant’s quality requirements. This is standard SAP behavior, ensuring flexibility across different plants for the same material.

Company Code Level (A): QM settings are not managed at the company code level, as this is a financial organizational unit unrelated to inspection processes.

Client Level (B): Client-level settings are too broad and apply globally, whereas catalog profiles need plant-specific granularity.

Business Area Level (C): Business areas are used for financial reporting, not QM organizational assignments.

Thus, "Plant level" is the correct answer, reflecting SAP’s organizational structure for QM data.References: SAP Help Portal - "Material Master in QM"; SAP S/4HANA QM User Guide - "QM View in Material Master".

Certificate profiles in SAP QM (transaction QC01) define the data included in outgoing quality certificates. The characteristic categories allowed are:

Master Inspection Characteristic (A): MICs (transaction QS21) are used in inspection plans and material specs, and their results can be included in certificate profiles to report quality data (e.g., measured values).

Class Characteristic (B): Class characteristics (from the Classification System, transaction CT04) are linked to batches or materials and can be included in certificate profiles to display classification data (e.g., batch properties).

Inspection Characteristic (C): This term refers to characteristics in an inspection lot/plan but is not a distinct category; it’s covered by MICs, so it’s not separately selectable.

Process Instruction Characteristic (D): Used in Process Industries (PI) for production, not applicable to QM certificate profiles in standard SAP.

Thus, "Master inspection characteristic" and "Class characteristic" are the correct answers.References: SAP Help Portal - "Quality Certificates - Certificate Profiles"; SAP S/4HANA QM User Guide - "Outgoing Certificates".

For quantitative characteristics in results recording (transaction QE51N), control indicators in the MIC (transaction QS23) define how results are confirmed:

Summarized Recording (B): Records a single aggregated value (e.g., average) for the sample, a standard option for efficiency.

Classed Recording (C): Results are grouped into classes (e.g., ranges like 10-15 mm), common for statistical analysis.

Single Result (D): Each individual result is recorded separately, ideal for detailed tracking.

Mean Value and Standard Deviation (A): These are calculated outputs, not control indicators for recording type.

Mean Value (E): This is a result, not a control indicator for how data is entered.

Thus, "Summarized recording," "Classed recording," and "Single result" are the correct answers.References: SAP Help Portal - "Results Recording for Quantitative Characteristics"; SAP S/4HANA QM User Guide - "Control Indicators".

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

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

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

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

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.References: SAP Help Portal - "Customer Complaint Notifications"; SAP S/4HANA QM User Guide - "Partner Functions".

To record quality certificate receipt independently from goods receipt (GR) in SAP S/4HANA QM, the system must decouple these processes:

Control of Certificate Receipt in the Quality Info Record: Procurement (B): In the quality info record (transaction QI01), the "Certificate Control" settings (e.g., "Certificate Required" and "Check at GR" unchecked) allow certificate receipt to be recorded separately (e.g., via transaction QC55) before or after GR. This is the standard setting to achieve independence, ensuring the GR posts to blocked stock or proceeds without certificate enforcement at that step (SPRO > QM > Quality Certificates > Procurement).

Assignment of a Status Profile in the Certificate Profiles (A): Certificate profiles (transaction QC01) define outgoing certificates, not incoming certificate receipt processes.

Indicator for Enhanced Certificate Processing in the Certificate Type (C): The certificate type (SPRO > QM > Quality Certificates > Define Certificate Types) has an "Enhanced Processing" indicator, but it relates to certificate creation, not independent receipt recording.

Assignment of a Status Profile in the Certificate Type (D): Status profiles in certificate types manage certificate statuses, not GR independence.

Thus, "Control of certificate receipt in the quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Certificate Receipt in Procurement"; SAP S/4HANA QM Customizing Guide - "Quality Certificates".

Source inspections (inspection type 0101) occur at the supplier’s site before GR:

Quality Info Record: Procurement (B): In the quality info record (transaction QI01), you activate source inspection by selecting the "Source Inspection" indicator and linking it to inspection type 0101 (predefined in Customizing). This triggers an inspection lot before delivery (SPRO > QM > Quality Inspection > Source Inspection).

Business Partner (A): Supplier data doesn’t control inspection location.

Purchase Order Item (C): POs can trigger the lot but don’t activate source inspection settings.

Material Master (D): The QM view activates inspection types (e.g., 0101), but the supplier-specific setting is in the quality info record.

Thus, "Quality info record: Procurement" is the correct answer.References: SAP Help Portal - "Source Inspection in QM"; SAP S/4HANA QM Customizing Guide - "Inspection Types".

Valuation modes (set in the sampling procedure, transaction QDV1) for qualitative characteristics include:

Attributive Inspection Nonconforming Units (A): Used for qualitative characteristics (e.g., pass/fail), counting nonconforming units against a sample to determine acceptance (e.g., ANSI/ASQ Z1.4).

Manual Valuation (C): Allows manual acceptance/rejection of qualitative results (e.g., "Good" or "Bad"), a flexible option for subjective assessments.

Variable Inspection s-Method (B): Applies to quantitative characteristics using statistical variance, not qualitative ones.

Mean Value Within Tolerance Range (D): Specific to quantitative data, not applicable to qualitative characteristics.

Thus, "Attributive inspection nonconforming units" and "Manual valuation" are the correct answers.References: SAP Help Portal - "Valuation Modes for Qualitative Characteristics"; SAP S/4HANA QM User Guide - "Sampling Procedures".

For clean core integrations in SAP S/4HANA (minimizing custom code):

SOAP (A): SAP recommends SOAP APIs for robust, secure integrations (e.g., enterprise services), supporting clean core by leveraging standard interfaces.

OData (D): OData is the preferred RESTful API type for S/4HANA, enabling flexible, standard integrations (e.g., via SAP Gateway), a cornerstone of clean core.

RFC (B): Remote Function Calls are legacy and less favored for clean core due to tight coupling.

IDoc (C): IDocs are traditional EDI-focused, not prioritized for modern clean core integrations.

Thus, "SOAP" and "OData" are the correct answers.References: SAP Help Portal - "Integration APIs in S/4HANA"; SAP S/4HANA Developer Guide - "Clean Core APIs".

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

Outbound quality inspections (e.g., inspection type 10) in Sales and Distribution (SD) occur for deliveries:

The Inspection is Skipped (A): If no inspection type (e.g., 10) is active in the material master or quality info record: SD, the inspection can be skipped, a valid option in standard SAP.

The Inspection Occurs Before the Goods Issue is Posted (D): For inspection type 10, the inspection lot is created with the delivery (before goods issue, transaction VL02N), allowing inspection before stock is moved (standard process).

After Release of the Sales Order (B): Inspections are tied to deliveries, not sales order release.

After Creation of the Sales Order (C): Inspection lots are not created at SO creation; they require a delivery.

Thus, "The inspection is skipped" and "The inspection occurs before the goods issue is posted" are the correct answers.References: SAP Help Portal - "Outbound Inspections in QM"; SAP S/4HANA QM User Guide - "SD Integration".

Partner determination in QM notifications (e.g., transaction QM01) assigns partners (e.g., responsible person) via:

Assignment to the Notification Type (D): The partner determination procedure is assigned in Customizing (SPRO > QM > Quality Notifications > Notification Creation > Define Notification Types), linking specific partner roles (e.g., coordinator) to a notification type (e.g., Q1 for customer complaints). This is the standard approach.

Notification Origin (A): Origins (e.g., 01 for GR) don’t directly assign partner procedures.

Material Type (B): Material types are MM settings, not linked to QM partner determination.

Material Master (C): Material master doesn’t store partner procedures for notifications.

Thus, "Assignment to the notification type" is the correct answer.References: SAP Help Portal - "Partner Determination in QM Notifications"; SAP S/4HANA QM Customizing Guide - "Notification Types".

Inspection points in SAP QM (configured in the inspection plan, transaction QP01) allow multiple result recordings over time or events for a single lot:

Goods Receipt Inspections (A): For inspection type 01, inspection points (e.g., per container) can be used to record results for partial deliveries or batches, common in procurement.

Inspections with Samples (D): Inspection points support sample-based inspections (e.g., physical samples), allowing results per sample point, as defined in the sampling procedure.

In-process Inspections During Production (E): For inspection type 03, inspection points (e.g., per shift or operation) enable ongoing checks during production, a standard use case.

Inspections for Quality Notifications (B): Notifications (e.g., QN01) record defects or issues but don’t use inspection points, which are lot-specific.

Inspections for Warehouse Defects (C): Warehouse defects (e.g., stock quality issues) typically use stock transfer inspections (type 08), not inspection points.

Thus, "A, D, E" are the correct answers.References: SAP Help Portal - "Inspection Points in QM"; SAP S/4HANA QM User Guide - "Inspection Scenarios".