The Scheduled Date in a Manufacturing Order (MO) can vary depending on how the MO is created, whether Work Orders (WOs) are generated, and whether the actions “Plan” or “Plan Based on Component Availability” are applied.
Let’s review each scenario step by step.
Default Scheduled Date
The default Scheduled Date depends on how the MO is created:
-
Manually created MO
When you create an MO manually, the Scheduled Date defaults to the creation date. No calculations are performed based on component availability, Work Orders, or other factors. -
MO triggered automatically (e.g., from a Sales Order)
When an MO is generated automatically to fulfill a demand, Odoo sets the Scheduled Date to:
Delivery Order Scheduled Date - Manufacturing Lead Time - Manufacturing Security Lead Time (if defined).
Actions That Affect the Scheduled Date After Confirmation
Once the MO is confirmed, two manual actions can recalculate the Scheduled Date:
- Plan
- Available only if Work Orders exist for the MO.
- Sets the MO Scheduled Date to the earliest Start Date of a WO.
(You can explore this action further in the post Understanding the "Plan" Button in Manufacturing Order.)
- Plan Based on Component Availability
- Calculates the Scheduled Date based on the forecasted availability of components.
- The Scheduled Date is set to the latest date when all required components are available.
- Each component must have an expected date defined for the calculation to be correct.
- Important: Make sure expected dates are set on Purchase Orders before confirming them. Updates made afterwards will not be reflected in the MO.
Manufactured Components
If the BoM includes manufactured components, the Scheduled Date for their MOs is calculated as:
Main MO Scheduled Date – Manufacturing Lead Time (child MO) – Manufacturing Security Lead Time (if defined).
Understanding how Scheduled Dates are calculated and which actions influence them is essential for designing effective manufacturing and procurement processes. Leveraging Odoo’s standard functionality helps avoid unnecessary customisations, which are often costly to maintain and migrate later.