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 – Standard Edition
    This release includes all ECOs closed between July 27, 2007 and February 21, 2008. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    Support for New Double-Byte Codepages
    QAD 2008 - Standard Edition includes support for new double-byte Progress codepages for Simplified Chinese, Traditional Chinese, and Korean.
    Previous Codepage
    New Codepage
    Simplified Chinese
    Traditional Chinese
    The new codepages include the character codes in the previous codepages and also include additional characters.
    Pending Invoices
    A Consume Forecast field has been added to the header and line levels in Pending Invoice Maintenance (7.13.1). The header field defaults to Yes; new line records default from the header. On existing orders, the line Consume Forecast value defaults from the order line, but you can modify it as needed.
    Previously, when you entered an order directly in Pending Invoice Maintenance, the system automatically used forecast consumption logic. Additionally, although the setting from existing order lines was stored in the pending invoice record, the field did not display in the user interface and could not be updated.
    Unvouchered Receipts
    A new PO Site selection range has been added to Unvouchered Receipts as of Date (5.13.10). This lets you generate a report for reconciling receipts in cases where the purchase order site and the receiving site are not the same.
    Previously, you could only generate a report based on the receiving site.
    Customer Address on Shippers
    A new Print Customer Address field has been added to Pre-Shipper/Shipper Print (7.9.4) and Pre-Shipper/Shipper Workbench (7.9.4).
    The default is Yes; the customer address code and name print on the shipping document. This was the system behavior before the new option was added.
    Set Print Customer Address to No to suppress the address code and name on the printed document. For example, this supports a direct-ship scenario in Enterprise Material Transfer (EMT). In that case, the customer address is actually the primary business unit (PBU) that recorded the order—not the real end customer. You can suppress the address code on the shipping document to avoid confusion when the end customer receives the order.
    Cost Sets
    Based on a new Sum Costs to MTL TL for DRP field in functions that copy cost sets, you can now copy and sum production costs from the manufacturing site to the distribution site. This new feature is available in the following programs:
    Current Cost Set Move to GL Set (1.4.22)
    Current Cost Set Move to Current Set (1.4.23)
    Current Cost Set Move to GL Set (1.4.22)
    Cost Set Copy to Cost Set (30.3)
    Simul Item-Element Cost Copy (30.13.9)
    Item-Element Cost Copy (30.17.9)
    When Sum Costs to MTL TL for DRP is Yes, the system rolls up this/lower-level costs into this-level (TL) material costs during the copy process. Otherwise, costs are copied as-is—the system behavior before this field was added.
    For example, the new feature lets you build subassemblies at one site, ship them to a second site, and continue the manufacturing process without requiring manual updates to the subassembly cost.
    EDI Customer Schedules
    A new EDI Update RSS field has been added to the Non-Cumulative Accounting Data frame of Scheduled Order Maintenance (7.3.13).
    When both this field and Merge RSS are Yes, the system updates the required ship schedule (RSS) after importing a ship schedule in Document Import (35.1).
    Note: The new field defaults to No. You can update it only when Merge RSS is Yes.
    Previously, you could update the RSS using Required Ship Schedule Update (7.5.5) or Selective Req Ship Sched Update (7.5.6). However, depending on how frequently you run the import process, it is possible to miss some requirements when you do the update manually. Updating the RSS at the same time the schedule is imported and merged avoids this problem.
    Lean Manufacturing
    This release includes several updates to the lean manufacturing features of the Kanban module.
    Kanban Master Copy
    A new Copy Number of Cards field has been added to Kanban Master Copy (17.22.8) to provide flexibility in the way loop records are copied.
    When this field is Yes (the default), the system creates the new loop record with the same number of kanban cards as the source loop. For two-card loops, both replenishment and move cards are included. This was the system behavior before the new field was added.
    Set the field to No to create the new loop with the Number of Cards field set to 0. You can then update the number in Kanban Master Maintenance (17.22.4) or Kanban Workbench (
    Note: This setting only controls the value of the Number of Cards field. You still must use standard card management functions to actually create the cards for the new loop.
    Inventory Transactions
    For loops supplied by a kanban process, Kanban Ship ( and Kanban Fill/Receive ( have been modified to record backflush and subcontract inventory transactions closer to where they occur in the workflow.
    Note: These changes only affect process loops on which Component/Op Transactions is Yes in Kanban Master Maintenance (17.22.4).
    When your business process uses Kanban Ship, backflush and subcontract inventory transactions for the operation range defined now take place when the card is shipped, instead of during fill/receive.
    Kanban Fill/Receive now looks at the status of the card to determine how much backflushing and subcontract work has been completed.
    If all of the ship transactions were skipped, Kanban Fill/Receive does all of the backflushing and subcontract inventory transactions.
    If some of the ship transactions have been done, but not all, Kanban Fill/Receive finishes where the ship transaction ended, and does the backflush and subcontract inventory transactions for the processes remaining to be done.
    If all of the ship transactions were completed, Kanban Fill/Receive does not do any backflush or subcontract inventory transactions.
    Example: A process has one primary process, P1, and two FIFO processes, Fifo1 and Fifo2. With the new transaction processing, the workflow is as follows:
    When P1 is shipped to Fifo1, all of the backflush and subcontract inventory transactions at P1 are recorded.
    When Fifo1 is shipped to Fifo2, all of the backflush and subcontract inventory transactions at Fifo1 are recorded.
    Fifo2 is skipped.
    When the fill transaction is done, backflush and subcontract transactions are recorded for Fifo2 because it was skipped. (This step also does the receipt of the parent item.)
    The release includes a conversion utility associated with this feature. See Kanban Conversion Utilities.
    Scrap Recording
    New fields have been added to Kanban Ship and Kanban Fill/Receive to let you record the actual quantity, rather than the kanban quantity. Previously, the system always used the kanban quantity even when some of the items were unacceptable for use.
    To control this feature, a new Modify Inventory Data field has been added to the Kanban Transaction Control frame in Kanban Master Maintenance. The value on new loop records defaults from the same field in Kanban Control. When the field is Yes for a loop, Kanban Fill/Receive and Kanban Ship display editable fields for certain kinds of inventory data. Depending on the source of the loop (supplier, inventory, process) and the transaction, fields can include:
    Quantity Accepted
    Quantity Scrapped
    Receipt Location
    Issuing Location
    The release includes a conversion utility associated with this feature. See Kanban Conversion Utilities.
    Threshold Warnings
    Another new feature lets you define a parameter that warns users about possible data-entry errors when they record cards.
    Use the Modify Inv Threshold field in Kanban Maintenance to specify the maximum percentage of the kanban quantity that is considered an acceptable difference between the kanban quantity and the quantity actually recorded in Kanban Ship or Kanban Fill/Receive. This value defaults from Kanban Control.
    When Modify Inventory Data is Yes and the user changes the quantity accepted from the default (the kanban quantity), the system calculates the difference as a percentage of the kanban quantity. If the percentage is equal to or greater than the specified threshold, a warning message displays so that the user can confirm the quantity entered is correct. The threshold logic also applies if you modify the Quantity Accepted field in a card maintenance function.
    Note: The system calculation is based on an absolute value, so the threshold applies to recorded quantities both greater than and less than the kanban quantity.
    When Modify Inv Threshold is 0, the system does not validate the quantity entered.
    Managing Shortfall
    You can now manage cumulative shortfall quantities that result from scrap. Each time a card is received with a quantity different from the kanban quantity, the system updates the new Receipt Shortfall field in Kanban Master Maintenance.
    For over-receipts, the additional quantity is subtracted from the Receipt Shortfall total. The field can be negative, indicating that excess quantities have been received.
    For under-receipts, the quantity is added.
    Note: This field is updated automatically only when Modify Inv Data is Yes. Otherwise, the amount received is automatically set to the kanban quantity, so differences do not occur.
    Use the new Option 7 (Processing Shortfall Option) in Kanban Card Management to manage shortfall quantities for selected loops. Options are:
    Create (the default): When the shortfall value is greater than the kanban quantity, the system creates enough limited-use cards to make the remaining shortfall value less than the kanban quantity. For example, for a kanban quantity of 10 and a shortfall of 22, the system would create 2 new limited-use cards. It would then set the Receipt Shortfall field to 2 for the loop.
    Zero All: Set the Receipt Shortfall field to 0 for all selected loops.
    Zero Neg: Set the Receipt Shortfall field to 0 for all selected loops that currently have a negative value in that field. These are loops on which the cumulative quantity received is larger than the total kanban quantities of the received cards.
    Kanban Conversion Utilities
    After installing this release, you should run the following one-time conversion utilities to support new Kanban features:
    Reset Cards with SHIP Status (, uxkbcrds.p). This utility finds cards in ship or in-fifo status, and records the inventory transactions that were skipped because the new functionality that moves backflush and subcontract transactions to Kanban Ship was not in place.
    Reset Card Quantity Accepted (, utkbcrd1.p). This utility initializes the new Quantity Accepted field on existing card records and sets it equal to the kanban quantity.