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

  • Fixes
    The following topics discuss fixes for this release.
    Application Interface Fixes
    Open, over-completed discrete production orders now display in the MSW/PSW. Previously, certain over-completed, open discrete production orders did not display in the workbenches.
    The system no longer incorrectly calculates production order dates when you reschedule a past due production order. Now, when you reschedule past due production orders to the present, you can reschedule them so that they retain the original order scheduled duration. Previously, in this scenario, the system recalculated the production order dates.
    For co-/by-products, when you enter a quantity for an order in a joint order set, the system now delivers expected results. Previously, the system had unexpected results in these scenarios when you entered:
    A quantity of 0 (zero) for base process item.
    The system did not update the orders of the joint order set. The system did not set the quantities of the joint orders to zero, and it deleted the order when you saved.
    A quantity of 0 (zero) for a by-product order.
    The system did not change the joint product orders.
    A quantity of 0 (zero) for a co-product order.
    The system corrupted the order, and you could no longer adjust the order without causing errors or causing the system to use the wrong calculations.
    Also, when you modified a co-product order quantity, the system did not respond to changes and corrupted the record.
    The MSW now correctly sorts the order by release/due date in the browse panel in the Production Scheduling tab when you:
    Click the Undo button on the order after dragging and dropping to a different date.
    Sort the PSW order browse by release/due date.
    Previously, in the above scenario, the order was not sorted.
    The MSW no longer displays a message informing you that the system was unable to process your request and correctly displays data in the workbench when you change the Qty Ordered field to 0 (zero) for a production order with a closed status, then save the workbench. Previously, in the above scenario, the system displayed an error.
    The MSW now correctly displays data in the workbench when you set your Windows Regional Settings to a language other than English; for example, Korean.
    The MSW now correctly retains the entered sequence when you change the sequence from 0 (zero) and the same sequence already exists. Previously, the system incorrectly assigned the entered sequence to another number.
    The MSW/PSW now correctly shows the long label for all the columns in the Production Order Maintenance tab when the following are defined:
    A term for the column in Label Detail Maintenance (
    A column label in the database schema
    Previously, in the above scenario, the Long Label was not displayed.
    The PSW column heading labels now correctly display long labels you define in Label Detail Maintenance ( and Label Master Maintenance ( Previously, when the column label for some database fields had a non-blank column-label property, the system incorrectly displayed the caret (^) for fields for which you did not define labels in Label Detail Maintenance or Label Master Maintenance.
    Schedule Maintenance (18.2.1 and now shows improved performance when you add schedules. Previously, the system obtained data without domain considerations and called the schedule program using temp tables, which caused non-indexed scans on the work order master table; both issues caused a slower system performance when you added schedules.
    The MSW Schedule Grid and the workbenches-embedded Production Order Maintenance no longer have a performance issue. Previously, data entry in the MSW Schedule Grid and in Production Order Maintenance was delayed 5-10 seconds for each newly created entry.