Logistics mailing list archives
logistics@odoo-community.org
Browse archives
Re: negative quants and returns
by@Joel
Just remember that Odoo creates negative quants itself when delivering serialised on output items.
* Don't force picking but make inventory if stocjk quantity are wrong* Unreserve something to deliver another customerThanks for update. We're going in the direction to provide a module that forbid the user to create negative quants. Only a specific group of user would have the right to do so. This way, it'll enforce people to correct the proper way before delivreing something.The proper way would be:On Mon, Dec 14, 2015 at 12:37 PM, <Pedro@pad.odoo-community.org> wrote:Joel, current module will finish with a quant of quantity 0, but that can be modelled other way.2015-12-10 12:08 GMT+01:00 Jonathan Wilson <jon@willowit.com.au>:@Joel: re following the quant trail - great idea but could get complicated I guess, eg if the quant that contained the non-serialsed item had several items included in it (which is very likely since it was non-serialsed when receipting) then it would have to be split and the split quant would have to have a retro-created history based on its parent. Maybe that why Odoo never attempted it? But the current situation is very messy with negative quants being created endlessly.Maybe an automated move to the Inventory Loss location from the existing non-serialsed quant and and move of the serialised quant back to the stock location (or wherever it came from)? Maybe not the inventory loss location as that could potentially cause an financial journal to be created, but some other virtual location? After this the new serialised quant and the negative serialised quant could be merged? (possibly too complicated and obscure?)Jonathan Wilsonph: +61 3 8506 0393mob: +61 4 000 17 4442013 & 2015 Odoo Best Partner Asia/PacificCreators of Odoo-Pentaho integration projectOn 10 December 2015 at 18:23, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:@Jonathan: I think Quants with different serial (event if on has and the other not) should not be merge in a "generic" case. May be for yours it make sense.Another way here is may be to follow the move_history_ids link to define wether we can merge a quant with and without serial. In that case, it makes sens for me that the resulting quants have a serial.On Thu, Dec 10, 2015 at 1:37 AM, Jonathan Wilson <jon@willowit.com.au> wrote:We have a similar issue for "serialise on delivery" items - the system leaves the original quant (un-serialised) in place and generates a new negative quant for the moved serialised item. There was a bug that was causing the QoH to just take into account the +ve quants which was causing mayhem resulting in rubbish QoH figures. We fixed that but now need a way to get then system "clean" again and have been wondering about the best way to do that. The "stock_quant_merge" nearly does it, however in our case, the original quant has no serial number. Maybe the module could be extended so that if the one of the merged quants was without a serial it could pick up the serial number from the other serialised quant. Not quite sure if this would break something though - thoughts?Jonathan Wilsonph: +61 3 8506 0393mob: +61 4 000 17 4442013 & 2015 Odoo Best Partner Asia/PacificCreators of Odoo-Pentaho integration projectOn 10 December 2015 at 08:22, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:JoëlWe can imagine a simple tools suggesting quants reconciliation that someone approves on a periodical basis. What do you think ?I mean, it makes sense, like dedupplicating partners or bank reconciliation. Those are similar uses cases made manually, with some automation magic.Hi there,I thought about this one. What about building an OCA addon to reconcile stock.quants in a same location ?My2cents,--On Wed, Dec 9, 2015 at 2:08 PM, Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:Hello all, I'm facing an issue on a customer's database. For various reasons (including, but exclusively, errors in custom addons), some availabilities of outgoing moves have been forced, resulting in negative quants. I need to repair the situation for my customer. My first attempt was to return the pickings, to have the quant reconciliation code do the work, but in case the quant that originally created the negative quant is being returned, the stock module explicitly refuses to reconcile them (see https://github.com/odoo/odoo/pull/9907). The official answer is that it breaks the traceability of quants, and that stock inventories should be used for this. I'm not fond of inventories there, because I don't think that the resulting traceability is clearer (quite the contrary in fact), but I'm concerned pushing 9907 could break other parts of Odoo (Joss mentionned mrp). Before moving further, I'd like to gather opinions from people here. Here are the options I could think of, feel free to add your suggestions: * stick to inventories to fix this * create an addon module to allow returns to reconcile the broken quants (possibly asking the user to explicitly say he wants to do so) * merge #9907 in OCB * ??? Thanks for your feedback. -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe
camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDivision ManagerBusiness Solutions_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe
--
camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDivision ManagerBusiness Solutions_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe
--
camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDivision ManagerBusiness Solutions_______________________________________________
Mailing-List: http://odoo-community.org/groups/logistics-21
Post to: mailto:logistics@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe