Our BOM synchronization from PLM to Epicor SCM is failing with a ‘Duplicate part revision’ error. The PLM import validation is rejecting updates even though we’re sending what should be unique revision identifiers.
Here’s the error from the import log:
<ImportError>
<PartNumber>ASM-2024-0156</PartNumber>
<Revision>C</Revision>
<Error>Duplicate revision exists in Part_Revision table</Error>
</ImportError>
The BOM sync process was working fine until we upgraded to 10.2.600 last month. Now every time PLM sends BOM updates, they fail validation. We’ve checked the part revision table and revision C does exist, but it’s marked as obsolete. Shouldn’t the system allow us to update obsolete revisions, or do we need a different approach for handling revision updates?
The 10.2.600 release changed the validation logic for part revisions. Previously, obsolete revisions could be overwritten, but now the system treats all revisions as immutable once created. You’ll need to modify your PLM import to create new revision letters (like C1, C2) or use a different revision numbering scheme that increments properly.
You need to implement a pre-import validation step. Query the Part_Revision table using the PartNumber and Revision combination. If found and status is obsolete, update the existing record instead of creating new. If status is active, either skip the import or create the next sequential revision. The key is distinguishing between update vs create operations in your import logic.
That makes sense. Our PLM integration was designed assuming we could overwrite revisions. How do we properly check for existing revisions before the import? Is there a specific API call or validation step we should add?
Also check your PLM export settings. Sometimes PLM systems send full snapshots instead of delta changes, which causes duplicate revision attempts. Configure your PLM to only export changed BOMs with proper revision increments.