If a customer is closing one of its sites and there is activity assigned to this site, you can use Customer Merge to transfer all activity from the old site to one of this customer's existing sites. For example, ACME currently has two bill-to sites, but they are planning to close one of these locations. Customer Merge lets you transfer all of their activity from the site that will be closed to their remaining open site.
Any predefined site uses or site uses that you defined in the Receivables Lookups window must be merged with similar site uses. For example, you are merging two of Customer ABC's sites. This customer has defined the following sites as described in this table:
| Address | Site Usage |
|---|---|
| Address1 | Bill-to |
| Address1 | Ship-to |
| Address2 | Ship-to |
In this example, you can only merge the ship-to site of Address1 with Address2 because they are both ship-to sites of different addresses.
The diagrams below illustrate what happens when ACME closes one of its locations. Customer Merge transfers all of ACME's activity from the site that is closed to the remaining open site.
Before the Merge
This illustration shows ACME before the company closes a site and transfers all activity from the old site to an existing site. Before the merge, ACME has two addresses: 255 Market and 38 Telegraph. The 255 Market address is both a bill-to and ship-to site and has one invoice against both sites. The 38 Telegraph address is also a bill-to and ship-to site with one receipt against the bill-to site.
The illustration shows how the merge program combines the two ship-to sites and the two bill-to sites of the 255 Market and 38 Telegraph addresses, and transfers all activity from the site that is closing (255 Market) to the existing site (38 Telegraph).
After the Merge
This illustration shows that there is no activity against ACME's 255 Market address after the merge. Instead, the invoice that was previously against the 255 Market bill-to and ship-to sites is now attached to the 38 Telegraph bill-to and ship-to sites. The receipt remains against the 38 Telegraph bill-to site.
Attention: When merging two sites for the same customer, you cannot submit the merge if Delete After Merge is set to Yes.
Complete Auto Invoice processing (optional). This minimizes the number of rows to be merged in the interface tables. The merge process can then run more efficiently.
Generate the Customer Listing report to see detailed information about the customer and site uses (optional). See: Customer Listing Detail and Summary Reports.
Create a map that shows the site uses you want to merge and the sites you want to maintain. Check that you are merging like site uses (for example, Bill-To's merged with Bill-To's).
Determine whether to inactivate or delete old site use information.
Navigate to the Customers Merge window.
In the From region, select the Type of customer you are merging, then select or enter the name or number of the customer.
Suggestion: If merging an individual, you can use the list of values to search for the person's first or last name.
Attention: The customer names and number LOVs include names and numbers of only those customers that have at least one account site in the operating units that are on your access list.
In the From region, select the operating unit in which you want to merge the account sites. Alternatively, you may select All to merge the account sites in all the operating units that are on your access list and in which the customer has account sites.
In the Account Site area of the From region, the Operating Unit, Site Number, Addresses, and Usage are auto populated.
Attention: If your responsibility allows access to only one operating unit, then that operating unit and related customer account details, such as Site Number, Addresses, and Usage, are defaulted in the Account Site area.
In the From region, select a Merge Reason: De-duplication or Merger.
In the To region, enter the same customer name or number or select it from the list of values.
In the From region, select each site you want to merge.
In the To region, enter the new Address for the site or select it from the list of values.
The Site Number is auto populated in the To region.
Note: Site usage is defaulted in the To region based on the usage in the From region. For example, a bill-to site use is defaulted in the To region for each site with a bill-to site use in the From region.
Attention: You cannot merge sites with different account site usage or across operating units.
Assign a processing priority, P1-High, P2-Medium, or P3-Low, to the merge process.
Note: Use the processing priority when creating merge batches. For example, you can create a batch for merges having the priority P1 to process all the high priority merges first.
To save your merge details without submitting the merge, save your work. This lets you review your mapping for accuracy before actually merging your customer and site information.
Note: At any time before you choose the Merge button, you can use the Cancel button to cancel the merge
To submit the merge process immediately, choose Merge. Because batch processing is more efficient, you can decide to save the merge for later batch processing or to immediately continue with processing. To immediately process the merge, choose Continue. To save the proposed merge for later batch processing, choose Save. See: Submitting the Merge Process.
Attention: If required, repeat these steps for the other operating units, if any, for the customer account.
If you wish to merge account sites in another operating unit for the same customer account or if you wish to perform an account merge for an entirely different customer account, press the Down Arrow key. This action clears the Customer Merge window and readies it for the next account merge.
