It is important to understand the behavior when importing a part when that part number already exists in the database.

When importing a part or group of parts, if any of the part number/scenario combinations already exist in the database, the list of parts which do already exist will be displayed. You will then have the option to cancel the import or proceed. If they choose to cancel, nothing will be imported. If they choose to proceed, all of the parts will be imported and the ones which already existed will be overwritten (regardless if they are locked or unlocked). If none of the parts being imported exist in the database, you will not be prompted at all.

If part 123456.initial exists in the database and is the only scenario for part number 123456, and 123456.india is imported. Scenario 123456.initial will remain and 123456.india will be added. If 123456.india was official when it was exported it will become the official scenario when it is imported.

Therefore, when a user in India costs a sub-assembly, they will need to export the “.initial” scenario so that its cost will be pulled into the higher-level assembly. As described above, if that sub-assembly already exists in the US database it will be overwritten upon import.