Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[11.0][MIG] stock_available: Migration to 11.0 #353

Closed
wants to merge 47 commits into from

Conversation

kikopeiro
Copy link
Contributor

No description provided.

Lionel Sausin (Numérigraphe) and others added 30 commits November 14, 2017 13:00
Generic module to compute the stock quantity available to promise using several implementations.
stock_available_immediatly is changed to become the first optional implementation.
Cherry pick of commit 0b060f6 from the v7 branch
Module to take immediate manufaturing capability into account in the stock quantity available to promise.

Conflicts:
	stock_available/res_config.py
Take sale quotations into account in the stock quantity available to promise
Cherry-picked from 497068f

Conflicts:
	stock_available/res_config.py
Cherry-picked from v7 at 8add4be

Conflicts:
	__unported__/stock_available_mrp/__openerp__.py
	stock_available/__openerp__.py
	stock_available_immediately/__openerp__.py
odoo/odoo#5512 and odoo-dev/odoo@b3e5a94 makes it clear the standard intends to support decimal precision on the product form.
…uct and

product.template, now takes in account variants and correctly displays value.
[FLAKE8]

Removing duplicate modules and moving README.rst into __unported__
not using internal qty_available that seems not to
take in consideration reserved quants.
Commit 6c16913 changed the way we compute the immediately_usable_qty: instead of using the virtual stock, we used the sum of quants without reservations. But a quant may actually be reserved and still be available (for example it may be reserved for an internal move).
Fixes OCA#79
The previous fix restored stock_available but then there was no way to exclude the incomming moves from the count. This belongs in stock_available_immediately, restoring it cleanly.
This commit also takes care to respect the distinction between templates and variants, so it should fix OCA#73 too.
* fix the dependencies for the computed field

* use api.multi instead of api.one to avoid calling
  super()._immediately_usable_qty in a loop (this improves perfs on a tree view
  display)
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
@kikopeiro kikopeiro changed the title [MIG] stock_available: Migration to 11.0 [11.0][MIG] stock_available: Migration to 11.0 Nov 14, 2017
@pedrobaeza pedrobaeza added this to the 11.0 milestone Nov 14, 2017
@pedrobaeza pedrobaeza mentioned this pull request Nov 14, 2017
46 tasks
@fanha99
Copy link
Contributor

fanha99 commented Dec 29, 2017

hi, is this module need in v11.0?
there is a field name Forecasted Quantity and it show exact the value as field Available for sale ?

@gurneyalex
Copy link
Member

@fanha99 no, forecasted quantity is current stock - reserved + incoming. This module provides current stock - reserved (because sometimes incoming will only be available in a long time in the future)

</div>
</div>

<!--<div>-->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to keep the commented out section?

@yvaucher
Copy link
Member

yvaucher commented Apr 6, 2018

OCA Transbot updated translations from Transifex can be squashed together

@asaunier
Copy link

asaunier commented Apr 6, 2018

What do the coverage error messages (No report found to compare against) actually mean?
Except the squashing of the OCA Transbot commits, does this PR require some more changes?

@pedrobaeza
Copy link
Member

Don't worry about that message. It's an old one.

@pedrobaeza
Copy link
Member

Superseeded by #405

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet