Skip to content

[19.0][MIG] sale_report_delivered : Migration to 19.0. - #387

Open
kalpeshgajera-uncannycs wants to merge 34 commits into
OCA:19.0from
kalpeshgajera-uncannycs:19.0-mig-sale_report_delivered
Open

[19.0][MIG] sale_report_delivered : Migration to 19.0.#387
kalpeshgajera-uncannycs wants to merge 34 commits into
OCA:19.0from
kalpeshgajera-uncannycs:19.0-mig-sale_report_delivered

Conversation

@kalpeshgajera-uncannycs

Copy link
Copy Markdown

[19.0][MIG] sale_report_delivered : Migration to 19.0.

sergio-teruel and others added 30 commits July 8, 2026 19:20
[UPD] Update sale_report_delivered.pot
…moves always is product is a product or consumible

sale_report_delivered 13.0.1.0.1
…at not to refund

TT34713

sale_report_delivered 13.0.1.0.2
…lations

TT34568

[UPD] Update sale_report_delivered.pot

sale_report_delivered 13.0.1.0.3
…easing the total instead of decreasing it

sale_report_delivered 13.0.1.0.4
TT38067

[UPD] Update sale_report_delivered.pot

[UPD] README.rst
TT40378

[UPD] Update sale_report_delivered.pot
Currently translated at 100.0% (47 of 47 strings)

Translation: sale-reporting-16.0/sale-reporting-16.0-sale_report_delivered
Translate-URL: https://translation.odoo-community.org/projects/sale-reporting-16-0/sale-reporting-16-0-sale_report_delivered/it/
…lines

When the valuation layers were being grouped, the COALESCE function was acting on each one separately. Now, they are all processed at once.
Currently translated at 100.0% (48 of 48 strings)

Translation: sale-reporting-16.0/sale-reporting-16.0-sale_report_delivered
Translate-URL: https://translation.odoo-community.org/projects/sale-reporting-16-0/sale-reporting-16-0-sale_report_delivered/it/
…e delivery report in the same way as they have access to the sales report.

TT51606
Currently translated at 100.0% (48 of 48 strings)

Translation: sale-reporting-18.0/sale-reporting-18.0-sale_report_delivered
Translate-URL: https://translation.odoo-community.org/projects/sale-reporting-18-0/sale-reporting-18-0-sale_report_delivered/it/
…_product_uom_qty

When revaluation of Valuation Layers happens, another valuation is created linked to the Stock Move and the report lines were duplicated.
Using the quantity on the Valuation Layer (if exists) before taking product_uom_qty, adjust the real Quantity delivered and Price delivered on each Valuation Layer line of the report.
Done moves are splitted in 2 when quantity done exceedes quantity reserved.
When valuation layer is confirmed, only is linked to the first move, using the quantity done and not the product_uom_qty
So, if these qty done 0.0 moves are excluded, the one with all quantity done will be propagated across the report.
Also, use ABSolute values for unsigned values in sub_select because in select query will be multiplied by signed_qty.
Aggregate svls by stock move before joining them. A single move
can generate multiple valuation layers after corrections, and
joining them row by row makes the report sum absolute quantities
instead of the net delivered quantity.

How do we come to this situation? Well, apparently a user can
change the move line done quantity from the move line form that
can be accessed from the Inventory dashboard > <operation type> >
(three dots menu) > Operations.

MT-14369
Restore Dropshipping calculation.
When grouping SVLs on stock moves, dropshipping layers are taking
accordingly to avoid zero quantities (-X +X == 0).
A new unsolved bug is described in ROADMAP.
Added more tests to prevent future modifications that could remove actual workflows.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:sale_report_delivered Module sale_report_delivered series:19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.