oca / stock-logistics-workflow

Odoo Stock, Workflow and Organization

stock-logistics-workflow

TODO: add repo description.

Available addons

addon	version	maintainers	summary
delivery_procurement_group_carrier	16.0.1.0.0		Delivery Procurement Group Carrier
delivery_total_weight_from_packaging	16.0.1.0.0		Include packaging weight on move, transfer and package.
purchase_stock_picking_invoice_link	16.0.1.0.0		Adds link between purchases, pickings and invoices
sale_line_returned_qty	16.0.1.0.0		Track returned quantity of sale order lines.
sale_order_global_stock_route	16.0.1.0.0		Add the possibility to choose one warehouse path for an order
sale_stock_restocking_fee_invoicing	16.0.1.0.0		On demand charge restocking fee for accepting returned goods .
stock_account_product_run_fifo_hook	16.0.1.0.0		Add more flexibility in the run fifo method.
stock_auto_move	16.0.1.0.0		Automatic Move Processing
stock_customer_deposit	16.0.1.0.1		Customer deposits in your warehouse
stock_customer_deposit_elaboration	16.0.1.0.1		Glue module betwen stock_customer_deposit and sale_elaboration
stock_delivery_note	16.0.1.0.0		This module allows to fill in a delivery note that will be displayed on delivery report
stock_grn	16.0.1.0.3		Goods Received Note
stock_landed_costs_currency	16.0.1.0.0		Stock Landed Costs Currency
stock_landed_costs_purchase_auto	16.0.1.0.0		Stock landed costs purchase auto
stock_landed_costs_security	16.0.1.0.0		Stock landed costs security
stock_lot_production_date	16.0.1.0.0		Stock Lot Production Date
stock_lot_scrap	16.0.1.0.0		This module adds a button in Production Lot/Serial Number view form to Scrap all products contained.
stock_move_free_reservation_reassign	16.0.1.0.1		Try to reassign a move when its reservation is removed due to the related quant becoming unavailable
stock_move_line_auto_fill	16.0.1.1.0		Stock Move Line auto fill
stock_move_line_change_lot	16.0.1.0.0		Stock Move Line Change Lot
stock_move_line_expiration_date_required	16.0.1.0.2		Stock Move Line Expiration Date Required
stock_move_line_reserved_quant	16.0.1.0.0		This module allows to get the link from a stock move line to the reserved quant
stock_move_line_serial_unique	16.0.1.0.0		Stock Move Line Serial Unique
stock_move_manage_priority	16.0.1.0.0		Stock Move Priority Management
stock_move_priority_picking_assign	16.0.1.0.0		This module allows to create a stock movement with a priority and transfer it to the picking during assignation (for new ones)
stock_move_propagate_first_move	16.0.1.0.1		This addon propagate the picking type of the original move to all next moves created from procurement
stock_no_negative	16.0.1.0.2		Disallow negative stock levels by default
stock_override_procurement	16.0.1.0.0		This technical module allow to override procurement values
stock_owner_restriction	16.0.1.1.0		Do not reserve quantity with assigned owner
stock_partner_delivery_window	16.0.1.0.1		Define preferred delivery time windows for partners
stock_picking_auto_create_lot	16.0.1.0.0		Auto create lots for incoming pickings
stock_picking_back2draft	16.0.1.0.0		Reopen cancelled pickings
stock_picking_batch_extended	16.0.1.1.0		Allows manage a lot of pickings in batch
stock_picking_batch_extended_account	16.0.1.0.2		Generates invoices when batch is set to Done state
stock_picking_batch_extended_account_sale_type	16.0.1.0.2		Generates invoices when batch is set to Done state
stock_picking_batch_invoice_frequency	16.0.1.0.1		Invoice Sale Orders from Stock Pickin Batch
stock_picking_batch_print_invoices	16.0.1.0.2		Print invoices from stock picking batchs
stock_picking_batch_print_pickings	16.0.1.0.2		Print Picking from Stock Picking Batch
stock_picking_customer_ref	16.0.1.0.0		This module displays the sale reference/description in the pickings
stock_picking_filter_lot	16.0.1.0.0		In picking out lots' selection, filter lots based on their location
stock_picking_grn_mandatory	16.0.1.0.0		This module allows to require a GRN (Goods Receive Note) when doing a Stock Picking
stock_picking_group_by_base	16.0.1.0.0		Allows to define a way to create index on extensible domain
stock_picking_group_by_max_weight	16.0.1.0.0		Allows to filter available pickings for which a maximum weight is not exceeded.
stock_picking_group_by_partner_by_carrier	16.0.1.1.1		Stock Picking: group by partner and carrier
stock_picking_import_serial_number	16.0.1.0.0		Import S/N from excel file for incoming pickings
stock_picking_info_lot	16.0.1.0.0		Add lot information on Stock Transfer lines
stock_picking_invoice_link	16.0.1.0.2		Adds link between pickings and invoices
stock_picking_kind	16.0.1.0.0		Computes the kind of picking based on locations
stock_picking_line_sequence	16.0.1.0.0		Manages the order of stock moves by displaying its sequence
stock_picking_mass_action	16.0.1.1.0		Stock Picking Mass Action
stock_picking_partner_note	16.0.1.1.0		Add partner notes on picking
stock_picking_product_link	16.0.1.0.0		Adds a "Product" smart button on stock pickings.
stock_picking_progress	16.0.1.0.0		Compute the stock.picking progression
stock_picking_purchase_order_link	16.0.1.0.1		Link between picking and purchase order
stock_picking_quick	16.0.1.0.0		Quick Stock Picking
stock_picking_restrict_cancel_printed	16.0.1.0.0		Prevent canceling a stock transfer if printed.
stock_picking_sale_order_link	16.0.1.0.0		Link between picking and sale order
stock_picking_send_by_mail	16.0.1.0.0		Send stock picking by email
stock_picking_show_backorder	16.0.1.0.0		Provides a new field on stock pickings, allowing to display the corresponding backorders.
stock_picking_show_return	16.0.1.0.1		Show returns on stock pickings
stock_picking_start	16.0.1.1.1		Add button to start picking
stock_picking_supplier_ref	16.0.1.0.0		Adds a supplier reference field inside supplier's pickings and allows search for this reference.
stock_picking_to_batch_group_fields	16.0.1.0.1		Allows to create batches grouped by picking fields.
stock_picking_warn_message	16.0.1.0.0		Add a popup warning on picking to ensure warning is populated
stock_procurement_customer	16.0.1.0.1		Allows to store customer if different from the partner
stock_product_set	16.0.1.0.0		Add product sets in pickings
stock_putaway_hook	16.0.1.0.1		Add hooks allowing modules to add more putaway strategies
stock_quant_package_dimension	16.0.1.0.1		Use dimensions on packages
stock_quant_package_dimension_total_weight_from_packaging	16.0.1.0.0		Estimated weight of a package
stock_quant_package_product_packaging	16.0.1.0.1		Use product packagings on packages
stock_receipt_lot_info	16.0.1.1.0		Be able to introduce more info on lot/serial number while processing a receipt.
stock_restrict_lot	16.0.1.1.0		Base module that add back the concept of restrict lot on stock move
stock_rule_reserve_max_quantity	16.0.1.0.1		Allows to reserve max available quantity when a move comes from an stock rule
stock_split_picking	16.0.1.0.4		Split a picking in two not transferred pickings
stock_valuation_layer_usage	16.0.1.0.0		Trace where has the stock valuation been used in, including the quantities taken.

