[19.0][MIG] rma

rma/README.rst

@@ -0,0 +1,164 @@
+.. image:: https://odoo-community.org/readme-banner-image
+   :target: https://odoo-community.org/get-involved?utm_source=readme
+   :alt: Odoo Community Association
+
+======================================
+RMA (Return Merchandise Authorization)
+======================================
+
+.. 
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! This file is generated by oca-gen-addon-readme !!
+   !! changes will be overwritten.                   !!
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! source digest: sha256:310ce4e3f5919e5be643c54f11481d09bb8fc79cab65f08ac969ef3bf9d799fe
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
+    :target: https://odoo-community.org/page/development-status
+    :alt: Beta
+.. |badge2| image:: https://img.shields.io/badge/license-LGPL--3-blue.png
+    :target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html
+    :alt: License: LGPL-3
+.. |badge3| image:: https://img.shields.io/badge/github-ForgeFlow%2Fstock--rma-lightgray.png?logo=github
+    :target: https://github.com/ForgeFlow/stock-rma/tree/19.0/rma
+    :alt: ForgeFlow/stock-rma
+
+|badge1| |badge2| |badge3|
+
+A Return Merchandise Authorization (RMA), is a part of the process of
+returning a product in order to receive a refund, replacement, or repair
+during the product's warranty period.
+
+The purchaser of the product must contact the manufacturer (or
+distributor or retailer) to obtain authorization to return the product.
+
+The resulting RMA number must be displayed on or included in the
+returned product's packaging.
+
+The issuance of an RMA is a key gatekeeping moment in the reverse
+logistics cycle, providing the vendor with a final opportunity to
+diagnose and correct the customer's problem with the product (such as
+improper installation or configuration) before the customer permanently
+relinquishes ownership of the product to the manufacturer, commonly
+referred to as a return.
+
+As returns are costly for the vendor and inconvenient for the customer,
+any return that can be prevented benefits both parties.
+
+**Table of contents**
+
+.. contents::
+   :local:
+
+Configuration
+=============
+
+Security
+--------
+
+Go to Settings > Users and assign the appropiate permissions to users.
+Different security groups grant distinct levels of access to the RMA
+features.
+
+-  Users in group "RMA Customer User" or "RMA Supplier User" can access
+   to, create and process RMA's associated to customers or suppliers
+   respectively.
+-  Users in group "RMA Manager" can access to, create, approve and
+   process RMA's associated to both customers and suppliers.
+
+RMA Approval Policy
+-------------------
+
+There are two RMA approval policies in product catogories:
+
+-  One step: Always auto-approve RMAs that only contain products within
+   categories with this policy.
+-  Two steps: A RMA order containing a product within a category with
+   this policy will request the RMA manager approval.
+
+In order to change the approval policy of a product category follow the
+next steps:
+
+1. Go to *Inventory > Configuration > Products > Product Categories*.
+2. Select one and change the field *RMA Approval Policy* to your
+   convenience.
+
+Other Settings
+--------------
+
+1. Go to RMA > Configuration > Settings > Return Merchandising
+   Authorization and select the option "Display 3 fields on rma:
+   partner, invoice address, delivery address" if needed.
+2. Go to RMA > Configuration > Warehouse management > Warehouses and add
+   a default RMA location and RMA picking type for customers and
+   suppliers RMA picking type. In case the warehouse is configured to
+   use routes, you need to create at least one route per rma type with
+   at least two push rules (one for inbound another for outbound) it's
+   very important to select the type of operation supplier if we are
+   moving in the company and customer if we are moving out of the
+   company.
+
+Usage
+=====
+
+RMA are accessible though Inventory menu. There's four menus, divided by
+type. Users can access to the list of RMA or RMA lines.
+
+Create an RMA:
+
+1. Select a partner. Enter RMA lines associated to an existing picking,
+   or manually.
+2. Request approval and approve.
+3. Click on RMA Lines button.
+4. Click on more and select an option: "Receive products", "Create
+   Delivery Order".
+5. Go back to the RMA. Set the RMA to done if not further action is
+   required.
+
+Known issues / Roadmap
+======================
+
+-  Picking operations report in customer RMA dropshipping case is
+   showing "Vendor Address" while it should be "Customer Address".
+-  Dropshipping always counted as a delivery on the smart buttons.
+-  Uninstall hook.
+-  Constraints instead of required fields on rma.order.line.
+-  Rename type field on rma.order and rma.order.line
+
+Bug Tracker
+===========
+
+Bugs are tracked on `GitHub Issues <https://github.com/ForgeFlow/stock-rma/issues>`_.
+In case of trouble, please check there if your issue has already been reported.
+If you spotted it first, help us to smash it by providing a detailed and welcomed
+`feedback <https://github.com/ForgeFlow/stock-rma/issues/new?body=module:%20rma%0Aversion:%2019.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
+
+Do not contact contributors directly about support or help with technical issues.
+
+Credits
+=======
+
+Authors
+-------
+
+* ForgeFlow
+
+Contributors
+------------
+
+-  Jordi Ballester Alomar <jordi.ballester@forgeflow.com>
+-  Aaron Henriquez <ahenriquez@forgeflow.com>
+-  Lois Rilo <lois.rilo@forgeflow.com>
+-  Bhavesh Odedra <bodedra@opensourceintegrators.com>
+-  Akim Juillerat <akim.juillerat@camptocamp.com>
+-  Alexandre Fayolle <alexandre.fayolle@camptocamp.com>
+-  Chafique Delli <chafique.delli@akretion.com>
+-  Héctor Villarreal <hector.villarreal@forgeflow.com>
+
+Maintainers
+-----------
+
+This module is part of the `ForgeFlow/stock-rma <https://github.com/ForgeFlow/stock-rma/tree/19.0/rma>`_ project on GitHub.
+
+You are welcome to contribute.

