Search 1.9 billion lines of Odoo code on GitHub
purchase_delivery_split_date
<h1 class="title">Purchase Delivery Split Date</h1>
<p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external" href="https://github.com/OCA/purchase-workflow/tree/11.0/purchase_delivery_split_date"><img alt="OCA/purchase-workflow" src="https://img.shields.io/badge/github-OCA%2Fpurchase--workflow-lightgray.png?logo=github" /></a> <a class="reference external" href="https://translation.odoo-community.org/projects/purchase-workflow-11-0/purchase-workflow-11-0-purchase_delivery_split_date"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external" href="https://runbot.odoo-community.org/runbot/142/11.0"><img alt="Try me on Runbot" src="https://img.shields.io/badge/runbot-Try%20me-875A7B.png" /></a></p>
<p>When this module is installed, each Purchase Order you confirm will
generate one Incoming Shipment for each schedule date indicated in the
Purchase Order Lines.</p>
<p>Once the Purchase Order has been confirmed, subsequent changes made to the
scheduled dates in the PO lines will produce a reorganization of the
corresponding stock moves in the Incoming Shipments, creating/deleting new
Incoming Shipments when needed, to ensure that each Incoming Shipment
contains moves to be received in the same date.</p>
<p>This module is also designed for extensibility, so that you can define
in other modules new criteria to split deliveries.</p>
<p><strong>Table of contents</strong></p>
<div class="contents local topic" id="contents">
<ul class="simple">
<li><a class="reference internal" href="#usage" id="id3">Usage</a></li>
<li><a class="reference internal" href="#changelog" id="id4">Changelog</a></li>
<li><a class="reference internal" href="#bug-tracker" id="id5">Bug Tracker</a></li>
<li><a class="reference internal" href="#credits" id="id6">Credits</a><ul>
<li><a class="reference internal" href="#authors" id="id7">Authors</a></li>
<li><a class="reference internal" href="#contributors" id="id8">Contributors</a></li>
<li><a class="reference internal" href="#maintainers" id="id9">Maintainers</a></li>
</ul>
</li>
</ul>
</div>
<a name="usage"></a>
<h2><a class="toc-backref" href="#id3">Usage</a></h2>
<p>When a Purchase Order is confirmed, shipments will be grouped by same scheduled date.</p>
<div class="figure align-center">
<img alt="Purchase Order Split Shipments" src="https://raw.githubusercontent.com/OCA/purchase-workflow/11.0/purchase_delivery_split_date/static/description/split_delivery.png" style="width: 80%;" />
</div>
<a name="changelog"></a>
<h2 class="with-subtitle"><a class="toc-backref" href="#id4">Changelog</a></h2>
<h2 class="section-subtitle" id="id1"><span class="section-subtitle">11.0.1.0.0 (2018-09-16)</span></h2>
<ul class="simple">
<li>Migration to 11.0.
(<a class="reference external" href="https://github.com/OCA/purchase-workflow/issues/461">#461</a>)</li>
<li>When the scheduled date is changed in the PO after confirmation the
pickings are reorganized so as to force that every picking will have only
moves to be delivered on the same date.</li>
</ul>
<a name="bug-tracker"></a>
<h2><a class="toc-backref" href="#id5">Bug Tracker</a></h2>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/purchase-workflow/issues">GitHub Issues</a>.
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
<a class="reference external" href="https://github.com/OCA/purchase-workflow/issues/new?body=module:%20purchase_delivery_split_date%0Aversion:%2011.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p>
<p>Do not contact contributors directly about support or help with technical issues.</p>
<a name="credits"></a>
<h2><a class="toc-backref" href="#id6">Credits</a></h2>
<a name="authors"></a>
<h3><a class="toc-backref" href="#id7">Authors</a></h3>
<ul class="simple">
<li>Numérigraphe</li>
<li>Eficent</li>
</ul>
<a name="contributors"></a>
<h3><a class="toc-backref" href="#id8">Contributors</a></h3>
<ul class="simple">
<li>Philippe Rossi <<a class="reference external" href="mailto:pr@numerigraphe.com">pr@numerigraphe.com</a>> (initial patch against v6.0)</li>
<li>Lionel Sausin <<a class="reference external" href="mailto:ls@numerigraphe.com">ls@numerigraphe.com</a>> (modularization for v7+)</li>
<li>Jordi Ballester Alomar <<a class="reference external" href="mailto:jordi.ballester@eficent.com">jordi.ballester@eficent.com</a>> (modularization v8, v9)</li>
<li>Lois Rilo <<a class="reference external" href="mailto:lois.rilo@eficent.com">lois.rilo@eficent.com</a>> (migration to v10)</li>
</ul>
<a name="maintainers"></a>
<h3><a class="toc-backref" href="#id9">Maintainers</a></h3>
<p>This module is maintained by the OCA.</p>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.</p>
<p>This module is part of the <a class="reference external" href="https://github.com/OCA/purchase-workflow/tree/11.0/purchase_delivery_split_date">OCA/purchase-workflow</a> project on GitHub.</p>
<p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>