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  |   On Demand  |   Home  |   qad.com




Enhancements
Several new enhancements were added to the workbenches for this release, as discussed in the following topics.
Personalization Architecture
Personalization architecture provides a way to easily add columns, fields, and associated processing logic to any of the workbench grids that reference the production order master and/or component detail tables.
New sections and fields are included in Workbench Control (22.20.24) as part of this enhancement.
Note: For restrictions and additional information, as well as instructions, code examples, and customization sample scenarios, refer to Administration Guide: Planning and Scheduling Workbenches, version 70-3174-3.2.3.2.
Use the following Additional Default Display Fields section in Workbench Control:
Work Order
Enter fields, separated by commas, to add to the production order grid column pull-down list. The pull-down list shows you the default columns that you can add to the grid.
Work Order Component
Enter fields, separated by commas, to add to the production order component detail grid column pull-down list. The pull-down list shows you the default columns that you can add to the grid.
Use the following Additional Default Edit Fields section in Workbench Control:
Work Order
Enter fields, separated by commas, in the work order display list that are editable.
Modify Filters for Browses
You can now modify the filters that the supporting browses use when they display records. You can modify to filter by dates, or by other specific values, such as an order status, or a specific numeric value that has meaning in your company within item numbers. For example, you can view all transactions for the last two years, only records with dates of today plus all future dates, or specify a specific date upon which to view records. You do this by modifying the ConfigControl.xml file.
Note: Chapter 4 of Administration Guide: Planning and Scheduling Workbenches tells you how to access and modify the ConfigControl.xml file and explains the file layout. It also provides a table of valid date entries in the correct format for the XML file. It also includes several code examples that show you how to make specific changes to filter records.
Modifying Browse Record Limit
By modifying the ConfigControl.xml file, you can change the default number of records that display in the supporting browses in the workbenches. Chapter 4 of Administration Guide: Planning and Scheduling Workbenches provides code examples that show you how to change the record limit for the browses.
New User Preference Scheduling Options
Several enhancements were made to the Scheduling tab of the User Preferences window in the workbenches. Changes were made to streamline and enhance date calculations. The following changes were made:
When calculating production order dates using the context menu selections Calculate Due Date or Calculate Release Date, you had to select these functions multiple times before getting the correct date calculation. This has been resolved.
The production order Duration field is now calculated correctly when the release date is in the past and the due date is either today or in the future. Before this release, the Duration field was not always calculated correctly in this situation.
Anchor Order Date and Order Duration Calc Method were removed.
Several new fields were added in place of the removed Anchor Order Date and Order Duration Calc Method fields. The new fields are grouped under the following three headings in the Scheduling tab of User Preferences, and each heading has several fields:
Date Calculation Rules By Order Status
Due Date Calculation Inputs
Release Date Calculation Inputs
The new Date Calculation Rules by Order section has the following fields, and each field has its own rule that informs the system which date to calculate when the order is in that particular status:
Planned.
When the order has a P(lanned) status and the system calculates dates, the date (due versus release) assigned here is the date calculated.
Firmed
When the order is in F(irm), E(xplode) or A(llocate) status, and the system calculates dates, the date (due versus release) assigned here is the date calculated. The default is the release date.
Released
When the order is in R(eleased) status, and the system calculates dates, the date (due versus release) assigned here is the date calculated. The default is the due date.
Sequenced
When the order has been sequenced and the system calculates dates, the date assigned here is the date calculated. This setting takes precedence over the Planned, Firmed, and Released user preference settings. The default is the due date.
Production Reported
When the order has production reported, and the system calculates dates, the date assigned here is the date calculated. This setting takes precedence over the Sequenced, Planned, Firmed, and Released settings. The default is the due date.
The new Due Date Calculation Inputs section has the following fields:
Anchor Due Date
When Yes, the due date stays fixed during date calculations, unless you select the due date to be calculated.
Scheduled Duration
When Yes, the system uses the value in the production order Scheduled Duration field to calculate order dates. This value is usually the item’s manufacturing lead-time.
Projected Duration
When Yes, the system uses the value in the production order Projected Duration Days field to calculate order dates. Projected Duration is calculated based on required capacity and various other inputs.
Planned Capacity
When Yes, a date’s remaining planned capacity is used to determine whether a production order can be scheduled for that date.
The new Release Date Calculation Inputs section has the following fields:
Anchor Release Date
When Yes, the release date stays fixed during date calculations, unless you select the release date to be calculated.
Scheduled Duration
When Yes, the system uses the value in the production order Scheduled Duration field to calculate order dates. This value is usually the item’s manufacturing lead-time.
Projected Duration
When Yes, the system uses the value in the production order Projected Duration Days field to calculate order dates. Projected Duration is calculated based on required capacity and various other inputs.
Planned Capacity
When Yes, the system uses a date’s remaining planned capacity to determine whether a production order can be scheduled for that date.

