During initial implementation of QAD Enterprise Applications or during initial setup of a new domain, you may need to change some of the key parameters. To support this flexibility, you can modify most aspects of a domain as long as you need to and then confirm the setup when you are satisfied that it meets your business requirements. Until a domain is confirmed, it is not available to your operational functions.

Certain financial functions are also disabled in an unconfirmed domain:

As a result, no accounting transactions can be created before confirmation occurs. In addition, no operational transactions can be created since the domain entities are not available to be associated with sites in Site Maintenance.

Confirming a domain freezes its base currency, statutory currency, and shared set codes, as well as locking the relationships with any entities that reference it. Note that new entities can still be added to the domain later, but entities cannot be removed from a domain or transferred to another domain. Confirming a domain also sets up domain-specific master records for all existing shared set data. Because the amount of shared set data may be large, especially if the domain is not the first one in a database, this process is completed through a background process called the Replication daemon. Daemon setup is described in QAD System Administration User Guide.

The setup of a domain can be unconfirmed only when no data exists that is shared with other domains.