The continental accounting requires a cost for such moves.
issue11654
review439401003
(grafted from c2158d1ef10a4b87f09a353d5db6ba07dc87a95d)
--HG--
branch : 6.0
The outgoing moves of an internal shipment with transit must use the effective
start date when done.
issue11337
review397651002
(grafted from 8536360509ed74b63390ff550684510c2367ead7)
--HG--
branch : 6.0
The internal quantity is stored without precision constraint and so the sum
result of many rows cumulate the rounding issue.
So the quantity must be rounded to return correct result when operator is
equality.
But as getting the digits from the product default uom would require to make
many joins, the simplest and more efficient solution is to use the highest
digits of the units.
issue11235
review390001002
(grafted from 4b8495cb0efdfb71f11a7520967ed5ef9d9dfca9)
--HG--
branch : 6.0
If the index is created only in __register__ then it is dropped before being
created again.
issue11197
review389881002
(grafted from c994fc728bf3ce1530eebf8fea14960960456d3c)
--HG--
branch : 6.0
When modify in __setup__ the domain of a field defined in the same class, this
alter the original copy of the field. So the domain is appended to itself on
each __setup__ call (each time the model is extended by another module).
issue10406
review336241002
(grafted from 3670b1a582ecf41612f1f84b73b8ab68f8bf8b1b)
--HG--
branch : 6.0
Staging moves are automatically assigned when purchased so
we should remove them when packing a shipment as they are
not part of the shipment.
We also skip moves with zero quantity because they will
always succeed.
issue9448
review313951002
As the inventory creates and do the moves in the same transaction, the warning
about effective date in future can not be ignored (the ids change).
Also the warning name should be based on an ordered list of record to ensure to
generate always the same name.
issue9707
review328441002
We can use the compute quantities query if the request is for a single location
because all the locations are children and so we can do a SUM.
issue9594
review323991002
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 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
It is forbidden to create move with the same source and destination locations.
To avoid this case, we remove the destination location from the quantities to
pick.
issue7856
review66541002