1. Administration and Configuration Guide
  2. Entity Resolution
  3. Persisting the Data
  4. Persisting the Data When F_PERSIST_GUID Flag is Set to True and F_MANUAL_APPROVAL Flag is Set to True/False Condition

4.5.2 Persisting the Data When F_PERSIST_GUID Flag is Set to True and F_MANUAL_APPROVAL Flag is Set to True/False Condition

Note:

  • This section is applicable only if F_PERSIST_GUID flag is set to True and F_MANUAL_APPROVAL flag is set to True/False in the FCC_ER_GUID_PERSIST_CONFIG table in the ER schema.
  • Generally, Global Party ID will be persisted to the party that has most number of entities and if the number of entities are same between the parties, then the least Global Party ID will be persisted (it differs case to case).
No change

Existing group elements are a subset of probable group elements, and the number of elements is the same in both groups. All elements in the existing Group have the same global id. The existing global id is assigned to probable group elements.

For example, G1 has C1, C2 and C3 entities. After the Day 1 batch execution, if there is no change in the existing group. Still, G1 has C1, C2 and C3 entities with the same global id.

Figure 4-19 No change


Description of Figure 4-19 follows
Description of "Figure 4-19 No change"

Add

Existing group elements are a subset of probable group elements, and the number of elements in the probable Group is more than the existing Group. Extra elements in the probable Group do not have any global id assigned yet. New elements are added to the existing Group, and the same global id is assigned.

For example, G1 has C1 and C2 entities. After the Day 1 batch execution, if C3 entity ma

Figure 4-20 Add


Description of Figure 4-20 follows
Description of "Figure 4-20 Add"

Merge
Existing group elements are a subset of probable group elements, and the number of elements is the same in both groups. Elements in the existing Group have different global ids assigned. Elements are merged into a single group, and the existing global id is persisted.

Note:

You can manually persist the existing global id based on your requirement, only if F_PERSIST_GUID flag is set to True and F_MANUAL_APPROVAL flag is set to True/False in the FCC_ER_GUID_PERSIST_CONFIG table in the ER schema.

For more information about manually persisting the existing global id, see Persisting the Global Party ID through the Manual Action section in the OFS Compliance Studio User Guide.

Case 1: If number of entities are different between the groups

For example, G1 has C1 and C2 entities and G2 has a C3 entity. After the Day 1 batch execution, if C3 entity matches with an existing group then C3 will be merged into the existing group with same global id is persisted and G2 will be deactivated.

Figure 4-21 Merge Action for most Number of Entities


Description of Figure 4-21 follows
Description of "Figure 4-21 Merge Action for most Number of Entities"

Case 2: If number of entities are same between the groups

For example, G1 has C1 entity and G2 has a C2 entity. After the Day 1 batch execution, if C2 entity matches with an existing group then C2 will be merged into the existing group with same global id is persisted and G2 will be deactivated.

Figure 4-22 Merge Action for Lowest Global ID


Description of Figure 4-22 follows
Description of "Figure 4-22 Merge Action for Lowest Global ID"

Merge and Add
Existing group elements are a subset of probable group elements, and the number of elements in the probable Group is more than the existing Group. Extra elements in the probable Group do not have any global id assigned yet, and standard elements have different global IDs assigned already. Common elements are merged into a single group, and new elements are added to the Group with existing global id is persisted.

Note:

You can manually persist the existing global id based on your requirement, only if F_PERSIST_GUID flag is set to True and F_MANUAL_APPROVAL flag is set to True/False in the FCC_ER_GUID_PERSIST_CONFIG table in the ER schema.

For more information about manually persisting the existing global id, see Persisting the Global Party ID through the Manual Action section in the OFS Compliance Studio User Guide.

Case 1: If number of entities are different between the groups

For example, G1 has C1 and C2 entities, G2 has C3 entity. After the Day 1 batch execution, if C4 entity is added newly and C3 entity got changed then common entities are merged into a single group and a new entity is added to the group with existing global id (G1 has C1, C2, C3, and C4 entities) is persisted and G2 will be deactivated.

Figure 4-23 Merge and Add Action for most Number of Entities


Description of Figure 4-23 follows
Description of "Figure 4-23 Merge and Add Action for most Number of Entities"

Case 2: If number of entities are same between the groups

