Initial commit: OCA Technical packages (595 packages)

odoo-bringout-oca-rma-rma/rma/readme/CONFIGURE.rst

@@ -0,0 +1,21 @@
+If you want RMAs to be created from incoming emails, you need to:
+
+#. Go to *Settings > General Settings*.
+#. Check 'External Email Servers' checkbox under *Discuss* section.
+#. Set an 'alias domain' and an incoming server.
+#. Go to *RMA > Configuration > RMA Team* and select a team or create a new
+   one.
+#. Go to 'Email' tab and set an 'Email Alias'.
+
+If you want to manually finish RMAs, you need to:
+
+#. Go to *Settings > Inventory*.
+#. Set *Finish RMAs manually* checkbox on.
+
+By default, returns to customer are grouped by shipping address, warehouse and company.
+If you want to avoid this grouping you can:
+
+#. Go to *Settings > Inventory*.
+#. Set *Group RMA returns by customer address and warehouse* checkbox off.
+
+The users will still be able to group those pickings from the wizard.

odoo-bringout-oca-rma-rma/rma/readme/CONTRIBUTORS.rst

@@ -0,0 +1,12 @@
+* `Tecnativa <https://www.tecnativa.com>`_:
+
+  * Ernesto Tejeda
+  * Pedro M. Baeza
+  * David Vidal
+  * Víctor Martínez
+
+* Chafique Delli <chafique.delli@akretion.com>
+* Giovanni Serra - Ooops <giovanni@ooops404.com>
+* Michael Tietz (MT Software) <mtietz@mt-software.de>
+* Jacques-Etienne Baudoux - BCIM <je@bcim.be>
+* Souheil Bejaoui - ACSONE SA/NV <souheil.bejaoui@acsone.eu>

odoo-bringout-oca-rma-rma/rma/readme/DESCRIPTION.rst

@@ -0,0 +1,8 @@
+This module allows you to manage `Return Merchandise Authorization (RMA)
+<https://en.wikipedia.org/wiki/Return_merchandise_authorization>`_.
+RMA documents can be created from scratch, from a delivery order or from
+an incoming email. Product receptions and returning delivery operations
+of the RMA module are fully integrated with the Receipts and Deliveries
+Operations of Odoo inventory core module. It also allows you to generate
+refunds in the same way as Odoo generates it.
+Besides, you have full integration of the RMA documents in the customer portal.

odoo-bringout-oca-rma-rma/rma/readme/ROADMAP.rst

@@ -0,0 +1,6 @@
+* As soon as the picking is selected, the user should select the move,
+  but perhaps stock.move _rec_name could be improved to better show what
+  the product of that move is.
+* Add RMA reception and/or RMA delivery on several steps - 2 or 3 - like
+  normal receptions/deliveries. It should be a separate option inside the
+  warehouse definition.

odoo-bringout-oca-rma-rma/rma/readme/USAGE.rst

@@ -0,0 +1,57 @@
+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.
+#. You can also finish the RMA without further ado. To do so click on the *Finish*
+   button. A wizard will ask you for the reason from a selection of preconfigured ones.
+   Be sure to configure them in advance on *RMA > Configuration > Finalization Reasons*.
+   Once the RMA is finished, it will be set to that state and the reason will be
+   registered.
+
+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.