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 2009 – Standard Edition
    This release includes all ECOs closed between November 7, 2008 and June 12, 2009. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    QAD Reporting Framework
    This release of QAD Enterprise Applications introduces a brand new reporting framework with comprehensive tools that lets you easily create simple reports from multiple data sources, design complex or specialized reports, and customize the way you want to run your reports and send them to various output destinations.
    Note: Enhanced features available in QAD Reporting Framework are designed to work with the QAD .NET user interface.
    Multiple Data Sources
    The QAD Reporting Framework supports a range of data sources. You can extract data from Progress databases, browses, or through APIs for reporting purposes.
    Powerful and Flexible Report Authoring
    The QAD Reporting Framework offers you both simplicity and flexibility in creating your reports.
    Built-in Report Wizard guides you step by step through building basic reports and completing common reporting tasks. Report Designer and Template Designer provide you with a rich set of report design tools to create more complex reports tailored to your specific requirements. Columns, groups, calculated fields, subreports, and formatting help make sense of data and uncover important relationships that might otherwise be hidden.
    Multiple Output Formats
    The flexibility of the QAD Reporting Framework does not end with creating reports. Your reports can be published to a variety of outputs including printer, PDF, and Excel files.
    Report Scheduling
    You can schedule the system to run your reports automatically at a certain time or at a specified interval and send scheduled report outputs to your desired destination, such as a printer or the QAD .NET UI document service on the report server. You can also have the system notify you that your scheduled reports have run.
    Report Filters
    When running a report, you can set filter criteria to filter data in the generated report. The filter criteria can be saved as your personal filter so that you can load the same set of filter conditions the next time you run the report.
    New and Modified Functions
    The following new functions have been added in this release.
    Menu Number
    Program Name
    Scheduled Report Maintenance
    Scheduled Report Browse
    Scheduled Report History Browse
    Report Settings Restore
    The following functions have been modified.
    Menu Number
    Program Name
    Report Resource Maintenance
    Report Synchronization
    Report Parameter Maintenance
    Admin User Filter Maintenance
    Personal User Filter Maintenance
    Service and Support Management (SSM)
    Depot Order Functionality
    SSM now includes the ability to handle depot orders (repairs). Typically a depot order is defined as activity that occurs in-house at the site of the manufacturer or distributor, rather than at the site of the end user. Repair activities that take place at the customer site are usually defined as constituting field service repair.
    A depot order may require a replacement part to be sent to the customer before the damaged part is received in-house. A depot order also requires the defective part to be tracked when received in-house for repair from the customer.
    As with any repair, the repaired items may or may not be covered by a warranty contract. Chargeable labor, material, and miscellaneous expenses may be incurred during evaluation and repair processes. Changes to installed base records must be recorded timely and accurately.
    Depot Order Collection
    You can use the new Depot Order collection in the QAD .NET UI to access programs that let you record and monitor depot orders as they progress through the system. Typically the collection will be used by employees who have a shop floor role, and customer service representatives when working with customers.
    Note: Collections are designed specifically for the QAD .NET UI. They do not work with other UIs.
    The Depot Order collection consists of the following browses:
    Depot Order browse - Lists customer-returned items for repair or replacement. The browse displays the call/order ID, item number, end user, status, receipt date, shipment date, and so on. This browse drives the records displayed in the other browses listed below.
    Parts List browse - Displays parts list records, including item number, description, and quantity.
    Material Order browse - Displays material order-related information, including sold-to and order date information.
    Call Labor Recording browse - Displays labor activity-related information, including start and end time, engineer, work code, and service category.
    Depot Inventory Tracking browse - Displays inventory tracking information for the item, including unit of measure, lot/serial information, site, and transaction type (repair or replacement, receipt or shipment).
    Functionally related programs are available by right-clicking entries in the browses. For example, right-clicking an entry in the Material Order browse allows you to launch the new Material Order ATP Inquiry using the currently selected record as the default. Depot order-related programs also display in the application menu.
    Depot Order Maintenance
    A new program, Depot Order Maintenance (, has been created to enable the creation and maintenance of depot orders.
    Important: Depot orders cannot be created manually: a depot order is a service call that is associated with a work code that has its Repair Center field set to Yes.
    The header frames of Depot Order Maintenance contain fields that display information defaulted from the call: call/order ID, sold-to, bill-to, name and address, and ship-to information. Other fields are used to record receipt and delivery data. By default, the system sets the Confirmed field to Yes to enable items to be shipped against this order; a Confirmed setting of No indicates that customer authorization for the repair has not yet been received. Other fields on the header contain tax environment, salesperson, and freight-related information.
    When entering information about a specific line item, you indicate the repair type for the item (Repair or Replace). If Replace is selected, the system automatically generates a second depot order line with a repair type of Replacement.
    You use the Item Repair Data frame to record information about the item repair; for example, if the repair type is Replacement, you can specify an alternate item ID. The alternate item ID would then be used by the system when a repaired end-item is returned to inventory (that is, restocked) rather than sent back to the customer. Restocked items often use an alternate item ID to indicate they are restocked, rather than new, items.
    You also can use the Item Repair Data frame to record BOM code, routing, service type information, and pricing information. You can use either fixed pricing or time and materials pricing types.
    Use the Item Receipt frame to record receipt information for the returned item: receipt date, quantity, site, and so on. The Item Shipment frame displays read-only information such as line, activity (Rpr Rcpt or Rpr Ship, for example), actual date of shipment, quantity, and so on. This shipment data is updated when the repair or replacement item is shipped out using sales order shipments or the workbench.
    If a depot order line is identified as being a replacement repair type, an MO is created automatically for this line using the alternate item ID if one has been specified on the depot order; otherwise the material order uses the item ID. The remainder of the information required to create the MO defaults from the depot order/call. The system uses existing credit checking functionality to ensure that the order does not exceed authorized credit limits.
    Use the new Depot Order Browse ( to view information about current depot order records, such as status of the call/call line, receipt, and shipment dates.
    Call Parts Recording
    The new Call Parts Recording ( program allows parts to be issued/consumed from a parts list or parts to be returned that were consumed previously. For example, at the end of a repair call, an engineer can use Call Parts Recording to return items previously identified in error as being consumed in Call Activity Recording (CAR).
    Returning the items reverses the original consumption activity and updates the quantity to return on the associated MO.
    After entering the call ID and call line—these fields are populated automatically if Call Parts Recording is accessed from the Parts List browse—if a BOM is associated with the call line, you are given the option of exploding it. Exploding the BOM populates the item ID and quantity. If the BOM is associated with a labor routing, the system issues a warning that the BOM will not be exploded as part of the Call Parts Recording process (but will continue to be done in CAR).
    After selecting the items to process, indicate the items consumed and the quantity to return. Optionally you can record details about the consumed items and the returned items by using the Item Usage Detail and Item Return Detail screens.
    On exiting the screens, fault code information can be entered. The system prompts for the effective date and destination for the report output, and then processes the items.
    The system handles items to consume like this:
    Selecting a quantity to consume for an item with a material order causes that MO line to be shipped and updates CAR with the consumption of the item.
    Selecting a quantity to consume for an item without an MO updates CAR with the consumption of the item.
    The system handles items to return like this:
    Selecting a quantity to return for an item with an MO causes the item to be received back into inventory. CAR is updated to indicate the item is not consumed.
    Selecting a quantity to return for an item without an MO (on the parts list only) returns the item to inventory and updates CAR to indicate it is not consumed.
    Call Labor Recording
    To record labor for inspection and repairs against a depot order call, use the Call Labor Recording ( program. Typically an engineer records labor after evaluating an item that has been returned by a customer, and then again later when repairs to the item are complete. Labor activity can be recorded by call/call line or effective date.
    Labor activity for existing records can be modified as long as the record is not closed. You can modify duration, start time, and end time, but cannot change the date of an existing labor activity record. For example, the duration may need to be modified if it was overestimated and needs correcting. A second line can be entered for the same Operation ID as the first line, using a negative value for the new line in the Duration field; the start time or end time must also be adjusted accordingly.
    Note: If the call labor record is associated with a call report that has already been invoiced, but the invoice has not yet been posted and printed, the system issues a warning that the invoice has been generated, and prompts you to continue to edit the call record. Responding Yes causes the Ready to Invoice field to be set to No in Call Invoice Recording (
    Call Labor Recording does not support recording activity for service items. Instead, use Call Activity Recording (
    Call Labor Recording is available from the Labor browse in the Depot Order collection and from the application menu.
    Use the Call Labor Browse ( to view existing call labor activity records.
    Material Order ATP Inquiry
    You can use the new Material Order ATP Inquiry (11.11.7) program to view available-to-promise (ATP) information associated with a specific material order and lines. Right-clicking a record in the Material Order browse causes the inquiry to run using the currently selected record.
    Specifying a material order displays all unconfirmed material order lines whose due date is less than or equal to the date specified. If a material order line is not specified, all MO lines display. MO lines may be skipped if:
    No due date is specified for the MO line.
    Site security does not allow the current user to view the line.
    The line is an EMT part, a configured part, or ATP enforcement for the line is None.
    The system generates a report to the output device you specify.
    Material Order Control
    A new field, Consume Shipped Lines, has been added to Material Order Control (11.11.24). This field is used in material order shipments to automatically consume the items that are shipped. The field defaults on the header from the control program.
    The Consume Shipped Lines field has three possible values:
    Consume all Material Orders - Enables the automatic MO Shipment/CAR consumption for all material orders.
    Consume all Depot Material Orders - Enables the automatic MO Shipment/CAR consumption only for depot material orders. (These are orders associated with calls that have a work code with Repair Center set to Yes.)
    Do Not Auto Consume - Auto-consumption is not enabled.
    Material Order Shipment
    Several new fields have been added to Material Order Shipment (11.11.6) to enable the optional consumption of items that are shipped. This ability means you do not have to explicitly consume MO parts in CAR. Consumption takes place against open calls only; if the call is complete or closed, no consumption will occur, even though the MO can be created and shipped.
    The MO consumption report displays the details of the items consumed and any errors encountered during the consumption process. Any lines that remain unconsumed due to errors must be corrected and consumed within CAR. Transaction history is created for consumed lines.
    The following fields are new:
    Consume - Set this field to Yes to cause the items to be consumed.
    Consume Shipped - This field on the line detail frame defaults from the field above. Set this field to Yes to cause this line to be consumed.
    Consumption Report Output - This field lets you specify the output option for the Consumption report.
    Depot Item Restocking
    You can use the new Depot Item Restock ( program to restock inventory with items that were originally returned by customers, repaired in-house, and then restocked in refurbished inventory.
    Restocked items may have a different item number to indicate that the item is a refurbished—as opposed to new—unit. You can give an item that will be restocked a different item number by entering a value in the Alternate Item Number field in Depot Order Maintenance.
    Depot items must be received before they can be restocked. If required, you can update site information.
    Only depot order lines that have a complete status can be restocked. The line selected is passed to the Receipts–Return to Stock (3.11) program. The installed base is updated to reflect that the item was restocked into inventory and removed from the customer’s installed base.
    Depot Order Shipment
    After the item is repaired and ready to ship, the existing sales order shipment and pre-shipper workbench screens are used to ship the item to the customer.
    The shipment of the item is prevented if:
    The Confirmed field is set to No, indicating that the order has not been accepted by the customer.
    The shipment is on credit hold.
    The depot order line status is not complete. The order status can be set to Complete if there is an open material order. The order status cannot be set to Closed unless the material order is for a Replacement line.
    The actual date of shipment records is updated. After the item ships, the invoice ISB is updated while printing and posting occurs.
    Use the new Depot Inventory Tracking browse to review depot order, item ID and description, quantity and unit of measure, lot/serial number, end user ID, site (receipt or shipment, depending on the activity), location (receipt or shipment, depending on the activity), transaction type, and transaction date.
    Depot Order Invoicing
    A depot order line can be invoiced when the line status is complete and Ready to Invoice is set to Yes. Ready to Invoice cannot be set to Yes if any of the following apply:
    Open MOs are associated with the depot order (with the exception of MOs for a line that has had, or will have, a replacement part shipped out against it).
    An outstanding item receipt quantity is due from the customer for that depot order line (for example, a replacement unit was sent and the customer never returned their broken unit for repair, which was part of the agreement).
    Customers must manually update the status of the depot order/order line to Closed.
    As part of depot order invoicing, you can update the service type on the depot order line if no activity has been posted against the order/call, or if the order/call status is complete and is ready to invoice. The service type cannot be changed if the line has been either partially or fully invoiced.
    The service type for a replacement item cannot be updated: it is read-only. This ensures that the service type of the replacement item matches the service type of its associated replace item.
    If you change the service type, the system check to see if the inventory, work order, and service GL accounts associated with the new service type product line are different than those GL accounts associated with the old service type product line. If they are the same, no further processing is required. But if the GL accounts are different, the system:
    Reverses any associated WO or IC transactions already created for the call/call line.
    Creates new WO/IC transactions that use the product line inventory, WIP, and GL accounts associated with the updated service type.
    This ensures that the inventory history and GL transaction activity are synchronized and posted to the correct product line accounts.
    Reverses any other labor, item, or other expenses posted against the call in CAR that require reversing.
    All transactions created after the service type is changed are posted to the GL accounts associated with the product line of the new service type.
    The GL effective date for these reversing/correcting transactions defaults to the effective date for the original GL transaction; this date can be modified if required (or if the original GL posting period has been closed). The effective date for the reversing transaction defaults from the old effective date if the GL period is open; otherwise it defaults to the system date.
    New Programs
    New Programs for Depot Orders lists new Depot Order programs.

    New Programs for Depot Orders
    Call Labor Recording
    Call Labor Browse
    Call Parts Recording
    Depot Order Maintenance
    Depot Order Browse
    Depot Inventory Tracking Browse
    Depot Item Restock
    Parts List Browse
    Material Order ATP Inquiry
    Contact Center Collection
    The new Contact Center Collection in QAD .NET UI allows access to a variety of related SSM browses, reports, and functions that assist customer service representatives (CSRs) in executing their daily work. This collection actually consists of three separate collections: one each for Customers, Installed Base, and Calls. Together, these collections provide CSRs with a working environment that not only improves efficiency, but provides for a higher level of customer service by giving the CSRs the right information at their fingertips.
    Note: Collections are designed specifically for the QAD .NET UI. They do not work with other UIs.
    The Customer Collection consists of the following:
    All Call Browse - Lists all of the open and closed calls for the selected customer
    Installed Base Browse - Lists the items in the customer’s installed base
    Contract Browse - Displays customer contracts
    End User Move - Allows the movement of an installed base item from one end user to another end user
    End User Inquiry - Provides address information and credit data for selected end user
    Customer History Report - Provides an overview of the customer repair order history
    The Installed Base Collection consists of the following:
    All Call Browse - Lists all of the open and closed calls for the selected item/serial number
    Installed Base Inquiry - Provides a quick listing of the installed base items for a selected end user
    Installed Base Item Tracking History - Provides a detailed listing of the transactions associated with a specific installed base item
    Installed Base View - Displays detailed information about the installed base end user
    The Call Collection consists of the following:
    Call Detail Inquiry - Displays all of the details about a specific call in a view-only format
    Material Order Browse - Displays all of the material orders created for the selected call
    Call Print With History - Displays complete tracking of call status, assigned engineer, and problem identification throughout the call life cycle
    Call Labor Browse - Displays the repair labor activity that has been recorded against the call
    Parts List Browse - Displays the list of parts needed to complete the call repair
    Functionally related programs are available by right-clicking entries in the browses. For example, right-clicking an entry in the All Call Browse allows you to launch Call Maintenance or Depot Order Maintenance. Right-clicking on the Material Order Browse allows you to launch the new Material Order ATP Inquiry, or review the Material Order Shipment Report.
    Invoice Post Utility
    A new utility, Stranded Invoice qad_wkfl Delete (7.25.6, utinvpst.p), is now available to delete stranded QAD Work Table (qad_wkfl) records created when Invoice Post (7.13.4) is aborted abnormally.
    You can run the program in simulation mode to identify the records that will be deleted. When update is Yes, the system deletes stranded records from the current domain.
    1099-MISC Form
    The 1099-MISC Magnetic Media Report ( has been updated to conform to reporting requirements for tax year 2008. In the Transmitter “T” record, two fields, Cartridge Tape File Indicator (positions 409-410) and Transmitters Media Number (411-416), were deleted. These positions are now blank.
    Lean Manufacturing
    Use the new Stop Accumulator Monitor program ( to gracefully stop Accumulator Monitor ( Previously, you could only stop the process by terminating the user session that was running it.
    EDI eCommerce
    Trading Partner Library Load and Unload
    Trading Partner Library Load (35.17.7) and Unload (35.17.8) have been enhanced to add flexibility to the way you can create and load sets of trading partner document records. These new tools extend the existing Trading Partner Document Load and Unload functions by generating and loading XML files that contain more comprehensive sets of trading partner documents and supporting records.
    Unloading Records
    Trading Partner Library Unload now generates one XML file containing all the trading partner setup data—in addition to the file definitions and transformation map—rather than 19 individual files with different file extensions. You can control which domains, trading partners, and trading partner documents are included in the exported files. The system creates one XML file for each document.
    Note: This program does not check or enforce data integrity. For example, you can choose to export document definitions but not the associated transformation definition.
    This program is typically used by EDI system administrators to create source files that can be uploaded for submittal to the QAD Trading Partner Library. They can then be downloaded and used to create new sets of trading partner records using Trading Partner Library Load.
    Use the first frame to select the documents that will be written to XML files. At three levels of granularity (domain, trading partner, trading partner document), you can either have the system export all the records, or manually select the records from a list by setting the associated field to Select Some. On each level, when you choose to select records manually, you can specify filter criteria to limit the items that are selected by default when the list is displayed.
    From the selection list, use the space bar to toggle the Export field between Yes and No in the character UI. In the QAD .NET UI, use the check box to select records. When you finish selecting records at each level, press Go or click Next to move to the next selection field.
    You also can specify which prefix the system adds to the exported XML files. When Use TP Domain as Source ID is Yes, the file name is in the form domain name-trading partner ID-document ID .xml. When the field is No, you can add your own prefix in the Source ID field; this replaces the domain name.
    The program creates an activity log for each document in the specified dump directory. It shows the document definitions that were unloaded, a list of any non-QAD functions needed to support transformation, and any error messages that were generated during processing.
    Additionally, if transformation processing calls for user-defined functions, the system attempts to find the program files in the Function Directory specified in eCommerce Control. If it finds the files, it includes the source code in the XML file. The functions can then be created during the load process.
    Loading Records
    Trading Partner Library Load now lets you load XML files created using the unload program.
    Note: The program still allows you to load records created using the old multiple-file method.
    You can select individual trading partner documents from a list, or load all the documents in a specified directory at the same time. Source files are typically downloaded from the online QAD Trading Partner Library.
    Optionally, you also can decide which specific components of the XML files have records created in the destination domain.
    Note: This program does not check or enforce data integrity for records you choose not to import. For example, you can choose to create document definitions but not the associated transformation definition. This does not cause the import process to generate an error message.
    Use the first frame to identify the source directory for imported files, as well as the domain to which domain-specific types of records will be loaded. To select all documents in the directory, leave Import set to Select All. If you want to select from a list of documents in the specified directory, set Import to Select Some to display another frame when you press Go. When you finish selecting documents, press Go.
    Note: To select a single file, you also can press the up and down arrow keys with the cursor in the Import field. The system scrolls through all the documents in the specified directory. When the document you want to load displays, press Go.
    Use the Components field to control which specific types records are created as a result of the load. When that field is Select All, the system loads all of the records from each selected XML file. Set the field to Select Some to display a list of available record types. Deselect any types that you do not want to load.
    You can also control whether the source ID (stored in the XML file when it was created using Trading Partner Library Unload) is used as part of the new record names. If you choose to use it, you can specify whether it appears as a prefix or as a suffix.
    Subsequent frames display several types of information about the document currently being loaded. You can update many of the fields as needed. Note that navigation may vary depending on whether you choose not to create some types of records.
    The system determines if cross-reference records exist for the specified target domain. You are prompted to create new cross-references if required. If no target domains are available, the system prompts you to select an existing eCommerce domain as the target.
    Only when the target domain has not had eCommerce Control initialized, the next frame displays the fields from that program. You can update default values as needed; an additional field lets you specify the process log directory that will be associated with the newly created EC subsystem record.
    If one of the fields includes a directory that does not exist, the system prompts you to create it. If you respond No, you can still enter the directory path and create it later in the file system.
    When you load multiple documents during a single session, this frame displays only when the first document is loaded. Control settings apply to all the documents in the target domain.
    For outbound definitions only, the system next displays Transmission Group Maintenance fields. If required, you can edit them, or change the Name field to associate a different existing transmission group with the trading partner. If you update the directory path or subsystem, the system validates the new values.
    The system then displays the trading partner ID from the load data and prompts you to change it before proceeding.
    The Trading Partner Document Records frame displays. As required, select a record to update TP location cross-references.
    The program checks for any existing definitions that match the data being loaded and displays a list of duplicates, along with an Overwrite setting. If the trading partner definition is a duplicate, it is listed first, with Overwrite set to Yes. If you change the field to No, the system cancels the load process for this trading partner.
    All other duplicate records have Overwrite set to No. For each one that you change to Yes, the system displays information about where the existing record is used and prompts you to rename the new record, overwrite the existing record with the new definition, or keep the existing one.
    The system prompts you to apply the update.
    If the document references user-defined functions, the system compiles the code and saves the files in the function directory specified in eCommerce Control.
    If multiple documents are selected for loading, the system repeats the load process for the next document on the list.
    After you have completed all the documents, the system lists the files that were loaded. It also indicates whether any errors occurred. A log file called filename -import.log is created in the specified input directory.
    New Update Utility
    Update Token Variables (35.17.20) lets you update existing trading partner records with the most recent tokens. You can use this function as part of ongoing system maintenance when updates to the transformation engine modify or add tokens.
    This program was previously not delivered with the product.