For example, G1 has C1 and C2 entities, G2 has C3 and C4 entities. After the Day 1 batch execution, if C5 entity is added newly and C4 entity got changed then common entities are merged into a single group and a new entity is added to the group with existing global id (G1 has C1, C2, C3, C4 and C5 entities) is persisted and G2 will be deactivated.

Figure 4-24 Merge and Add Action for Lowest Global ID


Description of Figure 4-24 follows
Description of "Figure 4-24 Merge and Add Action for Lowest Global ID"

Split
After applying merging rules criteria, if multiple groups are created for elements of a probable group, these elements are also a subset of existing group elements. The number of elements in both probable and existing groups is the same. A single global id is assigned to all elements in the existing Group, and then probable group elements are split into different groups with existing global id is persisted for one group and new global id assigned to another group.

Note:

You can manually persist the existing global id based on your requirement, only if F_PERSIST_GUID flag is set to True and F_MANUAL_APPROVAL flag is set to True/False in the FCC_ER_GUID_PERSIST_CONFIG table in the ER schema.

For more information about manually persisting the existing global id, see Persisting the Global Party ID through the Manual Action section in the OFS Compliance Studio User Guide

Case 1: If number of entities are different between the groups

For example, G1 has C1, C2, and C3 entities. After the Day 1 batch execution, if C3 entity is not matched with the existing entities of the group then C3 will be split into a new group. G1 has C1 and C2 entities with existing global id is persisted and G2 has C3 entity with new global id assigned.

Figure 4-25 Split Action for most Number of Entities


Description of Figure 4-25 follows
Description of "Figure 4-25 Split Action for most Number of Entities"

Case 2: If number of entities are same between the groups

For example, G1 has C1 and C2 entities. After the Day 1 batch execution, if C2 entity is not matched with the existing entities of the group (regardless which entity was changed) then C2 will be split into a new group. G1 has C1 entity with existing global id is persisted and G2 has C2 entity with new global id assigned.

Figure 4-26 Split Action for Lowest Global ID


Description of Figure 4-26 follows
Description of "Figure 4-26 Split Action for Lowest Global ID"

Split and Merge
After applying merging rules criteria, if multiple groups are created for elements of a probable group, these elements are also a subset of existing group elements. The number of elements in both probable and existing groups is the same, and different global ids are assigned to elements in the existing Group,then probable group elements are split into different groups and merged, satisfying the same ruleset criteria with existing global id is persisted for one group and new global id assigned to another group.

Note:

You can manually persist the existing global id based on your requirement, only if F_PERSIST_GUID flag is set to True and F_MANUAL_APPROVAL flag is set to True/False in the FCC_ER_GUID_PERSIST_CONFIG table in the ER schema.

For more information about manually persisting the existing global id, see Persisting the Global Party ID through the Manual Action section in the OFS Compliance Studio User Guide

Case 1: If number of entities are different between the groups

For example, G1 has C1 and C2 entities and G2 has C3 and C4 entities. After the Day 1 batch execution, if C2 matches with C3 and C4 then C2 will be split separately and merged with C3 and C4 respectively. G1 has C1 with a new global id assigned and G2 has C2, C3 and C4 entities with existing global id is persisted.

Figure 4-27 Split and Merge Action for more Number of Entities


Description of Figure 4-27 follows
Description of "Figure 4-27 Split and Merge Action for more Number of Entities"

Case 2: If number of entities are same between the groups

For example, G1 has C1 and C2 entities and G2 has C3 and C4 entities. After the Day 1 batch execution, if C1 matches with C3 and C2 matches with C4 then C3 and C4 will be split separately and merged with C1 and C2 respectively. G1 has C1 and C3 entities with existing global id is persisted and G2 has C2 and C4 entities with a new global id assigned.

Figure 4-28 Split and Merge Action for Least Global ID


Description of Figure 4-28 follows
Description of "Figure 4-28 Split and Merge Action for Least Global ID"

Delete

If an element exists in the existing group, but the same element does not belong to any probable group and does not exist in the customer/entity dataset, it is deleted from the existing group with same global id is assigned to the Group. If the deleted record is part of STG_DELETED_PARTIES_PRE table then underlying customers will also be deleted.

For example, G1 has C1, C2, and C3 entities. After the Day 1 batch execution, if C3 is deleted from the existing group then G1 has C1 and C2 entities with same global id is persisted.

Figure 4-29 Delete


Description of Figure 4-29 follows
Description of "Figure 4-29 Delete"