← Back to team overview

openerp-wms-expert team mailing list archive

Fwd: unify product and uos

 

This is not a framework topic, rather a warehouse management or sale topic:
please let me forward your answer to the WMS experts.
Lionel.

Le 08/05/2012 18:42, Olivier Dony a écrit :
On 05/08/2012 03:13 PM, Nicolas Bessi wrote:
Hello,

Shouldn't  we transform the product sale coefficient (uos_coef) and make it a
related fields of the ratio of the related uos ?
They have separate conversion rates because they do not have the same purpose:
the UoS (and various uos_*) fields are meant to specify a secondary unit of
measure that is *not* in the same category as the main product UoM.
Historically we even had a constraint checking this, but I see that it was
removed in the past without sufficient review and without properly
understanding the design and consequences [1].

A typical case where you might want to use this is agro-food retailers:
the "Blue Cheese" product has a default UoM of "Piece" because that's what the
Warehouse guys care about, but the customer expects to see how many slices or
grams of cheese he bought. And the conversion rate between Cheeses and Grams or
Slices is often variable!
Obviously this requires an extra (optional) conversion rate.

This UoS quantity is really supposed to be an extra value on the order line,
meant for the customer. If you use it with a UoM that is from the same category
as the main UoM you are duplicating the UoM values on the order line for no
good reason.
If the latter is really what you needed, an alternative mechanism to select the
preferred UoM for a certain product should be found (e.g. via the defaults
mechanism), without duplicating the values and field on the order line.

This certainly deserves fixing and polishing at the moment, but not in the
direction you're suggesting, I think.


It will be more coherent and will unifiy sale order object that use some time
the UOS  ration and some time the coeff leading to side effect and difficultiy
to update product.
I can understand the confusion because the constraint was erroneously removed,
and the purpose of the UoS field was never made very clear from the start, but
there is a good reason why the rates are separate, as explained above.


[1] Bug https://bugs.launchpad.net/openobject-addons/+bug/543979

_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help   : https://help.launchpad.net/ListHelp