[ADD] stock_move_planned_consumed_date

[petrus-v]

Base module to avoid mixing move line that is planned to consumed in different dates

[rousseldenis]

@petrus-v Have you tried with date_deadline field ?

[rousseldenis]

@petrus-v Have you tried with date_deadline field ?

Which is propagated at sale order confirmation from the commitment_date on the order level

[petrus-v]

@petrus-v Have you tried with date_deadline field ?

I know about the date_deadline which propagate on stock_picking, but if you check the availability of those picking a bit earlier nothing prevent to reserved products that will be expired before the deadline (At the moment we haven't installed stock release modules mechanisms), also in complex industry with multiple warehouse where procurement group are not necessarily propagated we could get some transfer (stock.picking) with different moves where expected consumed date are different (to make this easier to reproduce we are using #1226 which basically round the deadline date time to date)

this is the base module for #1509 and #1511

[rousseldenis]

@petrus-v Have you tried with date_deadline field ?

I know about the date_deadline which propagate on stock_picking, but if you check the availability of those picking a bit earlier nothing prevent to reserved products that will be expired before the deadline (At the moment we haven't installed stock release modules mechanisms), also in complex industry with multiple warehouse where procurement group are not necessarily propagated we could get some transfer (stock.picking) with different moves where expected consumed date are different (to make this easier to reproduce we are using #1226 which basically round the deadline date time to date)

this is the base module for #1509 and #1511

Ok, understand.

FYI, there is a change in v16 (and v15) merged yesterday that allows to ignore date_deadline when merging: odoo/odoo@fdaba15

[alexandregaldeano]

My comments are about code style preference, as such, you can of course discard them :)

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.