Setting up supporting data

In each site, set up data that is required to support your transactions.

Note: It is not necessary to set up supporting data at sites that are defined as financial entities.

The forms listed in this section add data to supporting tables that are used when entering customer, vendor, and item information, creating transactions, and so on. Your company might not use some of this data; in that case, you can skip those forms.

Note: Be careful about the order in which the data is defined, so that table dependencies are not violated, which will prevent records from loading. For example, product codes must be defined before distribution accounts are defined, both of which must precede the definition of items. Items must be defined before routings, BOMs, CO and PO lines, jobs, and so on.

The forms are listed in the order that the data should be entered because of data dependencies.

  • Offices
  • Companies: optionally includes CEO (from Employees, which is not available until later)
  • Divisions: requires Company and Office, optionally includes Div Manager (from Employees, not available until later)
  • Departments: optionally includes Company, Office and Manager (from Employees, not available until later)
  • Price Codes: you might want to skip until later when items are defined
  • Project Cost Codes
  • Product Codes: optionally includes Price Code and Project Cost Code. Even though the account fields are not required fields in this form, you must specify them now. When you add items later, the product cost requires these associated accounts.
  • Nature of Transaction Codes (NOTC)
  • Secondary NOTC
  • Carrier Codes
  • Ship Via Codes: optionally includes Carrier Code
  • Delivery Terms
  • Warehouses: optionally includes Prov/State, Country, NOTC, Secondary NOTC, Delivery Terms and Ship Via
  • Distribution Accounts: requires Warehouse and Product Code (In-Transit account values default from the product code)
  • Tax Codes: requires Tax System - but there is a default Tax System 1 defined here, optionally includes Tax Jurisdiction
  • Tax Systems: requires Tax Code
  • Tax Jurisdictions: requires Tax System, optionally includes EC Code (from Countries form) and Vendor number (not available until later)
  • Billing Terms
  • Reason Codes: there are many of these - use Form > Open and filter on reason to find them all. Some of them optionally include NOTC and Secondary NOTC
  • Scheduling Shifts
  • Resource Types
  • Resources: requires Resource Types and Shift Exception ID, optionally includes Item (not added until later), Scheduling Shift, Fixed Asset Number (which in turn requires other data)
  • Resource Groups: requires Resources
  • Work Centers: requires Department, optionally includes Scheduling Shift and Resource Group
  • Locations: optionally includes Work Centers
  • Unit of Measure Codes: some U/M information is replicated between sites when the sites are replicating the Centralized Order Entry, Inventory/Transfers, Purchase Order Builder, or Voucher Builder categories
  • Shift Codes
  • Commodity Codes
  • Language IDs
  • Multi-Lingual Ship Via
  • Multi-Lingual Terms
  • Unit of Measure Conversions: requires Unit of Measure Codes
  • End User Types
  • Customer Types
  • Vendor Categories
  • Fixed Asset Class Codes: optionally includes Department
  • (on-premises only) Printers
  • Territories
  • Sales Periods
  • Campaign Statuses, Campaign Types
  • Lead Statuses
  • Opportunity Task Types, Opportunity Sources, Opportunity Statuses, Opportunity Stages
  • Email Types
  • Lot Attributes
  • Manufacturers
  • Electronic Signature Setup
  • Electronic Signature Authorizers