Using Multi-Database Functions Across Domains
A number of functions update data in more than one domain or database. Database switching is automatically initiated when the domain associated with one of the sites referenced in the function exists in a different database. The system determines the database involved based on information defined in Site Maintenance (1.1.13).
This section discusses three such functions and points out the differences in how they work across domains rather than across databases.
• Enterprise Material Transfer (EMT)
• Distribution Requirements Planning (DRP)
• Enterprise Operations Planning (EOP)
Using Enterprise Material Transfer
When Use Enterprise Material Transfer is Yes in Sales Order Control (7.1.24), you can create EMT sales orders. EMT automatically translates sales orders into purchase orders. You then transmit them to the appropriate supplier using EDI ECommerce. EMT also manages and coordinates changes so that sales order and purchase order information is synchronized.
See User Guide: Distribution for details.
Multi-level EMT manages orders across multiple levels within an organization. Order changes can be made at the top or bottom of the hierarchy and are then transmitted up or down to the next level.
EMT can function between business organizations in one domain, in different domains within the same database, or in different databases. The way EMT functions in these various scenarios is basically the same. However, if the related business units are represented by different domains within the same database, it becomes easier to use the direct allocation feature of EMT.
With direct allocation, the primary business unit (PBU) can make a special, temporary allocation of an EMT sales order or material order line item at the secondary business unit (SBU) site. When the SBU imports the PBU’s EMT purchase order to create a secondary sales order, the system automatically converts this temporary allocation to a general allocation.
When the different business units in an EMT relationship are in separate databases, direct allocation can be used only when the business partners use the same version of QAD Enterprise Applications and when the databases are connected.
The following list summarizes the scenarios supported for EMT:
• Within a single database where the PBU and SBU are within the same domain.
• Within a single database where the PBU and SBU are in different domains.
• Across multiple databases where the PBU and SBU are in different domains.
• Across multiple databases where the PBU is in a database with domains (later versions of QAD’s ERP application) and the SBU is in a database on an earlier release. In this case, direct allocation cannot be used.
• Across multiple databases where the PBU is in a database without domains and the SBU is in a database with domains. In this case, direct allocation cannot be used.
Note: The SBU could also be using a non-QAD system. Direct allocation is not supported in this scenario either, regardless of the PBU’s application version.
Using Distribution Requirements Planning
In a multiple database environment, you can use DRP to plan supply to meet demand for multiple sites within the current database and distribute demand to other connected databases. DRP can be used only under the following conditions:
• The base currencies of the databases are the same.
• Taxes do not need to be calculated.
• Customs documentation is not needed.
See User Guide: Supply Chain Management for details.
You can also use DRP to plan supply to meet demand for multiple sites within a single domain, and to distribute demand to:
• Other sites within the current domain
• Other sites in other domains within the same database
• Other sites in connected, remote databases
The execution of DRP with domains does not require any special setup. The system determines whether database switching is needed based on the domain associated with the site in Site Maintenance.
If all of your domains are located in one database, the DRP process is simplified since you never have to be concerned about database connections not being available. In this case, the following functions are not needed:
• Intersite Demand Validation (12.17.12), which is run at the supply database to search for all changes to intersite demand that occurred in the demand database while the database connection was not available
• Intersite Demand Transfer (12.15.9), which is used to transfer system-generated intersite requests to the supply site’s database
• Intersite Demand Export (12.15.10), which is used to place demand records in an ASCII file to send to the supply site
• Intersite Demand Import (12.17.10), which is used to import demand records in an ASCII file into the supply site’s database
Using Enterprise Operations Planning
Functions in the Enterprise Operations Planning (33) module let you plan for end items and family items for multiple sites both within a single database and across multiple connected databases. With Shared Services Domain, you can also execute planning functions for sites in multiple domains within a single database.
See User Guide: Supply Chain Management for details.
The execution of Enterprise Operations Planning with domains does not require any special setup. The system determines whether database switching is needed based on the domain associated with the site in Site Maintenance.