Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Results record the outcome of a specified quality check. Defects record identified problems, so a measurement and a problem report are related but different records.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Quality Management defines and records inspections. The planned check, the measured result and the final decision serve different purposes, and any stock movement needs its own evidence.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for QM results versus defects: Record measurements and problems separately
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP ERP/S/4HANA QM results and manual defect recording during inspection. Classic documented Edit→Defects navigation is included;automatic defects,notification activation and serial/inspection-point behavior depend on setup.

Documentation review on 14 November 2026 used the official SAP sources listed below, including indexed excerpts where full text was unavailable. Scope and availability depend on the stated product, release and configuration. All document references, quantities, dates and outcomes in worked cases are illustrative; no customer SAP system or tenant was accessed and the proposed exercises were not executed.

A MANUFACTURING EXAMPLE

Separate a dimension result from a defect

Count defects separately from affected units

Inspected units: 5. U1 findings: Diameter failure + scratch. U2 finding: Scratch. Totals: 3 defects on 2 units
What to notice: Fictional findings. Preserve required measured results,defect context and the counting basis used by valuation.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Inspected units
5
U1 findings
Diameter failure + scratch
U2 finding
Scratch
Totals
3 defects on 2 units
Words you’ll meet in this guide
Inspection lot
A record grouping a quality inspection task.
Characteristic
Something to inspect, such as length or color.
Usage decision
The recorded conclusion about an inspection lot.
Stock posting
A recorded inventory change under a supported goods-movement process.
Fiori
SAP’s approach to business application design.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Inspection characteristic → Measured result → Recorded defect. Conceptual diagram for QM results versus defects: Record measurements and problems separately.
Apply the idea: A factory inspector records a measured component value and also reports a visible defect; these are related evidence with different purposes.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Separate a dimension result from a defect

    A factory inspector records a measured component value and also reports a visible defect; these are related evidence with different purposes.

  2. Measurements and problem records answer different questions

    Inspection results record what a specified characteristic found.

  3. Keep result identity explicit

    A result belongs to its inspection context.

  4. Understand defect scope and coding

    SAP documents manual defect recording for inspection lot, operation or characteristic during results recording.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.