In our current implementation of Planning Optimization, we’ve encountered a significant limitation: approved planned orders are being overwritten by subsequent MRP runs if the approval occurs after the batch job has started. This behavior, while aligned with current system design, is creating operational friction for our business users.

In our environment, it is common for users to make changes to planned orders and approve them throughout the day. However, because the Planning Optimization engine only captures a snapshot of data at the start of the batch job, any approvals made afterward are not respected—leading to those orders being overwritten. This was not the case with the classic master planning engine, which allowed for more flexible MRP execution without disrupting approved plans.

Proposed Enhancement:

Introduce a feature or configuration option that ensures approved planned orders are preserved during MRP runs, even if the approval occurs after the batch job has started. This could involve:

• A real-time check for approval status before overwriting.
• A buffer or grace period for recently approved orders.
• A toggle to prevent overwriting of any approved orders regardless of timing.