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 2008.1 – Standard Edition
    This release includes all ECOs closed between February 21, 2008 and November 7, 2008. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    Work Orders
    Work Order Components
    A new program, WO Component Check Report (16.14), has been added to expand the features available with Work Order Component Check (16.5).
    By entering a work order and ID, you can review component-by-component availability information, as well as a summary of component requirements for all orders due at the same time. When Detail is Yes, the report also lists all work orders that require one or more of the same components. If components have expiration dates before the work order due date, the system does not consider them available, but instead lists expired quantities in a separate column.
    Just as in Work Order Component Check, you can show all components, or limit the display to only components with calculated shortages.
    The new report also provides a simulation feature. To view the effects of additional, currently unscheduled component requirements, you can leave the work order and ID fields blank and enter an item number, quantity, release date, and optional BOM/formula code. The system generates a report showing component requirements from your new, simulated work order. Based on MRP detail records, it shows the simulated component requirements in the context of requirements from existing work orders, as well as other demand such as sales orders.
    You can also use the simulation feature with an existing order to examine what-if scenarios. For example, when you specify a work order and ID, the system fills in the site, order quantity, and release date from the work order record. You can modify these values to determine the effects of modifying the work order.
    Note: The report displays requirement and receipt data from MRP detail records. To produce up-to-date results, you should generate this report immediately after an MRP run.
    Additional Work Order Release Control
    A new inventory transaction type (REL-WO) has been added to prevent work orders for specified items from being released to the shop floor. For example, you might want to restrict from release any items that are going to be phased out or obsoleted in the near future.
    To use the new feature, use Item Status Code Maintenance (1.1.5) to identify one or more status codes that you want to associate with items that cannot have work orders released. Assign REL-WO to these codes as a restricted transaction, then enter one of these codes in the Status field in Item Master Maintenance (1.4.1) or Item Data Maintenance (1.4.3) for any item you want to prevent from being released on a work order.
    If you attempt to release an order for such an item in Work Order Maintenance (16.1), Work Order Release/Print (16.6), or Multiple WO Release/Print (16.7), the system displays an error message.
    Component Availability Check Collections
    Three new Component Check programs are embedded in browse collections in the QAD .NET UI environment:
    Component Check by WO/Production Line
    Component Check by WO/Work Center
    Component Check by Item/Work Order
    The Component Check browse collections consist of the following:
    Work Order Browse lists selected work orders along with component shortage severity status. The WO component status that displays is the most severe component status found among the components. The browse is located at the top of the screen.
    Work Order Component Browse lists work order components for a particular work order. Each component listed has a component shortage severity status associated with it. The browse is located at the top of the screen.
    Work Order Component Details contains Supply/Demand Detail and Supply/Demand Summary. The browses are located at the bottom of the screen.
    Supporting Business Process Browses and Programs. The default Component Check browse collections contain other supporting browses and programs. For example, Schedule Maintenance is provided so that you can quickly access and modify a scheduled quantity if a material shortage exists. Net Change MRP is also provided so that you can view results once you change the schedule, make a net change, and explode a schedule.
    Note: Programs and browses in Component Check by Item/Work Order differ slightly.
    The system calculates component availability for a work order component record by calculating projected quantity on hand (PQOH) using MRP supply and demand detail information. The calculation results display within the Work Order and Work Order Component Browses.
    The following topics discuss features of each Component Check browse collection.
    Component Check by WO/Production Line
    Production schedulers can use Component Check by WO/Production Line to quickly determine if the production schedule is viable for the week, month, or any specified period. For repetitive production schedules, they can determine if there are material shortages, which components are short and by when, or whether you have enough supply coming in to meet future demand. Production schedulers can:
    View production schedule data by any combination of site; production line or operation; item, due, or release dates; quantity complete, open, or ordered; and more.
    View both planned and scheduled orders associated with a production line.
    Identify which repetitive orders have material shortages related to them.
    Identify the components causing the shortage related to a repetitive order.
    Component Check by WO/Work Center
    Production schedulers who need to quickly determine component availability for discrete work orders for a particular work center can use Component Check by WO/Work Center. For discrete work orders, they can:
    View work order/work center data by any combination of site; work center or operation; item; due or release date; quantity complete, open, or ordered; and more.
    Identify which discrete work orders have material shortages related to them.
    Identify the components causing the shortage related to a discrete order.
    Locate and determine the cause of material shortages.
    View both planned and scheduled orders associated with a primary production line.
    View in-transit supply in the form of ASN receipts.
    Component Check by Item/Work Order
    Materials planners can use Component Check by Item/Work Order to quickly identify the components they manage and determine if there are shortages that impact production. Material managers or expediters typically use this program to ensure that there are no component shortages for scheduled production orders. They can view a list of items and the jobs (work orders) that are impacted by item shortages. Having this information helps keep production running and expedites order processing. Material planners use Component Check by Item/Work Order to:
    Select from a wide range of item attributes to include in the component check, such as buyer/planner codes.
    Identify which items have component or material shortages related to them.
    Identify the work order to which the shortage is related.
    Locate and determine the cause of material shortages.
    Product Structure
    You can use the new Expired Component Delete function (13.25.1, utpscdel.p) to delete specific expired components from product structures. Previously, you could only delete an entire product structure using Product Structure Delete/Archive (13.23).
    The new program lets you enter an item number as well a maximum expiration date for selecting records. Additionally, you can set Delete to No to review a report on the effects of the program before running it in update mode.
    Lean Manufacturing
    This release includes the following enhancements to the Kanban module:
    When you record a scrap quantity in Kanban Fill/Receive ( or Kanban Ship (, you can now enter a reason code set up in Reason Codes Maintenance (36.2.17) for type Scrap. A Multi field lets you enter additional reason codes.
    A new program, Kanban Quantity Audit Report (, lets you identify loops with cards on which the recorded quantity does not equal the kanban quantity. You can specify a tolerance percent to limit the selection to cards where the difference exceeds a given threshold.
    Transaction Delete/Archive ( has been modified to delete or archive Kanban Transaction Reject Detail (kbtrr_det) records when the associated Kanban Transaction History (kbtr_hist) records are deleted or archived.
    Several programs on the new Kanban Detail Maintenance Menu (17.22.22) let you directly access detail-level kanban setup information. Previously, you could maintain this information only by navigating through Kanban Master Maintenance (17.22.4) or Kanban Process Maintenance (17.22.3).
    An additional new program on that menu, Kanban Card By Kanban ID Detail, lets you access card information in the kanban master record based on an individual kanban card ID.
    The following table lists the new detail maintenance programs.
    Menu Label
    Program Name
    KB Mstr - Supermarket Item Detail
    KB Mstr - Accumulator Detail
    KB Mstr - FIFO Lane Detail
    Kanban Process Item Detail
    Kanban Card By Kanban ID Detail
    The way the system calculates per-piece costs for kanban controlled items has been revised. This change corrects a problem in the way setup costs were applied to individual kanbans and to the items produced against them.
    When multiple kanbans make up an order quantity for a kanban loop, there is only a single setup even though there will be multiple kanban fill transactions processed when the order is completed. In this situation, the single setup cost should be spread over all the authorized kanbans. If three kanbans make up the order or lot, one-third of the setup costs should be applied to each of the kanbans. In earlier versions of the system, the accounting logic applied the setup cost to each of the kanbans, substantially overstating the per-kanban cost as well as the per-piece cost for the item.
    The revised logic prorates the setup cost across the number of kanbans to calculate an accurate per-kanban cost. This is averaged over the number of units in the kanban to calculate the per-unit cost of the item produced.
    Price Lists
    You can now use the Minimum Order field (previously labeled Min Ord Qty) in Price List Maintenance ( to enforce a minimum item quantity on order lines. On sales orders, you can also track the reason a user chooses to override a system-generated warning message when the minimum order requirement is not met.
    When you set up a price list with Quantity Type set to Quantity and a minimum quantity specified, and best-pricing logic selects that list during order entry, the following programs validate the order, quote, or invoice line quantity against the Minimum Order value:
    Sales Order Maintenance (7.1.1)
    Sales Quote Maintenance (7.12.1)
    Pending Invoice Maintenance (7.13.1)
    RMA Maintenance (
    This updated logic applies only when the line quantity is greater than 0 (zero). Additionally, in programs other than Sales Order Maintenance, it applies only when Line Pricing is Yes on a new order, or you are modifying an existing order and Reprice is set to Yes.
    When the cumulative order quantity for any item number is less than the specified minimum for the price list, a warning message displays at the end of line-item entry.
    Note: When multiple price lists are selected for an item, the system applies the largest Minimum Order value.
    When Quantity Type is set to Amount, the system behaves the same way it did before this enhancement. If the total order currency value is less than the Minimum Order value, the system displays a warning message in the order trailer to provide an option to complete the order using the selected price list.
    Additional Sales Order Maintenance Minimum-Quantity Features
    In Sales Order Maintenance only, if the user chooses to continue using the price list after a below-minimum order warning displays, you can optionally have the system prompt for a reason code:
    Use Reason Code Maintenance (36.2.17) to define appropriate reason codes associated with reason type Ord_Chg.
    Set Keep Booking History to Yes in Sales Order Control (7.1.24).
    When you use this feature, navigation depends on the value of Line Pricing.
    Yes: The system displays a prompt after each line when a below-minimum quantity is entered.
    No: The system displays an additional frame before the trailer listing all lines on the order that do not meet minimum-quantity requirements. You can select a line number and specify whether you want to accept the quantity, then add a reason code and comment as needed.
    You can then use Booking Transaction Report (7.15.14) with Include Reason/Comments set to Yes to review the reason the user gave for entering a quantity below the specified minimum.
    Item-Level Tare Weight
    You can now enter a tare weight when you add an item to a pre-shipper, shipper, or container. Additionally, you can update the Tare Weight field on an existing line. This enhancement applies to Pre-Shipper/Shipper Workbench (7.9.2) and Container Workbench (7.7.1).
    Previously, you could not enter a tare weight during line data entry; it displayed as read-only after the line was entered. The tare weight could be updated only at the top level of the pre-shipper, shipper, or container.
    Tare weight is the weight of the container only, not counting the contents.
    Orders To Ship Report
    A new Orders To Ship Report (7.15.12) lets you view information about the following types of orders from a single program:
    Sales orders
    Material orders
    Customer scheduled orders
    Distribution orders
    Specify criteria to select orders based on required or due date, site, item number, and so on. For example, you can view all orders that are due to ship to a specific address code or from a specific site on a given day.
    Use individual fields to add customer schedules and/or distribution orders as needed. (By default, sales orders and material orders are always included in the report.) When you choose to include scheduled orders, you can select the order type. You can also control whether the report includes orders with memo item lines, as well as those that include a value in the Action Status field, such as orders on credit hold.
    Pallets on Shipping Documents
    A Total Pallets field has been added to the second header frames of Pre-Shipper/Shipper Workbench (7.9.2) and Sales Order Shipper Maintenance (7.9.8).
    You can use this field to record the number of pallets or skids that are included in a shipment so that it can be printed for reference on shipping documents. For example, you ship a total of six containers of merchandise, but your customer requests that you deliver it on pallets that hold two containers each. Enter 3 in the Total Pallets field.
    Three programs have been modified to print the Total Pallets label and value:
    Pre-Shipper/Shipper Print (7.9.4)
    Sales Order Shipper Print (7.9.9)
    Bill of Lading Print (
    New Reason Type
    A new RTV (return to vendor) reason type has been added to Reason Code Maintenance (36.2.17) that lets you define reason codes that can be specified in Purchase Order Returns (5.13.7). Additionally, a new lookup browse has been added to the Reason field in Purchase Order Returns that limits the selection to reason codes associated with type RTV.
    This requires a change to QAD-provided system data. The new reason type is loaded during installation.
    Retained Taxes on Printed PO Returns
    A new Include Retained Tax field has been added to Purchase Order Return Document Print (5.13.8). Set the field to No to have the system suppress printing of retained tax amounts from the output and exclude taxes from totals. When the field is Yes (default), the system includes retained taxes on the documents, as it did before the field was added.
    Retaining taxes is a common practice in some countries. For example, when customers in the European Community send POs to suppliers outside their national boundaries, taxes are typically retained. Customers of these suppliers pay the purchase amount minus tax to the supplier but are required to calculate, post, and periodically pay the tax amounts on their purchases directly to the government of the supplier’s country.
    EDI eCommerce
    New Audit Reports
    A new Export Audit Reports menu (35.4.6) has been added. You can use these programs to view information about exported documents. Specific details vary by document type; for example, the ASN report includes the site, shipper number, ship-to address, and shipping date, as well as status data. All reports include batch information.
    The following table lists the new audit report programs.
    Menu Label
    Program Name
    ASN Export Audit Report
    Invoice Export Audit Report
    Order Export Audit Report
    Schedule Export Audit Report
    Order Ack Export Audit Report
    Improved File Selection
    In Document Import (35.1), you can use a new File Mask field and wild cards to specify one or more patterns (for example, *.gen) that file names must match to be selected. The system generates a list of matching files found in the EDI Inbound Directory specified in eCommerce Control (35.13.24), and you can make your final selection.