Component-to-defect-disposition records in SAP EWM, MES and QMS: tracing a nonconformance back to its batch

Short answer

A referral partner can describe a manufacturer's component-to-defect-disposition records without opening one: which system records material movements (SAP EWM, for example), which records production batches (an MES), which records nonconformance reports and their disposition (a QMS), the years each covers, how many reports exist, which batch or lot number links them, and who owns each step. The case to test first is a relabeled component, because relabeling can cut the link to the original batch.

Visual briefFull-size diagram
A batch genealogy tree runs from supplier lot S-2207 to warehouse batch B1, breaks at a relabel step that creates batch B9, and continues to three production orders, one of which carries nonconformance report NCR-0931.
Illustrative. The backward trace from the nonconformance stops at the relabeled batch, so two sibling production orders stay hidden.

The business task: decide what to do with a bad part, and where else it went

A part fails inspection. The quality team opens a nonconformance report and has to decide its disposition: use as is, rework, scrap or return to the supplier. The harder question comes next. Which other production orders used parts from the same lot, and should they be held too? Answering it means walking backward from the failed order to the batch it consumed, and from that batch to the supplier lot and every other order it fed.

Three systems usually hold the steps. A warehouse system such as SAP EWM records receipts, repacks and stock movements; an MES records production orders and which batches they consumed; a QMS records the nonconformance, the disposition and its approver. SAP documents a batch where-used list that shows how a batch is created and used through production stages, built from inventory postings and reversals. Where those postings exist, the backward trace is recorded rather than reconstructed.

What metadata can a referral partner collect about component-to-defect-disposition without reading private content?

Systems, years, volumes, link fields, dispositions, owners and unknowns: a short packet of facts the plant quality manager can give in one meeting. No drawings, no NCR text, no supplier names.

The packet (Illustrative answers)

  • Systems and their role: SAP EWM for receipts, repacks and stock; an MES for production orders and test results; a QMS for nonconformances, dispositions and corrective actions.
  • Years covered: EWM since 2019; MES since 2016; QMS since 2014, with paper NCRs before that.
  • Rough volume: About 900 nonconformance reports a year; roughly 60,000 production orders a year.
  • Link fields: Production order number between MES and QMS; batch number between EWM and MES; supplier lot stored on receiving batches since 2020.
  • Known weak step: Repacks into line bins create new batches without a parent reference.
  • Dispositions recorded: Use as is, rework, scrap, return to supplier, each with approver and date since 2018.
  • Owners: Warehouse manager (EWM), manufacturing systems lead (MES), quality manager (QMS).
  • Unknowns: Whether repack worksheets were kept; whether pre-2018 dispositions name an approver.

For finding plants with these records, see the field guide to quality inspection records, the introduction checklist for quality inspection records and how to identify manufacturing quality workflows. The quality assurance workflows page describes the data type.

What breaks when a relabeled component loses its original batch link

The trace stops one step short. The graphic on this page shows an Illustrative case at a fictional 260-person pump manufacturer. Supplier lot S-2207 is received as warehouse batch B1. A repack into line bins relabels the remaining 600 seals as a new batch, B9, with no parent reference. B9 feeds three production orders: P-5512, P-5520 and P-5534. When nonconformance report NCR-0931 records 138 failed seals on P-5512, the backward trace reaches B9 and stops. Without the B1 link, nobody can show that P-5520 and P-5534 used the same supplier lot, so only P-5512 is held.

SAP's documentation explains why this happens in ordinary systems. In EWM a batch number can come from another system or be created in EWM itself, including new batch numbers for inbound deliveries, so a new number is not unusual. And the where-used list is built from postings: a step that relabels stock without a posting that names the parent leaves no record to follow.

For the packet, the partner only needs three facts about relabeling:

QuestionIllustrative answerOwner
Which steps create a new batch number?Repacks into line bins; supplier returns re-receivedWarehouse manager
Does the new batch store its parent?Not for repacks before 2022Warehouse manager
Is the relabel recorded anywhere else?Paper repack worksheets, retention unknownQuality manager

That last row belongs in the unknowns line of the packet. SourceX's review decides whether the gap matters; the partner's job is to say it exists.

Who can authorize a discussion, and what stays unknown

Genealogy records cross the warehouse, production and quality, so the CEO, usually the owner in an owner-run manufacturer, is the person who can authorize a licensing discussion, with the plant's general manager or the COO as a likely sponsor. The quality manager can describe the QMS but usually cannot authorize licensing production records, and customer contracts may give customers rights over part-specific data. Medical device makers add a regulatory layer: the FDA's Quality Management System Regulation, effective February 2, 2026, amends 21 CFR Part 820 to incorporate ISO 13485:2016 by reference. If the plant makes devices, note it in the packet and leave its effect on licensing to SourceX's review.

Before you introduce, confirm:

  • The company has 50+ full-time employees at peak, contractors excluded, and a documented operating history.
  • The company owns the records or has the right to license them; customer quality agreements and supplier agreements are where restrictions usually sit.
  • A named decision-maker will take a first call.
  • Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews it: whether the records can be de-identified to a buyer's standard, which product lines and years a buyer would want, how customer and regulatory obligations limit use, and what the company would be paid. You never handle or forward raw records. The manufacturing industry page covers related records, plants on SAP's smaller ERP can start from SAP Business One data export, and the systems hub lists other record locations.

Go deeper on component-to-defect-disposition records

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If your client's quality manager can answer the relabel question and name who owns the warehouse, production and quality systems, register as a partner, check who qualifies and read the program terms before you introduce them.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does the company need SAP EWM specifically?

No. SAP EWM, an MES and a QMS are named because that combination is common in larger plants. Any set of systems that records material movements, production batches and nonconformance decisions can hold this chain.

Are regulated manufacturers off limits because of quality-system rules?

Not automatically. Regulation affects how records are kept and who must approve their use, which SourceX reviews with the company. The partner's job is only to describe what exists and who owns it.

Should I ask about specific defects or customers?

No. Ask how many nonconformance reports exist per year, over how many years, and which dispositions are recorded. Defect descriptions, part drawings and customer names stay inside the company.

Sources

  1. refer.sourcex.si/terms
  2. help.sap.com/saphelp_46c/helpdata/en/25/283d074f7811d18a1…
  3. help.sap.com/saphelp_ewm70/helpdata/en/f5/cbcb53ad377114e…
  4. fda.gov/medical-devices/postmarket-requirements-devi…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment