The first method is: StockLocation.is_sublocation_of()
This method is currently used in:
* wms/stock_dynamic_routing
* wms/shopfloor
* wms/stock_move_source_relocate
* stock-logistics-warehouse/stock_reserve_rule
* ddmrp/ddmrp
The goal will be to use this module as dependency instead of
reimplementing the method in each.
Other methods should follow in "stock_helper".
Note: I opened https://github.com/odoo/odoo/pull/53866 to propose a
generic version of this method, expecting odoo's opinion, but got no
answer.
When the 2 last moves of a stock.picking are assigned at the same
time by 2 jobs (different products both available), none of the
transaction will see that it is the last move to be assigned. As a
result, the picking will stay in state "confirmed" even if all its
moves are assigned.
Lock the stock.picking records when we call auto_assign.
If we have many pickings touched for the same product, the lock
can be quite large, so we may have to find a better option.
I could not write a test to exercise this, because we can't have 2
transactions being aware of it, even if we create the picking in demo
data as tests can be run during install.
Automatically check availability of stock moves when a move is set to "done".
It uses queue jobs to verify the availability in order to have a minimal impact
on the user operations.
The conditions to trigger the check are:
* A move is marked as done
* The destination locations of the move lines are internal
* The move doesn't have successors in a chain of moves
At this point, jobs are generated:
* One job per product
* Any move waiting for stock in a parent (or same) location of the internal
destination locations from the done move has its availability checked
Only one job is generated for an identical set of (product, locations).
