Use the Addresses page to map addresses either within a party for Single type merge requests or among the parties in Multiple type requests. You determine which addresses are duplicates by creating duplicate address sets and specify the master address that remains after the other addresses merge into it. When you submit the request for the Party Merge process, the duplicate address sets would be merged based on your mapping, with the resulting master addresses.
Every address has a grouping status:
Mandatory: Addresses in a Mandatory duplicate set must merge together because they have the same location ID.
Optional: Addresses in an Optional duplicate set can be removed from the group and included in another set.
Not Grouped: Addresses are not currently mapped to any duplicate set. These addresses will exist after the merge as an address either of the one party for Single type merge requests or of the master party for Multiple type requests.
If the HZ: Show Address Mapping Suggestions profile option is set to Yes, all suggested address mapping is shown by default. If not, the Addresses page displays addresses without any groupings except for the Mandatory duplicate sets. You can use the search to narrow down the list of addresses and subsequently find more addresses to map, or select Apply Suggested Groupings for the Change Grouping option.
Note: If you already have duplicate sets of addresses and run a search for more addresses, any search results would be added without disrupting the existing groupings.
At any point of the address mapping process, you can:
Apply the mapping suggestions and override whatever groupings you currently have, if any.
Clear all groupings, including suggested defaults, except for Mandatory duplicate sets.
The Addresses table shows duplicate address sets in a hierarchical manner. For each set, the master address is the parent and the other duplicates are its children. Any address that does not belong to a hierarchy is not included in any duplicate address set and is automatically transferred to the resulting party after the merge.
Attention: If every address to be merged is also an account site address for the same respective party, then tax validation applies to the merge. See: Tax Validation for Merge.
The validation adapter and level are displayed if the address has been validated. See: Address Validation.
You can personalize this page and display the number of source systems, which is hidden by default. The number indicates how many source systems the address is mapped to. See: Source Systems.
To map addressees, you can:
Update Set:
Select another master address if the current master is not Mandatory.
Remove Optional or Not Grouped addresses from the set.
If you remove all addresses other than the master, you ungroup the entire set and all addresses in the set would have the Not Grouped grouping.
Merge: Select at least two addresses to create a duplicate address set to merge. If you select a master address from any duplicate address set, the other addresses in that set are also included.
Note: Addresses from a purchased source such as D&B can only be merged into addresses of the same source.
For Mandatory duplicate sets:
You must select the master to merge the set with other addresses because the Mandatory addresses must merge together.
You can select only one Mandatory master to include in the new duplicate set.
You must keep the Mandatory master as the master in the new set.
Select the master address if applicable and optionally remove any Optional or Not Grouped address from the set. You do not delete the address from the TCA Registry, and the removed address is available to be included in other duplicate address sets.
Optionally enter any notes, if available, for the address mapping step and click Save Note.