Community mailing list archives
Re: Cancel done delivery orderby
I do agree allowing these operations is painful from a technical perspective, however I also think that some of this pain is caused by the architecture of the data model, and eventually this could be optimized quite a bit.
Ultimately, I think this should be a configuration setting that the company administrator decides. Allow canceling of delivery, Allow canceling sale, purchase, etc and then if cancel to implement strict control or not.
Joel,Your solution sounds ok to me. I think for some customers or especially european clients or countries that have very strict legal requirements this would be the ultimate solution. On the other hand for some other customers, like American companies that have no such legal requirements this proposed solution would be significantly more technically complex than required to serve the purpose.
On Tue, Mar 10, 2015 at 8:07 AM, Marc Cassuto <email@example.com> wrote:
Count on me for testing !!
On 15-03-10 08:53 AM, Joël Grand-Guillaume wrote:<blockquote cite="mid:CACk3wO+L4+2KbYrKeW3FHiHcZ1nkD5SifPv7e6h71o6VAX_zzA@mail.gmail.com" type="cite">
=> So like the backorder for pickings, the new copy for revision is in fact the historized version. The ID 36 will always be the "running" order.- SO0001, ID 36 -> is kept as the "running" order- Copy SO0001, ID 37 -> is kept as revision 1- SO0001, ID 36 -> Make a new revision* Add revision to SO/PO => So when canceled, you can make a new revision of the SO/PO by providing a reason for this action. The new version will have a tab where you can access to all past revision (for audit purpose). The idea is here to have:Hi,First, I mostly agree with Eva here. I'm on a same kind of problematic on a quite huge project. My last thoughts about this is that may be a good way to achieve such a feature would be :
* Add a button that will :
- Cancel the picking & related invoice if possible
- Done deliveries are kept as done (as the new order is in fact the old revision)
- If it succeed, cancel the SO, ask for a reason and create a new revision as draft
This way, we would only allow to make a new revision if you can first cancel what is remaining. If you can't, this is probably because it is wrong to do so !
I will start working on this (to be publish under the OCA). I think it is a clean way to do this, because if the system allow you to cancel something, then why can't you ease the user experience by providing some improvements around it !
On Tue, Mar 10, 2015 at 1:18 PM, Eva Pinter <firstname.lastname@example.org> wrote:
+1 to Lionel ;-)
On 10 Mar 2015, at 08:42, Lionel Sausin <email@example.com> wrote:
Le 10/03/2015 05:51, OpenERP Master a écrit : > Hello, > > Thanks for your input. Unfortunately, this does happen and also > unfortunately other enterprise software supports this easily and it > comes out of box. To give you an example, in Netsuite ERP when you > confirm shipment the sale transforms into whats called an item > fulfillment. Kind of like Odoo's procurements? You can cancel them in Odoo too I think. > (...)There is a legitimate business case for the ability to delete a > delivery order and recreate it. Yes, and most ERPs targetting SMBs have more relaxed data entry rules, BUT the price to pay is that they will produce ie. wrong product cost when you make a mess of the data. That's why the new WMS has pretty strict requirements regarding data entry. You must enter data in the same order as the real events they represent, and as close to real time as is practically possible. You must never delete data, nor fake the data (fake dates, quantities etc.). These restrictions let Odoo make somewhat complex computations (real product cost for example) with a code base that is just simple enough to stand a chance of eventually being correct. So if you make that change, be sure to analyse the whole WMS app line by line.