Licenses

This repository is licensed under AGPL-3.0.

However, each module can have a totally different license, as long as they adhere to Odoo Community Association (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.

stock-logistics-workflow's Issues

How can I delete Stock Move in 'Done' state?

How can I delete Stock Move in 'Done' state?

stock_ownership_availability_rules disables stock accounting

No journal entry gets generated for stock valuation from receipt/delivery after installing this module even when the owner of the stock is the company.

According to stock_account module, accounting valuation entry is designed not to be generated in case a quant has an owner.
https://github.com/odoo/odoo/blob/8.0/addons/stock_account/stock_account.py#L113

8.0: stock_cancel breaks stock levels

Here is the scenario with an up-to-date code on odoo v8:

• install the stock_cancel module
• we will use the demo product "USB Headset", which doesn't have any stock move in the demo data
• On the product form of USB headset, click on "Update" next to the Quantity on hand and set a qty of 10.
• Create a new sale order with 1 sale order line with 2 USB headset. Confirm it and transfer the picking. Now, the "Quantity on hand" for USB Headset = 8.
• On the picking, click on the "Re-open" button. The "Quantity on hand" for USB Headset = 8 ; it should be 10 ! It's a bug.

Feature request : "lock" lots/serial numbers

We and others have the need to "lock" arbitrary serial numbers/production lots for various reasons (usually related to quality control).
Basically, while a lot is locked, no stock move and reservation can be allowed.

Hi, is anyone working on this?

module: stock_cancel
version: 8.0

Steps to reproduce

• ...

Current behavior

Expected behavior

[8.0] stock_ownership_availability_rules fails to reserve quants in Reverse Transfer to supplier

Impacted versions:

• 8.0

Steps to reproduce:

1. create a quant with incoming picking with owner != company
2. click on 'Reverse Transfer' to return the quant back to supplier to generate an outgoing picking

Current behavior:

The move record in generated outgoing picking does not have the quant reserved (unlike the standard behavior). You need to open the move and manually assign the owner to be able to reserve the correct quant by 'Check Availability' button.

Expected behavior:

The quant should be automatically reserved for the move when outgoing picking is generated.

[7.0] Duplicate invoice when stock_picking_invoice_link is instaled

When trying to duplicate an invoice with related pickings you are blocked by this constraint.

odoo/addons/stock.py:
class stock_picking
...
_sql_constraints = [
('name_uniq', 'unique(name, company_id)', 'Reference must be unique per Company!'),
]

No accounting entries created when stock_ownership_avalaibility_rules installed, even for real time valuation

Hi,

Steps to reproduce:

1. Install stock_ownership_avalaibility_rules
2. Create product with Real Time valuation
3. Create PO to purchase that product
4. Transfer receipt

Expected behaviors:

1. stock.move on Receipt will create accounting entry (account.move)

Result:

1. No accounting entry created

It might be because stock_ownership_avalaibility_rules module make owner_id on stock.quant required. According https://github.com/odoo/odoo/blob/8.0/addons/stock_account/stock_account.py#L123 no accounting entry will create if owner_id is not null.

Can someone confirm it?

stock_route_transit: transit picking type src and dest locations not updated

package_preparation: Package done does a transfer of the goods

Hi,

I have an issue with the button "package done". It should not do the transfer as I may want to package it further. Can you please explain the logic in the workflow.

My expected workflow is:

• Select product to package, select the packaging, packaging is finished.
  The actual workflow is:
  • Select product to package, select packaging, transfer within the packaging preparation.
    How to do multi level packaging this way?

thanks a lot for the answer

[8.0][BUG] stock_dropshipping_dual_invoice - Error bringing payment data to invoice from company and customer

module: stock_dropshipping_dual_invoice
version: 8.0

Steps to reproduce

To reproduce this bug you must install also module account_payment_partner: https://github.com/OCA/bank-payment/tree/8.0/account_payment_partner

• Define in you company a Bank account which customer will pay you.
• Choose a product that has a supplier.
• Choose a customer who has defined (or define it) fields:
  • property_payment_term
  • customer_payment_mode
• Create to this customer a Sale Order of the product. Choose in the line the Drop Shipping route, and choose to invoice in delivery.
• Find the automatically generated RFQ, in it specify invoicing on delivery, and validate.
• Open the delivery, transfer it, and click the button to generate the invoice.
• Fill in the wizard. Two invoices will be generated -- one for the customer, one for the supplier.
• You can find the generated customer and supplier invoices from the Sale and Purchase Orders, respectively.

Current behavior

• You will check that in the customer invoice:
  • partner_bank_id is empty
  • payment_mode_id is empty
• You will check that in the supplier invoice:
  • partner_bank_id is empty
  • payment_mode_id is empty

Expected behavior

• In the customer invoice it must be filled:
  • partner_bank_id with the company bank account
  • payment_mode_id with the res.partner customer_payment_mode
• In the supplier invoide it must be filled:
  • partner_bank_id with the supplier account bank number
  • payment_mode_id with the supplier payment mode

Calculate qty_available takes a lot of time

Hello everyone, @pedrobaeza

I am using the module stock_filter_none_zero_qty in v7. But apply "Real stock" filter takes a lot of time for finishing.

An looking for the main cause of the problem I noticed that in https://github.com/OCA/stock-logistics-workflow/blob/7.0/stock_filter_none_zero_qty/product.py#L59, the operations are made including all items. But the function does not care if there is a limit value or and offset value at the moment of returning the result.

Then I was wondering ... is there a way to pass at the function what is the limit value and the offset value? Maybe with the new api? or to accomplish it from other way?

Thanks in advance

Missing labels *needs fixing* and *needs review*

Read OCA/maintainer-tools#29 to know more about it

stock_ownership_availability_rules: traceback on install

Steps to reproduce:

1. use OCB branch (did not check with official)
2. first install stock_route_sales_team and stock_dropshipping_dual_invoice with demo data
3. Then install stock_ownership_availability_rules

I get:

openerp.service.server: Failed to initialize database `test_ocb_oca_70`.
Traceback (most recent call last):
  File "work/oerp/odoo/odoo/openerp/service/server.py", line 909, in preload_registries
    registry = RegistryManager.new(dbname, update_module=update_module)
  File "work/oerp/odoo/odoo/openerp/modules/registry.py", line 366, in new
    openerp.modules.load_modules(registry._db, force_demo, status, update_module)
  File "work/oerp/odoo/odoo/openerp/modules/loading.py", line 355, in load_modules
    loaded_modules, update_module)
  File "work/oerp/odoo/odoo/openerp/modules/loading.py", line 255, in load_marked_modules
    loaded, processed = load_module_graph(cr, graph, progressdict, report=report, skip_modules=loaded_modules, perform_checks=perform_checks)
  File "work/oerp/odoo/odoo/openerp/modules/loading.py", line 150, in load_module_graph
    getattr(py_module, pre_init)(cr)
  File "work/OCA/stock-logistics-workflow/stock_ownership_availability_rules/__init__.py", line 11, in fill_quant_owner
    orphan_quants = env['stock.quant'].search([('owner_id', '=', False)])
  File "work/oerp/odoo/odoo/openerp/api.py", line 239, in wrapper
    return new_api(self, *args, **kwargs)
  File "work/oerp/odoo/odoo/openerp/api.py", line 462, in new_api
    result = method(self._model, cr, uid, *args, **kwargs)
  File "work/oerp/odoo/odoo/openerp/models.py", line 1649, in search
    return self._search(cr, user, args, offset=offset, limit=limit, order=order, context=context, count=count)
  File "work/oerp/odoo/odoo/openerp/api.py", line 241, in wrapper
    return old_api(self, *args, **kwargs)
  File "work/oerp/odoo/odoo/openerp/models.py", line 4602, in _search
    query = self._where_calc(cr, user, args, context=context)
  File "work/oerp/odoo/odoo/openerp/api.py", line 241, in wrapper
    return old_api(self, *args, **kwargs)
  File "work/oerp/odoo/odoo/openerp/models.py", line 4415, in _where_calc
    if 'active' in self._fields and active_test and context.get('active_test', True):
