Component-to-defect-disposition record chain: the lot, batch and work order keys from SAP EWM receipt to QMS disposition

Short answer

A company connects component-to-defect-disposition records by writing an identifier into every hop: the supplier lot onto the receiving batch, the parent batch onto any batch split from it, the batch onto each work order that consumes it, and the work order onto each nonconformance report. With those pointers in place, a reviewer can walk from a disposition back to a supplier lot, or from a supplier lot forward to every affected work order. One hop without its identifier stops the walk in both directions.

Visual briefFull-size diagram
A vertical chain of seven record links from supplier lot SL-5106 down to disposition, joined by lot, batch, work order and NCR keys, with the kitting link from batch R20 to kit batch R27 shown open and then closed by a parent-batch reference.
Illustrative chain for a fictional contract manufacturer. The kitting link is the one with no key.

This record chain sits under the component-to-defect-disposition guide, which covers the metadata a partner collects. Here the job is narrower: walk one Illustrative case hop by hop and name the identifier at each.

Seven hops and the identifier each one passes on

Illustrative. A fictional 480-person contract manufacturer of molded fluid-handling assemblies keeps its warehouse in SAP EWM, its shop floor in an MES and its nonconformances in a QMS. Every number below is invented.

HopRecordIdentifier passed forwardHeld in
1. Goods receiptSupplier lot SL-5106: 2,000 O-rings, put away as batch R20Supplier lot written on R20Warehouse
2. Kitting800 O-rings counted into assembly kits, issued as kit batch R27None: R27 does not point to R20Warehouse
3. ConsumptionR27 issued to work orders WO-881, WO-886 and WO-893Kit batch R27 on each work orderShop floor
4. Pressure test61 of 320 assemblies on WO-886 failWork order numberShop floor
5. NonconformanceNCR-1477 raised; suspected cause: undersized O-ringWork order and part numberQuality
6. Disposition49 assemblies reworked, 12 scrapped; approver and dateNCR numberQuality
7. ContainmentHold requested on anything else built from SL-5106Needs hops 1 to 3 intactQuality

Five hops pass an identifier on. Hop 2 passes nothing, and hop 7, containment, cannot work without it.

The five identifier types and the boundaries they cross

Each identifier carries the record across one boundary. Knowing which is which tells you where to ask.

IdentifierFromToWritten where
Supplier lotSupplier paperworkReceiving batchBatch attribute at goods receipt
Parent batchOriginal batchAny batch split, kitted or relabeled from itBatch genealogy, only if the split is posted
Batch or kit numberWarehouseWork orderGoods issue on the work order
Work order numberShop floorNonconformance reportNCR header
NCR numberNonconformanceDisposition and containmentQuality workflow

The parent batch is the identifier most often skipped, because it is the only one that depends on how a routine warehouse task is posted. SAP documents that in EWM a batch number can come from another system such as SAP ERP or be set directly in EWM, and that EWM can create new batch numbers for inbound deliveries. That flexibility is how a second number for the same physical O-rings can appear. SAP's batch where-used list shows how a batch is created and used through production stages, built from inventory postings and reversal postings; kitting that is not posted as a movement from R20 to R27 leaves nothing for the list to show.

Walking the chain in both directions

From the failure back toward the supplier. NCR-1477 names WO-886. WO-886 consumed kit batch R27. R27 has no parent identifier. The walk ends one hop short of SL-5106, so the records alone cannot show which supplier lot the undersized O-rings came from.

From the supplier forward toward the product. SL-5106 points to R20. R20 still holds 1,200 O-rings and points nowhere else. The walk cannot see R27, so it never reaches WO-881 or WO-893.

The containment hold therefore covers R20's remaining stock and WO-886, while two work orders that used O-rings from the same supplier lot ship unexamined. The connection exists on the kitting bench, perhaps on a printed kit list, but not in any system. The missing-context comparison shows a related case read one export at a time.

Repairing the kitting hop

The repair is an identifier, not a project.

RepairIdentifier it addsWhat a reviewer can then do
Post kitting as a batch split with R20 as parentParent batch on R27Walk NCR-1477 back to SL-5106 from records
Copy the supplier lot onto every kit batchSupplier lot on R27Walk SL-5106 forward to all three work orders
Keep dated kit lists showing source batch and kit batchPaper bridge from R20 to R27Rebuild the link by hand for past cases

A referral does not need any of these done. It needs to know which one, if any, the plant used and from when. The completeness checklist scores that hop alongside the others.

Why the quality end of the chain tends to be strong

For medical device work, the obligations are documented. FDA's Quality Management System Regulation, effective February 2, 2026, amends 21 CFR Part 820 to incorporate ISO 13485:2016 by reference. Device manufacturers, and contract manufacturers building under their quality agreements, therefore tend to record nonconformances and dispositions carefully: who approved, when and on what basis. That tends to make hops 5 and 6 the strongest. It says nothing about hop 2, which is why the kitting question comes first.

Owners, authorization and what stays unknown

The warehouse manager owns hops 1 and 2, the manufacturing systems lead owns hops 3 and 4, and the quality manager owns hops 5 to 7. Each can describe their identifiers from configuration and habit without opening a record. Authorizing a licensing discussion across all three takes the CEO, usually the owner in an owner-run manufacturer, with the plant general manager or COO as a likely sponsor, and customer quality agreements may give customers rights over part-specific data.

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. 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.

Unknown until SourceX reviews it: whether records can be de-identified to a buyer's standard, how customer and regulatory obligations limit use, and whether a buyer wants the chain. Partners never handle drawings, defect descriptions or supplier names. Related pages: warranty claims data, Form 6765 Section G, after-call work notes and the manufacturing industry page.

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 warehouse manager can say which identifier joins a kitted or split batch to its parent, and a plant executive will take the call, register as a partner, check who qualifies and read the 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

Is a broken kitting link common?

Splitting, kitting and relabeling are frequent weak points wherever material moves into line-side containers under a new number. Whether the link is broken at a given plant is a question for the warehouse manager, not something to assume.

Does the chain have to run through SAP EWM?

No. SAP EWM, an MES and a QMS are a common combination in larger plants. Any warehouse, production and quality systems that record lots, batches, orders and dispositions can hold the same chain.

What should a partner write down about the chain?

The key used at each hop, the year each key started being recorded, and the owner of each system. No part numbers tied to customers, no defect descriptions and no supplier names.

Sources

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

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