QAD 2017 Enterprise Edition > Installation-Conversion > Conversion Guide > Pre-conversion > Set Conversion Parameters
  
Set Conversion Parameters
Conversion Parameters Utility (utfinpar.p)Conversion Parameters Utility (utfinpar.p)
This utility prompts you for values for the parameters used in the QAD Enterprise Edition conversion when creating new financial objects. Customers converting from eB2.1 and later with multiple domains may want to provide a different set of values for each domain. For eB2.1 and later, run the utility in each active domain, regardless of whether values differ by domain.
Most these parameters are for daybook codes used in various areas of the applications. Other parameters are items such as default credit terms, sub-account, cost center, and so on. You can specify some parameters by domain whereas others are system level and apply to all domains.
Since there are so many parameters, QAD suggests running this utility well in advance of the conversion to allow ample time for planning and decision making. The following table lists the parameters along with a brief explanation of each. eB2.1 and later users could find it helpful for planning purposes to extract this table to a spreadsheet with one column per domain.
If new validations were added to the utility since it was last run, the Data Exists flag for parameters with existing values is set to No. This behavior causes a warning to appear when the utility starts because the existing values are treated as invalid. Attempting to reaccept an invalid parameter displays an error message that explains why the parameter is no longer valid.
Rerun the utility as often as needed and delete or change values.

New Financial Object Parameters
 
