Search 1.9 billion lines of Odoo code on GitHub

mrp_bom_state

Author: OdooMRP team,AvanzOSC,Serv. Tecnol. Avanzados - Pedro M. Baeza
License: no license
Branch: pr-supplierinfo_for_customer_sequence_workaround
Repository: Antiun/odoomrp-wip
Dependencies: mrp
Other branches: pr-qty_change_fix
Other repositories: InakiZabala/odoomrp-wip, Innovahn/odoomrp-wip, JuaniFreedoo/odoomrp-wip, LudLaf/odoomrp-wip, SetRac/odoomrp-wip, StefanRijnhart/odoomrp-wip, Vauxoo/odoomrp-wip, alexteodor/odoomrp-wip, annieclone/odoomrp-wip, chajmill/odoomrp-wip, cialuo/odoomrp-wip, digitalwow/odoomrp-wip, duanyp1991/odoomrp-wip, farfansixto/odoomrp-wip, fevxie/odoomrp-wip, gmoncada/odoomrp-wip, hotkee/odoomrp-wip, initOS/odoomrp-wip, juanfe/odoomrp-wip, kkarolis/odoomrp-wip, leangjia/odoomrp-wip, lepistone/odoomrp-wip, mathi123/odoomrp-wip, mikelarre/odoomrp-wip-1, mohzein/odoomrp-wip, morgana68/odoomrp-wip, msteinfeld-intero/odoomrp-wip, muguli22/odoomrp-wip, mutita/odoomrp-wip, myodoo/odoomrp-wip, numerigraphe/odoomrp-wip, oihane/odoomrp-wip, richard-willdooit/odoomrp-wip, syci/odoomrp-wip, vrms/odoomrp-wip, and yastri/odoomrp-wip

<h1 class="title">MRP - BoM version</h1> <p>This module provides a state in the LdM whether to allow their use in manufacturing, to do the following states are defined:</p> <ul class="simple"> <li><strong>Draft</strong>: The form will be available for data entry, and may move to &quot;active&quot; state.</li> <li><strong>Active</strong>: You can modify all of the form fields except for the fields: routing, BoM lines, and the new field Active, for false default when you create a new BoM. The &quot;active&quot; state may be passed back to state &quot;draft&quot;, if we mark the new field &quot;Allow re-edit the BoM list&quot;, this new field is defined in <em>Configuration &gt; Configuration &gt; Manufacturing</em>. The active state may move to state &quot;Historical&quot;.</li> <li><strong>Historical</strong>: This is the last state of the LdM, you can not change any field on the form.</li> </ul> <p>When the MRP BoM list is put to active, a record of who has activated, and when will include in chatter/log. It also adds a constraint for the sequence field to be unique.</p> <ul class="simple"> <li><strong>New version</strong> : By clicking the button version, current BOM is moved to historical state, and a new BOM is creating based on this but with version number +1 and changing state to draft</li> </ul>