We’re experiencing critical failures in genealogy tracking when our ERP system sends BOM updates without component serial numbers. This is creating major traceability gaps for regulated products.
The ERP-to-MES mapping appears incomplete. When components are added to the BOM in ERP, the feed includes part numbers and quantities but omits serial number fields for serialized components:
<Component>
<PartNumber>COMP-8472</PartNumber>
<Quantity>1</Quantity>
<SerialNumber></SerialNumber>
</Component>
MES genealogy tracking rejects these updates because serial number enforcement is enabled for compliance reasons. This leaves our genealogy records incomplete and fails audit requirements. We can’t disable serial number enforcement due to regulatory requirements. How do others handle ERP feeds that don’t consistently provide serial numbers for all serialized components?
ERP does track serial numbers for these components - they’re entered during receiving. The issue is the BOM sync feed doesn’t pull serial number data, only part master data. It seems like a mapping gap in how the ERP export is configured.
I work on the ERP side and we’ve dealt with similar issues. The standard BOM export typically doesn’t include serial numbers because BOMs define structure, not instances. Serial numbers are usually in inventory transactions or work order consumption records. You might need to create a custom export view that joins BOM structure with inventory allocation data to get the serial numbers. This requires careful handling because serial numbers are assigned during consumption, not at BOM definition time.
This is tricky because you’re caught between ERP limitations and MES compliance requirements. First question - is the ERP system actually tracking these serial numbers, or are they only captured at the MES level? If ERP has them but isn’t including them in the feed, that’s a different problem than if ERP doesn’t track them at all.
Raj is right about fixing it at the source, but that might take time. As an interim solution, you could implement a two-phase sync: first sync the BOM structure without serial numbers (using a temporary staging table), then run a second query against ERP to pull serial numbers and update the genealogy records. Not ideal, but it maintains compliance while you work on the proper ERP export fix.