AttributeError: 'stock.quant' object has no attribute '_fields'

Feature request: new put-away strategy "First empty location"

We have a requirement to add a new put-away strategy, which would let us substitute a destination location with one of its empty sub-locations.
The standard lets us easily substitute a location for another but they are fixed locations, whereas our users want the system to propose a new location each time (basically we have 1 location = 1 pallet).

Does someone in the community have a module which implement this strategy, or would be interested in co-developping it ?

I'm filing this issue here as a follow-up to a conversation on the mailing-list:
https://www.odoo.com/groups/community-59/community-11676091

[8.0] stock_split_spicking Why is only allowed to split outgoing or incoming shipment ?

I would like to split internal shipment.

Picking dispatch: field picker can be empty, the system considers it as assigned

Steps to reproduce:

1. Create a picking dispatch
2. Add some stock moves
3. Click assign (the field picker is empty, still)

Migration to version 10.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0

Modules to migrate

• picking_dispatch_wave
• product_customer_code_picking
• product_serial
• stock_batch_picking
• stock_cancel
• stock_deposit
• stock_disable_force_availability_button - By @rousseldenis - #338
• stock_dropshipping_dual_invoice
• stock_filter_none_zero_qty - Not needed since quants
• stock_inventory_retry_assign
• stock_location_flow_creator
• stock_move_backdating - By @tafaRU - #426
• stock_move_description
• stock_move_on_hold
• stock_obsolete
• stock_ownership_availability_rules
• stock_ownership_by_move - By @Cedric-Pigeon - #333
• stock_picking_back2draft - By @Saphery - #456
• stock_picking_backorder_strategy - By @rousseldenis - #432
• stock_picking_compute_delivery_date
• stock_picking_deliver_uos
• stock_picking_invoice_link - By @eLBati - #347
• stock_picking_mass_action - By @cubells - #407
• stock_picking_package_preparation - By @archetipo - #271
• stock_picking_priority
• stock_picking_reorder_lines
• stock_picking_show_return - By @pedrobaeza - #314
• stock_picking_show_backorder - By @aheficent - #362
• stock_picking_transfer_lot_autoassign - By @rgarnau - #366
• stock_sale_filters
• stock_split_picking - By @cubells - #310
• stock_transfer_split_multi

