The planning engine issues exception messages (exceptions) to:
Alert you to a situation that may need your intervention, for example, a past due sales order
Recommend that you perform an action, for example, change the date of a supply order
The planning engine issues certain exceptions for all plan types and others for only certain plan types.
The planning engine only issues exceptions against items and resources that have exception sets assigned to them.
You can consider exception messages and recommendations when you:
Run plans
Review plans
When running plans, you can:
Set plan options that make your plans consistent with your company business practices.
Run them for a single plant or for an entire supply chain.
Run them with no material and resource constraints, with some material and resource constraints, and with optimization objectives (for example, profit, inventory turns, customer service, and overloading resources).
When reviewing plans, you can:
Search for specific exceptions (for example, exceptions that relate to a specific buyer or item)
View exceptions grouped by type
Drill down to related exceptions and detailed supply and demand information
Run simulations to test improved plan suggestions
Use Oracle Workflow to notify employees and trading partners of specific exception and to create automatic resolution actions
Oracle Advanced Planning and Scheduling displays exception messages by exception group. An exception group is a group of exception messages that deal with a common issue.
This section lists the exception groups and the exception messages in each exception group.
Sales order/forecast at risk
Past due sales orders
Past due forecast
Late replenishment for sales order
Late replenishment for forecast
Early replenishment for sales order
Early replenishment for forecast
Sales order/forecast at risk due to resource shortage
Sales order/forecast at risk due to material shortage
Requirement causes resource overload
Order causes supplier capacity overload
Order causes transportation weight capacity overload
Order causes transportation volume capacity overload
Order with insufficient lead time
Requirement with insufficient lead time
Order lead time constraint
Requirement lead time constraint
Demand quantity not satisfied
Late supply pegged to forecast
Late supply pegged to sales order
Order violates a business calendar
Material constraint
Resource constraint
Resource overloaded
Supplier capacity overloaded
Resource underloaded
Batch was started with less than minimum capacity
Batch was started with more than maximum capacity
Transportation resource constraint
Transportation resource's weight overloaded
Transportation resource's volume overloaded
Items with a shortage
Items below safety stock
Items with excess inventory
Past due orders
Orders to be rescheduled out
Orders to be cancelled
Orders to be rescheduled in
Orders with compression days
Orders scheduled to next inventory point
Order is firmed late
Requirement is firmed late
Order is firmed early
Requirement is firmed early
Shared supply scheduled late
Planned order uses alternate BOM/routing
Planned order uses substitute components
Planned order uses alternate resources
Order sourced from alternate facility
Order sourced from alternate supplier
Demand satisfied using end item substitution
Items with a shortage in a project/task
Items allocated across projects/tasks
Items with excess inventory in a project/task
Items with negative starting on hand
Items with expired lot
Items with no activity
Sourcing split percentage violated
Batches
Discrete jobs
Flow schedules
Jobs
Purchase requisitions
Use planning exception sets in the source instance to specify sensitivity controls and exception time periods for exceptions.
The fields in the exception set are not item and resource attributes but they act as if they are. Define as many planning exception sets as you need for your different types of items and resources (use the Planning Exception Sets form). Then, assign exception sets to items and resources.
The planning engine only issues exceptions against items and resources that have exception sets assigned to them.
Sensitivity controls control the quantity and percent thresholds for exception messages. For example, setting Excess Quantity to 3000 limits reporting of excess to situations in which supply exceeds demand by 3000.
Exception time period types control the time period for exceptions. For example, setting shortage exceptions to Planning time fence limits reporting of shortage to those situations in which the shortage is within the planning time fence.
Before creating and updating exception sets, study the exception messages. When the description of an exception message indicates that it is subject to exception set values, consider sensitivity controls and time periods that make sense for your business.
Navigate to the Planning Exception Sets window.
Create or select a planning exception set name.
Enter sensitivity controls except User-Defined Time Fence (Days).
Select exception time period types.
If you selected User-defined time fence in any of the fields, specify the length of the time fence in days in User-Defined Time Fence (Days).
Save your work.
To assign a planning exception set to an item, navigate to the Items form, MPS/MRP Planning attribute group, Exception Set field.
To assign a planning exception set to a resource:
Navigate to the Departments form, click Resources, and view the Resources form
Navigate to the Owned region, Planning tabbed region, Exception set field
To assign a planning exception set to an item, navigate to the Items form, MPS/MRP Planning attribute group, Exception Set field.
To assign a planning exception set to a resource:
Navigate to the Departments form, click Resources, and view the Resources form
Navigate to the Owned region, Planning tabbed region, Exception set field