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  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • QAD 2007 (MFG/PRO eB2.1 Service Pack 5)
    This release includes all ECOs closed between January 27, 2006, and October 6, 2006. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    Repetitive and Advanced Repetitive
    A new Allow Zero Run Rate field has been added to Repetitive Control (18.24) and Advanced Repetitive Control (18.22.24). It lets you define a global run rate in Production Line Maintenance (18.1.1 or 18.22.1.1) that applies to all items on the line.
    When the new field is Yes, the Units/Hour field at the item level in Production Line Maintenance defaults to 0 (zero). The system then uses the production line-level Units/Hour to determine the item run rate. If you change the item-level value, the system uses that run rate for the specific item only. This lets you define item-level run rates by exception—using the production line-level rate for the majority of items.
    Leave Allow Zero Run Rate set to No (the default) to have the system behave as it did previously. The Units/Hour field for new item records defaults from the production line value. Although you can update it, you cannot set it to zero. The system always uses the individual item value to determine the run rate.
    Purchasing
    The Exclude Unconfirmed Vouchers field in Unvouchered Receipts as of Date (5.13.10) has been relabeled Unconfirmed Vouchered Receipts to more accurately reflect the field’s purpose.
    Enter Yes (the default) to include in the open quantity any amounts from receipts that have been matched with a supplier invoice but are unconfirmed. These amounts do not update the GL so they are typically considered still open and included in the report.
    Enter No to exclude receipts that have been matched with an invoice but are not confirmed.
    Consignment Menu Changes
    Two consignment inventory programs have been moved to utility menus:
     
    Menu Label
    Program
    Old Location
    New Location
    Consignment Inventory Adjustment
    pocnadj.p
    5.18.21
    5.18.25.21
    Consignment Inventory Adjustment
    socnadj.p
    7.18.21
    7.18.25.21
    These programs were designed as limited-use functions that only adjust consignment balances without affecting such elements as inventory valuation, general ledger, and quantity on hand. They are typically used under very specific, limited circumstances. Moving them to utility menus makes it less likely that users might inadvertently run them without knowing that they are not adjusting all the transactions related to the sales or purchase order business cycle.
    Accounts Payable
    This service pack includes the following enhancements to the Accounts Payable module.
    AP Aging Reports
    A new List Type field has been added to the selection criteria in AP Aging by Voucher Date Report (28.17.4), AP Aging by Due Date Report (28.17.5), and AP Aging as of Effective Date (28.17.6).
    Note: This field was already present in the equivalent aging reports on the Accounts Receivable (27) menu.
    Support for New Canadian Check Printing Requirements
    This service pack enhances Payment–Automatic Checks (28.9.9) to support recent changes in check format standards defined by the Canadian Payment Association. The new standard calls for checks to be printed with an extended date format, which appears on its own line above the numerical amount of the check, including a Date label.
    To comply with the modified requirements, set the new Use MM/DD/YYYY Date field to Yes. The default is No; you can update the field only when Check Form is 1 or 2.
    Regardless of the value of the new field, the program has been modified to include a dollar sign ($) before the amount.
    Service/Support Management
    This service pack includes several SSM enhancements.
    Contract Revenue Accounts
    Invoice Post (7.13.4) has been modified so that it posts deferred or accrued revenue for contracts to the appropriate accounts associated with the service type product line for the individual contract lines. Previously, the system consolidated all deferred or accrued revenue from all contract lines to the account associated with the product line assigned to the contract service type.
    To support this change, three new fields—Revenue Account, Revenue Sub-account, and Revenue Cost Center—have been added to Contract Quote Maintenance (11.5.1.1) and Contract Maintenance (11.5.13.1). Default values for the fields depend on the revenue type:
    Cash: The fields default to blank and cannot be updated.
    Deferred or accrued: Based on the level at which accounts are defined, the fields default from the associated revenue account fields in Sales Account Maintenance (1.2.17), Product Line Maintenance (1.2.1), or Domain/Account Control (36.1). You can update the fields only when Modify Sales Accounts is Yes in Contract Control (11.5.24).
    Additionally, a new utility, Update Contract Revenue Account (11.5.13.25.5, utsarrv.p), lets you modify line records on existing contracts that have end dates later than the current date to update the additional fields. Invoices can then be posted correctly during the next processing cycle. The utility does not affect existing deferred revenue records.
    Contract Billing
    Sales Order and Line fields have been added to the contract line detail frame in Billing Date Correction (11.5.18.19).
    The new fields expand the functionality available when you need to correct a billing error by reversing an unposted contract invoice in Billing Reversal Maintenance (11.5.18.18).
    Previously, Billing Date Correction only let you update the sales order at the contract header level. If necessary, you can now update the sales order and line associated with a contract line in Billing Date Correction before reversing the invoice.
    CAR Effective Date
    An Effective Date field has been added to Call Activity Recording (11.1.1.13). Use it to record the date when transactions created by the program are effective in the GL. It is included in the frame where you specify the output device for the report generated during inventory processing.
    Previously, the system date was always used as the GL effective date.
    The new field defaults to the current date. When Verify GL Accounts in Yes in Domain/Account Control (36.1), the specified date must be in an open GL calendar period.
    For example, in some cases the engineer may perform the labor on a call several days before the record is updated in Call Activity Recording. The new field lets you make the labor transactions affect the GL on the same day the labor was performed.
    EDI ECommerce
    Naming inconsistencies in QAD-provided records defined in Trading Partner Parameter Maintenance (35.13.10) have led to processing issues with some types of documents.
    After installing the service pack, use a new utility, Trading Partner Para Desc Update (36.13.25.2, utrplpd.p), to correct these inconsistencies.
    Important: Program code throughout the EDI ECommerce module is updated by the service pack to use the corrected values. If you install this service pack, you must run the utility.
    When you run this program, the system updates all character and integer parameter records with the following abbreviations. This both makes the naming consistent and allows more room for text strings in the 25-character field:
    Document is changed to Doc.
    Change is changed to Chg.
    Ver is changed to Vers.