MCP consistency rules
When you add work to the plan on request, the scheduler typically
handles operation conditions as external objects. Some checks and
restrictions, that are valid for external predecessors, are valid
also for conditions. In particular, this applies for:
- Status change consistency:
-
- You cannot directly change the status of an operation with undefined or false conditions (the scheduler applies the same checks as it does for not completed external predecessors). Only when rerunning an occurrence might you indirectly have this kind of change.
- You cannot directly change the status of an operation with external or conditional successors that are already S (Started), C (Completed), X (Suppressed by condition), or E (Ended in error). Only when rerunning an occurrence might you indirectly have this kind of change.
- Dependency resolution:
- When adding an occurrence to the current plan, you must require the dependency resolution if you want to add also the related conditions, even for conditions that specify only internal predecessors. For details, see Including dependencies defined in the database.