[19.0][MIG] rma#684
Merged
Merged
Conversation
AaronHForgeFlow
force-pushed
the
19.0-mig-rma
branch
7 times, most recently
from
0d76a18 to
66d50c8
Compare
Otherwise the anglo saxon entries won't be correct. For example, the Interim (Delivered) account should balance after receiving and triggering a refund on a customer rma.
Without this, some policies are not being copied from the operation selected when creating new rma line from a rma group. In v16 this patch and the usage of such onchange can be removed in favor of (pre)computed stored editable fields for all policies and configuration in the RMA operation.
The goal is to simplify view defintion and do not duplicate things, requiring to do view changes in two places. The same change was done from rma lines some time ago.
This was not the intended way to add RMA lines to a group. Users are supposed to use the wizards to do so (add from stock move, add from serial, etc.). Having the option to use "add new line" was only leading to errors and confusion.
We shoul not force reservation on next steps on a multi step
route, oherwise a inconsistency is generated and the transfers
cannot be processed or cancel so the user gets stuck ("it is
not possible to unreserve more products that you have in stock"
error).
…om wizard views to rma_order_view.xml files
… made during the review
Those fields in the rma.operation allows us to control if we want to ensure that the same lot as the one indicated in the RMA should be used in deliveries to customers and receipts from suppliers
Also add a hook for the procurement location calculation. Currently the rma reception location can be specified. I propose to so the same for the destination locations. This is useful when you want to deliver to a different location than the specified in the property of the delivery address, for example, for specific subcontracting location
…rying to hide the full column
…on usage as internal to compute outgoing moves
AaronHForgeFlow
force-pushed
the
19.0-mig-rma
branch
from
e7c6d09 to
58ebe81
Compare
AaronHForgeFlow
force-pushed
the
19.0-mig-rma
branch
3 times, most recently
from
39fc966 to
3d81998
Compare
MiquelRForgeFlow
approved these changes
May 19, 2026
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
18 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.
No description provided.