Regarding undo a fully paid invoice with your example isn't the right way to go. When one receive goods back, the original picking order is used to generate a return shipment. That return shipment will generate a refund invoice. In many countries this is the only way allowed. It does exactly reflect the live situation. Still if you want to undo a fully processed invoice, losing your invoice numbner and generate a gap in your first free number range then first the (sales)journal should be set to allow canceling a invoice. Secondly the reconciliation done for the invoice versus payment should be made undone. Thereafter the invoice can be undone.
Regarding the sales-order with insufficient stock, the sales-order will list a procure method (from stock or on order) and a delivery lead time, your company has inserted. That would be the first available moment that a product can be delivered. If the product is sold physically from stock, there is no physical out out of stock e.g. a shop and only a system out of stock. One would not have a system protection not to sell something you have in house. Your minimum stock value and MRP (eventually also your MPS) should set right to prevent out of stock. With all implementations done into the past with systems that had a parameter to prevent sales with out of stock products, soon or later that parameter is switched to allow negative stock for the sake of workability. Nevertheless it would indeed be nice to have a warning option in that case, perhaps you can register a blueprint for that? ------------------------ Jan www.veritos.nl www.supportandmaintenance.org -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=58055#58055 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
