We add a new model based on stock move that compute the cumulative quantity for
each incoming or outgoing move.
The product quantities by warehouse is refined to only get row at the date the
quantity actually change.
We also add company and access rules for both models.
On back-end without window function, the cumulative quantity is the initial
quantity of the day.
issue9389
review297881002
We add a common method to round prices that are stored using the price digits.
It is useless to use the digits from the field because it can not be changed in
any other way than by configuration.
issue9146
review299521002
We remove the lost and found location on the inventory to only used one define
on the warehouse or parent of the inventoried location.
issue9071
review276901002
Shipments that create inventory moves should fill a planned date for them as we
have a method to compute it. The probability is high to inventory the product
once received.
issue9043
review272871002
We add the flake8 configuration used so we ensure everyone uses the same.
We remove the usage of __all__ for non public API.
When possible, we rationalize the class name according to its __name__ and module.
issue9082
review297061002
An empty stock_date_end is converted into max date in compute_quantities_query
and forecast context should be explicitly disable.
issue9044
review282931002
The windows that display product quantities should explicitly manage the
stock_skip_warehouse context to ensure static result.
issue9041
review253051002
The "Modify Cost Price" wizard create a revision record for each template or
product. The cost price re-computation methods apply those revisions at the
beginning of their date.
The stock accounting move is created and posted when the cost price is modified
by the re-computation.
issue8930
review260751002
We sent an order to the client for action and xxx2Many so its screen has
always a default order set.
To position a new record on non editable tree, we use the order of the 'id'
column if presents.
issue8880
review276501003
sao prevents to open tree with more children than its limit and it switches to
the form view. So to allow the user to see the data, we must add a form view.
issue8844
review274341002
Cédric Krier