Customer Administration Change Customer Number Report overview

Customer > Reports > AR Reports > ARAC

Function acronym: ARAC

Use this report to change customer numbers in all active records where the customer number is stored.

You can perform these tasks:

  • change an old customer number to a new customer number
  • merge two customer numbers for the same customer into one set of records.

When you change customer numbers, all records with the old number are changed to contain the new number. When you merge customer numbers, the two sets of records are combined under the new number. In either case, the old customer number is deleted. When running this report, Customer Billing Setup is updated.

Customers cannot be combined if ship to records exist for the destination customer.

If you use Infor ION to exchange BODs with another ION-extended application and the CustomerPartyMaster BOD is activated, you are not permitted to run Customer Administration Change Customer Number Report. Data renaming of this type cannot be communicated to other components by business object documents (BODs).

Note: Changing customer numbers can be a slow process if you have a large number of customer records. Change customer numbers when other processes are not being executed. In addition, if accounts receivable updates are made when you run the Customer Administration Change Customer Number Report, important data may be lost.

Use the Combine Customers If New Cust Exists? option to combine ship to information. If you combine customers with different ship to records, the ship to for the new customer replaces the ship to for the old customer. Ensure that you want to replace the old customer ship to with the new customer ship to before you use this option.

If duplicate active transactions exist in Vendor Invoice Center Entry when customer numbers are merged , a prefix of 9 is assigned to the duplicate transaction under the old customer number. If the transaction number has seven digits, this makes a new transaction number that is eight digits long, which is outside the normal field length. An eight digit transaction number can cause display problems on any inquiries performed after the merge. To avoid this, view the outstanding transactions for both the old and new customer numbers before you merge. This way you can change any duplicate numbers and avoid the assignation of a prefix.

The report displays all files that were updated with the new customer number. If any active transactions exist, those transactions are displayed.

Note:  When you run the Customer Administration Change Customer Number Report for several customer numbers, use a stored report and a job name. If failure occurs during processing, you can re-run the report without re-entering the data. If Customer # Not Set Up in Customer Setup – AR Setup Customer is displayed during the second run, this customer number was updated successfully during the first attempt before failure occurred.