You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you partially deliver but you don't deliver anything from the initial SO that created the procurement group, the shipping will be declared for that original SO (deliver_... modules) and delivery fee will be added on the original SO where there is nothing to invoice (in standard odoo, a sales order with only delivery fees to invoice is not marked as to invoice).
I think stock_picking_group_by_partner_by_carrier is lacking the update of sale_id (as well as likely sale_ids) on action_done before the call to send_to_shipper.
Maybe there is also an issue if you add a move in the delivered picking and it doesn't get added to one of the delivered SO but to the original SO.
Needs to be tested if this suspected issue can be reproduced and confirmed
As the module merges pickings from different sales orders, a new
sale_ids
field is incremented. The standard fieldsale_id
represents the first sales order that created the procurement group.Many odoo delivery modules relies on the
sale_id
field. The OCAdelivery_packag_fee
also: https://github.com/OCA/delivery-carrier/blob/16.0/delivery_package_fee/models/stock_picking.py#L23If you partially deliver but you don't deliver anything from the initial SO that created the procurement group, the shipping will be declared for that original SO (deliver_... modules) and delivery fee will be added on the original SO where there is nothing to invoice (in standard odoo, a sales order with only delivery fees to invoice is not marked as to invoice).
I think
stock_picking_group_by_partner_by_carrier
is lacking the update ofsale_id
(as well as likelysale_ids
) onaction_done
before the call tosend_to_shipper
.Maybe there is also an issue if you add a move in the delivered picking and it doesn't get added to one of the delivered SO but to the original SO.
Needs to be tested if this suspected issue can be reproduced and confirmed
@sebalix @rousseldenis
The text was updated successfully, but these errors were encountered: