IRC logs of #tryton for Wednesday, 2023-10-04

irc.libera.chat #tryton log beginning Wed Oct 4 12:10:01 AM CEST 2023
-!- tbruyere(~Thunderbi@mail.saluc.com) has joined #tryton06:18
-!- mrichez(~Maxime@mail.saluc.com) has joined #tryton06:31
-!- htgoebel(~htgoebel@p200300d5df316000d5b6b70db63ea593.dip0.t-ipconnect.de) has joined #tryton07:01
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton07:02
-!- ChanServ changed mode/#tryton -> +o cedk 07:02
-!- acaubet(~Thunderbi@194.224.31.235) has joined #tryton07:38
-!- acaubet1(~Thunderbi@2a02:9130:fd00:bade:7c94:aaff:f0df:1df1) has joined #tryton08:03
-!- udono(~udo@183-153-117-131.ip-addr.inexio.net) has joined #tryton08:06
-!- acaubet(~Thunderbi@2a02:9130:fd00:bade:7c94:aaff:f0df:1df1) has joined #tryton08:10
-!- acaubet(~Thunderbi@194.224.31.235) has joined #tryton08:43
-!- acaubet(~Thunderbi@194.224.31.235) has joined #tryton08:54
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton09:54
-!- ChanServ changed mode/#tryton -> +o cedk 09:54
mrichezhi, what could prevent to create a return shipment from a customer shipment (wizard to get data from selected shipment and create return shipment) to keep a track of shipment and return shipment on the same sale ? 12:39
pokolimrichez: nothing? 12:40
mrichezpokoli: :-) ? it seems strange to create a return sale (and it's difficult to understand what happens to a sale where there's a problem with a shipment) so why not a return shipment on the original sale12:43
pokolimrichez: normally the full sale is refunded to force the creation of a credit note, if you do not need a credit note you can just return directly the shipment12:44
pokolimrichez: Having a wizard to just return the shipment by creating a return shipment with the proper origins makes sense for me12:45
pokoliIf you set the proper origins then the sale workflow will recreate another customer shipment once the return is received12:45
mrichezpokoli: ok... and also if invoice is not posted, will be invoice updated with the return shipment quantities ?12:46
pokolimrichez: if you have the sale_invoice_grouping module yes, otherwise an invoice will be created for each shipment12:47
mrichezpokoli:  ok.... i will think about it :-) we are using lots number and sale returns model needs to communicate lot number to select the same lot for the return shipment so we try to make something easier for the user..12:49
pokolimrichez: but you must not set the lot number on creation but let the user input it when receiving the goods12:54
mrichezpokoli: ok. we did the test with a customer return (we set sale_line as origin for the inventory move) and we notice that actual quantity on sale_line is the double instead of 0... bug ? (return move should be subtracted?)13:06
cedkmrichez: you are not supposed to link a return move with a sale line13:08
cedkalso such move will be added to the quantity shipped13:09
mrichezcedk: why? it allows to understand what happens to the sale... we ship some products, customer returns some for problem... 13:09
mrichezcedk: could we distinct customer move and return move with a negative quantity ?13:10
cedkmrichez: origin is supposed to be filled by the system, it creates links for the system13:10
cedkthe system never creates a return move for a sale line with quantity > 013:11
mrichezcedk: ok... maybe we could add some features on sale: (https://discuss.tryton.org/t/help-with-sale-procedure-and-sale-return/6563) indentify a sale return among the sales (in the treeview) , adding a one2many (like for amendments) to link sale returns13:13
pokolicedk: if you link both moves (out and return) to the same sale line it will just generate the missing quantity to fill the quantity requested by the customer 13:25
cedkpokoli: no13:31
pokolicedk: why not?13:32
cedkpokoli: because the code does what it does, not what you think it does13:41
pokolicedk: but what is the rational to sum a retun move when when it is not really shipped?13:41
pokolicedk: yes, you are right about what the code does, but I can not understand why13:43
cedkit is not possible to distinct all the moves13:47
pokolicedk: the form and  to location is what distincs if its an customer out, or a return move, or any other move13:49
cedkpokoli: you can not deal with all the cases13:50
pokolicedk: there are just three cases: Sum, Substract and ignore13:50
cedkpokoli: you can not ignore13:50
pokolicedk: ok, then what we do with a production move related to a sale? 13:51
cedkthat's the point13:51
pokoliI do not understand why you said that it can not be ignored? 13:52
cedkpokoli: because user make the link13:53
pokoliso?13:53
pokolicedk: event it can be the case that a third party module is creating the link on purpose13:54
pokolianother point, is that if we want to prevent such mistakes we should consider making the origin readonly so the user will never update it, but that won't fix the case of third party modules14:01
mrichezforget about use of origin: i'm using user admin for my tests... users don't have access to origin field... so this is a bad idea to use it... (or using it with a wizard)14:14
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton19:40
-!- ChanServ changed mode/#tryton -> +o cedk 19:40

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!