What NCR data typically comes from ERP and MES?

Typically, ERP provides the commercial, planning, and inventory context for a nonconformance record, while MES provides the production execution, traceability, and event context. In practice, many sites also rely on QMS, PLM, or manual inputs, so there is rarely a universal split that applies across all plants.

Common data pulled from ERP into an NCR includes:

• Part number, revision in use, and item master data
• Sales order, work order, job, or production order references
• Purchase order, supplier, receipt, and lot references for incoming issues
• Inventory identifiers such as lot, batch, serial, heat, or stock location, where ERP is system of record
• Cost-related context such as material value, scrap value, or financial disposition categories
• Customer, program, contract, or project references when needed for impact assessment
• Planned routing or operation references if those are managed in ERP rather than MES

Common data pulled from MES into an NCR includes:

• Operation, work center, machine, resource, and shift where the issue occurred
• Actual process step, routing state, and timestamps
• Operator actions, electronic signoffs, and execution history
• Traceability and genealogy details such as consumed materials, subassemblies, and as-built links
• Inspection results, measurement data, test outcomes, and in-process check failures
• Rework attempts, hold events, scrap events, and production status changes
• Device, equipment, tool, or recipe context when MES captures it directly or through connected systems

The practical answer is that ERP usually tells you what order, item, supplier, and inventory object is affected, while MES tells you where in execution, by whom, and under what process conditions the issue was found.

What often does not fit neatly in either system

Some NCR fields do not belong cleanly to ERP or MES. Examples include disposition decisions, containment actions, root cause analysis, CAPA linkage, approval workflow, and formal quality classification. Those are often managed in a QMS or dedicated NCR workflow tool. If a site tries to force all NCR logic into ERP or all of it into MES, gaps in workflow control, evidence trails, or user adoption are common.

Key constraints in real plants

In brownfield environments, the answer depends heavily on system ownership and integration maturity. One plant may keep lot genealogy in MES; another may keep it in ERP. One ERP may hold inspection lots or supplier quality data; another may not. Some MES platforms capture rich event history, while others only track basic labor and completions.

That means NCR data mapping should be defined field by field, not assumed by product category alone. At minimum, teams usually need to agree on:

• System of record for each NCR field
• When data is copied versus referenced live
• How revisions, lot identifiers, and serial numbers stay synchronized
• What happens when ERP and MES disagree
• How audit trail, approval history, and change control are preserved

Full replacement of ERP or MES just to simplify NCR data flow is often not realistic in regulated, long-lifecycle operations. The qualification burden, validation effort, downtime risk, and integration complexity are usually too high, especially where existing equipment, travelers, and quality records must remain traceable over many years. Coexistence with clearer interfaces is usually more practical than rip-and-replace.

If you are designing an NCR process, the safer assumption is not that ERP or MES alone has the complete truth. The safer assumption is that NCR completeness depends on disciplined data ownership, reliable interfaces, and validation of the workflow end to end.