A Diumenge 21 Juliol 2013 14:38:15, Cédric Krier va escriure: > On 21/07/13 01:38 +0200, Albert Cervera i Areny wrote: > > A Divendres 27 Gener 2012 11:12:50, Cédric Krier va escriure: > > > On 27/01/12 10:49 +0100, Albert Cervera i Areny wrote: > > > > A Divendres, 27 de gener de 2012 10:12:17, Cédric Krier va escriure: > > > > > > I agree it gives a bad UX. At the same time, I must admit that > > > > > > when working with serial numbers, splitting the lines can also > > > > > > be cumbersome. We've got a customer that can create a production > > > > > > of more than a thousand units and that creates shippments with a > > > > > > large number of lines. > > > > > > > > > > You will still have thousand of lot lines. So still the same issue. > > > > > > > > Sure, but it's not exactly the same. Let's say you have to ship, 500 > > > > hundred units of each products A, B and C. All of them use serial > > > > numbers. With a lot per stock move you have a shipping with 1.500 > > > > lines and so there is no way you know you're actually shipping 500 > > > > units of A, 500 of B, and 500 of C. At most you're informed that > > > > there are 1.500 lines in the shippment. > > > > > > > > > > > > > > > > With sharoon's approach you've got three lines which clearly describe > > > > what you're sending. > > > > > > You can make a view that group moves by product. > > > > We need to address this issue for a couple of customers who regularly > > work with a lot of serial numbers. Did you have something in mind? > > See above. > > > The main problem > > I see with trying to make a view that groups moves is that would be > > needed in stock moves, production, and all shipment types. Not to say > > that any inheritance in stock.move views is lost or must be re-adapted > > to the new view. > > Yes but it is just a displaying.
Displaying only is easier but then the user has to switch between the place where she changes stuff, and the place where that information is summarized. Possibly in two different tabs of the shipment. It is the UX that I don't like. > > I'm thinking that maybe serial numbers should be managed with another > > kind of relationship instead of reusing stock.lot. > > I think it is a wrong decision. > > > By the way, it seems the problem has been there in other systems too [1] > > :) > > > > [1] > > http://www.navisioninfo.com/whitepapers/Navision%20Item%20Tracking%20Tech > > nical%20White%20Paper.htm > > Yes and their "Sales Shipment Line" is just the grouped moves I talked. Yes, but users can "operate" with those lines. It seems that they use "Item Ledger Entry" (stock.move) for registration only, but it is not the object with which the user works on the shipment. If the user has to change information in the "grouped" view he can do it and it has a one2many relationship with the Ledger Entry. -- Albert Cervera i Areny Consultor funcional Tel. 93 553 18 03 @albertnan www.NaN-tic.com Avís legal >>
