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.com



  •     QAD Glossary

  • Product Fixes
    The following topics discuss workbenches fixes.
    Application Interface Fixes
    The system now displays warnings and other messages in the workbenches when you deny access to users to certain maintenance programs that interact with the workbenches. Previously, the system did not display warnings or error messages, and changes to the orders or calendar exceptions were saved. Now, when you deny access to the following programs through QAD SE security programs, the system displays messages informing users that they do not have access to the following programs and that the system does not save their changes:
    Work Order Maintenance (16.1)
    Master Schedule Order Maint (22.13)
    Shift Maintenance (18.1.22)
    Shift Maintenance (18.22.1.22)
    For planned orders, the system now correctly displays the quantity in the BOM Qty field in the workbenches-embedded Production Order Maintenance Components tab. Previously, the system displayed all 0s (zeros) in the field for planned orders and did not display the quantity for orders with a Planned status.
    The workbenches-embedded Holiday Calendar browse no longer displays past holidays. Previously, the Holiday Calendar Browse displayed all holiday records, including those created many years in the past, making the browse difficult to use.
    The system no longer displays incorrect data when you change the Comment Reference field in the MSW embedded Production Order Maintenance. Previously, the system was overwriting the data in the production order comment table, causing incorrect defaulted data to display.
    The system now correctly displays component detail records when values in different cases do not match. Previously, for example, when production order master records had an uppercase-specified production order domain, but associated detail records had a lowercase-specified production order domain, the system did not display component detail records.
    The MSW frame that informs you of merging data no longer displays over other application windows. Previously, when you merged, the system displayed an alert, informing you that it was merging data; however, the alert overlaid other application windows that were running on your desktop.
    You can now cancel the error message that displays when you enter a large value that exceeds 9999999 in the Qty Ordered field in the MSW. Previously, even though the field let you enter a very large, invalid number, the system displayed an error message that you could not cancel, and you had to end the .NET UI session to continue.
    The system no longer has overflow exceptional issues when processing production lines with large run rates. Previously, very large run rates—especially with large decimal values to the right of the decimal point—combined with issues with cumulative loads or hours that the system attempted to carry forward caused exceptions when processing.
    The MSW no longer displays an error that indicates that it cannot update the data value because the value in the editor is not valid when you leave the quantity blank for an order in the MSW Production Order Maintenance Tab. Previously, depending upon where the cursor was when you entered the blank value, the system could constantly display the error.
    User Preferences Fixes
    The default for the Component Availability Check user preference Computation Method field was changed from Dynamic to On Search and Save.
    Workbenches Component Availability Check (CAC) Fixes
    The Quantity Short field was changed to Quantity Short PQOH for the Shortage Report.
    Production Order Function Fixes
    The system no longer corrupts production order bill records when you change an S type order quantity. Previously, in this scenario, the system corrupted the production order bill records.
    Corrections were made to operation schedule logic for production orders so that selective MRP no longer leaves the production order start and due dates blank. Previously, MRP left the dates blank.
    You can now correctly save changes to a discrete production order when you report production. Previously, for discrete orders, you were unable to save changes to an order when you reported production.
    You can now correctly modify a production order when the scheduled quantity on the order is less than the completed quantity. Previously, in this scenario, you were unable to modify the order.
    The production rate is now correct for production line records. Previously, when you created a production order with the release date prior to the production line item record change date, the production rate displayed as the new rate and not the old rate until you saved.
    Save Function Fixes
    When you save views in the workbenches, the system now retains the panel formatting. Previously, the view load and save functionality only functioned with grid layouts and did not appear to function with UI element layouts such as the panel layouts for tabs.
    Search Function Fixes
    When you save views in the workbenches, the system now retains all grid and panel layouts. Previously, the view load and save functionality only functioned with certain grid and panel layouts.
    The system no longer has out-of-memory issues during consecutive searches. Previously, for each consecutive search you conducted using the same search criteria, the application memory usage increased until the system reached an out-of-memory limit.
    Non-Workbench Function Fixes
    Auto Firm Planned Orders (22.20.2) now correctly displays product line look-up data from the line master for the Line field. Previously, the system incorrectly displayed look-up data from the product line master for the field.
    You can now correctly report production for items in Backflush Transaction (18.22.13) when a closed repetitive scheduled order exists; however, you should delete the closed repetitive scheduled order, change the status to E, change the quantity to 0, or change the quantity to Quantity Completed before attempting the report. Previously, the system displayed an error that informed you of existing unexploded schedules when you attempted to report production and had unclosed repetitive scheduled orders that you deleted.
    Prod Line/Item Update Delete (18.22.1.21) now correctly validates when production order records exist before you delete items from the production line. Previously, the program did not validate existing production order records before deleting the item from the production line.
    Note: Even though you can manually delete the item when there is more than one record for the item with a different start date in other SE programs, you cannot do this in Prod Line/Item Update Delete. So when there are repetitive schedules with multiple items defined with different start dates, you cannot delete using Prod Line/Item Update Delete.
    Production Line Item Create (18.22.1.20) now correctly populates existing production orders with a status of P(lanned), F(irm), B(atch), E(xploded), or R(eleased) when you associate the production line with the item. Previously, the items were correctly added to production; however, the Production Line field remained blank on existing production orders.
    Work Order Maintenance (16.1) now correctly validates the Quantity ordered cannot be less than quantity completed message when you enter a negative order quantity. Previously, the program incorrectly validated and displayed the message when you entered a negative order quantity.
    Work Order Receipt Backflush (16.12) now correctly picks up orders from the workbenches that were indicated for printing using the Release/Print function in the workbenches.