A domain serves as a template for entities and comprises business operations with a single currency and shared data sets. A domain can have one or more entities. You can have multiple domains per database and can change to another domain from within the application, provided you are an authorized user for that domain.

The currency in which all entities within a domain conduct business. Exchange rates must exist between the base currency and any non-base currencies specified on transactions. The system also maintains these transaction currencies for every transactions.

In Enterprise Edition, a third Management currency can also be maintained. So for example a US based subsidiary of a European company doing business in Canada and Mexico would have a base currency of USD, transaction currencies of USD, CND, and MXN and a management currency of EUR.

An independent unit for financial reporting purposes. An entity generates a separate balance sheet and income statement, plans budgets, and is assessed for taxes. All GL transactions are posted by entity. The primary entity is the default entity for GL transactions. There is no limit to the number of entities in a database.

An inventory and planning concept correlating to a physical location. All inventory is stored by site and all planning is done by site. Each site belongs to one and only one entity, but an entity can have multiple sites. Most functions work within one site— manufacturing orders expect to find all their components at the same site; MRP and DRP calculate requirements one site at a time. A few functions deal with multiple sites, such as multi-site purchase or sales orders, distribution orders, distributed inventory inquiries, and EMT.

Areas of a site where inventory is stored, used, or shipped. Location parameters identify what can be stored and how it can be used. Every inventory transaction must have a site and location. The same locations can exist at more than one site. This is recommended for multisite processing.

Control programs let you update database records and are used to setup and configure various functions of QAD applications. Typically control records are defined during the implementation process and control settings are determined by analysis of the business processes that are required at the time of application installation.

Master data is typically static data that does not change frequently. Entering data in a maintenance program creates a record in one or more tables controlled by the maintenance program. For example, item records are stored in the Item Master table controlled by Item Master Maintenance. Master data is contrasted with transaction data, which is associated with business events that use master data such as a sales order shipment.

Specifies the quantities in which an item is stocked and planned.

A method of defining acceptable values for fields and having the system validate user entry. Codes can display in a look-up browse for selection.

Calculated demand, not forecast, for component items and raw materials that are directly related to production of higher level assemblies or end products.

Demand unrelated to demand for other products.