What Do the Planning Notifications Mean?

1. Operation cannot be started because previous operation(s) were not completed in time

A planning operation has a previous planning operation (by order) that is not ready and an end date that conflicts with the start date of the current planning operation.
Starting point: planning operation

2. Operation is not completed when it should have been completed

A planning operation is not ready and the end date of the planning operation is before today + any delay days (configured in the administration settings).
Starting point: planning operation

3. Operation was not started when it should have been started

A planning operation has not been started and the start date of the planning operation is before today + any delay days (configured in the administration settings).
Starting point: planning operation

4. More time was spent than planned

A planning operation has a spent time that is greater than the total time + any percentage deviation (configured in the administration settings).
Starting point: planning operation

5. Current Time Registration data is available

The total time of the hours is not equal to the time spent on the planning operation (the planning operation receives the Advice = Time field).
Starting point: planning operation

6. Operation is reported ready in Time Registration

A planning operation has not been reported as completed, while it has been reported as completed in the time records (the planning operation receives the Advice = Ready field).
Starting point: planning operation

7. Planning date is not met

Retrieves all end products where 'Quantities Ready' = false and where Planning Date is less than Planned Date.
Starting point: assembly

8. Planning has yet to be released

Retrieves all assemblies for which Planned Date is empty.
Starting point: assembly

9. Planning must be released again

Retrieves all sub-assemblies for which Planned Date is not empty and greater than the end date of the sub-assembly.
Starting point: sub-assembly

10. Material will not be available on time

This notification checks in two different ways. If the PC operation (linked to the planning operation) has linked materials, the check is done on these materials. If the PC operation has no associated materials, this is done over all materials within the sub-assembly.
Starting point: planning operation

Retrieves all Purchasing-Material (transaction type 20) links from the linked materials with status = 0 (not booked). This checks whether the date (1st check: confirmed delivery date; if empty: receiving date) + material handling time on the purchase order line is greater than the start date of the planning line or the start date is less than or equal to today.

Or:
Retrieves all Production-Material (transaction type 32) links from the linked materials with status = 0 (not reported ready). This checks whether the date on the production order line (1st check: planned date; if empty: planning date) + material handling time is greater than the start date of the planning line or the start date is less than or equal to today.

11. Outsourcing will not be available on time

Retrieves all batch transaction links of planning operations for which 'Outsourcing' = true and status = 0 (not booked). This checks whether the date of the purchase order line (1st check: date confirmed; if empty: receiving date) + outsourcing handling time is greater than the end date of the planning line or the end date of the planning line is less than today.
Starting point: planning operation

12. Sales delivery date is not met

Retrieves all batch transaction links of assemblies whose status = 0 (not reported ready). This checks whether the delivery date on the sales order line is less than the end date of the assembly.
Starting point: assembly

13. Operation started on different resource than planned

Retrieves (when 'Started' = true) all hours clocked on the same planning operation, but have a different operation.
Starting point: planning operation