The following conversions are run automatically from MFG/UTIL. Where additional application information is available, a reference appears in the margins. If a conversion does not apply to your database—for example, you do not have commodity codes—the program runs quickly, updates nothing, and ends.

QAD Standard Edition conversions enable you to convert each of your source production databases to new physical databases with a primary domain defined for the target database and connection domain designations for connected databases. Primary domains reference the current database; connection domains point to domains located in other databases.

The addition of domains to the database affects most database tables and indexes. Conversion is required. The conversion:

Beginning with QAD eB2.1, new security features have been added that increase the access-control options available to system administrators—particularly when they are tasked with meeting the security requirements of external regulatory agencies.

New fields and tables have been added to support the security enhancements. Highlights of the conversion process include the following:

Using the sub-account length setting in Domain/Account Control (the gl_sub_len field in the gl_ctrl table), this post-processing conversion moves sub-account information to a new sub-account field. This conversion also saves elements of the source version account structure for use by the Global Tax Management (GTM) conversion programs.

See User Guide: Financials.

The euro data conversions require that you post foreign currency transactions in the source database and enter accounts for multicurrency transactions in the conversion function prompts. Two programs are then run during the target database conversion step to populate the database with euro data to comply with European Monetary Union requirements and the introduction of additional multicurrency functionality. If the Euro Toolkit is implemented in your source version, the conversion transfers the toolkit data to the euro tables in the target version.

See User Guide: Financials.

This conversion consists of a post-processing conversion program that moves fields from the QAD work table (qad_wkfl) to the new line allocation detail table to enable the MRP to Repetitive Approval Phase 2 functionality. It also requires several post-processing steps in the target database and launching a post-processing utility.

See User Guide: Manufacturing.

This post-processing conversion program converts PO receipt history into pending vouchers, loads voucher receipt history, and updates the indexes and key values.

The Service/Support Management (SSM) module has major changes to service contracts offering options for designing contracts, generating contract billing, and managing the general ledger (GL) effects of contracts. Implementing this requires a set of three post-processing conversion programs. Do not rerun these conversion programs.

See User Guide: Service/Support Management.

This post-processing conversion program converts intercompany accounts defined in the Inventory, Accounts Receivable, Accounts Payable and Fixed Assets Control tables to intercompany accounts defined for each entity master record.

This post-processing conversion program initializes the mrp_keyid field in the mrp_det table and assigns one mrp_det record with a keyid value. The conversion allows the MRP detail records to be indexed. A test using a line of Progress code is required to test whether the conversion was successful:

The conversion was successful if the code returns TRUE.

This post-processing conversion program updates the inventory site in the in_mstr table from the inventory General Ledger cost site in the same table: in_gl_cost_site = in_site.

This post-processing conversion program initializes the User Type and Access Location fields in the user master table (usr_mstr.usr_type and usr_mstr.usr_access_loc). This update is required to enable new User Maintenance (36.3.1) features such as time zones, country codes, and locations. The Location field is then initialized to Primary.

This post-processing conversion program populates the so_consignment field in the sales order master table (so_mstr). Initial data values are obtained from the so_conrep field.

This post-processing conversion program realigns the Kanban master and detail records, moving data from the master to the detail tables and converting data from integer to decimal values for greater precision.

Lean manufacturing upgrades the Kanban module to Lean Manufacturing. Any existing Kanban data is dumped to a dump directory and is reloaded into the new lean manufacturing tables during automated post-processing.

This post-processing conversion program updates the sod_cum_time in the sales order detail table.

This post-processing conversion program moves e-mail master data from the QAD work table, qad_wkfl, and properly updates the e-mail master table (em_mstr).

The commodity code conversion programs move commodity code data from your source version item master table (pt_mstr) and QAD work table (qad_wkfl) to the new target version corporate commodity code table (comd_det). These programs run during post-processing on the target database.

User groups in QAD Standard Edition are limited to 8 characters in length. Use the User Group Conversion utility to convert existing group name lengths to the correct length and to update security features that use groups, such as menus and sites. Run this program only after all other conversions have been run.