# SAP EWM export missing context: before and after | SourceX

Canonical: https://refer.sourcex.si/guides/component-to-defect-disposition-missing-context
Last updated: 2026-11-04

Each system exported alone keeps its own part of the story and loses the connection between the decision and the material. The quality file keeps the nonconformance, the disposition and the approver but not which supplier lot was involved. The production file keeps orders and test results but not the lot behind them or what quality decided. The warehouse file keeps receipts and relabels but not that the material failed. Joined, they fill each other's gaps, except at any step where no key was ever written.

This before-and-after reading belongs to the [component-to-defect-disposition guide](/guides/chain-component-to-defect-disposition). It takes one Illustrative nonconformance and reads it from each export, then from all three together. The case differs from the one on the [record chain page](/guides/component-to-defect-disposition-record-linkage) on purpose: here the cost of the missing link falls on a supplier claim, not on a hold.

## Before: three exports, three partial stories

Illustrative. A fictional 360-person maker of industrial valve assemblies runs a warehouse system, an assembly-line system and a quality system, here SAP EWM, an MES and a QMS. Springs arrive from an outside supplier. A torque test fails on 52 of 250 valves from one assembly order. Here is what each team would see from its own export.

**The quality team's file.** NCR-2215 on assembly order A-318: 52 failures, suspected spring fatigue, 44 valves reworked with new springs, 8 scrapped, and the remaining W11 springs flagged for return to supplier, with approver and date. The return needs the supplier lot number to support a claim. The file does not hold it.

**The production team's file.** Assembly orders A-310 and A-318 both drew springs from stock labeled W11. A-318 failed its torque test; A-310 passed. The file carries W11 and nothing upstream of it, and has no field for the disposition.

**The warehouse team's file.** Supplier lot L-7730 received as W4, 1,800 springs. A pallet label was damaged in storage, so 900 springs got a fresh label and were put away as W11. The relabel created a new number; W11 does not name W4. The file shows stock movements, not that anything made from W11 failed.

Each file is accurate on its own terms, and each would mislead a team that acted on it alone.

## After: the three read together

Joined on order and stock numbers, NCR-2215 points to A-318, A-318 drew from W11, and W11 also fed A-310. Quality now knows a second order shares the same springs and can decide whether to retest it.

One link stays missing. W11 has no parent, so the joined history still cannot prove the failed springs came from supplier lot L-7730. The quantities suggest it, because 900 springs left W4 and W11 holds 900 springs, but that is an inference, not a recorded key, and a supplier can reasonably dispute a claim built on an inference. SAP's batch where-used list builds its view from inventory postings and reversal postings; a fresh label that is not posted as a movement from W4 to W11 leaves nothing for it to follow. SAP also documents that EWM can create new batch numbers, which is how W11 came to exist with no parent.

## What each export loses, and where it lives

| Exported alone | What it keeps | What it loses | Where the lost context lives |
|---|---|---|---|
| Quality file | NCR-2215, failures, rework, return flag, approver | Supplier lot; the other order using the same springs | Production consumption records; warehouse receipt |
| Production file | A-310, A-318, W11, torque results | The supplier lot behind W11; the disposition | Warehouse receipt; quality file |
| Warehouse file | Receipt of L-7730 as W4, the relabel to W11 | That the springs failed; what quality decided | Production test results; quality file |
| All three joined | W11 through to disposition, across both orders | Only the W4 to W11 link | A relabel log or label printout, if one was kept |

The bottom row is the honest result for many plants: a joined history complete except at one step. It is still useful. Records that place the material, the decision and the outcome side by side are rarely found in public data, a gap described in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training).

## What the missing context changes in practice

Read from the QMS alone, the response is rework on one order and a supplier return with no lot to cite. Read with the MES, a second order comes into view. Read with a recorded parent batch, the supplier claim would rest on a documented lot instead of matching quantities, and every other batch made from L-7730 could be checked.

That is the kind of judgment connected manufacturing records can teach. A system learning to recommend dispositions or supplier actions needs to see the material history and the quality decision together. Exception records of this kind are discussed in [exception handling data for AI agents](/guides/exception-handling-ai-agents-data), and escalation paths in [support escalation process records](/data-types/support-escalation-process).

For medical device work the quality end tends to be well kept: FDA's Quality Management System Regulation, effective February 2, 2026, amends 21 CFR Part 820 to incorporate ISO 13485:2016 by reference. Strong QMS records still say nothing about whether a warehouse relabel kept its parent, which is where the gap usually sits.

## Asking about the gaps without opening a record

A partner can learn all of this from the owners. Ask the quality manager which number an NCR carries, the manufacturing systems lead which number an order carries, and the warehouse manager whether a relabeled or repacked batch names its parent, and since when. The [completeness checklist](/resources/component-to-defect-disposition-completeness-checklist) turns those answers into a score. For a related record type, see [warranty claims data](/data-types/warranty-claims-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: the CEO, usually the owner in an owner-run manufacturer, with the plant general manager or COO as a likely sponsor. 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: how customer and supplier agreements limit use, how records would be de-identified, and whether a buyer wants the set.

## 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, production and warehouse records can be read together, with the missing step named, [register as a partner](/register), confirm [who qualifies](/who-qualifies) and read the [terms](/terms) before making the introduction.

## Sources

- https://help.sap.com/saphelp_46c/helpdata/en/25/283d074f7811d18a150000e816ae6e/content.htm
- https://help.sap.com/saphelp_ewm70/helpdata/en/f5/cbcb53ad377114e10000000a174cb4/content.htm
- https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr
- https://refer.sourcex.si/terms
