8.0 stock available immediately #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For weird reasons, force-assigning a move does not associate quants. action_assign'ing the picking does, and is the same procedure that you can do via the interface.
fix: stock reserve should reserve quants
Separated Lint tests
fix pep8 W503
[UPG] Upgraded to version 8, fixed references to new 8.0 views and moved fields that were in product.product to product.template [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [UPG] stock available immediately, corrected the calculation method of immediately_usable_qty to take in accountthe sign change in outgoing_qty (from negative to positive) in version 8. [FLAKE8] [FIX] renaming of a class, comment removing, useless code. [UPD] move out from unported to 8 for update [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [FIX] renaming of a class, comment removing, useless code. [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [UPD] move out from unported to 8 for update [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [FIX] renaming of a class, comment removing, useless code. [UPD] move out from unported to 8 for update [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [FIX] renaming of a class, comment removing, useless code. [UPD] move out from unported to 8 for update [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [FIX] renaming of a class, comment removing, useless code. [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [UPD] move out from unported to 8 for update [fix] remove duplicate view and correct view name [UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0. [FIX] renaming of a class, comment removing, useless code.
[UPG] Upgraded to version 8, fixed references to new 8.0 views and moved fields that were in product.product to product.template [RFR] Removing useless code and renaming
…-logistics-warehouse into stock_available_immediately2 Conflicts: stock_available_immediately/product.py
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
Set a keyword argument on the context to better respect the convention. Allow the context to contain iterable types supported by the ORM. Cherry-picked from v7 at 9ab7f78 Conflicts: stock_available/product.py stock_available_immediately/product.py
Cherry-picked from v7 at 8add4be Conflicts: __unported__/stock_available_mrp/__openerp__.py stock_available/__openerp__.py stock_available_immediately/__openerp__.py
Cherry-picked from v7 at 853f5d4 Conflicts: stock_available/product.py
In order to get visibility on https://www.odoo.com/apps the OCA board has decided to add the OCA as author of all the addons maintained as part of the association.
…into 8.0-stock_available_immediately2 Conflicts: 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.
…ately2 Thank you @clonedagain for your help.
This has always been wrong on v8, but because of the very obscure odoo/odoo#5797, this seemed to work every time we had single-step reception. Please note that this block of XML is noupdate, so for existing installations you need to change the parent of the reservation location to something outside your warehouses manually. Incidentally, this makes the branch green independently of odoo/odoo#5797.
fix OCA#42: reserve location should be outside WH
1. Make it float, because quantity is float. 2. Respect unit of measure (instead of adding apples and pears). 3. Do that for both product and template. 4. Test the above.
fix crash: excepted singleton
This module was written to enter a location's area based on different units of measure The information is dependant on the different locations entered
make stock_reserve and stock_reserve_sale owner_aware
Follow OCA/maintainer-quality-tools#187 and use addons/apt/package directive to install our build dependencies. This allows using container based Travis builds (which should be faster).
Add README.rst and remove description from __openerp__.py
…eadme [IMP] Add README.rst and remove description from __openerp__.py
Add README.rst and remove description from __openerp__.py
Add partner_area_data and partner_area_management
…uct and product.template, now takes in account variants and correctly displays value. [FLAKE8] Removing duplicate modules and moving README.rst into __unported__
calculations done in product template are fine.
not using internal qty_available that seems not to take in consideration reserved quants.
TODO: Immediately available quantity is now on template. So no indication when we want to select a product variant on how much stock is available. It will be needed to have different fields for product.product and product.template.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Correct computation of quantity available.