In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • Setting Up and Using Domains
    This chapter describes the concept of domains and how to set them up and use them. It also includes information on using domain features across databases and across domains within a single database.
    Introduction to Shared-Services Domain
    Explains how domains are used as flexible implementation options to support multiple operations in single domains and lists potential impacts of combining operations in a single database and potential deployment methods.
    Domain Setup Overview
    Discusses how to implement domains and gives an illustrated workflow.
    Creating Database Records
    Explains the rules for creating database records in single- and multiple-database environments.
    Creating Domains
    Explains how to create domains and gives details on system domains, how to use multiple database validations, active and inactive domains, domain PROPATH, how to use Domain Maintenance (36.10.1), and how to view domain information.
    Changing the Current Domain
    Explains how to use Change Current Domain (36.10.13) with details on domain access and database switching.
    Associating Domains with Sites
    Discusses how domains and sites are associated as part of the site definition process.
    Setting a Default Time Zone
    Explains how to use Database Control (36.24).
    Giving Users Access to Domains
    Explains how to use User Maintenance (36.3.1) to create users and assign them access to domains.
    Configuring UI Settings
    Discusses how to configure and view domain-related information on the UI with details on setting display mode, updating program information, using ctrl+F to view information, and viewing session details.
    Using Cross-Domain Features
    Discusses how to use multi-database functions across domains and use features across domains in a database.
    Introduction to Shared-Services Domain
    Note: Shared Services Domain is a separately licensed module. Unless you purchase appropriate licences, the system prevents you from having more than one active domain per database.
    The domain concept in the database provides flexible implementation options for supporting multiple business operations within a single database and eliminates the need for a single database-wide base currency or database-wide control settings. The domain is essentially a logical partition within a single database. Any number of domains can be set up in one physical database—each domain with its own base currency, chart of accounts, operating controls, document numbering, and security.
    Domain Solution illustrates how multiple databases can be mapped into multiple domains within one database.

    Domain Solution
    Note: A database with one or multiple domains can continue to connect to another database also with one or multiple domains.
    Some system administration functions can be managed across domains, such as defining users, currency codes, country codes, menus, messages, and labels. This includes the ability for a system administrator to control exactly which users can access data in which domains. All other data updates take place within the context of a specific domain.
    Replication tools let system administrators synchronize common master data across domains, where appropriate. Processes that currently operate between databases can be used between domains within a database in a more streamlined and reliable manner. These processes include distribution requirements planning (DRP), enterprise material transfer (EMT), and enterprise operations planning.
    Combining operations in a single database can have the following advantages:
    Facilitate the standardization of business processes among operational units.
    Reduce IS costs as a result of having fewer databases to manage.
    Facilitate reporting and custom queries because all data is stored in the same table structure referenced by the domain field.
    Support data sharing.
    Each business can choose the most appropriate deployment method:
    A solution with a different database for each business operation
    A central solution with one database serving all
    Any combination of these