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