The table below lists the profile options that are used for customer merge deployment.
Customer Merge Deployment Category
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| AR: Customer Merge Commit Size | 1000 | View Only | Update | Update | Update | No Access |
| HZ: Audit Customer Account Merge | No | View Only | Update | No Access | No Access | No Access |
| HZ: Location Updatable | No | Update | Update | Update | Update | Update |
This profile option determines how many site uses are included in a merge set when you run the Customer Merge program from the Standard Request Submission windows. This profile is not used when you submit the program from the Customers Merge window. A merge set contains one or more pairs of customer accounts to merge and is created based on these two rules, with the first rule taking precedence:
Site uses for a customer account cannot be split between two merge sets.
The number of site uses in a merge set is as close to the profile option value as possible without violating the first rule.
For example, you leave the profile option at the default value of 1000, and you have three groups of customer accounts to merge. Each merge involves 100 addresses with 20 site uses per address, so each of the three merges has 2000 site uses that must belong to the same merge set. With the profile option set to 1000, the Customer Merge program runs three merge sets, each with 2000 site uses.
If you set the profile option to 3000, the program runs two merge sets. After processing the first 2000 site uses, the Customer Merge program checks that the profile option is not yet reached and processes another 2000 for a merge set of 4000 total site uses. With the profile option already reached in the first merge set, the program creates another merge set and processes the last 2000 site uses.
When you set this profile option, consider the number of site uses of the merge-from customers. If you set the value too low, a small number of records are saved in each merge set. If you set the profile option too high, indexes might not be properly used. In addition, if you set the profile option to less than 1000, 1000 is the value that the program uses.
For more information about the Customer Merge program, see Merging in Batch Process.
This profile option causes the creation of a log file when customer accounts are merged. If this option is set to Yes, an audit log file is generated. The default value for this profile option is No.
Set this profile option to Yes or No to determine whether the Location field for the merge-to customer in the Customers Merge window can be updated or not. See: Merging Different Customers.
The default value for this profile option is No.