[16.0][3504][ADD] purchase_next_reception_date (#43)

Co-authored-by: Rinaldi Firdaus <rinaldi@quartile.co>
qrtl · Aug 28, 2023 · d237f33 · d237f33
1 parent f5e79f3
commit d237f33
Show file tree

Hide file tree

Showing 11 changed files with 630 additions and 0 deletions.
diff --git a/purchase_next_reception_date/README.rst b/purchase_next_reception_date/README.rst
@@ -0,0 +1,61 @@
+============================
+Purchase Next Reception Date
+============================
+
+.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! This file is generated by oca-gen-addon-readme !!
+   !! changes will be overwritten.                   !!
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+.. |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/licence-AGPL--3-blue.png
+    :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
+    :alt: License: AGPL-3
+.. |badge3| image:: https://img.shields.io/badge/github-qrtl%2Faxls--custom-lightgray.png?logo=github
+    :target: https://github.com/qrtl/axls-custom/tree/16.0/purchase_next_reception_date
+    :alt: qrtl/axls-custom
+
+|badge1| |badge2| |badge3| 
+
+This module adds next_reception_date in purchase order to recognize the upcoming receipt date of the orders.
+
+Background
+~~~~~~~~~~
+
+For purchase orders with multiple order lines, each having different 'date_planned' values,
+the expected arrival date field will not display the next order line's 'date_planned' after the first reception has been completed.
+Due to this condition, purchase users are required to open each record individually to see the upcoming receipt dates of the other order lines.
+
+The 'Next Reception Date' field is designed to provide information about the upcoming reception date of orders at a glance in the purchase order list view.
+
+**Table of contents**
+
+.. contents::
+   :local:
+
+Bug Tracker
+===========
+
+Bugs are tracked on `GitHub Issues <https://github.com/qrtl/axls-custom/issues>`_.
+In case of trouble, please check there if your issue has already been reported.
+If you spotted it first, help us smashing it by providing a detailed and welcomed
+`feedback <https://github.com/qrtl/axls-custom/issues/new?body=module:%20purchase_next_reception_date%0Aversion:%2016.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
+~~~~~~~
+
+* Quartile Limited
+
+Maintainers
+~~~~~~~~~~~
+
+This module is part of the `qrtl/axls-custom <https://github.com/qrtl/axls-custom/tree/16.0/purchase_next_reception_date>`_ project on GitHub.
+
+You are welcome to contribute.
diff --git a/purchase_next_reception_date/__init__.py b/purchase_next_reception_date/__init__.py
@@ -0,0 +1 @@
+from . import models
diff --git a/purchase_next_reception_date/__manifest__.py b/purchase_next_reception_date/__manifest__.py
@@ -0,0 +1,13 @@
+# Copyright 2023 Quartile Limited
+# License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl.html).
+{
+    "name": "Purchase Next Reception Date",
+    "version": "16.0.1.0.0",
+    "author": "Quartile Limited",
+    "website": "https://www.quartile.co",
+    "category": "Purchase",
+    "license": "AGPL-3",
+    "depends": ["purchase_stock"],
+    "data": ["views/purchase_order_views.xml"],
+    "installable": True,
+}
diff --git a/purchase_next_reception_date/i18n/ja.po b/purchase_next_reception_date/i18n/ja.po
@@ -0,0 +1,26 @@
+# Translation of Odoo Server.
+# This file contains the translation of the following modules:
+# 	* purchase_next_reception_date
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Odoo Server 16.0\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2023-08-24 09:19+0000\n"
+"PO-Revision-Date: 2023-08-24 09:19+0000\n"
+"Last-Translator: \n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: \n"
+"Plural-Forms: \n"
+
+#. module: purchase_next_reception_date
+#: model:ir.model.fields,field_description:purchase_next_reception_date.field_purchase_order__next_reception_date
+msgid "Next Reception Date"
+msgstr "次回入荷予定日"
+
+#. module: purchase_next_reception_date
+#: model:ir.model,name:purchase_next_reception_date.model_purchase_order
+msgid "Purchase Order"
+msgstr "購買オーダ"
diff --git a/purchase_next_reception_date/models/__init__.py b/purchase_next_reception_date/models/__init__.py
@@ -0,0 +1 @@
+from . import purchase_order
diff --git a/purchase_next_reception_date/models/purchase_order.py b/purchase_next_reception_date/models/purchase_order.py
@@ -0,0 +1,36 @@
+# Copyright 2023 Quartile Limited
+# License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl.html).
+
+from odoo import api, fields, models
+
+
+class PurchaseOrder(models.Model):
+    _inherit = "purchase.order"
+
+    next_reception_date = fields.Datetime(
+        compute="_compute_next_reception_date", store=True
+    )
+
+    @api.depends(
+        "order_line.product_id",
+        "order_line.product_qty",
+        "order_line.qty_received",
+        "order_line.qty_invoiced",
+        "order_line.date_planned",
+    )
+    def _compute_next_reception_date(self):
+        for order in self:
+            lines = order.order_line.filtered(
+                lambda x: (
+                    (
+                        x.product_id.detailed_type != "service"
+                        and x.qty_received < x.product_qty
+                    )
+                    or (
+                        x.product_id.detailed_type == "service"
+                        and x.qty_invoiced < x.product_qty
+                    )
+                )
+            )
+            dates = lines.mapped("date_planned")
+            order.next_reception_date = min(dates) if dates else False
diff --git a/purchase_next_reception_date/readme/DESCRIPTION.rst b/purchase_next_reception_date/readme/DESCRIPTION.rst
@@ -0,0 +1,10 @@
+This module adds next_reception_date in purchase order to recognize the upcoming receipt date of the orders.
+
+Background
+~~~~~~~~~~
+
+For purchase orders with multiple order lines, each having different 'date_planned' values,
+the expected arrival date field will not display the next order line's 'date_planned' after the first reception has been completed.
+Due to this condition, purchase users are required to open each record individually to see the upcoming receipt dates of the other order lines.
+
+The 'Next Reception Date' field is designed to provide information about the upcoming reception date of orders at a glance in the purchase order list view.