Search 1.9 billion lines of Odoo code on GitHub

stock_planning_improved

Author: NDP Systèmes
License: AGPL-3
Branch: 8.0
Repository: ndp-systemes/odoo-addons
Dependencies: connector, procurement, stock, and stock_working_days
Languages: Markdown (40, 6.7%), PO File (166, 27.9%), Python (222, 37.4%), and XML (166, 27.9%)
Other branches: 8.0-entrepot-production, 8.0-entrepot-qualif, 8.0-sirail-de-qualif, 8.0-sirail-production, 8.0-sirail-qualif, 8.0-thomas-sirail-production, 8.0-thomas-sirail-qualif, 9.0, 9.0-brasserie-production, 9.0-brasserie-qualif, 9.0-fluxtendu-production, 9.0-fluxtendu-qualif, 9.0-mayette-production, 9.0-peopleandbaby-production, 9.0-reanova-production, 9.0-reanova-qualif, 9.0-sirail-bus-production, 9.0-sirail-bus-qualif, and 9.0-thomas-reanova-qualif
Other repositories: VbossEkat/odoo-addons, aaltinisik/odoo-addons, appnessgit/odoo-addons, cialuo/odoo-addons-1, gitstalker/odoo-addons, haylahi/odoo-addons-2, kit9/odoo-addons-3, leangjia/odoo-addons, loftwah/odoo-addons, marcelsavegnago/odoo-addons-4, mgielissen/odoo-addons-2, mohamedhagag/odoo-addons-1, molandtoxx/odoo-addons-4, odoousers2014/odoo-addons-supplier_price, osstw/odoo-addons, qponline/odoo-addons, quadit-dev/odoo-addons, rossasa/ndp-addons, shouyejing/odoo-addons, suningwz/odoo-addons-5, tate11/odoo-addons-2, thomas-tankengine/odoo-addons, tmp2000/odoo-addons-1, and vidtsin/odoo-addons-8

<h1>Stock Planning Improved</h1> <p>This modules implement the improved planning to the stock module.</p> <h2>Improved planning concept</h2> <p>The improved planning is a standardization of planning management in Odoo based on the following concepts:</p> <ul> <li>A planning is made of several tasks linked together. Each task can happen only when all the previous tasks are done.</li> <li>Each task has two dates: <ul> <li>A due date which is the date before which the task is to be done at the latest. The due date is changed only when a major rescheduling occurs. It is calculated backwards, task by task, from the due date of rightmost task of the planning (which is usually the date at which we promised to deliver the product to the customer).</li> <li>A planned date which is the date at which we imagine the task is going to be executed given the information we have now. The planned date should be changed each time we have a new information and should never be in the past (since we are today and the task is not done, we have the information that the task will be executed sometime from now, but not before). It is calculated forwards, task by task, from the task(s) currently in execution.</li> </ul></li> <li>When a task is done, the actual execution date and the planned date are the same, but the due date is unchanged.</li> <li>The only relevant way to measure whether the project is late or early is for each task to compare the due date and the planned date.</li> <li>Comparing the planned date with today&#39;s date gives a indication on the accuracy of the planning, not on whether we are late or early.</li> </ul> <h2>Improved planning applied to stock</h2> <p>In the stock module, the application of the improved planning concepts is the following:</p> <ul> <li>Tasks are stock moves to be executed.</li> <li>Tasks links are links between stock moves made by the procurement rules (make-to-stock)</li> <li>The due date of a move is the date of the procurement order. It is represented by the &quot;date&quot; field of the stock move.</li> <li>The planned date of the move is the date at which we suppose the move will be performed. It is represented by the &quot;date expected&quot; field of the stock move.</li> <li>If a procurement is rescheduled, the &quot;date&quot; fields of its stock moves are also modified to reflect the new date. If one of the move has previous moves (make-to-order configuration), the procurement date for the previous moves is also modified, which will modify the date of the previous moves in turn.</li> <li>If a stock move is done at a given date and has a following move, the &quot;date expected&quot; of the latter will be updated accordingly.</li> <li>When &quot;date&quot; and &quot;date expected&quot; are updated, the delay taken between moves is the one of the procurement rule which generated the move.</li> </ul> <h2>Notes</h2> <ul> <li>This module interfaces with the other planning improved modules such as purchase and mrp.</li> <li>This module depends on stock<em>working</em>days module since no decent planning can be done without taking into account the working days.</li> </ul>