Make a SO for some products with weight and a delivery set.
Put some products in a pack. It returns a wizard to choose the package type.
This wizard also allows to input the shipping weight.
It always defaulted to 0, instead of the sum of the weight of the products.
Due to ff7df19bd3, default_stock_quant_package_id is in context so
_default_shipping_weight would try to use stock_quant_package.shipping_weight,
which is always set to 0 at that point.
Note that furthermore, the active_id might not be a picking (e.g. a SO).
Therefore we always make the computation, with the default_picking_id in context
opw 2006566
closesodoo/odoo#33930
Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
Purpose : during a transfer, if some move lines have different
destination locations and the user click on 'put in pack' button, an
warning is triggered. This message, saying : 'You cannot put in the same
pack move lines having different destination location', is replaced by a
wizard allowing the user to choose a unique destination location. This
location will be set as location_dest_id on all transfer's stock move
lines. After that, the wizard calls again the _put_in_pack() method
where all the logic remains the same.
Task : 1872345
Odoo made the bad choice of using the 'btn-sm' class for every button
instead of configuring the padding for default 'btn' to be smaller.
In BS4, the style of btn-sm is actually more complex, lowering the
font-size too. Also, btn-xs was removed so we would not have the
possibility to display smaller button than our default ones.
This commit removes btn-sm wherever it was used. Unfortunately, this
might remove it at some places where it made sense but this can be
restored in a second time.
When a max weight is set on a packaging type is set, you get a warning
when you put in pack some content that weighs bigger than the max weight
of the packaging type
As the product.packaging model is used for two different business cases,
the views shown when the model is used for product packaging must only
contains a product_id, barcode, and qty because and when it's used for
delivery packages we must show the carrier, barcode, size and wheight.
So for usability purpose, we have made two different views explicitly
called in each use case.
We have moved the 'quant.package' view into a wizard, because it's
always used as a wizard, and and there was context trouble with the
'Save' button as a button with nale 'write' (the context was mixed with
the field, and there were two write action whan "Save button was
clicked.
* Purchase Order from scheduler: use tax from partner if any.
* Report Purchase Order: if address, it uses the name of the company and the address of the customer. Change to use the name of the customer.
* Print Packing List: don't display the lines with state=confirmed (only assigned)
* When invoice on picking: if I generate invoice on the sale order, it must set the pickings as invoiced
* When invoicing from picking: sale order lines stays as 'To be Invoiced'
* make new method to get partner property field data same like getting address on partner module and fetch property using this function on needed on onchange partner on sale, purchase module
* on delivery module, take taxes from partner if partner has default tax other wise take from delivery product when creation invoice line
* on overdue payment report, tel no is display with company invoice address's tel no
* Purchase Order from scheduler : assign note of purchase order line with product purchase description
* product model : all description should be translatable
* fixed bug : on scheduler.py file on mrp module ( got error when select Auto orderpoint on scheduling wizard)
* fixed bug : on product available function on stock module ( got error when call it with field_name=None )
bzr revid: hmo@tinyerp.com-20080926102510-nrjwloh0ojkl4hgn
Nans Lefebvre