Level
Parameter
Use
Domain
Default AR Finance Charges Daybook
Default daybook code to use for this daybook type. If Finance Charges are not used, this parameter is not required.
Domain
Default AR Credit Note Daybook for Operational Invoices
Default daybook code to use for this daybook type
Domain
Default AR Credit Note Daybook for Financial Invoices
Default daybook code to use for this daybook type
Domain
Default AR Invoice Daybook for Operational Invoices
Default daybook code to use for this daybook type
Domain
Default AR Invoice Daybook for Financial Invoices
Default daybook code to use for this daybook type
Domain
Default AR Payment Daybook
Default daybook code to use for this daybook type
Domain
Default Customer Adjustment Daybook
Default daybook code to use for this daybook type
Domain
Prefix for AR Tax Register Daybook Sets
The prefix to use when creating AR Tax Register Daybooks Sets
Domain
Prefix for AP Tax Register Daybook Sets
The prefix to use when creating AP Tax Register Daybooks Sets
Domain
Default AP Credit Note Daybook for Financial Invoices
Default daybook code to use for this daybook type
Domain
Default AP Invoice Daybook for Financial Invoices
Default daybook code to use for this daybook type
Domain
Default ERS Supplier Invoice Daybook
Default daybook code to use for this daybook type. This prompt only appears if ERS is used.
Domain
Default ERS Supplier Credit Note Daybook
Default daybook code to use for this daybook type. This prompt only appears if ERS is used.
Domain
Default AP Payment Daybook
Default daybook code to use for this daybook type
Domain
Default Intercompany Daybook
Default daybook code to use for this daybook type. Specify a daybook code for each functional area (IC, FA, Inventory, SO, and WO), but they can the share code if desired.
Domain
Default Matching Entry Daybook
Default daybook code to use for this daybook type
Domain
Default Banking Entry Daybook
Default daybook code to use for this daybook type
Domain
Default Inventory Daybook
Default daybook code to use for this daybook type
Domain
Default Work Order Daybook
Default daybook code to use for this daybook type
Domain
Default Sales Order Daybook
Default daybook code to use for this daybook type
Domain
Default Fixed Assets Daybook
Default daybook code to use for this daybook type
Domain
Default Daybook for Journal Entries
Used for any domain that has not previously used daybooks when converting GL transactions. Note: This parameter is a new daybook code that the conversion creates and not one of the default daybooks specified previously.
Domain
Default Daybook Sequence Effective Date (MM/DD/YYYY)
The earliest date when the new Financial daybooks can be used.
This value is also used for operational daybooks if daybooks were not used before the conversion. Therefore, set the date to the earliest of the first open transaction or contract.
Domain
Account for Posting Balances
The conversion uses this account when it balances any unbalanced double-sided GL transactions. The account where such offsets are posted.
Note: This is a new account that does not exist in the database. This account is created automatically during the conversion process.
Domain
Account for Year-End Balances
New account the conversion creates for posting the offset to year-end closing entries.
Domain
Account for Results of Current Year
This account is used to accumulate the YTD profit/loss total for printing on the Balance Sheet.
You are only prompted for this account if GL transactions have been posted to the Profit/Loss Account (BS) (co_ctrl.co_pl) in General Ledger Control (25.24, glcopm.p).
If prompted for this account, it must be an account with no transactions posted against it. It can be a new account. If so, the conversion creates it.
If you are not prompted for this account, the conversion uses co_ctrl.co_pl.
Domain
Account for Current Year Income Offset
This prompt only appears if the GL Report Writer is not used or no account was assigned for this purpose in that module. If prompted for this account, it must be new and not exist. The conversion creates it.
Domain
Account for Results of Previous Years
The conversion creates this account. It is used to accumulate the profit/loss total for previous unclosed years when printing the Balance Sheet.
Domain
Default Account for Unmatched Invoices
Default GL account to use for Unmatched Invoices. If using European Accounting, the use Waiting Expenses account in European Accounting Control (25.23, eueupm.p) defaults to this field and the user cannot modify it. If not using European Accounting, specify a new account to create during conversion.
Domain
Default Sub-Account
Default sub-account to use when an account requires a sub-account. Note: This is a new value that does not exist in the database. See also COA Mask.
Domain
Default Cost Center
Default cost center to use when an account or sub-account requires a cost center. Note: This parameter is a new value that does not exist in the database. See also COA Mask.
Domain
Default Project
Default project code to use when an account, sub-account, or cost center requires a project code. Note: This parameter is a new value that does not exist in the database. See also COA Mask.
Domain
Default Credit Term
Used when an invalid credit term is referenced against a source record.
Domain
Convert Unused Cashbooks?
Should the conversion convert “not used” cashbooks (for example, ba_mstr records where ba_status = “NU”)?
Domain
Create Entity Tax Periods?
Should the conversion create Tax Periods for each entity?
If this option is selected, the conversion creates the Tax Periods that are the same as the existing GL Periods.
System
Default Tax Class for Suspended Tax
The default tax class to use for Suspended Tax. This prompt only appears if the European Accounting module is in use. SP3 and above only.
System
Reporting Currency
This parameter is used as the default value for the Reporting Currency in QAD Enterprise Edition Financials.
System
Country for default Tax Box
Country code for the default Tax Box used in Tax Reporting
System
Source directory for Payment Format XML files
The directory from which the Payment format XML files are loaded. This option only appears if the source database uses European Accounting.
System
Convert existing security?
Should the conversion convert the existing security or convert Users, Groups, and allow the user to re-implement the security after the conversion?
You can exit the utility without providing all of the answers, but you must complete it before running the conversion.
The report output file name is utfinpar-<dbname>-<domain>-<date>_<time>.prn.
This utility does not affect the system or future transactions. It only creates QAD Work Table (qad_wkfl) records.
Pre-conversion Completion
Converted GL Account Definitions Report (glacdfrp.p)
This optional report provides a preview of how the Enterprise Edition Financials will define your accounts after conversion. You cannot run this report until you have completed the Control Account Utility, GL Account Type Utility, and GL Project Account/Project Utility (if pre-eB). You also must have entered the account parameters into the Conversion Parameters Utility.
Process Pending Transactions
Process pending transactions as follows:
1 Print any pending invoices (Pending Invoice Print, 7.13.3, sosorp10.p).
2 Post any remaining invoices (Invoice Post, 7.13.4, soivpst.p).
3 Confirm all unconfirmed vouchers (Voucher Confirmation Automatic, 28.6, apvoco01.p; Voucher Confirmation Manual, 28.7, apvoco.p).
Note: This step is optional. See Unconfirmed Supplier Vouchers.
4 Post all GL transactions (Transaction Post, 25.13.7, gltrpst.p).
Close the Production Database to Users
Use Menu Security (36.10, mgpwmt.p) to prevent the addition of new data to the database and further transactions.
Rerun Pre-conversion Integrity Report (gpinckrp.p)
Rerun the Pre-conversion Integrity Report. See Pre-conversion Integrity Report (gpinckrp.p).
Rerun GL Account Type Utility (uxglacup.p) in Update Mode
1 Rerun the GL Account Type Utility in Update mode (in all active domains for eB2.1 and later). See GL Account Type Utility (uxglacup.p).
An error displays if the GTM Conversion was not done and conflicts were found in the accounts from the obsolete tax tables (tax_mstr, vt_mstr). The utility is not flagged as complete until the GTM Conversion is done. Run this utility again to check for conflicts involving accounts in the new tax table Tax Master (tx2_mstr).
2 Resolve any new conflicts.
Run the Converted GL Account Definition Report (glacdfrp.p)
This report provides a preview of how the GL accounts and their key attribute settings will look after the conversion. Use the output from this report to more accurately plan and prepare a company’s GL account data before conversion execution.
You can only execute this report after you run the following utilities:
• Control Account (uxctrl.p)
• GL Account Type (uxglacup.p) (in update mode)
• Conversion Parameters (utfinpar.p)
• GL Account Project Code (if pre-eB)
The report is provided for informational purposes and is not mandatory. For versions eB2.1 and later, the report content is specific to the domain in which the report was initiated.
This report has no effect on the system or future transactions. You can run it as often as desired.
Standard Period Closing Reports
Although their use is optional and does not directly affect the conversion, QAD recommends that you run the standard period closing reports for later comparison with the equivalent post-conversion reports. This action helps ensure that the conversion did not change the data. The standard period closing reports are as follows:
• Trial Balance (25.15.4, gltbrp.p or 25.15.5, gldtbrp.p)
• Balance Sheet (25.15.8, glbsrp.p)
• Income Statement (25.15.13, glinrp.p)
• AR Aging as of Effective Date (27.18, arcsrp05.p)
• AP Aging as of Effective Date (28.17.6, apvorp04.p)
• AR Tax by Tax Rate (2.13.15.14, txarrp01.p)
• AP Tax by Tax Rate (2.13.15.17, txaprp01.p)
• AR Balance Report (27.20, arcsrp.p)
• Inventory Valuation (3.6.13, ppptrp03.p)
• Unvouchered Receipts Report (5.13.10, poporp11.p)
• Purchase Receipt Report (5.13.5, poporp06.p)
• Asset Owned Report (32.5.11, faaorp.p)
• Sales Order Report (7.15.1, 2 or 3, sosorp.p, sosorp01.p, sosorp02.p)
Rerun (Finalize) Data Preparation Report
Rerun the Data Preparation Report to ensure that no errors were introduced. Correct the data until no errors are present.