Skip to Content
Menu

Block "mark as done" parent MO if child MOs are not finished

by
Odoo

198.25

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Manufacturing (mrp)
Inventory (stock)
Discuss (mail)
Lines of code 46
Technical Name fal_mrp_block_confirm
LicenseOPL-1
Websitehttps://www.cluedoo.com/shop/block-mark-as-done-parent-mo-if-child-mos-are-not-finished-6756
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Manufacturing (mrp)
Inventory (stock)
Discuss (mail)
Lines of code 46
Technical Name fal_mrp_block_confirm
LicenseOPL-1
Websitehttps://www.cluedoo.com/shop/block-mark-as-done-parent-mo-if-child-mos-are-not-finished-6756

STORY BEHIND THE FEATURE

ODOO BEHAVIOR
In Odoo, Manufacturing Orders (MOs) operate independently . Even if a parent MO relies on a child MO for a semi-finished product, the system allows users to mark the parent MO as Done before the child MO is completed. This flexibility comes with drawbacks in traceability and production control.






CLUEDOO BEHAVIOR

CLuedoo enhances Odoo’s manufacturing logic by enforcing BoM-based sequencing across MOs. It prevents the completion of a parent MO until all its dependent subMOs are marked as Done . This ensures that production strictly follows the BoM hierarchy.


Key features:

✅ Block the parent MO from being completed if child MOs are still open

✅ Enforces execution order based on BoM levels (e.g., L5 → L4 → L3 → L2 → L1)

CLUEDOO RECOMMENDATION

Install on 100% of your database.


OUR FEATURES AS SOLUTIONS

Block parent MO confirmation if child MOs are not finished

HOW TO USE THIS MODULE

1. Go to Settings > Checkbox Block Confirm for Manufacturing Order
2. Create a product with multiple BoM levels
3. Create a Manufacturing Order > Add the product > Confirm > A Child MO smart button will appear > Produce All
4. If you try to produce the MO without finishing the child MO > An Invalid Operation warning will pop up
5. After the child MO has been marked as done > You can produce the parent MO as usual

Note: This module introduces a hierarchical execution restriction

e.g., you have a BoM with 5 levels:
L5 → L4 → L3 → L2 → L1
(L5 is the most basic component, L1 is the final product)

Under CLuedoo, the sequence to finish MOs must follow:
✅ Finish L5 → then L4 → then L3 → then L2 → finally L1
❌ You cannot finish L1 if L3 or L2 is still open.




Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.