Comment 9 for bug 796320
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote Re: incoming shipment does not trigger corresponding delivery order | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Hi Patrick,
I understand your concern and I kind of agree that we could improve the model a bit to support cases with split deliveries in a more reliable way. However as Kirti tried to explain, this represents a non-trivial change in the model, for a limited immediate benefit.
Usually when a split move line fails to be considered correctly by the system, the workaround is to resort to handling it manually. This is in fact consistent with the philosophy of OpenERP flows: the regular flows are handled automatically by the system, without going to far in specific cases as to make the system overly complex. And for the rest, give enough control to users so they can manually handle any special case without the system coming in the way.
This is illustrated by your example in comment #3, where the workaround is trivial: when the system did not do the work for you, you can just "Check availability" manually and fix it.
Nevertheless we can think about improving the model in the long run, for instance by having a more explicit way to link "split" moves together so they can be considered all together when that matters. For this reason I suggest we keep this bug open as "Wishlist", and foresee a deeper analysis to improve this in the future (i.e. after 6.1 release).
On the other hand, you related bug 794412 does highlight a case where this could lead the user to wrongly believe that an order has been completely delivered. This is different and we should indeed implement a workaround right now, without waiting for a future new model.
Thanks for your well documented bug reports!