rma/__init__.py

@@ -0,0 +1,5 @@
+# Copyright (C) 2017-20 ForgeFlow S.L.
+# License LGPL-3.0 or later (https://www.gnu.org/licenses/lgpl.html)
+
+from . import models
+from . import wizards

rma/__manifest__.py

@@ -0,0 +1,39 @@
+# Copyright (C) 2017-20 ForgeFlow S.L.
+# License LGPL-3.0 or later (https://www.gnu.org/licenses/lgpl.html)
+
+{
+    "name": "RMA (Return Merchandise Authorization)",
+    "version": "19.0.1.0.0",
+    "license": "LGPL-3",
+    "category": "RMA",
+    "summary": "Introduces the return merchandise authorization (RMA) process in odoo",
+    "author": "ForgeFlow",
+    "website": "https://github.com/ForgeFlow",
+    "depends": ["stock", "mail", "web", "stock_restrict_lot"],
+    "demo": ["demo/stock_demo.xml"],
+    "data": [
+        "security/rma.xml",
+        "security/ir.model.access.csv",
+        "data/rma_sequence.xml",
+        "data/stock_data.xml",
+        "data/rma_operation.xml",
+        "report/rma_report.xml",
+        "report/rma_report_templates.xml",
+        "report/report_deliveryslip.xml",
+        "wizards/rma_make_picking_view.xml",
+        "wizards/rma_add_stock_move_view.xml",
+        "wizards/rma_make_supplier_rma_view.xml",
+        "wizards/rma_add_serial_views.xml",
+        "views/rma_order_view.xml",
+        "views/rma_operation_view.xml",
+        "views/rma_order_line_view.xml",
+        "views/stock_view.xml",
+        "views/stock_warehouse.xml",
+        "views/product_view.xml",
+        "views/res_partner_view.xml",
+        "views/res_config_settings_views.xml",
+        "views/rma_menu.xml",
+    ],
+    "installable": True,
+    "application": True,
+}

rma/data/rma_operation.xml

