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
The value stored in a period are at the date so it should be forbidden to
create move ate this date and we can use the value up to this date.
issue7489
review45721002
If the flat location children are not explicitly in the requested locations,
they should not be included because the quantity is already included in the
parent location and they will be added twice if a single location is requested
(because of the quick loop).
issue7162
review44871003
It uses the product_uom_category field which is a Function to allow other
modules to extend the computation to enforce a specific category.
issue6839
review39791002
In case of negative quantity, the unit price is used as cost price if it is an
incoming and the cost price is kept if tit is an outgoing.
issue6770
review44311002
- Save the move state only when a second same products is going to be
proceeded.
- Write the new cost prices when the moves are saved.
- Use get_multivalue with extensible pattern using explicit company value.
- Rename _update_product_cost_price into _compute_product_cost_price
- Use grouped instances of moves with the right context to avoid to
instantiate a product on each call to _compute_product_cost_price.
issue6626
review36431002
The product quantity must be computed on all storage location but without
childs otherwise the children quantity are added a second time on parent by
Move._get_quantity
To allow this behaviour the Move._get_quantity and Move._search_quantity use
the 'with_childs' context. If the context is not set, the default value will
be False if there are more than one location. This provides a sane default
behaviour because the locations could be children from each others.
issue6627
review35491002
The search quantity can not use an having clause because the SQL query does
not sum the children. The evaluation of the domain expression must be done
after.
issue6605
review37501002
When the effective date is set on assignation, if the move stays in this state
for more than 1 day, it is no more taken into account for stock quantity
computation.
But if the effective date is not set on assign, the stock quantity computation
must always include assigned moves when stock_assign is set with the exception
of delta computation which must always use the effective or planned date.
issue6371
review36261002
It is not allowed to assign remaining consumable on the current location if
this location is a view because the domain on location field of move does not
allow it.
issue6372
review33981002
As a concurrent transaction could update a moves after waiting for the release
of the table lock, we must take a lock on each rows used for the computation.
issue6134
review25921002
Since changest 29ab3d9bd918 we allow using view locations in draft and staging
moves making it possible to have a warehouse with a view location as main
storage location. But if the user wanted to cancel a shipment with such location
she would have to change the location of all moves before cancelling which is
very annoying.
issue5891
review29531002
Cédric Krier