Creating Planning Exception Sets
You can define and update planning exception sets to identify items, orders, and resources that require attention based upon a set of predefined action messages. This facilitates control over message sensitivity, message priority, and marking those messages where action has been taken. After you have defined a planning exception set, you can assign it to the appropriate items when you set the Exception Set attribute for the MPS/MRP Planning group in Oracle Inventory. (If you're creating an exception set that includes exceptions involving resources, you also need to associate the exception set to resources in Bills of Material.) You will see exceptions based on your exception set associated with your items, and resources.
To enter and update planning exception sets:
You will use this window to set the conditions under which you want to see an exception message.
2. Select a planning exception set name to identify items, orders, and resources that require attention based upon a set of predefined action messages.
To enter exception time period types for monitoring exceptions:
2. Enter exception time period types for monitoring different types of exceptions within a time period.
An exception will occur only if the type of exception occurs during the specified time period. The different types of exceptions for which you must specify a time period type are:
Shortage Exceptions: occur when the projected on-hand quantity of the item is negative or below safety stock.
Excess Exceptions: occur when the projected on-hand quantity of the item exceeds zero or safety stock by more than the value you entered in Excess Quantity.
Resource Shortage Exceptions: occur when capacity is over-utilized by a percentage greater than the value entered in the Over-utilization field in the Sensitivity Controls portion of the Planning Exception Sets window. For example, an exception will occur if you entered 10% in Over-utilization and capacity is over-utilized by 15%.
Resource Excess Exceptions: occur when the capacity is under-utilized by a percentage greater than the value entered in the Under-utilization field in the Sensitivity Controls portion of the Planning Exception Sets window.
Repetitive Variance Exceptions: occur when the suggested aggregate repetitive schedule differs from the current aggregate repetitive schedule by more than the value entered in Repetitive Variance.
Note: Some exceptions only occur if you also enable pegging at the item level (using the Pegging attribute in the MPS/MRP Planning Group) and the plan level (using the Plan Options form). These exceptions are:
- Late order due to resource shortage
- Late supply pegged to forecast
- Late supply pegged to sales order
The different exception time periods are:
Cumulative manufacturing lead time: the processing lead time on a Make end assembly plus the processing lead time on a Make subassembly
Cumulative total lead time: the cumulative manufacturing lead time plus the preprocessing, processing, and postprocessing lead time on a Buy component
Planning time fence: the period starting from today's date and continuing for the number of days specified in the Planning Time Fence item attribute
Total lead time: the preprocessing lead time plus the processing lead time on a Make end assembly
User-defined time fence: the number of days you specify in the User-defined Time Fence field in the Sensitivity Controls portion of the window
Planning Exception Sets
Reviewing Planning Exceptions
Item Defining Attributes