Skip to Content

Security lead time for PO/MO

by
Odoo

$ 147.69

v 19.0 Third Party 1
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Purchase (purchase)
• Invoicing (account)
• Discuss (mail)
• Manufacturing (mrp)
• Inventory (stock)
Lines of code 344
Technical Name fal_security_leadtime
LicenseOPL-1
Websitehttps://www.cluedoo.com/shop/lic-clu-set-tim-0097-security-lead-time-for-po-mo-6805
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Purchase (purchase)
• Invoicing (account)
• Discuss (mail)
• Manufacturing (mrp)
• Inventory (stock)
Lines of code 344
Technical Name fal_security_leadtime
LicenseOPL-1
Websitehttps://www.cluedoo.com/shop/lic-clu-set-tim-0097-security-lead-time-for-po-mo-6805






ODOO'S FUNCTION

In Odoo, key planning dates (like Expected Arrival for purchases or Scheduled Date for manufacturing) are calculated based on fixed lead times configured in the global Settings.

Security lead times are applied to all transactions, meaning you cannot easily set different safety margins for specific vendors or products. This generic approach often leads to planning mismatches, especially when dealing with international vendors who have varying reliability.


CLUEDOO'S FUNCTION

Cluedoo enhances the accuracy of planning dates by introducing:

​1️⃣ Vendor Security Lead Time : A specific buffer defined directly on the Vendor Pricelist for Purchase Orders.

​2️⃣ Manufacturing Security Lead Time : A specific buffer defined directly on the Bill of Materials (BoM) for Manufacturing Orders.

​3️⃣ A smart fallback hierarchy : The system first checks for these specific Cluedoo lead times; if none are found, it falls back to the standard Odoo settings.

This allows the system to automatically recalculate deadlines with high precision. You can apply stricter safety margins to unreliable sources while keeping standard times for others, ensuring your planning reflects reality.


1. ODS has the setting for Security Lead Time (sales/purchase/MO) in config panel.

  • Sales Security Lead Time : a buffer notifying the team to prepare for outgoing shipments earlier than the scheduled date.
  • Purchase Security Lead Time : a buffer is set to account for potential delays in supplier deliveries.
  • Manufacturing Security Lead Time : a buffer is set to account for potential delays in the manufacturing process

Note: In v19, Manufacturing Security Lead Time and Security Lead Time for Purchase is unavailable

2. Fill field Vendor Security Lead Time and Delivery Lead Time on product

3.
  • Customer Lead Time : default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. You can config or not.
  • Create a SO with a product which has route MTO and Buy > check date in Delivery Order
  • if you set Delivery date, it will take date from delivery date. If you do not set, it will take order date normally.
  • Deadline (7/7) = Order Date (7/7) + Customer Lead Time (0 day)
  • Schedule Date from DO (5/7) = Deadline (7/7) - SO security Lead Time (2 days)


Note : if you set Delivery date, it will take date from delivery date. If you do not set, it will take order date normally.

4. Go to PO > Expected Arrival and Order Deadline on the PO will be computed automatically due to this formula:
  • Expected Arrival (date_planned) = schedule date from Delivery Order - Vendor Security Lead Time
Note:
It will take data from Vendor Security Lead Time if you set in it and if you do not > it will take from ODS ( Security Lead Time for Purchase )

  • Order Deadline (date_order) = Expected Arrival - Delivery Lead Time from ODS ( You can recheck in step 2)
5. You can fill field Manufacture Security Lead Time and Manufacture Lead Time on BoM of product that you want to produced
6. Create SO with MTO product > Open MO > Schedule Date & Scheduled End of that MO will be computed automatically due to this formula:

  • Scheduled End (date_finished) = Scheduled Date from Delivery Order - MO Security Lead Time
Note: it will take data from MO Security Lead Time if you set it and if not > take from ODS ( MO Lead Time)

  • Scheduled Date (fal_date_start) = Scheduled End - MO Lead Time from ODS


7. This module also applies to Purchase Order created in MPS . Go to MPS > Choose a product that needs replenishing > Replenish > a PO will be created, and Order Deadline will also be filled with the same formula.

Note: The first day of the week or month that you replenish in MPS will be the Expected Arrival .


8. Manufacture Order from MPS

Note: The first day of the week or month that you replenish in MPS will be the Expected Arrival.

Note: From v18, cluedoo lead time changed to manufacturing security lead time.
MO Scheduled Date = The time you confirm Product Replenish
MO end date = Scheduled Date in Product Replenish wizard
MO Start date =  MO end date - manufacturing lead time (Manuf lead time)





9. Go to Replenishment
If a product have 2 vendors, you can choose to vendor for calculate forcasted date by click "Set as Supplier" 






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.