Code Search and Replace Reports (eB2.1 and later only)
Run this suite of reports/utilities only if you are converting from eB2.1 and later. If you are not converting from eB2.1 and later, go to
Set Conversion Parameters.
Use of these utilities and reports is optional (unless indicated in the Data Preparation Report), but recommended. They require that you run Table Extension Domain Update Utilities first.
The Code Search and Replace Reports are used to highlight conflicts in several areas that changed between eB2.1 and QAD Enterprise Edition, QAD 2007 and Enterprise Edition, and Standard Edition and Enterprise Edition.
Due to schema and architecture changes introduced in QAD Enterprise Edition, the scope of some data objects has changed from domain level to system level.
During the conversion, if two records exist with the same code in more than one domain, they are assumed to be the same and only one record is converted. As a result, some domain-level data could potentially be lost when converting a database with more than one domain.
The purpose of the Code Search and Replace Utilities is to provide a way to identify and correct instances of duplicate domain-level data.
Examples of Data Moved from Domain Level to System Level
• In QAD Enterprise Edition, addresses remain at the domain level, but map to business relations, which are at the system level in the new Financials. Each business relation must have a unique code.
• In QAD Enterprise Edition, entities remain at the domain level, but map to companies (now called entities) in the new Financials. The entity code must be unique in the database going forward.
• Before QAD Enterprise Edition, credit ratings were stored in the Generalized Code Master (code_mstr) table against field cm_cr_rating. Generalized Code Master is a domain-level table in eB2.1 and later. In QAD Enterprise Edition, credit ratings are stored in a new Financials table and become system-level data.
• Before QAD Enterprise Edition, customer and supplier types were stored in code_mstr against fields cm_type and vd_type. In QAD Enterprise Edition, customer and supplier types are stored in a new Financials table and become system-level data.
• Before QAD Enterprise Edition, voucher types were stored in code_mstr against field vo_type. In QAD Enterprise Edition, voucher types are called purchase types and stored in a new Financials table as system-level data.
• State and county codes are stored in the code_mstr against fields ad_state and ad_county. In QAD Enterprise Edition, states and counties become system-level data.
• Before QAD Enterprise Edition, tax classes were stored in code_mstr against field taxc_taxc. In QAD Enterprise Edition, tax classes are stored in a new table Tax Class Master (txcl_mstr) and become system-level data.
• Before QAD Enterprise Edition, tax usages were stored in code_mstr against field tx2_tax_usage. In QAD Enterprise Edition, tax usages are stored in the new table Tax Usage Master (txu_mstr) and became system-level data.
• Before QAD Enterprise Edition, tax types were stored in code_mstr against field txt_tax_type. In QAD Enterprise Edition, tax types are stored in a new table Tax Type Master (txty_mstr) and become system-level data.
• Tax zones are stored in the Tax Zone Master (txz_mstr) table. This table is a domain-level table in eB2.1 and later. In QAD Enterprise Edition, the domain field was removed and tax zones are system-level data.
• Tax environments are stored in the Tax Environment Master (txe_mstr) and Tax Environment Detail (txed_det) tables. In QAD Enterprise Edition, tax environments are system-level data. Before QAD Enterprise Edition, they were domain-level data.
• Credit terms are stored in the Credit Terms Master (ct_mstr) and Credit Terms Detail (ctd_det) tables. In QAD Enterprise Edition, credit terms are system-level data. Before QAD Enterprise Edition, they were domain-level data.
• Rounding methods are stored in the Rounding Method Master (rnd_mstr) table. Before QAD Enterprise Edition, they were domain-level data. In QAD Enterprise Edition, rounding methods are system-level data.
Duplicate Code Report (utsarrp1.p)
This report highlights codes (entities, credit ratings, credit terms, tax parameters, and so on) occurring in multiple domains. These codes were moved to the system level in QAD Enterprise Edition, and only one instance of each code can remain after conversion. This report allows you to identify any differences in the codes across domains. One execution spans all active domains.
The report output file name is utsarrp1-dtl-<dbname>-<date>_<time>.prn or utsarrp1-sum-<dbname>-<domain>-<date>_<time>.prn, depending on the report option selected.
Use the Replace Code Utility (utsarrp3.p) to correct any issues.
Code Usage Report (utsarrp2.p)
This report highlights the number of instances where a particular code is used in the current domain, providing more insight into the use and analysis of the code.
The report output file name is utsarrp2-<dbname>-<domain>-<date>_<time>.prn.
Use the Replace Code Utility (utsarrp3.p) to correct any issues.
Execute this report separately for each domain that is listed in the Duplicate Code Report with conflicts.
Replace Code Utility (utsarrp3.p)
Use this utility to replace specified code values in the current domain with a new user-specified value.
The report output file name is utsarrp3-<dbname>-<domain>-<date>_<time>.prn.
Warning This utility can have a broad effect on the system and future transactions, depending on the codes replaced. Use it with caution and only after backing up the database.