Vendor Administrator Change Vendor Number overview

Vendor > Administration > APA Reports > APAC

Function acronym: APAC

Use this report to change an existing vendor number to a new vendor number.

All records with that vendor number are changed to reflect the new vendor number, including these files and fields:

  • Customer Entry Batch Update Report
  • Vendor Entry Payment Action Report
  • Vendor Invoice Center Entry
  • Vendor Transaction Entry
  • Vendor Transaction Entry Line Items Addons
  • Vendor Transaction Entry Line Costing Amounts
  • Vendor Purchase History Setup
  • Vendor Ship From Setup
  • Vendor Setup
  • CR Check Center Entry
  • Product Warehouse Product Setup
  • Product Unavailable Inventory Entry
  • Product Catalog Setup
  • Product Line Setup
  • Sales Order Entry Non-Stock ARP Vendor
  • Sales Order Entry Batch Line Items
  • PD Entry Rebate Reconciliation
  • PD Rebate Reconciliation Entry Rebate Header Claim Sequence Receipt file
  • PD Pricing Setup - Rebates
  • PD Pricing Setup - Vendor Pricing
  • Purchase Order Entry Header
  • Purchase Order Entry Header EDI Specific Audit file
  • Purchase Order Entry Line Items
  • Purchase Order Entry Line Item Addons
  • Purchase Order Entry Line Item Costing Amounts
  • Purchase Order Entry Line Item EDI Specific Audit file
  • PI New Product Default Setup
  • PI Edit Product Update Entry

Vendor Setup is the last file that is updated so if processing is interrupted, the vendor record will still be intact. If you attempt to change an existing vendor number to another existing vendor number, this error message is displayed on the report: Record Already Exists (1115). No changes are made. Correct your entries and process the report again.

Note: Existing vendor numbers set up on stored reports must be changed manually. Otherwise, the vendors are invalid the next time reports are printed.

If you use Infor ION to exchange BODs with another ION-extended application, you cannot run the Vendor Administrator Change Vendor Number. Data renaming of this type cannot be communicated to other components using business object documents (BODs).