mirror of
https://github.com/OCA/stock-logistics-warehouse.git
synced 2025-01-21 14:27:28 +02:00
d1b7a6f47c
Instead of going through the onchange machinery. The intended usage of onchange methods is to update something on the screen, without side-effects in the database, then let the user save the form with the proposed changes. Weirdly, the barcode scanner event triggers an onchange on the field `_barcode_scanned`. It doesn't work well with our use case, as the whole form is read-only and we only care about having the barcode events doing side-effects on the backend and displaying back the changes. This particular onchange will then be executed as a normal method, with side-effects. However, contrarily to other actions on the form, the frontend does not reload the view after an onchange, as it relies on the data returned back in the values. As we cannot know which values may have been changed in the different implementations (location destination, state, ...), the onchange returns a read with every field.
stock-logistics-warehouse
TODO: add repo description.
Available addons
| addon | version | maintainers | summary |
|---|---|---|---|
| scrap_reason_code | 14.0.1.0.0 |  |
Reason code for scrapping |
| stock_archive_constraint | 14.0.1.0.0 |  |
Stock archive constraint |
| stock_available | 14.0.1.0.2 | Stock available to promise | |
| stock_available_immediately | 14.0.1.0.0 | Ignore planned receptions in quantity available to promise | |
| stock_available_mrp | 14.0.1.0.2 | Consider the production potential is available to promise | |
| stock_available_unreserved | 14.0.1.0.1 |  |
Quantity of stock available for immediate use |
| stock_demand_estimate | 14.0.1.1.0 | Allows to create demand estimates. | |
| stock_demand_estimate_matrix | 14.0.1.0.0 | Allows to create demand estimates. | |
| stock_free_quantity | 14.0.1.0.0 | Stock Free Quantity | |
| stock_generate_putaway_from_inventory | 14.0.1.0.0 |     |
Generate Putaway locations per Product deduced from Inventory |
| stock_helper | 14.0.1.0.0 | Add methods shared between various stock modules | |
| stock_inventory_preparation_filter | 14.0.1.0.0 | More filters for inventory adjustments | |
| stock_location_children | 14.0.1.0.0 | Add relation between stock location and all its children | |
| stock_location_lockdown | 14.0.1.0.0 | Prevent to add stock on locked locations | |
| stock_location_position | 14.0.1.0.0 | Add coordinate attributes on stock location. | |
| stock_location_tray | 14.0.1.1.0 | Organize a location as a matrix of cells | |
| stock_location_zone | 14.0.1.0.0 | Classify locations with zones. | |
| stock_measuring_device | 14.0.1.0.0 |  |
Implement a common interface for measuring and weighing devices |
| stock_measuring_device_zippcube | 14.0.1.0.0 | |
Implement interface with Bosche Zippcube devicesfor packaging measurement |
| stock_move_common_dest | 14.0.1.0.0 | Adds field for common destination moves | |
| stock_move_location | 14.0.1.0.0 | This module allows to move all stock in a stock location to an other one. | |
| stock_orderpoint_move_link | 14.0.1.0.0 | Link Reordering rules to stock moves | |
| stock_packaging_calculator | 14.0.1.0.1 | Compute product quantity to pick by packaging | |
| stock_picking_cancel_confirm | 14.0.1.0.1 |  |
Stock Picking Cancel Confirm |
| stock_pull_list | 14.0.1.0.0 | |
The pull list checks the stock situation and calculates needed quantities. |
| stock_putaway_method | 14.0.1.0.0 |  |
Add the putaway strategy method back, removed from the stock module in Odoo 12 |
| stock_quant_manual_assign | 14.0.1.1.0 | Stock - Manual Quant Assignment | |
| stock_request | 14.0.1.0.3 | Internal request for stock | |
| stock_request_picking_type | 14.0.1.0.0 |  |
Add Stock Requests to the Inventory App |
| stock_reserve_rule | 14.0.1.0.0 | Configure reservation rules by location | |
| stock_search_supplierinfo_code | 14.0.1.0.0 | Allows to search for picking from supplierinfo code | |
| stock_warehouse_calendar | 14.0.1.0.1 |  |
Adds a calendar to the Warehouse |
Licenses
This repository is licensed under AGPL-3.0.
However, each module can have a totally different license, as long as they adhere to OCA
policy. Consult each module's __manifest__.py file, which contains a license key
that explains its license.
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.