@@ -0,0 +1,48 @@
+<?xml version="1.0" ?>
+<odoo noupdate="1">
+    <record id="rma_operation_customer_replace" model="rma.operation">
+        <field name="name">Replace After Receive</field>
+        <field name="code">RPL-C</field>
+        <field name="receipt_policy">ordered</field>
+        <field name="delivery_policy">received</field>
+        <field name="type">customer</field>
+        <field name="in_route_id" ref="rma.route_rma_customer" />
+        <field name="out_route_id" ref="rma.route_rma_customer" />
+        <field name="in_force_same_lot">True</field>
+        <field name="out_force_same_lot">False</field>
+    </record>
+
+    <record id="rma_operation_supplier_replace" model="rma.operation">
+        <field name="name">Replace</field>
+        <field name="code">RPL-S</field>
+        <field name="receipt_policy">ordered</field>
+        <field name="delivery_policy">ordered</field>
+        <field name="type">supplier</field>
+        <field name="in_route_id" ref="rma.route_rma_supplier" />
+        <field name="out_route_id" ref="rma.route_rma_supplier" />
+        <field name="in_force_same_lot">False</field>
+        <field name="out_force_same_lot">True</field>
+    </record>
+
+    <record id="rma_operation_ds_replace" model="rma.operation">
+        <field name="name">Dropship - Deliver to vendor</field>
+        <field name="code">DS-RPL-C</field>
+        <field name="receipt_policy">ordered</field>
+        <field name="delivery_policy">no</field>
+        <field name="type">customer</field>
+        <field name="customer_to_supplier" eval="True" />
+        <field name="out_route_id" ref="rma.route_rma_dropship" />
+        <field name="in_route_id" ref="rma.route_rma_dropship" />
+    </record>
+
+    <record id="rma_operation_ds_replace_supplier" model="rma.operation">
+        <field name="name">Dropship - Deliver to customer</field>
+        <field name="code">DS-RPL-S</field>
+        <field name="receipt_policy">no</field>
+        <field name="delivery_policy">ordered</field>
+        <field name="type">supplier</field>
+        <field name="supplier_to_customer" eval="True" />
+        <field name="out_route_id" ref="rma.route_rma_dropship" />
+        <field name="in_route_id" ref="rma.route_rma_dropship" />
+    </record>
+</odoo>

rma/data/rma_sequence.xml

@@ -0,0 +1,41 @@
+<?xml version="1.0" ?>
+<odoo noupdate="1">
+    <record id="rma_seq" model="ir.sequence">
+        <field name="name">Customer RMA sequence</field>
+        <field name="code">rma.order.customer</field>
+        <field name="padding">5</field>
+        <field name="prefix">RMAG/%(year)s/</field>
+        <field eval="1" name="number_next" />
+        <field eval="1" name="number_increment" />
+    </record>
+
+    <record id="rma_supplier_seq" model="ir.sequence">
+        <field name="name">Supplier RMA sequence</field>
+        <field name="code">rma.order.supplier</field>
+        <field name="padding">5</field>
+        <field name="prefix">RTVG/%(year)s/</field>
+        <field eval="1" name="number_next" />
+        <field eval="1" name="number_increment" />
+        <field name="company_id" eval="False" />
+    </record>
+
+    <record id="rma_line_seq" model="ir.sequence">
+        <field name="name">Customer RMA Line sequence</field>
+        <field name="code">rma.order.line.customer</field>
+        <field name="padding">5</field>
+        <field name="prefix">RMA/%(year)s/</field>
+        <field eval="1" name="number_next" />
+        <field eval="1" name="number_increment" />
+        <field name="company_id" eval="False" />
+    </record>
+
+    <record id="rma_line_supplier_seq" model="ir.sequence">
+        <field name="name">Supplier RMA Line sequence</field>
+        <field name="code">rma.order.line.supplier</field>
+        <field name="padding">5</field>
+        <field name="prefix">RTV/%(year)s/</field>
+        <field eval="1" name="number_next" />
+        <field eval="1" name="number_increment" />
+        <field name="company_id" eval="False" />
+    </record>
+</odoo>