[19.0][MIG] account_move_line_repair_info - #2382
Open
JasminSForgeFlow wants to merge 13 commits into
Open
Conversation
Currently translated at 100.0% (6 of 6 strings) Translation: account-financial-tools-16.0/account-financial-tools-16.0-account_move_line_repair_info Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-16-0/account-financial-tools-16-0-account_move_line_repair_info/it/
OCA-git-bot
added
series:19.0
mod:account_move_line_repair_info
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Odoo 19.0 API changes
stock.valuation.layerwas removed in 19.0. Stock valuation now lives directly onstock.move(value,account_move_id), so the_validate_accounting_entries()override isgone. The repair order is now stamped on the journal items at creation time, by overriding
stock.move._get_account_move_line_vals(). Since that method is called per stock move, eachjournal item gets exactly the repair order of the move it comes from — in 19.0 a single
valuation entry can gather several stock moves, which the old "write on
move.line_ids"approach could not express.
post_init_hook: the SQL no longer joinsstock_valuation_layer; it goes throughstock_move.account_move_id. The two former queries (materials consumed / product repaired)collapse into one, because in 19.0 the repaired-product move created by
action_repair_donealso carries
repair_id. Entries gathering more than one repair order — or mixing repair andnon-repair moves — are skipped rather than mis-assigned.
@ForgeFlow