a picking dispatch can be backorder of itself

Create a picking_dispatch, save it.
You can indicate as backorder the current dispatch : backorder of itself.

Expected Behaviour:
the current dispatch should not be proposed in the backorder many2one selection.

Short dump when clicking create on picking dispatch

Steps to reproduce:

1. select menu operations/picking dispatch
2. Press create.

Thanks

I just added the screen shot

package_preparation: The selection of the partners brings the user and the partner

Hi,

When I want to select a partner for package preparation, I am not expecting to have all users also in the selection, but rather customers and suppliers.

Best regards
Eva P.

stock_transfer_split_multi: Should not split units in half units

Hi,

I was able to split ONE unit into half a unit, what is wrong from the functional side.

But I have noticed that this is also the case with Odoo. It accepts part of units.

Thanks

Eva P.

stock_picking_reorder_lines: No number available

Hello,

I have installed the module, but I do not see the number. I can only drag and drop the lines to reorganise them. This only works when I have a very small delivery. With more than 20 lines, I am not really able to move the last delivery item to the first position.

Thanks for the help/remarks

Eva P.

module: stock_dropshipping_dual_invoice version: 8.0

Hi
My name is steve alexander and I am an Odoo ready partner from the UK.

I have installed the module: stock_dropshipping_dual_invoice v8.0 for a client to manage stock direct delivery from a supplier to a customer and to raise both the supplier and the customer invoices.