User Preferences
Using Schedule Maintenance with Workbenches Enabled for a Site
When you set the Use Plan/Sched Workbenches field to Yes in Site Maintenance (1.1.13), you can now use Schedule Maintenance (18.2.1 and 18.22.2.1) to enter repetitive schedules.
Using Scheduled Maintenance with the workbenches enabled helps customers who have a need to upload schedules from third-party applications or use the workbenches to enter schedules for some production lines within a site, and still enter schedules in Schedule Maintenance for other production lines within the same site.
Note the following when using Schedule Maintenance to enter repetitive schedules when you enable the workbenches in Site Maintenance.
When more than one scheduled production order exists for the same domain, item, site, production line, and/or due date, you:
Can only change the order quantity from a non-zero number to 0 (zero). When you change the order quantity to 0, the system deletes the corresponding set of scheduled orders for that due date.
Cannot make changes to the scheduled quantity, routing, or BOM.
When you try to make changes to the areas described, the system displays a message, indicating more than one order exists for the production order due date.
When you modify the order quantity, the routing, or the BOM, the system updates the scheduled order.
When you change the order quantity to 0, the system deletes the corresponding set of scheduled orders for that due date.
When you enter a new record, the system creates a scheduled production order. The system accepts valid alternate routing and BOM codes and creates a repetitive schedule master record that matches the scheduled production order. However, the system does not store the repetitive schedule alternate routing and BOM code in the repetitive schedule master; instead, it stores that information in the scheduled production order. This is consistent with how the workbenches generate new scheduled orders.
Delete Repetitive Orders Option
You can now delete repetitive orders with a closed status using Schedule Delete (18.22.2.7). Deleting the closed orders ensures that you do not delete orders that are not yet complete.
Create Performance Enhancements
The software has been enhanced to provide a spreadsheet performance feel when you create new production orders from the workbenches. The new performance feel minimizes application calls to the server. When you create a new production order as the first order created for the item, the original creation process occurs—typically, within two to six seconds; however, all subsequent orders that you create should be less than one second. This performance improvement is possible because the system uses the first order created as the master copy; then, it uses the master copy to create all subsequent orders. The system is aware of BOM or routing changes and effective dates as part of this process.
As part of this enhancement, when you enter a new scheduled quantity in the MSW Schedule Grid, the system uses the planned order instead of creating a new production order when the planned order due date equals the date or the quantity you enter in the Schedule Grid. Previously, the system created a new production order, even when a planned order existed for the same due date. This change results in much faster performance as it eliminates the system need to create redundant supply records as well as removes MRP cleanup during the next MRP run.
Note: All create performance enhancements do not apply to base or co-/by-product items.
Log File Enhancements
The log file was enhanced in several areas, as described in the following topics.
Retrieves item count data
During a search, the system now retrieves item count data for the log file. Previously, you had no way of knowing how many items the system actually retrieved. The log file now shows the number of items as well as the items retrieved. The system retrieves the following item counts:
Item count by resource
The system now retrieves the total number of items by resource, which contributes to workbench performance.
Unique item counts
The system now retrieves the number of unique items, which drives the workbenches Supply/Demand panel.
Includes the number of unique CAC components processed
The log file now includes the number of unique components processed by CAC. Previously, the file depicted how many CAC components were processed, but did not depict the number of unique processed components. The number of processed unique components is a primary driver to server-side CAC performance.
Includes the number of unique MRP details processed
The log file now includes the number of unique MRP detail records processed by CAC. This information is useful when you compare customers and environments. You can use the information to determine the average time to process each CAC component. You can put the information in context with the ratio of MRP detail records.
Entries removed
Area processing logs that took less then five seconds were removed from the log file. These entries were not useful and removing them lets you read the log file more efficiently.
Sales Quantity By Month
Using the fields in the Sales Quantity By Month Tab you can track sales history data by viewing the items, product lines, ship type, site, customer, ship-to, year, and year-to-date quantity. The panel displays quantities in a month-by-month grid so that you can track invoiced sales orders.
Seasonal Build
A new Seasonal Build Tab lets you review sales quantities for items that fluctuate according to some seasonal factor, such as weather or the way a firm handles its operations. You can review sales quantities for items in the panel.
New Quantity Available to Allocate Column in Shortage Report
A Quantity Available to Allocate column was added to the Workbenches Shortage Report. The system calculates quantity available to allocate as:
Qty with Available Status - Qty Allocated where
Qty with Available Status = in_qty_avail
Qty Allocated = in_qty_all
Production Line BOM and Routing
When production orders are firmed and you specify a production line for the order, the system now automatically populates the BOM and Routing code from the production line item to the order. When you switch an order from one production line to an alternate, the system now populates the BOM and routing code attached to the item at the alternate production line.
The system updates production orders with a status of P(lanned) or F(irmed) with the BOM/routing code from the production line, and the system updates repetitive scheduled orders with a status of E(xploded). The defaults for the BOM/Routing codes are as follows:
The BOM/routing codes for a production order default from the production line record only when you specify a production line on the order. When the BOM/routing codes are blank in the production line record, the codes are blank on the order.
When you create a new record in Production Line Maintenance (18.22.1.1) for a production line/item, the system defaults the BOM/Routing code fields from Item-Site Planning (1.4.17) detail records when they exist, or from Item Planning Maintenance (1.4.7) master records when detail records do not exist. You can change the defaulted codes. The system validates BOM/routing codes.
For existing records, Production Line Item Update (18.22.1.21) now includes the Update BOM/Routing selection field. For more information on the field, refer to MSW Setup section of User Guide: QAD Planning and Scheduling Workbenches, version 70-3127-3.2.3.2.
Important: After 3.2.3.2 is installed, you should run Production Line Item Update to have the appropriate sites/production lines. This lets the system default existing BOM/routing codes from either Item-Site Planning detail records or Item Planning Maintenance master records to the production line record. Once the Update program completes, you can update individual records on an as-needed basis and adjust the defaults when needed. Refer to Installation Guide: QAD Planning and Scheduling Workbenches, version 78-0953-3.2.3.2.
As part of this enhancement:
In the Production Line Maintenance (18.22.1.1.) Item frame, you can now use new look-up browses attached to the following fields:
BOM Code field to show all available alternate BOM codes for the item
Routing field to show all available alternate routing codes for the item
The system validates the BOM Code and Routing fields in Production Line Maintenance to verify if the code you specify is for a valid alternate code for the item. If not, the system warns you that the specified BOM or routing does not exist.
Additional Production Line Item Update Modifications
In Production Line Item Update, the Production Line field was modified so that when you specify a blank value in the field, the system updates all production lines for the specified site. You cannot leave Site blank.
Additionally, the Make Primary Line field now works in conjunction with the Production Line field. You can now only set Make Primary Line to Yes when you specify a production line in the Production Line field. When Production Line is blank, you cannot change Make Primary Line to Yes.