Enhancements
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 work 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 work 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:
The system now retrieves the total number of items by resource, which contributes to workbench performance.
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.
Area processing logs that took less than five seconds were removed from the log file. These entries were not useful and removing them lets you read the log file more efficiently.
