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

  • Product Fixes
    The following topics discuss workbenches fixes, including embedded component availability fixes.
    Performance Improvements
    Several performance improvements were made to the workbenches:
    For searches, the search now takes significantly less time and places a smaller load on the system that hosts the NetUI AppServer.
    For work order creation, the response time when entering values into empty cells in the schedule grid has been significantly improved.
    For work order save, the response time when saving changes has been significantly improved.
    The server side search processing has been improved. Specifically, calculation of the supply/demand data processing has been streamlined.
    Application Interface Fixes
    The Capacity Panel now correctly updates data after you switch from one resource to another when you use the Product Structure Filter capability. Previously, the Capacity Panel did not update correctly when you selected a resource in the Resource Panel and an item in the Schedule Grid, clicked on the Product Structure Filter feature button, then selected another item.
    The MSW background is no longer black as long as you do not change system settings.
    The Planning and Scheduling Workbenches now work properly with different cultures/locales. Previously, languages other than US/English caused breakage, errors, or other issues
    Resources now display correctly in .NET UI versions of the browses. Previously, some resources did not display correctly.
    When the Use Plan/Sched Workbenches field is No in Site Maintenance (1.1.13) and you attempt to pull workbenches records for the site, the system now displays a message, informing you that the workbenches are not enabled for that site.
    The workbenches and QAD repetitive functions now explode global phantom component items when creating scheduled work orders. Previously, the workbench and QAD repetitive and advanced repetitive functions only included the component global phantom item when creating scheduled work orders.
    The workbenches no longer freeze when you move a production order from a source to a destination production line. Previously, when the source production line had a single production order record for the item and you moved the production order record to another production line, the Production Order Maintenance frame displayed no records, and the screen froze.
    Quantity on hand (QOH) is now included in the Past Due column in the Supply/Demand Frame for the projected quantity on hand (POH) and available to promise (ATP) row. Also, the Supply/Demand Summary column now highlights correctly.
    Cumulative orders with a blank start/end effective date (release/due date) now process correctly. Also, the system no longer resequences cumulative orders that the system sends to the server to save. Previously, the system resequenced cumulative orders when saved on the server.
    With future planned orders outside the scheduling horizon, the system now prevents the display of Calculate Due or Release Date options in the right-click context menu. Previously, these options displayed even though the order was in the future. Also, the Calculate Date option is disabled now in the context menu when the order has a Planned or Closed status.
    The Past Due column is now formatted similar to the Capacity Panel.
    The workbenches now use data for the correct production line record when you create a new item in the workbenches that is not attached to an existing production line. Previously, when you created a new item that was not attached to a production line, the system incorrectly used another, existing production line.
    Within the Capacity Panel, the system now correctly updates the past due load in the past due column when you close a past due open order.
    The system now correctly displays POH status for work centers with no inventory issues within the scheduling horizon dates within the capacity frame. Previously, POH shortage visual indicators displayed for some work centers even though no shortage existed.
    The system now suppresses PQOH coloring in the Schedule Grid for alternate production lines with no orders.
    Additional logging messages are written to log files to facilitate troubleshooting. When searching, the client build number and chunk numbers are written to the AppShell and AppServer log files.
    The system now processes the holiday calendar and shift calendar exception records the same on both the client side and the server side of the workbenches. Previously, the holiday calendar and shift calendar exception records were processed differently on the client side and server side of the workbenches. The client side workbenches were corrected so that when you add a calendar exception on a holiday, the system ignores the calendar exception. For both the server side and the client side and for both work centers and production lines, holidays override calendar exceptions.
    The system now lets you make layout changes only after a search completes. Previously, the system displayed an error, indicating that it could not process your request, when you selected to change the layout before running a search.
    The system now displays information for an item in the Demand Details frame when you click anywhere in a Schedule Grid row. Previously, it was necessary to click in one of the Due Date columns in the Schedule Grid to display information for the item in the Demand Details frame.
    The system now correctly resets the sort indicator of a previously sorted column when you sort two or more columns consecutively in the Schedule Grid. Previously in this scenario, the system did not reset the sort indicator.
    The MSW Capacity Panel now correctly includes cumulative capacity calculations as found in capacity requirements planning reports. The new Cumulative Capacity row identifies the next available-to-promise date for an order, displays capacity in weekly and monthly buckets, and displays in weekly or monthly capacity buckets. The cumulative capacity uses remaining capacity or planned and required capacity as input.
    Remaining capacity as the input:
    [N] = each day. [N "Remaining Capacity" + Prior Day Cumulative Capacity = Cumulative Capacity of [N]
    Using the Required Capacity and Planned Capacity as an input:
    [N] = each day. [N "Planned Capacity - Required Capacity" + Prior Day Cumulative Capacity = Cumulative Capacity of [N]
    The workbenches Production Order Maintenance Summary Panel now displays cumulative orders as the first orders to display and sets fields for other Production Order Maintenance panels correctly based on the cumulative order. Previously, when the workbenches initiated, the Production Order Maintenance Summary Panel displayed the top order record and set the order attributes for other Production Order Maintenance panels for the top order, resulting in some fields having errors and displaying a red X for cumulative orders.
    The system now correctly populates Run sequence 1 and 2 values in the PSW when the values for them are from Item/Site Planning Maintenance (1.4.17). Previously, the system displayed values for Run sequence 1 and 2 from Item Master Maintenance (1.4.1).
    MSW planned capacity now correctly includes Shift Maintenance (18.1.22) exceptions for a date range.
    Open scheduled exploded orders now correctly update in the workbenches once you change data in Product Structure Maintenance (13.5). Previously, MRP picked up BOM changes and modified the BOM on the open scheduled exploded orders accordingly.
    User Preferences Fixes
    The system now preserves the History/Future Horizon values you set in the User Preferences from the last search. Also, when you introduce new preferences when pre-existing preferences were saved, the system no longer displays an error. The system also now processes changes you make to user preferences immediately.
    When you choose Order Duration Calculation Methods (Order-Release Date or Order-Due Date), the system now correctly recalculates the order dates when you modify:
    Order dates (directly or through drag and drop)
    Production Order Maintenance fields for quantity order, production rate, run crew size, setup time, number of lines, duration buffer
    Applying projected order duration now updates the work order duration field, too. When you change the quantity, required capacity, and projected hours/days duration, the system applies projected duration when you specify that the system use projected duration in the User Preferences option.
    The User Preference default value is now No for Use Shifts and Consume Prior Day Remaining Capacity.
    The horizon value within the CAC user preferences now means that the horizon value of 0 (zero) is today, a value of 1 is tomorrow, and so on. Also, the CAC horizon default was changed to 7 days.
    Workbenches Component Availability Check (CAC) Fixes
    The CAC-related Progress Bar no longer displays unless CAC is enabled.
    The CAC Shortage Monitor Report no longer displays incorrect values for the Buyer/Planner. Also, other Item Planning fields, such as Issue Policy, Pur/Mfg Code, and Item Replenishment are now correctly updated with values from Item or Item-Site Master data.
    The system no longer considers inventory set to expire in the future as allocated demand. Previously, the system applied the inventory set to expire in the future to the allocated demand, causing CAC to return the wrong PQOH calculation.
    Now, the workbenches consider inventory set to expire in the future as scheduled demand. For example, if today’s date is 12/7 and inventory is set to expire on 12/8, the system considers the demand status as scheduled and displays the correct quantity in Prior Gross Requirements in the Demand/Supply Summary panel.
    The system now processes correctly when you delete a production order in Production Order Maintenance within the workbenches before CAC recalculations complete. Previously, in this scenario, the system did not process correctly.
    CAC components no longer fail to process when you delete a production order before the system merges the calculation results.
    In the CAC user preferences, the Only Key Item field now correctly uses the value in Item-Site Inventory Data Maintenance (1.4.16) when a record exists, and the Issue Policy field now correctly uses the value in Item-Site Planning Maintenance (1.4.17) when records exists.
    Production Order Function Fixes
    The system no longer displays error messages when you:
    Create multiple orders with comments.
    Close an order in the workbenches.
    Create a new work order, then save it.
    Repeatedly select a resource or item and enter data for the selected resource or item on the Schedule Grid.
    Enter a quantity of 0 (zero) in the MSW Schedule Grid.
    The system no longer counts the setup time as part of required capacity when you close an order or reduce the quantity to zero. Previously, when an order had setup time and you either closed the order or set the order quantity to zero, the system viewed the setup time as left over and included it in residual required capacity for the order.
    The system no longer updates the run rate when you change the release date of an order. Previously, when the release date changed, the system overrode the value you entered for the run rate.
    The system now correctly defaults the routing code and BOM code from the item/site record. Previously, the system defaulted these values from the production line record.
    The system now populates the Tool ID field on a production order when you create the order in the MSW. Also, when you change the resource for an order in the PSW, the system updates the Tool ID field.
    The Required Capacity column in the Production Order Maintenance Summary frame is now correctly formatted so that it matches the display in the Details tab and PSW displays.
    The system now sequences correctly when you drag and drop two production orders into three production orders.
    The system now correctly filters MRP detail data in the Production Order Maintenance component Supply/Demand Detail panel for the item/site of the component you select to view.
    The system now properly recalculates the Run Time and required capacity when you change the Production Rate.
    The system no longer produces data errors when you assign a shift, then reassign a blank shift to a production order in the PSW Sequence Grid. Also, the system no longer displays errors when you enter a zero (0) or the number 5 in the Shift field.
    The system correctly handles warning and error messages that the system generates without contextual information. For example, previously, the Invalid Receipt Status message that the system generated from within the Attributes frame caused a system exception to occur. This no longer occurs.
    The system no longer changes the order routing record’s quantity ordered to the production order’s net open quantity (quantity ordered – quantity completed) when you modify scheduled orders with production reported.
    The Demand Details panel within Production Order Maintenance in the workbenches now correctly displays production forecast MRP detail line data, similar to data that displays in MRP Detail Inquiry (23.16) for associated items within the Schedule Grid.
    For orders of type S:
    The system now correctly deletes repetitive orders (type S) when you change the status to Closed in the workbenches. Previously, when you closed a repetitive (S) type production order by setting the order status to Closed, then tried to delete schedule history using Schedule Delete (, the system did not delete the order.
    Also, the system no longer displays a misleading error message when you delete a repetitive production order (type S) through the workbenches once you delete the cumulative order that is related to the production order using SE programs. Previously, in this scenario, the system displayed an error message informing you that the work order accounting close must occur first.
    When a backflush completes using Backflush Transaction (18.22.13) for a site enabled for the workbenches, the system applies the quantity completed to operations/orders that start with the earliest open operations/orders. Previously, the workbenches reapplied the entire cumulative quantity completed for a repetitive schedule across existing operations/orders.
    When you change the sequence of the orders since the last time they reported production, this cumulative reapplication can cause the system to reopen some orders and close others, confusing planners and schedulers. This change lets the system apply quantities to only open operations/orders.
    You can no longer change the order quantity to be less than the quantity completed for the order using Work Order Maintenance (16.1). When you try, the system displays an error message and does not change the order quantity.
    You can no longer access Cumulative Completed Maintenance (( for a site that is enabled for the workbenches.
    The workbenches no longer display 0s (zeros) within the PQOH column in the Supply/Demand data in the MSW/PSW Production Order Maintenance frame. Previously, the column displayed all zeros.
    You can now correctly close scheduled exploded orders in the MSW when the orders are for manufactured, production line items. Previously, the system considered the MSW-closed orders for closure by Work Order Accounting Close (16.21) and posted GL costs to the Method Change Variance account for the closed orders.
    Also, the system no longer displays messages indicating accounts are inactive without contextual information when you save production orders.
    The system no longer displays an unremovable error message when you enter values larger than 9999999 in the Qty Ordered field within the workbenches Production Order Maintenance panel, then click in the Grid. Previously, when you entered a value that was larger than the number of characters allowed for the field, then clicked in the Grid, the system displayed a data error that remained in the workbenches.
    You can now delete production orders with a status of either P(lanned) or F(irm). Previously, when you deleted the order and saved your changes, the workbenches informed you that Accounting Close must be run and restored the order.
    When you modify an order’s release date in the workbenches, the system now displays the correct order due date calculation. Previously, the date remained as the date you entered on the Schedule Grid.
    Save Function Fixes
    When you introduce new preferences when pre-existing preferences were saved, the system no longer displays an error. The system also now processes changes you make to user preferences immediately.
    The Production Activity panel now correctly displays expected results after you save or merge changes and the Production Cum Activity panel now correctly displays the cumulative order ID you selected.
    The system no longer displays an error message when you delete a production order in the workbenches Production Order Maintenance, then save.
    The system now correctly lets you edit and saves your changes when you activate compliance in the workbenches Compliance Panel Active field. Previously, the system displayed a warning, informing you that you cannot access the field to enable compliance and your changes will be lost.
    The system now correctly displays messages when you save. This means that warnings that indicate that modifying the order quantity on a released order no longer erroneously display, even though the system accepts the change. During a save, the system no longer:
    Treats messages that the client returns from the server as a commit rejection.
    Displays warnings during a successful commit and warnings from a rejected commit. (The system now correctly displays an error for a rejected commit.)
    Displays an exception when you invoke order maint subprograms without supplying contextual information.
    The system no longer displays planned orders as E(xploded) orders during a save process.
    The system now saves correctly when you have values in the Quantity Open field and other fields, such as Release Date, Due Date, and so on.
    Search Function Fixes
    The workbenches search function now correctly pulls item records where no demand records exist within the history or future.
    The workbenches now properly process when you search and there is production order routing data available with blank order IDs.
    When running a search, the system now correctly applies your saved view that you selected before the search. Previously, when you selected a view before running a search, the system displayed an error message.
    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
    New selection fields to include P(lanned), F(irm) Planned, E(xploded), A(llocated), and/or R(eleased) production orders were added to the reports and inquiries of the Capacity Requirements Planning (24) menu. Since the workbenches generate capacity loads for planned orders, planned order load was being included in the capacity load reports and inquiries. The new fields let you include or exclude load for orders of any status from the capacity load reports and inquiries.
    For Production Line Item Update (
    The program now correctly generates generalized codes when you set the Pur/Mfg field in the Item Data Master (1.4.1) for line scheduled items. Previously, the system did not generate generalized codes when you set the field.
    Production lines for older, past-due orders are now correctly populated after running Production Line/Order Update (
    Production Line Item Update no longer creates duplicate line or machine master records without first checking production scheduler master records or machine records. Previously, without checking for domain, site, resource type, resource ID, and machine in the production scheduler master or machine records, the system created duplicate records.
    For Production Line Maintenance (
    Production Line Maintenance and Site Maintenance (1.1.13) no longer cause lock table overflows. Previously, when processing a large number of work orders, a lock table overflow could result as the system processed work orders within one transaction. Code was changed so that the work order processing is done with one transaction per work order, thus preventing the lock tables from surpassing defined limits.
    The system now defaults the primary production line in Work Order Maintenance (16.1) when you enter the site in the program and when an item has a primary production line defined in Production Line Maintenance. Previously, the primary production line did not default in Work Order Maintenance when you entered the site for a new work order.
    The system no longer displays errors in the Item Detail frame of Production Line Maintenance when you create a new record.
    For Work Order Maintenance (16.1):
    The program no longer changes the order routing record’s quantity ordered to the work order’s net open quantity (quantity ordered – quantity completed) when you modify scheduled orders with production reported.
    Work Order Maintenance no longer lets you leave the Production Line field blank. Also, you can now use the workbenches-related utilities Production Line/Order Update ( to update production orders that have a blank production line as the default production line.
    The workbenches now correctly update the Run Rate, Run Crew Size, Duration Buffer, and the number of line in Work Order Maintenance when you change the production line for a discrete work order with a P or F status or for a repetitive order. Previously, the workbenches showed only the original production line data for these fields.
    Production Line Item Create ( now correctly locates all the items that are produced on a work center and then creates item records for the targeted production line. Previously, the program had problems locating items because of production order records that did not exist for many active items. The program was changed so that it interrogates every system routing, finds work centers and all item associated with work center routings, and adds items to the production line of the program selection.
    The system no longer displays buffer locking issue messages when you use Backflush Transaction (18.22.13) once you complete scheduling within the workbenches and attempt to backflush.
    Synchronize Resource Tables (16.25.14) no longer attempts to create duplicate production scheduler resource master records or set the machine field for the record to the work center. Previously, without a check to verify when the master record exists for domain, site, resource type, resource ID and machine, the utility program attempted to create duplicates under the production line and work center master tables. The utility did not check for previous machine field settings in work order records.
    The system no longer displays a lock error message and no longer generates component BOM requirements for remaining partial quantities when you use Work Order Receipt (16.11) to receive a partial quantity, then close the order. Previously, in this scenario, the system displayed an error message informing you that the work order master had a no-lock status, even though the order closed. It also indicated that requirements existed for remaining partial quantities orders even though you closed the order.
    Prod Line/Item Update Delete ( now correctly validates whether production order records exist.
    Programs now function consistently and interact with the workbenches correctly across all workbenches-supported service packs. Previously, some programs in some environments did not interact consistently with the PSW so that you could not correctly pull in past due items and dates or item sites to the PSW.