summaryrefslogtreecommitdiff
path: root/addons/stock/static
diff options
context:
space:
mode:
authorRémy Voet (ryv) <ryv@odoo.com>2020-07-30 08:00:12 +0000
committerRémy Voet (ryv) <ryv@odoo.com>2020-08-18 07:48:27 +0000
commit57f805f71e9357870dfc2498c5ef72ebd8ab7273 (patch)
treec60b7e9f22ad71b8d0beed7f6d5898cdf7c87f31 /addons/stock/static
parente40553723b893bcd2244e9b9fcc5c1a7e1bf27d3 (diff)
[IMP] stock*,mrp*: Dates Refactor
- The deadline of MO generated via procurements is calculated differently. Now, it doesn't take anymore in account the manufacturing_lead of the company (Security Lead Time of MO). The computation of planned date remains unchanged. - The date_expected fields was duplicated with the date fields except when the move was done. Merge both fields. The only information lost is: we can't know what was the scheduled date before processing move (`state` == done). Indeed, the date becomes the actual move processing datetime. - The `date` in `stock.picking` field contained the time of (purchase) order `date_order` (`purchase.order`). This field is was wrongly used in the kanban view where we expected to see date_planned instead. Also, the `_order` used this date instead of date_planned too. - The `delay_alert` is activate independently of stock rules. Then it is now activate in all case. - Remove the auto-reschedulting process of stock move via the stock rule (`propagate_date` and `propagate_date_minimum_delta`). Replace it by a automatic deadline date (`date_deadline`) propagation. The deadline is the promise done to/by vendor/client (SO/PO) then it is a readonly fields on picking/move and MO. - Now the Scheduled date (`date`) of stock move is never propagate and it is only related to the Scheduled date of related document (MO or picking). - Now when a move is created from procurement (sale), `date_planned` = `date_deadline` - `security_lead`. - The `delivery_date` of sale is no editable after confirmation and propagate as the deadline to related stock move linked to order_line - Adapt filter and decoration of MO and picking. - Because we are the client in case of purchase (PO), the promise of vendor can be not respected. Then we add the lead security to the deadline (inverse the sale order logic) of PO picking (promise reciept date + security lead) to match with the replenishment. task-2246665
Diffstat (limited to 'addons/stock/static')
-rw-r--r--addons/stock/static/src/xml/popover_widget.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/addons/stock/static/src/xml/popover_widget.xml b/addons/stock/static/src/xml/popover_widget.xml
index d9cf2b4fe8d..d5c503565ec 100644
--- a/addons/stock/static/src/xml/popover_widget.xml
+++ b/addons/stock/static/src/xml/popover_widget.xml
@@ -11,9 +11,9 @@
<div t-name="stock.PopoverStockRescheduling">
<p>Preceding operations
- <t t-foreach="late_elements" t-as="late_element">
- <a t-esc="late_element.name" href="#" t-att-element-id="late_element.id" t-att-element-model="late_element.model"/>,
- </t>
- planned on <t t-esc="delay_alert_date"/>.</p>
+ <t t-foreach="late_elements" t-as="late_element">
+ <a t-esc="late_element.name" href="#" t-att-element-id="late_element.id" t-att-element-model="late_element.model"/>,
+ </t>
+ planned on <t t-esc="delay_alert_date"/>.</p>
</div>
</templates>