Use this screen to set up and maintain basic parameters for operating Costpoint Master Production Scheduling. You establish forecast guidelines, rules for the consumption of sales forecasts, and procedures for processing planned orders generated from the MPS process.
All MPS Settings are applicable only to the company the user is currently logged into.
In addition to the settings listed below, the MPS module is also heavily dependent on the values defined in MRP Settings. Rules such as Process MRP by Company, Plan MRP by Company, Plan Warehouse Separately, supply and demand inclusion rules, etc., are referenced when running the Generate Master Production Schedules application.
The corporate setting, Plan MPS Part Requirements, also in MRP Settings, determines whether the MRP process will include MPS flagged parts when MRP planning occurs. If this option is checked, it is not necessary to run the Generate Master Production Schedules process to plan MPS parts, as the Update Materials Requirements Plan application will generate planned orders and action messages for MPS parts. Note that if MRP plans MPS parts, action messages will only be visible in the MRP module. Even if this option is selected, you can still execute the Generate Master Production Schedules, but without a firm workflow, it may be difficult for users to determine where action messages for MPS parts will be stored.
Enter the label to be used for user-defined forecasts, which are non-sales forecasts. Unlike sales forecasts, user-defined forecasts cannot be consumed by sales orders; they must be manually adjusted.
If you leave this field blank, no non-sales forecasts can be entered for MPS schedules — all schedules generated from MPS will be based on firm demand and sales forecasts. The associated forecast fields will be hidden on reports and screens.
The Edit Master Production Schedule (when the "MPS Default Option" setting is selected for the Schedule Display Option) and the Master Production Schedule Report use Display Horizon values to summarize and display time-phased supply and demand.
In the Weeks field, enter the number of weeks to display in the MPS schedule when showing both weeks and months.
In the Months field, enter the number of months to display after (after the number of specified weeks) in the MPS schedule when showing both weeks and months.
For instance, if you enter 26 weeks and 18 months, you will see the first six months of supply and demand quantities broken into weekly time periods (buckets). The supply and demand quantities for the next 18 months will be broken into monthly time periods (buckets).
Enter the number of weeks to display in the MPS schedule when showing daily and weekly schedules. The Edit Master Production Schedule application uses this value to limit the number of supply and demand data returned to the screen. Supply and demand data past the total number of weeks specified in this field will not be displayed on the screen.
The MPS time fence is intended to limit changes to the production schedule within a specified amount of time in the future. The MPS process uses the time fence to limit changes or to warn users about changes to planned orders that are needed within the time fence. MPS also flags reschedule action messages if the suggested due date falls within a part’s MPS time fence.
From the drop-down box, specify the method Costpoint uses to determine the window of time in which an MPS schedule should not be changed (calculated from the current date):
Use MPS Settings Value (the default)—You must use the corresponding MPS Planning Timing Fence (Days) option to specify the number of days used as the time fence.
Use Part Time Fence—You can specify, for each part, the MPS time fence in the MPS subtask of the Planning Part Data screen in Product Definition.
Use Part Cumulative Lead Time—Costpoint will use the part’s cumulative lead time as the part’s MPS time fence. The cumulative time represents the number of days required to complete a part, including lead times for all purchased components and manufactured subassemblies. The quantity can be defined in the MPS subtask off the Planning Part Data screen in Product Definition.
Use Part Lead Time—Costpoint will use the part’s lead time as the part’s MPS time fence. Component and subassembly lead time will not be included. The number is calculated in the Planning Part Data screen in Product Definition.
If the MPS Planning Timing Fence Method option is set to "Use MPS Settings Value," enter the number of days to use as the global time fence for all MPS parts. The number of days will represent either calendar days or shop days, depending on the value in Production Control Settings.
The Edit Master Production Schedule application uses this setting to spread the quantity on one planned order into multiple planned orders. This allows you to "smooth’"customer demand peaks and valleys for production scheduling purposes. From the drop-down box, select a setting to specify whether new planned orders should be backscheduled or forward scheduled from the original planned order due date. The value set here can be overridden in the Edit Master Production Schedule application.
Backschedule (the default)—New planned orders will be created with due dates prior to the selected planned order’s due date. For example, spreading a planned order with a due date of 2/28/07 into four planned orders with a spread increment of weekly creates new planned orders due 2/7/07, 2/14/07 and 2/21/07, if you select the backschedule spread method.
Forward Schedule—New planned orders will be created with due dates after the selected planned order’s due date. For example, spreading a planned order with a due date of 2/28/07 into four planned orders with a spread increment of weekly creates new planned orders due 3/7/07, 3/14/07 and 3/21/07, if you select the forward schedule spread method.
From the drop-down box, select the increment of time Costpoint uses in either backscheduling or forward scheduling new planned orders with the Planned Order Spread tool in Edit Master Production Schedule application:
Weekly (the default)—New planned orders will be created in weekly increments from the original planned order’s due date. If a shop calendar is used, and the calculated due date is not a shop day, use the next earlier (backshedule) or next later (forward schedule) shop day.
Daily—New planned orders will be created in daily increments from the original planned order’s due date. If a shop calendar is used, skip non-shop days.
Monthly—New planned orders will be created in monthly increments from the original planned order’s due date. If a shop calendar is used, and the calculated due date is not a shop day, use the next earlier (backshedule) or next later (forward schedule) shop day.
Check one or more of the following options to specify how Costpoint handles forecasts:
Select this checkbox to have Costpoint keep historical forecast data after the forecast is consumed or the forecast due date has passed.
Select this checkbox to default the consume forecast option to Y on new inventory sales order lines. If set to Y on a line, the Sales Order application will attempt to consume the appropriate open sales forecast quantity for that line.
Select this checkbox to allow users to override the consume forecast option default on sales order lines.
Select this checkbox to allow users to change the forecast consumption quantity manually in Enter Sales Orders.
Select this checkbox to allow users to change the forecast consumption quantity manually in Approve Sales Orders.
Select this checkbox to warn users in Enter Sales Orders if a sales order line quantity exceeds the forecast, or if no forecast quantity can be found to consume.
Specify how Costpoint matches sales order line quantity to the sales forecast quantity that should be consumed. The MPS application will always attempt to consume the open sales forecast quantities where the requirement equals the sales order line’s ship-by date. If an exact date match cannot be found, it will search for the requirement due date closest to the line ship-by date, within the limits identified below. If two open sales forecast dates are equally close, the earlier forecast will be consumed.
Don't Limit (the default)—The forecast with the closest due date will be consumed, regardless of how far apart the dates are.
Limit by Ship-By Date Week—Only forecasts with a due date in the same week as the sales order line ship-by date will be eligible to be consumed.
Limit by Ship-By Month—Only forecasts with a due date in the same month as the sales order line ship-by date will be eligible to be consumed.
Select this checkbox to allow planned orders generated from the MRP process to be firmed with the MPS Firm Planned Orders application.
Select this checkbox to allow planned orders generated from the MPS process to be firmed with the MRP Firm Planned Orders application.
The Costpoint tables impacted are listed in the following table:
|
Screens |
Tables |
|
MPS Settings |
MPS_SETTINGS |