We’re running TC 12.3 and encountering persistent failures with our EBOM batch import jobs when processing supplier BOMs. The job terminates with ‘Unit of Measure not found’ errors for approximately 30% of imported parts.
The batch job runs nightly to import supplier-specific part data from multiple vendors. Each supplier uses their own UOM conventions (EA, EACH, PCS, etc.), and we’ve configured BMIDE UOM mappings, but the job still fails. When I check the batch import job logs, I see:
ERROR: UOM mapping failed for part SP-4521
Supplier UOM: 'EA' not mapped to system UOM
Import terminated at line 1247 of 3500
This creates incomplete BOMs in our system and delays our procurement workflows. Has anyone dealt with comprehensive UOM mapping configuration in BMIDE for multi-supplier scenarios?
You’ll need to update the LOV with synonyms and redeploy the template, but no full restart required. However, I’d recommend also implementing a pre-validation step in your batch import script. Before the actual import, parse the supplier file and check all UOM values against your configured LOV. Log any unmapped values and either auto-map them using a lookup table or flag them for manual review. This prevents job failures and gives you visibility into new supplier UOM variations before they hit production imports. We reduced our EBOM import failures by 90% using this approach.
I’ll add a quick note about batch import job logs - make sure you’re capturing the full context. The error you showed only indicates the failed part number, but you should also log the supplier ID, the source file name, and the original UOM value. This makes troubleshooting much faster when you have multiple suppliers with overlapping part numbers. We modified our import job to write detailed logs to a database table rather than just flat files, which lets us run analytics on failure patterns and proactively identify new UOM variations before they cause widespread import failures.
One thing to add - when you configure LOV synonyms in BMIDE, make sure you’re setting them at the right level. If your suppliers are in different regions, you might need locale-specific synonym mappings. Also, check your batch import job’s error handling configuration. By default, TC terminates the entire batch on first error. You can modify the job to log errors and continue processing, then handle failed items in a separate reconciliation step. This way you don’t lose 70% of your import just because 30% have UOM issues.
We had exactly this issue with our SAP-to-Teamcenter integration. Beyond the LOV synonym approach, consider implementing a UOM translation layer in your integration middleware. We built a mapping table that sits between the supplier data feed and TC import, which normalizes all UOM variations before they reach Teamcenter. This keeps your BMIDE configuration clean and makes it easier to onboard new suppliers without template changes. The translation table is just a simple CSV that maps supplier-specific UOMs to standard TC values, and it’s maintained by the procurement team rather than PLM admins.
Thanks Mike. I checked our UOM LOV in BMIDE and we do have ‘Each’ as the primary value, but ‘EA’, ‘EACH’, and ‘PCS’ aren’t listed as synonyms. So the batch job can’t map these supplier-specific variations. I’m assuming I need to add these as LOV synonyms and then redeploy the BMIDE template. Will this require a full system restart or just a template update?