Issue 11626

Changing drop shipment quantity on customer_moves results to an empty origin
Nosy list
acaubet, pokoli
Assigned to

Created on 2022-08-04.11:43:58 by acaubet, last changed 1 week ago by pokoli.


Author: [hidden] (pokoli) Tryton committer Tryton translator
Date: 2022-08-04.11:56:23

What is the behaviout on Customer Shipments? Can we follow the same behaviour?
I mean if the user updates the outgoing moves of the customer shipment what happens with inventory moves?

Author: [hidden] (acaubet)
Date: 2022-08-04.11:43:58

Related to issue10430.
If the user change quantity of customer moves sending less units on drop shipment results in a new drop shipment (if remain quantity) with remaining units but without the origin on the customer moves.
If the user split customer moves on drop shipment results in a new splited move with no origin.
Only modifications on supplier moves are supported by now if you don't want to lose origins.

You can test with:

--- a/tests/scenario_sale_supply_drop_shipment.rst      Mon May 02 17:45:46 2022 +0200
+++ b/tests/scenario_sale_supply_drop_shipment.rst      Thu Aug 04 11:22:35 2022 +0200
@@ -193,13 +193,13 @@

     >>> set_user(stock_user)
     >>> move, = shipment.supplier_moves
-    >>> move.quantity = 100
     >>> move.unit_price
     >>> move.cost_price
     >>> move, = shipment.customer_moves
+    >>> move.quantity = 100
     >>> move.unit_price
     >>> move.cost_price

How to reproduce:
a. Create a Drop shipment (send x units)
b. On shipment, reduce the quantity to send on customer moves (x-1)
c. > Ship
A new drop shipment with supplier and costumer moves but it's only related to the purchase and not to the sale because customer moves don't have origin.

Which should be the solution? Sync moves? Blocking user change of customer moves?

Date User Action Args
2022-08-04 11:56:23pokolisetmessages: + msg77561
nosy: + pokoli
2022-08-04 11:43:58acaubetcreate

Showing 10 items. Show all history (warning: this could be VERY long)