mirror of
https://github.com/OCA/rma.git
synced 2025-02-16 17:11:47 +02:00
f94eadee13
[FIX] rma: views permissions Regular users don't have permissions to rma models, so we should avoid loading views that lead to permission errors. TT24986 rma 12.0.1.1.0 Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: rma-12.0/rma-12.0-rma Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/ [FIX] rma: portal views access errors - Portal mail thread needs token config. - Unpublished products will raise AccessError on RMAs portal views for portal users due to record rules. - Ensure active_id when getting actions in rma, since we could come from a context that pollutes the expected active rma id. [IMP] rma: teams flow - If no RMA Team is set, we'll assign a default one to the new RMA. - A sequence is now used to search for the top team and assign it. - No default user is assigned when it's not in the context (i.e. portal rmas). [UPD] Update rma.pot rma 12.0.1.2.0 Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: rma-12.0/rma-12.0-rma Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/ Translated using Weblate (Spanish) Currently translated at 96.2% (253 of 263 strings) Translation: rma-12.0/rma-12.0-rma Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/es/
53 lines
2.5 KiB
ReStructuredText
53 lines
2.5 KiB
ReStructuredText
To use this module, you need to:
|
|
|
|
#. Go to *RMA > Orders* and create a new RMA.
|
|
#. Select a partner, an invoice address, select a product
|
|
(or select a picking and a move instead), write a quantity, fill the rest
|
|
of the form and click on 'confirm' button in the status bar.
|
|
#. You will see an smart button labeled 'Receipt'. Click on that button to see
|
|
the reception operation form.
|
|
#. If everything is right, validate the operation and go back to the RMA to
|
|
see it in a 'received' state.
|
|
#. Now you are able to generate a refund, generate a delivery order to return
|
|
to the customer the same product or another product as a replacement, split
|
|
the RMA by extracting a part of the remaining quantity to another RMA,
|
|
preview the RMA in the website. All of these operations can be done by
|
|
clicking on the buttons in the status bar.
|
|
|
|
* If you click on 'Refund' button, a refund will be created, and it will be
|
|
accessible via the smart button labeled Refund. The RMA will be set
|
|
automatically to 'Refunded' state when the refund is validated.
|
|
* If you click on 'Replace' or 'Return to customer' button instead,
|
|
a popup wizard will guide you to create a Delivery order to the client
|
|
and this order will be accessible via the smart button labeled Delivery.
|
|
The RMA will be set automatically to 'Replaced' or 'Returned' state when
|
|
the RMA quantity is equal or lower than the quantity in done delivery
|
|
orders linked to it.
|
|
|
|
An RMA can also be created from a return of a delivery order:
|
|
|
|
#. Select a delivery order and click on 'Return' button to create a return.
|
|
#. Check "Create RMAs" checkbox in the returning wizard, select the RMA
|
|
stock location and click on 'Return' button.
|
|
#. An RMA will be created for each product returned in the previous step.
|
|
Every RMA will be in confirmed state and they will
|
|
be linked to the returning operation generated previously.
|
|
|
|
There are Optional RMA Teams that can be used for:
|
|
|
|
- Organize RMAs in sections.
|
|
- Subscribe users to notifications.
|
|
- Create RMAs from incoming mail to special aliases (See configuration
|
|
section).
|
|
|
|
To create an RMA Team (RMA Responsible user level required):
|
|
|
|
#. Go to *RMA > Configuration > RMA Teams*
|
|
#. Create a new team and assign a name, a responsible and members.
|
|
#. Subscribe users to notifications, that can be of these subtypes:
|
|
|
|
- RMA draft. When a new RMA is created.
|
|
- Notes, Debates, Activities. As in standard Odoo.
|
|
#. In the list view, use the cross handle to sort RMA Teams. The top team
|
|
will be the default one if no team is set.
|