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  |   On Demand  |   Home  |   qad.com




Working With Multiple Domains and Business Units
In implementing QAD domains in QAD CRM, the approach was taken to extend the usage of business units in CRM to assume the domain function. (In versions of CRM prior to 6.3, there was an indirect mapping between a single Enterprise Applications domain and a single CRM business unit.) However, the underlying assumption in CRM is that every domain in Enterprise Applications will map directly to a business unit in CRM of the same name. This mapping is created when CRM is installed and whenever a new domain is created in Enterprise Applications or a non-active domain is activated.
This can be seen diagrammatically as follows:

Remote Sales
This diagram also helps to illustrate the fact that most master data and all transactional data in QAD CRM is segregated by business unit. So Profiles, Opportunities, Activities and Marketing Campaigns all relate to a business unit. When sales orders or SSM calls are raised and they are passed to CRM via the integration, they are associated with the domain of their origin. This becomes the business unit that they reside in within QAD CRM.
The few exceptions to this rule are primarily system-wide configuration data such as Users and Integration Control files.
In common with domains in Enterprise Applications, when users are logged on to the system the data that they can see is confined to the business unit that they have logged on to. If they need to review or update data from another business unit, they need to re-logon to the other business unit.