> El 10/05/17 a les 15:48, Ralf Peschke ha escrit: >> Hi, >> >> is there a technical reason for this constraint or only the functional >> one (a bom should have one part only one times listed)? > I don't think so.
Very good! Then we should remove the constraint from the module, when there is no technical reason for it!? > >> For our customer we need to remove this constraint, but are not sure if >> there are any side affects removing it. > Can you explain what your use case? Then we can give a better advice. > Our customer gets bom's from his customers and sometimes they are using the same product more than one times on same hierarchy level. Our customer wants to keep the "original" boms. It is only unique together with the position number and sometimes more a construction recipe than a simple bom. Problem is that it is not possible to remove the original constraint without patching the module itself. The _register_ method of the production module is executed before the remove in the setup of the extending module is executed. > > What's the objective of having the same input/output product on the same > production multiple times? Defining only one time the same product > easies the pick process. > > Sure, but we cannot convince all customers of our customer;-) -- Peschke IT-Beratung Ralf Peschke Hüffener Heide 3 D-32257 Bünde Tel: 0049 (0)5223 - 97 89 079 Mobil: 0049 (0)175 - 32 72 561 E-Mail: [email protected] Homepage: www.peschke-it.de -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/113dbde2-3dec-a9a7-8dbd-e1ec9296a803%40peschke-it.de.
