This screen shows a list of issues requiring the planner’s attention.
Each entity type has it’s own set of exceptions:
No plan exists yet to satisfy this demand.
A demand is planned for more than the requested quantity.
A demand is planned for less than the requested quantity.
A demand is satisfied later than the accepted tolerance after its due date.
A demand is planned earlier than the accepted tolerance before its due date.
Some data problem prevents this object from being planned.
A resource is being overloaded during a certain period of time.
A resource is loaded below its minimum during a certain period of time.
A buffer is carrying too much material during a certain period of time.
A buffer is having a material shortage during a certain period of time.
Flagged when a buffer has no ways of replenishment or too many.
Flagged when an operationplan is being planned in the past.
For operationplans in the status approved or proposed, the start data is before the
current date of the plan.
For operationplans plans in the status confirmed, the end date is before
the current date of the plan (ie they are overdue and should have been finished
Flagged when an operationplan in the status approved or proposed
is being planned before its fence date, i.e. it starts 1) after the current date of
the plan, 2) it starts before the current date of the plan plus the release fence of
the operation, and 3) the status is approved or proposed.
Flagged when the sequence of two operationplans within a routing isn’t respected.
||Description of the problem.
A number expressing the seriousness of the problem.
Sorting on this field allows the user to focus on the most important
||Date at which the problem starts.
||Date at which the problem ends.