> > >
Use this form to create a coverage group and set up the parameters that are used in master scheduling. These parameters determine how to calculate net requirements for the items that are linked to the coverage group.
Typically, you set up a coverage group for items that share similar characteristics or circumstances. These could be items that are purchased from the same vendor or a family of end items.
Note
|
|---|
|
If you do not link a coverage group to an item, the program uses the that is specified in the as the default. |
Tasks that
use this form
Navigating
the form
The following tables provide descriptions for the controls in this form.
Tabs
|
Tab |
Description |
|---|---|
|
View a list of the coverage groups that have been created. |
|
|
Enter the detailed settings for the selected coverage group. |
|
|
|
Set up the time frames for the selected coverage group. |
|
|
Set up the action messagesparameters to specify which action messages to generate and how they should be generated. |
|
|
Set up the futures messagesparameters for the selected coverage group. |
Fields
|
Field |
Description |
||
|---|---|---|---|
|
|
Identification of the coverage group. |
||
|
|
Enter a description of the coverage group. |
||
|
|
The work-days calendar is used to calculate the order date, the requirement date, and the preferred delivery date. |
||
|
|
Select the method that master scheduling uses to calculate requirements for the item. The options are as follows:
|
||
|
|
Enter a time period, in number of days, during which master scheduling consolidates all requirements for the item and generates one planned order to cover the sum of these demands. If you enter 5, for example, planned orders are consolidated for 5-day periods. The coverage period starts on the date of the first requirement, and the planned order is generated on this date. The requirement date (for example, the delivery date) determines the period in which the planned order is included. The field is available when you select in the list. Example The coverage period is 5 and the minimum quantity is 0. There are sales orders with requirement dates of 9/1, 9/3, 9/10, 9/14, and 9/20. Master scheduling generates three planned orders:
|
||
|
|
Enter the time period, in number of days from today's date, during which requirements are calculated. |
||
|
|
Enter the days that are added to a requirement due date to define a time interval during which a planned receipt that is due can be used to fulfill the requirement. A planned receipt that is due outside the defined time interval is not valid to fulfill the requirement, and master scheduling will generate a new planned order. You can equate negative days with the number of past-due delivery days (during which there is a negative inventory level for the item) that you will accept before creating a new fulfillment order. The value that you enter in this field depends on factors such as item lead time and company policy regarding inventory. If an item has a long lead time, you can specify the typical lead time as negative days, because the procurement of new items is not possible in the short term, and you can wait for items that have been ordered. You can specify negative days in the form or the form. Example For a particular item, a purchase order is scheduled for receipt on the 20th of the month, and a sales order is scheduled for delivery on the 19th of the same month. Should master scheduling generate a new planned purchase order to cover the requirement, or do you accept a late sales order delivery on the 20th? If you set the negative days to zero, a new planned purchase order is generated. If you set the negative days to a number more than zero, no planned purchase order is generated. Instead, an action message is generated for the purchase order, and a futures message is generated for the sales order. For more information, see About action messagesand About futures messages. |
||
|
|
Enter the days that are subtracted from a requirement due date to define a time interval during which a planned receipt that is due can be used to fulfill the requirement. A planned receipt that is due outside the defined time interval is not valid to fulfill the requirement, and master scheduling generates a new planned order. You can equate positive days with the number of days that you use existing inventory (there is a positive inventory level for the item) before creating a new fulfillment order. For items that you regularly order and procure, you can specify the item's as positive days. For items with few transactions, you can specify the coverage group's as positive days. You can specify positive days in the form or the form. Example For a particular item, there is inventory and a sales order is scheduled for delivery in 90 days. Should master scheduling generate a new planned purchase order to cover the requirement, or do you accept that the order is fulfilled from the current inventory? If positive days are fewer than 90, a new planned purchase order is generated. If positive days are more than 90, no planned purchase order is generated. However, current inventory levels of the item are no longer available for new sales orders.
|
||
|
|
If you select this box, coverage planning will be influenced by the fact that a particular BOM version will be used. For a sales order, for example, you can indicate in the that the items ordered are to be produced by a particular BOM version. If that version is not the active BOM version for the item, then, regardless of the current inventory available, a new planned production order will be created by using requirements derived from the particular BOM version in order to cover the requirement. |
||
|
|
When this field is marked, coverage uses a specific route version. On an order, for example, you might specify in the field that the ordered item is to be produced through a specific route version. If this is not the active route version for the item, a new planned production order is scheduled in according to the specified route version to cover the requirement, regardless of the current inventory levels. |
||
|
|
Specify the production status you want to use for automatic firming of planned production orders. The options are as follows:
When planned orders are firmed, productions with the selected status are created automatically. |
||
|
|
The period during which planned purchase and production orders will automatically be firmed. The time fence is expressed in days and is calculated from the date of the requirement calculation.
|
||
|
|
Specify the period in which new planned orders are not to be created and where planned orders from previous requirement calculations are not to be changed. All requirements not covered in this period will be covered by a purchase--or a production order created at the end of the period with an action message that it is to be moved back in time. If an earlier requirement calculation created a planned purchase order in the period, that planned order will remain in the period and will not be moved, even if there is no need for it. The time fence is expressed in days and is calculated from the requirement calculation date. Example The locking time fence is 10 days. A sales order is to be delivered in 7 days, and there is no inventory that can cover the requirement. The requirement calculation will suggest that the planned purchase order be delivered in 10 days. |
||
|
|
The period in which planned production orders for BOM items are exploded into requirements for components. BOM proposals with requirement dates falling outside the explosion time fence are not exploded. The time fence is expressed in days and is calculated from the current date. |
||
|
|
The period during which the planned production order is capacity scheduled. The master schedule uses the item's active production route and plans the route based on the requirement date. |
||
|
|
The period for which the sales forecast from the forecast plan is to be included in master scheduling. The time fence is expressed in days and is calculated from the current date. |
||
|
|
The key that is used to reduce sales forecasts that are transferred from the forecast plan. Master scheduling reduces the sales forecast with a specific factor or according to a specific pattern. Set up the reduction keys in the form. The pattern that the sales forecasts follow will depend on how you set up the master plan in the field. |
||
|
|
A safety margin, expressed in days, that is added to the receipt's requirement date during master scheduling.
For example, if the receipt margin is set to four days, and a purchase order line is scheduled for receipt on 5/15, master scheduling calculates the adjusted receipt date as 5/19. |
||
|
|
A safety margin, expressed in days, that is deducted from the issue's requirement date during master scheduling.
For example, if the safety margin is set to four days, and a sales order line is scheduled for delivery on the 5/15, master scheduling calculates the adjusted delivery date as 5/11. |
||
|
|
A safety margin, expressed in days. It is added to the item lead time for all planned orders during master scheduling.
|
||
|
|
When marked, this field specifies that the items in this coverage group are to be set for action messages. The action messages will suggest ways you can avoid unwanted situations and change existing purchase and production orders. |
||
|
|
The number of days from the current date that there should be action messages for the requirement. |
||
|
|
The maximum number of days that receipts may arrive in inventory before issues without generating postponement actions. |
||
|
|
Enter the maximum number of days that receipts may be received in inventory after issues without generating advance actions. When you use this, the system lets issue orders be handled when the items have not yet been received in inventory without generating advance actions for the selected period. |
||
|
|
Specify whether the action messages should be based on the requirement date or the futures date. If you are also running the futures messages, it is wise to specify that the action messages should be based on the futures date instead of the requirement date. In this manner actions will function according to what is practical. |
||
|
|
When marked, this field specifies that master scheduling may propose that existing planned orders be advanced in time. The field specifies the maximum number of days permitted between orders that are to be advanced. Example A purchase order with a delivery time of five days is scheduled to arrive on 8/10. A sales order is to be delivered on 8/6. Master scheduling will suggest that the purchase order be delivered 8/6 instead of 8/10. |
||
|
|
Specifies whether master scheduling may suggest that existing planned orders be postponed. Specify in the field the maximum number of days permissible to be postponed between sales. Example A purchase order is scheduled to arrive on the August 10, and a sales order is to be sent on August 13. Master scheduling will suggest that the purchase order should arrive August 13 instead of August 10. |
||
|
|
Specifies whether master scheduling may suggest writing down production orders, purchase orders, or other receipt transactions to avoid excess inventory levels. |
||
|
|
When marked, this field specifies that master scheduling may suggest writing up production orders, purchase orders, or other receipt transactions to avoid shortages in inventory. |
||
|
|
Enable derived actions, that is, the transfer of actions to component items. |
||
|
|
Select the check box to enable futures messages for items. Futures messages warn when a sales order or production will not be completed by the scheduled date. A message is generated to indicate a date in the future by which an order can be delivered with the particular constraints. |
||
|
|
Enter the number of days from today's date that futures messages are calculated. |
