Skip to content

[18.0][MIG] rma_sale_mrp: Migration to version 18.0#525

Merged
OCA-git-bot merged 34 commits intoOCA:18.0from
Tecnativa:18.0-mig-rma_sale_mrp
Mar 17, 2026
Merged

[18.0][MIG] rma_sale_mrp: Migration to version 18.0#525
OCA-git-bot merged 34 commits intoOCA:18.0from
Tecnativa:18.0-mig-rma_sale_mrp

Conversation

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor

@eduezerouali-tecnativa eduezerouali-tecnativa commented Jan 15, 2026

@eduezerouali-tecnativa eduezerouali-tecnativa force-pushed the 18.0-mig-rma_sale_mrp branch 2 times, most recently from de70770 to f301357 Compare January 15, 2026 09:05
>data.get('phantom_bom_product') and data['quantity'] or 0</attribute>
</xpath>
<!-- TODO: We could give a clue about what's to be returned, with readonly detailed lines -->
<!-- TODO: We could give a clue about what's to be returned, with readonly detailed lines
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it necessary to comment on this now? If it is not necessary, the corresponding code should be removed and explained.

@eduezerouali-tecnativa eduezerouali-tecnativa force-pushed the 18.0-mig-rma_sale_mrp branch 2 times, most recently from 09c10e8 to 899ad94 Compare February 2, 2026 13:39
@pedrobaeza
Copy link
Copy Markdown
Member

/ocabot migration rma_sale_mrp

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone Feb 2, 2026
@OCA-git-bot OCA-git-bot mentioned this pull request Feb 2, 2026
7 tasks
Copy link
Copy Markdown
Member

@victoralmau victoralmau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not possible to select kit products on the portal.

v16
Image

v18
Image

@mariancuadranetkia
Copy link
Copy Markdown

It's not possible create RMA of a Kit, because we receive next error:
imagen

I'm not sure if this error could be because the 'delivery order' field isn't automatically filled in the kits, and that's why the validation is being skipped.:
imagen

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@victoralmau sorry for the late replay, now it is working as it should.
image

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@mariancuadranetkia first thank you to take the time for the review. Could you give more detail on how you got the error. Anyways i think it has to do with not valid the picking.

@mariancuadranetkia
Copy link
Copy Markdown

@eduezerouali-tecnativa
I created a sale with table kit and I finished picking.
After that, I returned to sale order, and I created RMA. Although I could choose product kit to create RMA, when I 'accept' to create it, I got error.
I attach a short video, where you can see the sale order and picking, and error when I try to create RMA. This sale order is created in order to test this feature.

rma.kit.error.mp4

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@mariancuadranetkia the main problem is that you are using a kit with one product that it is not trackable. Try again creating your own products and components and you will see that RMA is create correctly.

@mariancuadranetkia
Copy link
Copy Markdown

@mariancuadranetkia the main problem is that you are using a kit with one product that it is not trackable. Try again creating your own products and components and you will see that RMA is create correctly.

Mmm yes, but, this way customer can't create RMA to ask for a refund if a product is not trackable or a component of kit is not trackable? Because, I can create a return picking without RMA without problem of this product not trackable, problem it's only creating RMA.

I'm not sure if this is the expected behaviour, but, if I can return a product and I can refund it, I don't understand the reason to not allow create RMA to register this operation.

@victoralmau
Copy link
Copy Markdown
Member

Reviewing the behavior in v16, it should work correctly, i.e., even if the product kit (table kit, for example) does not have tracking set, if there are stock moves for the kit components, it should allow the corresponding RMA(s) to be created.

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@victoralmau I have check on v18 to do a RMA from Sale Order and it is not possible to do it if the product is not is_storable

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@mariancuadranetkia you were right it is fix in this PR #547

@mariancuadranetkia
Copy link
Copy Markdown

@eduezerouali-tecnativa ok, I tested this PR and I validated.
But I can't test this fix yet with kits, can I? I've tested in this runbot with same Kit but I have same error, I think that I should wait but I'm not sure.
Thanks!

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@mariancuadranetkia @victoralmau rebase done, now it should work as expected.

@mariancuadranetkia
Copy link
Copy Markdown

@eduezerouali-tecnativa I've checked, and, with new sales order if I create RMA from backend,, it works.
But, if I duplicate sales order, and I try to create RMA from e-commerce, I receive next error:
imagen

imagen

Thanks!!!

@eduezerouali-tecnativa
Copy link
Copy Markdown
Contributor Author

@mariancuadranetkia this is a clear bug. It is amend here #548.
Thank you for your review.

@pedrobaeza
Copy link
Copy Markdown
Member

Please update this one when the other PR is merged to make use of the new method.

Rodrigo Macedo and others added 8 commits March 17, 2026 10:03
Currently translated at 100.0% (55 of 55 strings)

Translation: rma-16.0/rma-16.0-rma_sale_mrp
Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/pt_BR/
The rma operation is required in the portal, and it makes sense
for it to be required in the sales wizard as well
Currently translated at 100.0% (57 of 57 strings)

Translation: rma-16.0/rma-16.0-rma_sale_mrp
Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/it/
Currently translated at 100.0% (57 of 57 strings)

Translation: rma-16.0/rma-16.0-rma_sale_mrp
Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/pt_BR/
- Display the allowed quantity to return
- Simplify data encoding by adding a button to select/deselect all lines
- Ensure that the quantity to return is always less than or equal to the allowed quantity
Currently translated at 100.0% (62 of 62 strings)

Translation: rma-16.0/rma-16.0-rma_sale_mrp
Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/it/
@eduezerouali-tecnativa eduezerouali-tecnativa force-pushed the 18.0-mig-rma_sale_mrp branch 3 times, most recently from 00c5c2e to a97040e Compare March 17, 2026 09:49
Copy link
Copy Markdown

@mariancuadranetkia mariancuadranetkia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional review ok!
Now create RMA with Kits or Consu products from backend/e-commerce is working fine.

@pedrobaeza pedrobaeza requested a review from victoralmau March 17, 2026 10:34
@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza
Copy link
Copy Markdown
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Copy Markdown
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 18.0-ocabot-merge-pr-525-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit f3c5690 into OCA:18.0 Mar 17, 2026
7 checks passed
@OCA-git-bot
Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at c9eae9a. Thanks a lot for contributing to OCA. ❤️

@pedrobaeza pedrobaeza deleted the 18.0-mig-rma_sale_mrp branch March 17, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.