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 Glossary

  • QAD 2010 – Standard Edition
    This release includes all ECOs closed between June 12, 2009 and June 11, 2010. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    .NET UI Updates
    QAD 2010 Standard Edition is supported by the new version 2.9.1 of the QAD .NET UI.
    Among other changes, this .NET UI release includes a change to the way in which Assistance Panel content is delivered. In earlier versions, all language-specific Assistance Panel content was delivered on the .NET UI release media. For QAD 2010 Standard Edition, however, Assistance Panel content will be provided with the associated language-specific Standard Edition installation media.
    For information on this change as well as other .NET installation and application changes, see Release Notes: QAD .NET User Interface.
    QAD Reference Architecture
    QAD 2010 Standard Edition introduces the QAD Reference Architecture (QRA), a library that standardizes the way APIs are exposed and called. QRA is automatically added to your configuration during QAD Standard Edition upgrade. Depending on your configuration, the presence of QRA may require that you reconfigure and rebuild the .NET UI following an upgrade.
    New EDI eCommerce Features
    This release includes several new EDI eCommerce features.
    New Repository Collection
    In the QAD .NET UI, you can now use Maintain eCommerce Repository Data to view and update EDI eCommerce repository and status records from a single workbench-style access point. Previously, you were required to look up cross-references between sequence numbers and view or maintain repository records from separate menu-level programs.
    In the initial browse window, use standard .NET UI filtering functions to limit the selection of documents displayed by process date, status, document direction, trading partner ID, and several other criteria. Next, select a record from the main browse window. The system populates the Sequence ID field in each of the five associated programs (shown as tabs below the browse window) based on the selected record.
    After selecting a record, you can use the workbench functions to:
    View status and processing messages in either the exchange or application repository. (In earlier versions, the application repository was called the MFG/PRO repository.) This is similar to the standard Exchange Doc Status Inquiry and Application Doc Status Inquiry programs, with some added functionality: You also can update the Passed/Failed status in either repository. Additionally, you can select an Ignore field, which makes the document unavailable for reprocessing through either the workbench Document Reprocess program or the menu-level Import Reprocessing/Export Reprocessing programs.
    Modify information in the associated exchange or application repository document. The two workbench repository maintenance programs are very similar to the menu-level Exchange Data Repository Maint and Application Data Repository Maint functions. The main difference is that the workbench programs display less read-only data because it is available in the main browse window.
    Reprocess the updated records in both repositories using values that you have updated in the other programs. This is similar to the menu-level Import Reprocessing and Export Reprocessing functions; the exception is that Document Reprocess only reprocesses the selected document. Note that reprocessing only takes place on the repository level. To re-import or re-export a file, use Document Import (35.1) or the appropriate program—based on the document type—from the Document Export menu (35.4).
    New Sequence Number Functionality
    The database sequences previously used to provide ID numbers for repository documents have been replaced by much more robust functions, which use existing Number Range Management (NRM) features.
    The programs on the new eCommerce Number Range Menu (35.21) work the same way as those on the standard Number Range Menu (36.2.21), with one exception: the eCommerce programs manage sequence IDs in the eCommerce processing domain.
    NRM sequences are more flexible than database sequences, which were significantly limited for customers with a very large volume of EDI transactions. In addition to supporting significantly longer number strings, NRM offers additional options such as a fixed segment at the beginning of the number to identify its type.
    Note: To support this new functionality, the repository sequence number data type was changed to Int64 to allow a larger number range. You must therefore update any user-defined functions in your configuration to change the data type of the tt_ht_seq variable in the temp table tt_ht from integer to int64.
    Create sequence IDs in EC Number Range Maintenance (35.21.1), then reference them in control and trading partner records. New frames in eCommerce Control (35.17.24) let you specify default sequence IDs used to generate document numbers in the inbound and outbound exchange and application repositories. Another field lets you specify a sequence ID for generating documents with processing errors. Optionally, you can override those values in another new control frame, in which you define sequence IDs that are used for a specific application, such as JITS.
    In Trading Partner Maintenance (35.13.7), you can optionally override the control program sequence IDs on the trading partner or trading partner document level.
    When generating a number for a repository document, the system looks for a sequence ID in the following order:
    The trading partner document definition in Trading Partner Maintenance
    The main trading partner definition in Trading Partner Maintenance
    The Application frame in eCommerce Control
    The eCommerce Transaction Control frame in eCommerce Control
    Enhanced Error Reporting and Handling
    Several new fields have been added to the new eCommerce Transaction Control frame in eCommerce Control. They provide more flexibility in the way the system handles and reports errors during processing.
    Three fields set defaults for new records in Trading Partner Maintenance. You can override these settings at the trading partner, trading partner document, and trading partner location cross-reference level:
    Suppress Warnings. Enter Yes to prevent the system from generating status messages that result from warning conditions during transformation or gateway processing.
    When this field is No (the default), the system always generates warnings in the status message table.
    Stop on Error. Enter Yes to have the system stop processing a document during transformation when the first error is encountered. The system skips the rest of the document and moves to the next sequence number.
    When this field is No (the default), processing continues regardless of the number of errors that occur.
    Suppress Session Report. Enter Yes to prevent the system from generating a session report following document load or unload.
    When this field is No (the default), the system always generates session reports.
    In the new Send E-mail on Error Only, enter Yes to have the system send e-mail only when the document does not process successfully. Otherwise, e-mail is sent regardless of document status. This field defaults to new trading partner location cross-reference records defined in Trading Partner Maintenance.
    eCommerce Control also now includes an E-mail Address field. Use it to enter the e-mail address of the person who receives a message when an error occurs during an import or export session.
    Transformation Map Editing
    New editing functions have been added to Transformation Definition Maintenance (35.15.17). You can now update transformation event records—along with several other related actions—without deleting and re-entering them.
    The functions include:
    Edit Current Record. Use this option to update a transformation map event. You can change the event type, qualifier, target, source, and sequence. If the event action calls a function, you can reset the parameter values or change to a different function.
    Delete Block. In this option, specify a range of event sequence numbers to be deleted from the current record.
    Create Gap. Use this option to create a gap of a specified length in sequence numbers after the selected event and renumber the subsequent events. For example, if focus is on event action sequence 60 and you set the Create Gap Of field to 100, the system adds 100 to all the subsequent events in the current record. So, if the next sequence numbers were 70, 80, 90, the system would set the sequence numbers for the record to 60, 170, 180, 190, and so on.
    Renumber. This option performs the same function as Transformation Renumber Utility (35.17.3). The system prompts you for an Interval—the new starting sequence number for each record in the transformation map, as well as the increment between event sequences. For example, if you set Interval to 5, the system renumbers the events in each record as 5, 10, 15, 25, 35, and so on.
    Copy Block. Use this function to copy a specified range of event actions to the current transformation map or any other map in the system.
    The new functions are available from all user interfaces:
    In QAD .NET UI, choose an option from the Actions menu.
    In the character and Windows UIs, use the appropriate keyboard shortcut:
    Character Shortcut
    Windows Shortcut
    Edit Current Record
    Delete Block
    Create Gap
    Copy Block
    Document Definition Creation Program
    You can use the new Create eCommerce Doc Definitions program (35.15.4) to:
    Copy an exchange file, application, or implementation definition to create one or more definitions of the same or another type.
    Create one or more document definitions based on:
    A temp-table definition in Progress syntax from either Progress source code (.p or .i file) or a .txt file
    An XML document (.xml file)
    An XSD document (.xsd file)
    Previously, you could only create definitions by loading a trading partner library entry, creating a definition record manually, or copying an existing definition to create another of the same type.
    Additional Changes
    The Non-Printable ASCII Character field has been removed from eCommerce Control. This character, used during transformation to separate the table name from the field name, is no longer user configurable. The system now uses a fixed value of chr(2).
    Three print option defaults have been added to the initial frame of eCommerce Control. You can override the values when running reports.
    Three new fields have been added to Transmission Group Maintenance:
    File Name Counter. Specify the sequence ID that is used to assign file names to files exported to this transmission group. This must be a valid sequence ID defined in EC Number Range Maintenance.
    Capitalize Outbound Data. Enter Yes to convert the data in exported files for this transmission group into all capital letters.
    Target Code Page. Specify the code page required by the receiving application for files sent to this transmission group. When creating the export file, the system converts the data as needed to match the specified code page.
    An optional Source Code Page field in eCommerce Control lets you specify the default code page used to import data into your system. During import processing, the system converts the data to the system code page. If you enter a value, it defaults to EC Subsystem Definition Maintenance. You can update it as needed for individual subsystems.
    Note: Code page fields are not validated. The specified code page must be included in the Progress file DLC/convmap.cp. Otherwise, the conversion program returns an error.
    A new Application ID field has been added to allow for the separation of documents for viewing and reporting in the data repositories. Application ID is assigned in Trading Partner Maintenance. The available application IDs are EDI, EMT, DOM, SV, JITS, MEW, and FIN.
    Group and Document Group fields have been added to Trading Partner Maintenance. You can use them to associate the current trading partner or document with others for reporting purposes.
    Some user interface changes have been made to improve usability:
    eCommerce Control has been reorganized for clarification. A new frame has been added to enter counters at the Application ID level.
    Trading Partner Maintenance has been reworked to include additional frames. This provides space for more meaningful field labels.
    New Programs
    New Programs for EDI eCommerce lists the programs added to support EDI eCommerce enhancements.

    New Programs for EDI eCommerce
    .NET only
    Maintain eCommerce Repository Data
    Create eCommerce Doc Definitions
    eCommerce Number Range Menu...
    EC Number Range Maintenance
    EC Sequence Browse
    EC Sequence Number Maintenance
    EC Sequence Number History Report
    EC Sequence Delete/Archive
    Enhanced Kanban Workbench Functionality
    Two new .NET kanban workbenches have been added to replace the functions of the HTML-based Kanban Workbench. Kanban Sizing Workbench and Kanban Process Workbench offer similar functionality while taking advantage of native .NET features to provide a much easier-to-use interface. Additionally, the new workbenches feature significantly improved performance.
    Note: Like Kanban Workbench, the new functions are available only through the QAD .NET UI—not other user interfaces.
    The new workbenches include the following major improvements over Kanban Workbench:
    A Search frame lets you select records using flexible .NET UI filtering tools, instead of simply entering values in a fixed number of selection criteria fields. Additionally, you can filter on different criteria in each workbench, so record selection in Kanban Process Workbench is very specialized.
    After you set up filters, an alternative Navigation panel offers a tree-structure view of the available records. You can click on nodes to further refine the list shown in the grid.
    Like Kanban Workbench, the new workbenches offer the option of viewing and updating data in an Excel-style spreadsheet interface, but in a more efficient layout.
    Separate workbenches allow the loop sizing and process grids to be separated, making the width of the grid more manageable. In Kanban Workbench, process and sizing records were displayed in a continuous grid that required extensive horizontal scrolling to view or update.
    The grid portion of Kanban Sizing Workbench includes only sizing data, although important process-related fields are still shown in the new tabbed frames.
    Kanban Process Workbench divides process data into two separate grids, process and process-item detail. Additionally, the loop sizing grid is also available in that workbench—providing a complete picture for process items.
    The workbenches are more configurable. Although Kanban Workbench offered some configurability—for example, you could control whether individual columns displayed, as well as the sequence—the new workbenches take advantage of .NET features to allow much more flexibility. For example, you can drag-and-drop columns into position, or hide individual tabbed frames. Additionally, after you have set up a workbench in the way you like, you can save it. As needed, you can save multiple configurations under different names for reuse based on different situations.
    The new workbenches also display data in individual tabs, in which fields are grouped logically based on their functions. The layout of fields and frames is designed to indicate the relationships between calculated fields and source values. Note that the majority of grid fields display on the tabs. However, a limited number of values display only in the grid.
    For the most part, the workbenches display the same data. Major differences are:
    The search criteria. In the Sizing workbench, you can search on several criteria related to kanban loops sourced by processes, exernal suppliers, or inventory supermarkets. The Process workbench provides search criteria to let you drill down to specific kanban processes.
    The information available in the grid. The Process workbench shows process, process-item, and loop sizing data for each process found by the search criteria. The Sizing workbench is limited to the same loop sizing data.
    The values you can update. For example, you can view process information related to a specific loop in the Sizing workbench for reference. However, since the process typically supports several loops, you must use the Process workbench to modify related values. When a field is modifiable in one workbench but not the other, the read-only version is shaded in gray.
    Enhancements to QAD Reporting Framework
    The infrastructure that supports reporting from operational and financial functions has been improved in several areas.
    The report template logic has been enhanced to support inheritance of top-level properties from templates, which is useful for scenarios where you want to control paper size and margins using a central template. For example, Letter paper reports can all be switched to A4 with one template change.
    Case-insensitive grouping is now supported.
    Group sections can now inherit template classes from other types of template sections. For example, a GroupHeader section can now inherit from a template PageHeader section class.
    The Report Resource Designer has been enhanced to allow metadata export, data export, and data import from a file. On the toolbar, choose Actions and click Export Metadata, Enable Data Export, or Enable Data Import. This feature is very useful for testing and troubleshooting. For instance, you can now supply test data from an XML file for testing without having to create the specific types of test data in the system database.
    For Label fields, the Reporting Framework can now intelligently select from short, medium, and long translated labels in the system. Alternatively, you can explicitly specify which type of label to use for a particular field, including stacked labels. The previous release of the Reporting Framework only supported long labels.
    You can now convert an integer in a calculated field into the words for that integer. For example, the integer 123 can be converted into the text string “one hundred and twenty three.” In the Properties window, when editing a field, add an N the Text setting. For example, change ${Sales Order} to ${Sales Order}N.
    You can now include the base currency on the report. To do so, in the Report Designer, in the Data tab’s Report Settings, click on the sys_base_currency parameter and include it anywhere on the report.
    Previously, logical values in reports were rendered as Yes or No rather than True or False. In this release, the reports now display the appropriate labels for the logical values as defined in the metadata. For example, the logical values will be True or False, or Debit or Credit, depending on what label is appropriate for the logical value.
    Fixed Assets Enhancement
    The Depreciation Adjustment frame of Fixed Asset Maintenance (32.3) lets you adjust the salvage value.
    When you click the Adjust button to adjust a fixed asset depreciation book, you can now specify Salvage as the adjustment type, and the Adjustment Amount field lets you enter the salvage adjustment.
    The Fixed Asset Maintenance, Depreciation Query frame displays any changes to the basis or salvage value. Fixed Asset Transaction Post (32.13) reflects salvage adjustments in the GL posting.
    Modified Programs
    Modified Programs for Fixed Assets lists the modified fixed asset programs.

    Modified Programs for Fixed Assets
    Fixed Asset Maintenance
    Fixed Asset Transaction Post
    New Inventory Location Update Utility
    You can use the new Inventory Location Update program (, utinloup.p) to add a value to the Location field in Item-Site Inventory Data (1.4.16 ) if the field is empty. This will prevent a large number of “Location Does not Exist” errors.
    Additional Enhancements
    New Field in GL Report Writer Control
    GL Report Writer Control (25.21.24) includes a new field, Display Acct with Zero Balance, that controls the display of accounts not used in transactions when you run your custom GL report using Run Report (25.21.17).
    Restriction Removed on Custom Field Help Records
    Field Help Maintenance ( has been modified to remove the restriction on the length of a supplemental record you can enter to augment QAD-provided help records with your custom content.
    Previously, the program prevented you from entering more than 15 lines of text.
    Documentation Updates
    Documentation-related changes in this release include:
    Content updates to reflect changes in the software.
    Reformatting of PDFs and printed documents. If you view or download PDF files from the Documentation area of, you will notice that the page format has been modified. Instead of the previous 7 by 9-inch page size, the documents are now sized to the width of standard A4 paper (about 8.25 inches) by 11 inches high.
    Because the new pages hold more content, the books now require significantly fewer pages. In addition, regardless of your location, the new page size lets you print PDFs on standard paper sizes (A4 or 8.5 by 11) without the large margins previously created by the smaller page size.
    Additional overview information. The summary list of topics at the beginning of user guide chapters now includes a brief description of each major topic.
    Structural changes in the user guide set:
    A new volume, Introduction to QAD Enterprise Applications, has been added. It includes a brief overview of both editions (Standard and Enterprise), as well as QAD .NET UI and character UI information of interest to typical users. The new book also includes a glossary of terms used in the user guides and the product.
    The contents of the QAD User Interfaces user guide have been redistributed into two new books:
    The portions that apply to daily use of the .NET UI (as well as the discussion of the character UI) have been moved to the new Introduction volume.
    Technical implementation and administrative aspects of the UI are now covered in the new Administration Guide: QAD .NET UI.
    A new EDI eCommerce user guide has been added. Its chapters were previously included in the Release Management user guide, which still provides information on Customer Schedules and Supplier Schedules.
    The Distribution A user guide is now simply called Distribution.
    The Distribution B user guide is now called Consignment Inventory.
    The Financials A user guide is now simply called Financials.
    The Financials B user guide is now called Fixed Assets.
    The SSM A and SSM B books have been renamed; they are now SSM Part 1 and SSM Part 2.
    A new user-assistance tool. In addition to QAD Assist (F1 in the .NET UI) and context-sensitive field and procedure help (F2 in the character user interface and F1 in the Windows UI), a new Guide Me tool is available to .NET UI users. When you mouse-over most field labels in the system, a tool tip displays the initial portion of the field help record. A More link lets you display the entire record as needed.
    Additionally, users whose menu permissions let them access Field Help Maintenance can click an Edit link. This allows them to add supplemental information to the existing QAD-provided help records.
    Note: The Guide Me feature is disabled by default. See Administration Guide: QAD .NET UI for information on enabling Guide Me functionality.