Use the Relationships page to map relationships either within a party for Single type merge requests or among the parties in Multiple type requests. You determine which relationships are duplicates by creating duplicate relationship sets and specify the master relationship that remains after the other relationships merge into it. When you submit the request for the Party Merge process, the duplicate relationship sets would be merged based on your mapping, with the resulting master relationships.
If the HZ: Create Suggested Merges from Party Merge profile option is set to Yes, then the system automatically creates suggested merge requests with parties related to the parties that are merged. For example, Joe Smith and Joseph Smith are merged, along with these selected relationships:
Joe Smith (ID: 123) as employee of Oracle (ID: 100)
Joseph Smith (ID: 125) as employee of Oracle (ID: 101)
The system would then create a suggested merge request with Oracle (ID: 100) and Oracle (ID: 101).
For each relationship role, the Relationships table shows the number of original relationships in the merge request and the number of relationships that will exist after the actual merge. You can resolve duplicates within each relationship role.
If the HZ: Show Relationship Mapping Suggestions profile option is set to Yes, all suggested relationship mapping for the relationship role is shown by default in the Resolve Duplicates page. If not, the page displays all relationships in the role without any groupings except for the Mandatory duplicate sets. You can use the search to narrow down the list of relationships and subsequently find more relationships to map.
At any point of the relationship 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.
Select the relationship role that you want to map and click Resolve Duplicates.
The table in the Resolve Duplicates page shows duplicate relationship sets in a hierarchical manner. For each set, the master relationship is the parent and the other duplicates are its children. Any relationship that does not belong to a hierarchy is not included in any duplicate relationship set.
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 related party is mapped to. See: Source Systems.
If no suggested duplicate sets are defaulted, optionally search for relationships to limit the list. If you are resolving duplicate contacts, you can search to see any or all relationship roles in the Party Contacts relationship group. You can merge relationships with different roles within this relationship group. See: Introduction to Contacts.
Note: If you already have duplicate sets of relationships and run a search for more relationships, any search results would be added without disrupting the existing groupings.
Every relationship has a grouping status:
Mandatory: Relationships in a Mandatory duplicate set must merge together because they involve the same parties.
Optional: Relationships in an Optional duplicate set can be removed from the group and included in another set.
Not Grouped: Relationships are not currently mapped to any duplicate set. These relationships will exist after the merge as a relationship either of the one party for Single type merge requests or of the master party for Multiple type requests.
To map relationships, you can:
Update Set:
Select another master relationship if the current master is not Mandatory.
Remove Optional or Not Grouped relationships from the set.
If you remove all relationships other than the master, you ungroup the entire set and all relationships in the set would have the Not Grouped grouping.
Merge: Select at least two relationships to create a duplicate relationship set to merge. If you select a master relationship from any duplicate relationship set, the other relationships in that set are also included.
Note: Relationships from a purchased source such as D&B can only be merged into relationships of the same source.
For Mandatory duplicate sets:
You must select the master to merge the set with other relationships because the Mandatory relationships 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 relationship that remains after the merge, if applicable. If the duplicate set has both active and inactive relationships, you can select only an active relationship as the master.
Optionally remove any Optional or Not Grouped relationship from the set. You do not delete the relationship from the TCA Registry, and the removed relationship is available to be included in other duplicate relationship sets.
Return to the Relationships page. Optionally enter any notes, if available, for the relationship mapping step and click Save Note.