Importing Item Structure ALWAYS triggers a new Item Structure even if it is not changing

Summary:

We use Import Maps to interface items and BOMs from another system. When an item is interfaced and it is unchanged compared to what is available in Product Data Hub, this interface file is simply ignored by the import process – which is good, as the item is simply unchanged.

 

However, when a BOM is interfaced, the current BOM in the Cloud is always end-dated and a new BOM created, even if there is no change to the BOM caused from the interface. This is an issue, as end- and start-dating a BOM triggers changes to the Work Definitions.

 

is there a way to avoid that the old BOM is end-dated and a new BOM is created in case that the interface provides the old (i.e. existing) BOM?