I have followed the settings recommended in the module however, when I check both Invoices that it has produced, I find that the sales invoice is correct but the purchase Invoice has used the sale price and Sale VAT(ST0) code rather than the supplier price and the Purchase VAT code( PT0).

Do you have any ideas what has caused this?

the sales order and the Purchase order are both correct the PO has the purchase price from the supplier record and has PT0 as the Tax code.

regards

Steve

[8.0][BUG] stock_split_picking - error when spliting move.lines in stock.picking

Module: stock_split_picking
version: 8.0

Steps to reproduce.

• Create a sale order with two lines of product.
• Define for each one a quantity. For example 83 units for each one.
• Confirm sale order.
• View delivery order.
• Check Availability and force it.
• Transfers and moves, each product, a smaller amount to the initial quantity. By example 10 units.

Current behavior

• The system change delivery order and deletes the second line, keeping the first line with the change.
• The system creates a new delivery order with two lines; in the first one, the amount oustanding of serving is 73 units, in the second line the delivery order keeping the 83 units.

Expected behavior.

• One delivery order with two lines, in each one the amount should be 10 units.
• Other delivery order with two lines, in each one the amount should be 73.

Can't enforce internal traceability, even with product_serial

For the moment there seems to be no clear way of forcing users to enter lots/serial numbers on internal moves (see https://bugs.launchpad.net/openobject-addons/+bug/670451).
product_serial does create a field "track_internal" with a helptext that says it forces users to enter the serial number, but I found no code to support that.

[8.0][BUG] stock_split_picking

Module: stock_split_picking
version: 8.0

Steps to reproduce.
• Create a sale order with two lines of product.
• Define for each one a quantity. For example 83 units for each one.
• Confirm sale order.
• View delivery order.
• Check Availability and force it.
• Transfers and moves, each product, a smaller amount to the initial quantity. By example 10 units.
Current behavior
* The system change delivery order and deletes the second line, keeping the first line with the change.
*The system creates a new delivery order with two lines; in the first one, the amount oustanding of serving is 73 units, in the second line the delivery order keeping the 83 units.
Expected behavior.
• One delivery order with two lines, in each one the amount should be 10 units.

Documentation / Screenshots for workflows

Hello is there a way to find documentation / screenshots for this module? I searched online but was not able to find it.

Missing readme.rst and readme to update

• stock_picking_invoice_link #107 (module was not ported) @tafaRU

To update (not following template, AGPL logo, OCA maintainers, etc):

• picking_dispatch #115
• stock_cancel #116
• stock_dropshipping_dual_invoice #117

Last Location search fix for product_serial

The _last_location_id_search method provided for last_location field added to stock.production.lot in product_serial/stock.py currently only serve the Prodlots shortcut where it would provide the domain in the [('last_location_id', '=', 9)] format where 9 is the database ID of stock.location being search. It does not suppoert searching by any means and hence searching through Advance Filter for Last Location generates various error. The patch here can also accomodate both Prodlots short cuts and search through Advance Filter:

diff --git a/product_serial/stock.py b/product_serial/stock.py
index 79ffae1..0e8558f 100644
--- a/product_serial/stock.py
+++ b/product_serial/stock.py
@@ -366,26 +366,44 @@ class stock_production_lot(orm.Model):
         return res

     def _last_location_id_search(self, cr, uid, obj, name, args, context=None):
-        ops = ['=', ]
-        prodlot_ids = ()
-        if not len(args):
-            return []
-        prodlot_ids = []
-        for a in args:
-            operator = a[1]
-            value = a[2]
-            if operator not in ops:
-                raise orm.except_orm(
-                    _('Error !'),
-                    _('Operator %s not supported in searches for '
-                      'last_location_id (product.product).' % operator))
-            if operator == '=':
-                cr.execute(
-                    "select distinct prodlot_id "
-                    "from stock_report_prodlots "
-                    "where location_id = %s and qty > 0 ",
-                    (value, ))
-                prodlot_ids = filter(None, map(lambda x: x[0], cr.fetchall()))
+        _not = False
+        _loc_pool = self.pool.get('stock.location')
+        _loc_ids = []
+        _is_null = False
+        for _leaf in args:
+            if _leaf[0] == 'last_location_id':
+                if isinstance(_leaf[-1], (int, long)):
+                    _val_id = _leaf[-1]
+                else: 
+                    _val = _leaf[-1]
+
+                _op = _leaf[1].strip()
+                _not = (('not' in _op) or ('!' in _op) or ('<' in _op) or
+                        ('>' in _op))
+                if isinstance(_leaf[-1], (bool)):
+                    if _leaf[1] == '=':
+                        _is_null = True
+                    else:
+                        _loc_ids.append(0)
+                elif isinstance(_leaf[-1], (int, long)):
+                    _loc_ids.append(_leaf[-1])
+                else: 
+                    _locs = _loc_pool.name_search(cr, uid, _leaf[-1], context=context)
+                    _locs = tuple([x[0] for x in _locs])
+                    _loc_ids.extend(_locs)
+
+        if _is_null:
+            cr.execute(
+                "SELECT DISTINCT prodlot_id "
+                "FROM stock_report_prodlots "
+                "WHERE location_id IS NULL AND qty > 0")
+        else:
+            cr.execute(
+                "SELECT DISTINCT prodlot_id "
+                "FROM stock_report_prodlots "
+                "WHERE location_id %s IN %%s AND qty > 0 " % (_not and 'NOT' or ''),
+                (tuple(_loc_ids), ))
+        prodlot_ids = filter(None, map(lambda x: x[0], cr.fetchall()))
         return [('id', 'in', tuple(prodlot_ids))]

     _columns = {

picking_dispacht traceback when creating a new picking dispacht

When I try to create a new picking dispatch, I find next error (I can continue working after this closing the popup):
2015-08-21 09:39:30,865 5816 ERROR base_stock openerp.http: Exception during JSON request handling.
Traceback (most recent call last):
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\http.py", line 537, in _handle_exception
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\http.py", line 574, in dispatch
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\http.py", line 310, in _call_function
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\service\model.py", line 113, in wrapper
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\http.py", line 307, in checked_call
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\http.py", line 803, in call
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\http.py", line 403, in response_wrap
File "C:\Program Files (x86)\Odoo 8.0-20150723\server\openerp\addons\web\controllers\main.py", line 944, in call_kw
File "C:\Program Files (x86)\Odoo 8.0-20150723\server\openerp\addons\web\controllers\main.py", line 936, in _call_kw
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\api.py", line 241, in wrapper
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\api.py", line 363, in old_api
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\models.py", line 5829, in onchange
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\api.py", line 239, in wrapper
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\models.py", line 5416, in new
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\models.py", line 5315, in _convert_to_cache
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\models.py", line 5316, in
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\fields.py", line 1615, in convert_to_cache
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\models.py", line 5573, in getitem
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\fields.py", line 820, in get
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\fields.py", line 928, in determine_draft_value
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\fields.py", line 867, in _compute_value
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\api.py", line 239, in wrapper
File "C:\Program Files (x86)\Odoo 8.0-20150723\server\openerp\OCA\picking_dispatch\picking_dispatch.py", line 53, in _get_related_picking
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\sql_db.py", line 158, in wrapper
File "C:\Program Files (x86)\Odoo 8.0-20150723\server.\openerp\sql_db.py", line 234, in execute
ProgrammingError: error de sintaxis en o cerca de «)»
LINE 1: ...ng_id FROM stock_move sm WHERE sm.dispatch_id in () AND sm.p...

[IMP] product_serial: Add constraint to deny moves with qty <> 1 on product with unique serial

Hello,
I'm reviewed product_serial module to work with unique serial number.
But I don't found the way to work with this case.

Am I doing any bad?
Or this module is out of scope of this case?

I want dev this new feature but I'm confused of how add it.

1. I add a new module. (out of scope of product_serial module).
2. I make a pr with this feature to product_serial.

What do you think?

picking_dispatch: cancel does cancel all the moves in the dispatch

Hi,

Not sure, if it is a feature or a bug. But when I press on cancel, without any warning, all moves are cancelled. I believe in a warehouse environment, this is very difficult to manage and quite dangerous, if a lot of moves are cancelled without warning.

Regards
Eva P.

[8.0] [stock_picking_package_preparation] fields weight and net_weight in view raise an Assertion

If I insert weight and net_weight field on stock_picking_package_preparation form view, when I try to create a new record, I obtain this:

Traceback (most recent call last):
  File "ROOT_PATH/Odoo/OCB/openerp/http.py", line 537, in _handle_exception
    return super(JsonRequest, self)._handle_exception(exception)
  File "ROOT_PATH/Odoo/OCB/openerp/http.py", line 574, in dispatch
    result = self._call_function(**self.params)
  File "ROOT_PATH/Odoo/OCB/openerp/http.py", line 310, in _call_function
    return checked_call(self.db, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/service/model.py", line 113, in wrapper
    return f(dbname, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/http.py", line 307, in checked_call
    return self.endpoint(*a, **kw)
  File "ROOT_PATH/Odoo/OCB/openerp/http.py", line 803, in __call__
    return self.method(*args, **kw)
  File "ROOT_PATH/Odoo/OCB/openerp/http.py", line 403, in response_wrap
    response = f(*args, **kw)
  File "ROOT_PATH/Odoo/OCB/addons/web/controllers/main.py", line 944, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "ROOT_PATH/Odoo/OCB/addons/web/controllers/main.py", line 936, in _call_kw
    return getattr(request.registry.get(model), method)(request.cr, request.uid, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 241, in wrapper
    return old_api(self, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 363, in old_api
    result = method(recs, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/models.py", line 5874, in onchange
    newval = record[name]
  File "ROOT_PATH/Odoo/OCB/openerp/models.py", line 5572, in __getitem__
    return self._fields[key].__get__(self, type(self))
  File "ROOT_PATH/Odoo/OCB/openerp/fields.py", line 820, in __get__
    self.determine_draft_value(record)
  File "ROOT_PATH/Odoo/OCB/openerp/fields.py", line 928, in determine_draft_value
    self._compute_value(record)
  File "ROOT_PATH/Odoo/OCB/openerp/fields.py", line 867, in _compute_value
    self.compute(records)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 239, in wrapper
    return new_api(self, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 398, in new_api
    result = [method(rec, *args, **kwargs) for rec in self]
  File "ROOT_PATH/Odoo/ExternalRepo/stock-logistics-workflow/stock_picking_package_preparation/model/stock_picking_package_preparation.py", line 141, in _compute_weight
    quants = quant_model.browse(package.get_content())
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 239, in wrapper
    return new_api(self, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 547, in new_api
    result = method(self._model, cr, uid, self.ids, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/addons/stock/stock.py", line 3931, in get_content
    child_package_ids = self.search(cr, uid, [('id', 'child_of', ids)], context=context)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 241, in wrapper
    return old_api(self, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/models.py", line 1643, in search
    return self._search(cr, user, args, offset=offset, limit=limit, order=order, context=context, count=count)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 241, in wrapper
    return old_api(self, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/models.py", line 4639, in _search
    query = self._where_calc(cr, user, args, context=context)
  File "ROOT_PATH/Odoo/OCB/openerp/api.py", line 241, in wrapper
    return old_api(self, *args, **kwargs)
  File "ROOT_PATH/Odoo/OCB/openerp/models.py", line 4464, in _where_calc
    where_clause, where_params = e.to_sql()
  File "ROOT_PATH/Odoo/OCB/openerp/osv/expression.py", line 1256, in to_sql
    assert len(stack) == 1
AssertionError

Unbale to see stock_cancel in my modules list

Hello guys,
Is this something special I should know about stock_cancel? Unable to see this module in module list. I have proceeded Like usuallly... Permission, owner checked...
What is the problem...
Help pleasae

cancel meaning of a picking dispatch (functional issue)

Steps
Create a picking dispatch
Add some moves.
Cancel the picking dispatch

Identified behavior
The moves and by extension the picking are cancelled too.

Expected behavior
In a functional context, it seems more coherent to "desassociate" moves from the cancelled dispatch, and don't change the move states.

Any opinions?

build broken by recent changes in odoo/odoo

Commit odoo/odoo@675357b7d7b broke the build by causing failures in the tests of stock_dropshipping_dual_invoice

https://travis-ci.org/OCA/stock-logistics-workflow/jobs/50039271#L313

[Question][product_serial] Migration to 8.0

Hello,
We like migrate to 8.0 of module: product_serial
We need to know what is the guidelines for migration.
-Use new api or use old api without problems.
-Stock has important changes and probably refactory of this module is required.

Can you help me with guidelines of this case?

[7.0] [product_customer_code_picking] Error accessing to the picking associated to a manufacturing order

Hello,
When you try to access to the picking associated to a manufacturing order, that has no partner, the following error appears:

stock-logistics-workflow/product_customer_code_picking/stock_picking.py", line 35, in _get_product_customer_code
move.picking_id.partner_id.commercial_partner_id.id)
AttributeError: 'NoneType' object has no attribute 'id'

I will be providing a PR that fixes this issue.

Feature request: stock_picking_invoice_link, Print the liste of pickings on invoices

In France (and probably elsewhere) it's now mandatory to print the delivery date of the goods on invoices.
Since stock_picking_invoice_link adds the list of pickings on the invoice form, I suggest we extend stock_picking_invoice_link to print the picking references and delivery dates at the bottom of the invoices.

[8.0] [stock_ownership_availability_rules] Incompatible with real-time inventory valuation

Module 'stock_ownership_availability_rules' sets an owner to the quant, even when the quant belongs to the company. However module "stock_account" in method "_account_entry_move" will define that if the quant has an owner, it assumes that the owner is a third party, regardless if the actual owner IS the company.

Migration to version 9.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Modules to migrate

• mrp_lock_lot
• picking_dispatch > stock_batch_picking - Assigned to @cyrilgdn - #241
• picking_dispatch_wave
• product_customer_code_picking
• product_serial
• stock_cancel
• stock_disable_force_availability_button - By @nicomacr - #278
• stock_dropshipping_dual_invoice
• stock_filter_none_zero_qty - Not needed since quants
• stock_inventory_retry_assign
• stock_location_flow_creator
• stock_lock_lot
• stock_lot_scrap - By @pedrobaeza - #280
• stock_move_backdating
• stock_move_description
• stock_move_on_hold
• stock_obsolete
• stock_ownership_availability_rules
• stock_ownership_by_move
• stock_picking_backorder_strategy
• stock_picking_back2draft - By @nicomacr - #276
• stock_picking_compute_delivery_date
• stock_picking_deliver_uos
• stock_picking_invoice_link - By @flotho merged in one module in OCA/account-invoicing/pull/140 - Alt. migration of only this module: #261
• stock_picking_mass_assign - By @mdietrichc2c - #244
• stock_picking_package_preparation - #199
• stock_picking_package_preparation_line - #199
• stock_picking_priority
• stock_picking_reorder_lines > stock_picking_line_sequence - By @mreficent - #385
• stock_picking_show_return - By @pedrobaeza - #251
• stock_sale_filters
• stock_split_picking @yvaucher #201 - By @lmignon #381
• stock_transfer_split_multi
• stock_route_sales_team

Error when creatring new picking with stock_picking_reorder_lines

I'm trying to create a new picking and i have that error: ValueError: max() arg is an empty sequence.

I FIX it adding that line: if picking.move_lines, because the problem is that if yo don't have any line, it's impossible to find a max sequence.

[8.0] stock_picking_invoice_link Error on Invoice creation

When i create 1 invoice from 2 or more pickings, on invoice's picking_lines appear only one picking.
I will be providing a PR that fixes this issue.

picking_dispatch: Short dump of availability check when the stock is not available

Steps to reproduce

1.Create a material of type stockable material
2. Create a sales order
3. Confirm the sales order
4. Create a picking dispatch
5. Add the newly created delivery order to the picking
6. Save and press availability check

check_unicity_qty_available fails with unique_lot active when move is split in wizard

Odoo: 8.0 (git)
Module: product_unique_serial 8.0.1.0.1 (git branch 8.0)

Problem:
When a picking with quantity N > 1 is received with unique_lot set and the move is split up into single itmes in the move-wizard with the native button to assign unique serial numbers, function check_unicity_qty_available fails with "Product X has active 'unique lot' but with this move you will have a quantity of N in lot Y". Executing the move is blocked.

Expected behavior:
product_unique_lot takes into account changes to move-lines inside the move-wizard and move succeeds.

[7.0] [stock_picking_deliver_uos] Error on Partial Delivering with user different from admin

Test Case:
Using a user different from admin
Create a Delivery Order, create a line with product quantity > 1
Deliver the order partially using the wizard, changing uos quantity.
Return Warning:
Quantities, Units of Measure, Products and Locations cannot be modified on stock moves that have already been processed (except by the Administrator).
I will be providing a PR that fixes this issue.

Advanced features for blocked lots/serial numbers

As a follow-up to #110, we developed the following features which could be proposed to OCA is there is interest:

• restrict blocking/unblocking to a specific group: https://github.com/numerigraphe/stock-logistics-workflow/tree/8.0-stock-lock-lot-group/stock_lock_lot#configuration
• enforce strict blocking, forbidding users to force the move: https://github.com/numerigraphe/stock-logistics-workflow/tree/8.0-stock-lock-lot-strict/stock_lock_lot_strict
• allow users to move blocked lots inside certain reception locations (quality control area, reception zone...): https://github.com/numerigraphe/numerigraphe-addons/tree/8.0/stock_lock_lot_receipt
• add a new state "first use" for newly referenced products, and automatically block received lots for these products: https://github.com/numerigraphe/numerigraphe-addons/tree/8.0/stock_lock_lot_firstuse

Each feature is implemented as a module. They can easily have a corresponding checkbox in the warehouse configuration when stock_lock_lot is installed (stock_lock_lot_strict already has it:https://github.com/numerigraphe/stock-logistics-workflow/blob/8.0-stock-lock-lot-strict/stock_lock_lot/models/res_config.py) .
They "work for us" and I expect they'd require only small improvements to meet OCA standards.

If you are interested please post your comments here.

[8.0] [stock_picking_back2draft] Sale order DONE instead of OPEN

Module: stock_picking_back2draft

Steps to reproduce:

1. Create a sale order for 100 units of any product.
2. Transfer 50 units of product.
3. Cancel the transfer of the 50 remaining units.
4. Click on picking Back to draft.
5. Mark as To Do.

Problem:

• The sale order is in state "DONE" even though the picking is not done.
• Invoice control on the picking is Not Applicable.

Expected behaviour:

• The sale order moves back to state OPEN as the shipping is not completely done yet.
• Invoice control should be To Be Invoiced.

package_preparation: Package done does a transfer of the goods

Hi,

I have an issue with the button "package done". It should not do the transfer as I may want to package it further. Can you please explain the logic in the workflow.

My expected workflow is:

• Select product to package, select the packaging, packaging is finished.
  The actual workflow is:
  • Select product to package, select packaging, transfer within the packaging preparation.
    How to do multi level packaging this way?

thanks a lot for the answer