When the import into the TCA tables starts, the matching phase of the import process automatically begins to identify if each record in the interface table has an associated record in the TCA Registry. The matching determines whether an imported record is inserted as a new party or updates an existing party in the TCA Registry.
The unique ID of each record in the interface table is compared against the Source System Management (SSM) mappings. See: Unique IDs for Interface Table Records.
A SSM mapping links a TCA record to the original record from an external source. SSM mappings are enabled for these tables:
HZ_PARTIES
HZ_PARTY_SITES
HZ_CONTACT_POINTS
HZ_ORG_CONTACTS
See: Source Systems Overview.
The unique ID indicates the source ID and source system of the interface table record. If that unique ID matches a SSM mapping, the interface table record will be used to update the corresponding existing record in TCA. If no match is found, the interface table record will be inserted into the TCA Registry as a new party.
For example, you import a record from the Vision source system, with source ID 100, for the first time. This record is inserted as a new party in TCA, and a SSM mapping is created between this TCA party and the source ID 100 from Vision. If you try to reimport the record from Vision with source ID 100, that record would be matched to the existing SSM mapping, and the reimported data would update the existing TCA party.
Note: Each combination of source ID and source system can update only one party in the TCA Registry.
You can choose to load only entities without the associated party, as long as the provided source ID and source system matches a parent record in the TCA Registry to be updated. For example, you can import addresses without parties, if the addresses are matched to existing parties. Otherwise, you must import associated parties along with addresses.
You cannot change the source ID of a record in the TCA Registry during the import process unless you are importing data from D&B.
If an address's source ID in the interface tables matches an existing SSM address mapping, then the interface table address is compared to the existing address.
If the addresses are exactly the same, the existing address will be updated with the imported address.
If not the same, the value passed in the CORRECT_MOVE_INDICATOR column of the HZ_IMP_ADDRESSES_INT table determines if the address should be a correction or move. The default is move.
Correction: The HZ: Allow Updates of Address Records During Import profile option must be set to Yes. The imported address will update the existing address. If the country, state, province, county, city, or postal code changes due to the update, the tax assignment is deleted.
If the profile option is set to No, you will get an error. You should either change the profile option or the CORRECT_MOVE_INDICATOR column value.
Move: A new location is created with the imported address, and the existing address is inactivated. Any SSM mappings to the existing address will be changed to the new address, but none of the transactions are automatically transferred.