You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Raj Saini <ra...@gmail.com> on 2008/05/17 07:38:45 UTC
weightUnitPrice field type of ShipmentCostEstimate entity
Hi,
I have a situation where shipping prices for weight breaks increments £1
per 1000 gm i.e. £ .001 per gram. (gram is UOM for the said product).
Field type for weightUnitPrice is defined as currency-amount and in
PostgreSQL it is mapped as numeric(18, 2). Due to this, shipment cost
estimate entry I create truncates the price to 0 instead of .001.
I believe this is a common scenario for weight breaks where price
increments can be very small for a UOM like gram. I have been thinking
of using the fieldType currency-precision instead of currency-amount.
Currency precision is mapped as numeric(18,3) in PostgreSQL. Is this the
right thing to do or there are better alternatives?
Thanks,
Raj
Re: weightUnitPrice field type of ShipmentCostEstimate entity
Posted by Raj Saini <ra...@gmail.com>.
Hi David,
Thanks for your response.
Only reason is that shipping estimates are in two slabs. 0-2000 have
various blocks (e.g 0-100, 100-250 etc) and each of them have a fixed
rate . second block is from 2001 gm to 10000 gm and shipping price
increments £1 for every 1000 gm.
I tried to set the weight UOM in the shipping estimate to WT_kg.
However, it would calculate shipping estimate very high (like £ 4000+
for 4000 gms.). It looks it is due the fact that the product weight uom
id is gm and it adds £ 1 for each gram.
I can not change weight UOM id of the product to kg as there are other
quantity breaks (e.g 0-100, 100-250 etc) and they need the weight UOM to
be grams.
Thanks,
Raj
David E Jones wrote:
>
> Is there a reason you can't set it up as one pound per kilogram?
>
> -David
>
>
> On May 16, 2008, at 11:38 PM, Raj Saini wrote:
>
>> Hi,
>>
>> I have a situation where shipping prices for weight breaks increments
>> £1 per 1000 gm i.e. £ .001 per gram. (gram is UOM for the said
>> product). Field type for weightUnitPrice is defined as
>> currency-amount and in PostgreSQL it is mapped as numeric(18, 2).
>> Due to this, shipment cost estimate entry I create truncates the
>> price to 0 instead of .001.
>>
>> I believe this is a common scenario for weight breaks where price
>> increments can be very small for a UOM like gram. I have been
>> thinking of using the fieldType currency-precision instead of
>> currency-amount. Currency precision is mapped as numeric(18,3) in
>> PostgreSQL. Is this the right thing to do or there are better
>> alternatives?
>>
>> Thanks,
>>
>> Raj
>>
>>
>>
>>
>
>
Re: weightUnitPrice field type of ShipmentCostEstimate entity
Posted by David E Jones <jo...@hotwaxmedia.com>.
Is there a reason you can't set it up as one pound per kilogram?
-David
On May 16, 2008, at 11:38 PM, Raj Saini wrote:
> Hi,
>
> I have a situation where shipping prices for weight breaks
> increments £1 per 1000 gm i.e. £ .001 per gram. (gram is UOM for the
> said product). Field type for weightUnitPrice is defined as
> currency-amount and in PostgreSQL it is mapped as numeric(18, 2).
> Due to this, shipment cost estimate entry I create truncates the
> price to 0 instead of .001.
>
> I believe this is a common scenario for weight breaks where price
> increments can be very small for a UOM like gram. I have been
> thinking of using the fieldType currency-precision instead of
> currency-amount. Currency precision is mapped as numeric(18,3) in
> PostgreSQL. Is this the right thing to do or there are better
> alternatives?
>
> Thanks,
>
> Raj
>
>
>
>