Using Profile Match List

Use profile match list to manage potential matches in advance of the next execution of the Auto Merge Profile scheduled job. Matching profiles above the Upper Threshold are automatically merged once the Auto Merge Profile job executes. You can manually merge a match or prevent selected profiles from being merged by setting a do not merge status on the profile.

Note:

When profile sharing is inactive, only profiles registered for the same resort are considered for match.

During Profile Auto Merge, when potential profile matches are identified, the process determines which profile is the surviving profile (the one that remains after merging) and which one is discarded. This decision depends on various match statuses, so it’s important to understand how each status impacts the merge process.

Note:

Only similar profile types can be merged. Profiles with an inactive date or profiles indicated for purging do not appear in the Profile Match List.

Match Statuses

DNM (Do Not Merge): The DNM status is assigned to profiles that cannot be merged due to certain criteria, such as:
- Active AR accounts
- Future reservations
- Inactive profiles
- Employee profiles
- Configurable Do Not Match Criteria
Note:
If the profile pair has a DNM status, the profiles are not merged, and no further processing occurs for these profiles in the merge queue.
MPC (Match Points Computed): The MPC status is assigned when the match points between two profiles are successful. This approach calculates the similarity between profiles to determine if they are likely duplicates. For more information, see Configuring Profile Match Rules.

Note:
If the match points meet the predefined Match Points threshold, the profiles are merged. The profiles with the lowest profile ID typically survive.
CNM (Cannot Merge): The CNM status is assigned when the profiles cannot be merged for technical or business reasons. For examples, profiles with active reservations or profiles with outstanding balance. When the profiles are indicated with CNM status, the profiles remain separate, and the merge process is halted. The reason for the failure is stored in the processing message field.

Note:

Profiles in the Profile Match List are kept for review for 24 hours and then processed during the job's next run, which typically happens after one day. You can trigger the job manually. For more information, see Configuring OPERA Chain Scheduler

Merging Profiles

From the OPERA Cloud menu, select Client Relations, select Profiles, then select Profile Match List.
Enter search criteria, then click Search.
Select profiles in the search result, then click Merge Profiles.

Adding Do Not Merge Status

From the OPERA Cloud menu, select Client Relations, select Profiles, then select Profile Match List.
Enter search criteria, then click Search.
Select profiles in the search result.
Click Do Not Merge. This option is enabled when the Do Not Merge check box is selected.

Removing Do Not Merge Status

From the OPERA Cloud menu, select Client Relations, select Profiles, then select Profile Match List.
Enter search criteria, then click Search.
Select profiles in the search result.
Click Allow Merge. This option is enabled when the Do Not Merge check box is selected.