Handle engineering revision transfer after migration Hello, I noticed that Engineering part transfer actions do not check wether the engineering revision already exist on destination site until a first transfer is made. I’m having an issue with a customer where inventory parts & engineering part revisions have been created via data migration. However, now each time a une an existing part revision in a new engineering structure, when I transfer the top code it creates revisions for all the components … This means the setup of Product structures (issue to location, conumption type, alternatives, ...) needs to be made every single time a component is transferred for the first time, for all the parts already in destination site. I tried to tag the transfer actions as ‘transferred’ but couldn’t reach my goal. => Has everyone encountered such an issue ? How could this be fixed ? Thank you,//Pierre