mirror of
https://github.com/OCA/stock-logistics-warehouse.git
synced 2025-01-21 14:27:28 +02:00
749f69e669
There are cases where we dot NOT want to simply sum the quantities of all the variants. For example when dealing with manufacturing capacities, we may have to chose between variants because we can't make ALL of them with the same components. So instead of a simple non-modular implementation, we'll let each module define his own implementation of how to compute the product template's quantity available for sale. Conflicts: stock_available/__openerp__.py stock_available_immediately/__openerp__.py
35 lines
1.3 KiB
Python
35 lines
1.3 KiB
Python
# -*- coding: utf-8 -*-
|
|
# © 2014 Numérigraphe, Sodexis
|
|
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl.html).
|
|
|
|
from openerp import models, fields, api
|
|
from openerp.addons import decimal_precision as dp
|
|
|
|
|
|
class ProductTemplate(models.Model):
|
|
_inherit = 'product.template'
|
|
|
|
@api.multi
|
|
@api.depends('product_variant_ids.immediately_usable_qty')
|
|
def _immediately_usable_qty(self):
|
|
"""No-op implementation of the stock available to promise.
|
|
|
|
By default, available to promise = forecasted quantity.
|
|
|
|
**Each** sub-module **must** override this method in **both**
|
|
`product.product` **and** `product.template`, because we can't
|
|
decide in advance how to compute the template's quantity from the
|
|
variants.
|
|
"""
|
|
for tmpl in self:
|
|
tmpl.immediately_usable_qty = tmpl.virtual_available
|
|
|
|
immediately_usable_qty = fields.Float(
|
|
digits=dp.get_precision('Product Unit of Measure'),
|
|
compute='_immediately_usable_qty',
|
|
string='Available to promise',
|
|
help="Stock for this Product that can be safely proposed "
|
|
"for sale to Customers.\n"
|
|
"The definition of this value can be configured to suit "
|
|
"your needs")
|