The methods for getting the quants took a lot of parameters,
as in most of the cases (only exception being the negative
quants reconcile) the parameters depended on the move/pack operation
being processed. By just passing the move and ops the code gets simpler.
There should also only be one place where most of the domain for searching the quants
based on the move/ops is calculated.
When a location is marked as return location,
upon a return it can be put it in the possible return locations,
when it is in the same warehouse or under the same parent location.
The push rules are also applied on returned moves now, but
only when the push rule does not return the return to the original location
The lot in the return line is removed as it does not make sense
(better to change it on the pack operations)
and the views are cleaned
The returned picking is also automatically reserved.
When assigning a move to picking upon confirmation,
it took into account the locations/group of the picking,
but it should also check they are of the same picking type.
By default the rules are propagate True, so when you cancel a purchase order,
it will cancel all subsequent moves and put the procurement to cancel too.
This means that for an MTO product it will put the original sale order in shipment exception.
If it is not propagate, it will not cancel the subsequent moves and put the procurement in exception.
The advantage of this change, is that when procurements are created from orderpoints and
you cancel the purchase orders, then you don't need to go run/cancel
the procurements in exception anymore (if propagate True)
Now depends on the number of reordering rules. If the
number == 1, the min and max qty for this rule are
displayed instead of the "Reordering Rules" string.
One2many kanban views already implemented in some form views but not displayed.
To notice : mode='...,kanban' is needed for all the views in the one2many widget to be loaded.
Kanban view (mobile friendly) will be selected instead of tree view on mobile.
- Rename some labels
- Add menu tips for picking type views
- Set Operations menuitem in group_no_one
- The options under configuration should not be in technical features
- Reorganized the configuration menuitems
- Hide the internal transfers in the picking type views if the option Use multi location and warehouse is disabled
Conflicts:
addons/stock/product_view.xml
model has been renamed to mail.channel to prepare the slack modeling.
In future commits the mail.group model will be merged with the channel
model from im_chat. The first move is to rename mail.group into
mail.channel to have a model that will unite both features.
It is necessary to round the quantities with the appropriate precision. Indeed,
since onchange_quantity and onchange_uos_quantity trigger each other indirectly,
it is quite easy to fall in an infinite loop if the uom and uos precisions are
different.
Follows commit 6e346f0adb
opw-643651
In view inheritance, selecting an element based on the attribute `string` is
broken, since this attribute may be translated before the inheritance is
applied. This fixes existing views to avoid such selections.
To be consistant with the results of _get_stock. Otherwise search made on
stock_available may not display results with the same value than the search
criteria.
Fixes#3976
There is no need in recomputing each time the link between pack operations and
moves, when changing a pack operation. It would change the remaining qty
on the move, but this is not shown anywhere.
In the tests of wise_operator, when moving pack operations to another picking,
the links shoud be deleted as it is not done somewhere else
Instead of having only outgoing, manufacturing, incoming, all... traceability on the product,
we can define on the product if there is no tracking, lot tracking or unique serial number tracking.
On the picking type we can define whether we will only create lots for the picking type or use existing lots.
The lots are required when the product and the picking type demand it.
The option for serial number will check that each piece (quantity 1) has its
own serial number.
A lot splitting wizard is added on the pack operations in the picking form.
We want to be able to handle the case where we receive a lot of iPads e.g. and we
only assign a serial number when the product is delivered. For this, when the product is
delivered, we see that we only have products with no lots. When we see that we take something
without lot for something that needed one, we assign the lot to that piece of stock.
For negative quants: a positive quant with no lot can reconcile with a negative quant with/without lot,
a positive quant with lot, will preferably reconcile with a negative quant with the same lot, afterwards
with that without lot.
If 'Product UoS' has a higher precision than 'Product Unit of Measure', the
method onchange_uos_quantity will be called over and over by an infinite loop
if 'product_uos_qty' doesn't have the sufficient number of decimals.
opw-643651
Ship in 2 steps:
The Packing zone location is inactive but it is used by default as destination
location (instead of Output) in the Pick operation.
opw-643734
Fabien Pinckaers