From user-return-53054-archive-asf-public=cust-asf.ponee.io@ofbiz.apache.org Thu Jan 4 02:46:42 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 1848F18077A for ; Thu, 4 Jan 2018 02:46:42 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 08004160C39; Thu, 4 Jan 2018 01:46:42 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 25AFF160C1B for ; Thu, 4 Jan 2018 02:46:40 +0100 (CET) Received: (qmail 83965 invoked by uid 500); 4 Jan 2018 01:46:39 -0000 Mailing-List: contact user-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ofbiz.apache.org Delivered-To: mailing list user@ofbiz.apache.org Received: (qmail 83953 invoked by uid 99); 4 Jan 2018 01:46:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2018 01:46:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1E8DCC22AD for ; Thu, 4 Jan 2018 01:46:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.88 X-Spam-Level: * X-Spam-Status: No, score=1.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, KAM_SHORT=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=cohsoft.com.au Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id PXb4u3A8Ix0J for ; Thu, 4 Jan 2018 01:46:37 +0000 (UTC) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 183065F3B5 for ; Thu, 4 Jan 2018 01:46:36 +0000 (UTC) Received: by mail-lf0-f44.google.com with SMTP id y71so205938lfd.12 for ; Wed, 03 Jan 2018 17:46:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cohsoft.com.au; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=LckkEZsm0HVJ/wPlhsB1MHCZqcwnSj9t1zy+x2Qs8wA=; b=bBRP8rHXZzfFsbB88rWePiKltZ6xuFqpZ8QDOiodVVnKz5BwCVRCakF/2FEh7BlWcq OgF2sP+9k4edKJlYVpJIwQUPtuBEBkLtsObx1cv305u8OfI0o2jxrVc/i0o3yiMdJzrS MOvppb4/CCaJzhjTBdyVAhglbSk2xujCxOoEE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=LckkEZsm0HVJ/wPlhsB1MHCZqcwnSj9t1zy+x2Qs8wA=; b=Dy6X0c1ec/+b8R7N1Ht6hjeM4YH1V0FSJ63dBMpzlk1XqeM5HiphHPDuvpNygBEe8v c7C0KP1IwpoIeG9EuZniyc2K1/g17Ju9sBWu9jmoaDXxoFWkw9tU6WBzxv/hsOXxj/A7 Ira0EZ3hxh2gxfyGOCJK7tqdgJHNumvh8qbZ9O8YLUM0yf67XvkLf2uWYCuMUuaB3/xr eq09mmGwkAgHenZVKiC4aW0n34ctJAr4aI5WF0W7OgKz1BJxtp6bOJUn4Kai5W12H5MJ i0yEkMi6QFP+GFJlAwTwNoTP4tlX0JLukSGLetmCZBzrGdsy2Twfes0WRvcKPFs1nZH5 rgbg== X-Gm-Message-State: AKGB3mJVOm59nthg0pC0HupkA7Tj9oBuJhW7tK55T2prhrH28h1GXYEf nUNTiV7cP62mfUYvqVYfS+lAST8RA90FIpKVDIYX754KY1g= X-Google-Smtp-Source: ACJfBougouESMTbSfQFcxIcfYAbXr8BpIXGs434W3LZhC60y+TDnmRf3JY+TqZuSBzzKSYbM6wEeR+dCc8o8L6cwogY= X-Received: by 10.46.99.211 with SMTP id s80mr1913915lje.7.1515030395153; Wed, 03 Jan 2018 17:46:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.207.5 with HTTP; Wed, 3 Jan 2018 17:46:34 -0800 (PST) In-Reply-To: References: From: Paul Foxworthy Date: Thu, 4 Jan 2018 12:46:34 +1100 Message-ID: Subject: Re: Add Product Supplier broken - similar to Edit Facility bug To: user@ofbiz.apache.org Content-Type: multipart/alternative; boundary="94eb2c1ab5008707060561e980b6" --94eb2c1ab5008707060561e980b6 Content-Type: text/plain; charset="UTF-8" Hi again, I've changed my mind about a Jira for the moment. I think this is not exactly the same thing as OFBIZ-6436. We could create a new issue in future, but I'd like to consider this some more. I see the general point that there's a need for more decimal places in prices. OFBiz has configuration options for decimal places in orders, invoices, indirect taxes, financial accounts and general ledger reports. (All of these are in https://github.com/apache/ofbiz/blob/trunk/applications/ accounting/config/arithmetic.properties ). Here are questions I'd like Tim and everyone to consider: - Is a rule for product price DPs a separate thing to rules for other amounts specified in arithmetic.properties? I think the answer is "yes". - Should OFBiz just accept a price to whatever level of precision a user wants to enter it, and not round it? - Product pricing and the number of DPs might vary significantly for different products. Is there any need to enforce some sort of consistency here? - If enforcement is needed, is a single configuration option for product pricing sufficient? - If enforcement is needed, should it be more fine-grained than one rule for all products? Should the number of DPs be an attribute of some entity, perhaps ProductCategory or SupplierProduct? Cheers Paul Foxworthy On 4 January 2018 at 11:57, Paul Foxworthy wrote: > Thanks, that makes sense. > > Maybe further discussion should move to https://issues.apache.org/ > jira/browse/OFBIZ-6436 . I will put a comment there with your link to the > NCES standard. > > Cheers > > Paul Foxworthy > > P.S. I buy my gasxxx petrol in litres and one place suffices :-). > > > On 3 January 2018 at 23:20, Boyden, Timothy > wrote: > >> Same reason your gas prices are quoted to 3 digits at the pump. Those >> extra cents amount to millions of dollars after millions of gallons or >> hundreds of thousands of component sales. It is also necessary in order to >> capture actual cost of products when using only a few of the components in >> a part, or like I said, grams of a precious metal coating on electrical >> connectors. Measurements to convert from grams to a purchase UM of ounces >> will almost always be a 5 digit decimal value. And you can bet those >> precious metal vendors count their hundreds and thousandths of ounces. >> Also, for the purposes of statistical analysis, which is used to analyze >> production quality, the US national standard is (at least) 4 decimal >> places: https://nces.ed.gov/statprog/2002/std5_3.asp >> >> -Tim >> >> >> -----Original Message----- >> From: Paul Foxworthy [mailto:paul@cohsoft.com.au] >> Sent: Tuesday, January 2, 2018 7:43 PM >> To: user@ofbiz.apache.org >> Subject: Re: Add Product Supplier broken - similar to Edit Facility bug >> >> Hi Tim, >> >> Thanks for your feedback. >> >> I am curious what you would use the unit price for. Do you order your >> washers in quantities of thousands, and might the price vary if you ordered >> in quantities like 10,000 or 100,000? So acquisition price might depend on >> quantity ordered. If you are calculating cost price for a manufactured >> product, the prices for washers might be imprecise but that's unlikely to >> be most significant contributor to the cost price. What am I missing? >> >> Thanks >> >> Paul Foxworthy >> >> >> On 24 December 2017 at 22:42, Boyden, Timothy >> wrote: >> >> > The issue that I had was that the underlying field would not accept a >> > value of 0.00590. I had to enter the value as a lot of 10000, to get >> > the price to 59.00, before it would accept the value. If I read the >> > first link correctly, that is referring to display format, and not >> > validation of the field input, or the size of fields. Looking at the >> > table spec, indeed the LAST_PRICE field of SUPPLIER_PRODUCT is only a >> > decimal field with 3 decimal place precision. It should be at least 5. >> > All price fields should be at least 5 decimal place precision. >> > >> > -Tim >> > >> > -----Original Message----- >> > From: Paul Foxworthy [mailto:paul@cohsoft.com.au] >> > Sent: Saturday, December 23, 2017 7:36 PM >> > To: user@ofbiz.apache.org >> > Subject: Re: Add Product Supplier broken - similar to Edit Facility >> > bug >> > >> > Hi Tim, >> > >> > Decimal places are configurable for many things in OFBiz - see >> > https://github.com/apache/ofbiz/blob/trunk/applications/ >> > accounting/config/arithmetic.properties#L24 >> > and below. >> > >> > I can see product pricing should be configurable too. In >> > https://issues.apache.org/jira/browse/OFBIZ-6436, Ingo Wolfmayer was >> > proposing adding a similar thing for prices. >> > >> > Cheers >> > >> > Paul Foxworthy >> > >> > >> > On 24 December 2017 at 08:02, Boyden, Timothy >> > >> > wrote: >> > >> > > Also, it looks like the Last Purchase Price field doesn't accept 5 >> > > digit decimal places. Major bad for a manufacturing system. A steel >> > > washer, priced per each, would be like $0.00590 USD. Similarly, >> > > precious metals, like silver for silver plating, would be ordered in >> > 5-digit decimal ounces. >> > > That needs to get fixed. >> > > >> > > Thanks, >> > > >> > > Tim >> > > >> > >> > >> > >> > -- >> > Coherent Software Australia Pty Ltd >> > PO Box 2773 >> > Cheltenham Vic 3192 >> > Australia >> > >> > Phone: +61 3 9585 6788 >> > Web: http://www.coherentsoftware.com.au/ >> > Email: info@coherentsoftware.com.au >> > >> >> >> >> -- >> Coherent Software Australia Pty Ltd >> PO Box 2773 >> Cheltenham Vic 3192 >> Australia >> >> Phone: +61 3 9585 6788 >> Web: http://www.coherentsoftware.com.au/ >> Email: info@coherentsoftware.com.au >> > > > > -- > Coherent Software Australia Pty Ltd > PO Box 2773 > Cheltenham Vic 3192 > Australia > > Phone: +61 3 9585 6788 <+61%203%209585%206788> > Web: http://www.coherentsoftware.com.au/ > Email: info@coherentsoftware.com.au > -- Coherent Software Australia Pty Ltd PO Box 2773 Cheltenham Vic 3192 Australia Phone: +61 3 9585 6788 Web: http://www.coherentsoftware.com.au/ Email: info@coherentsoftware.com.au --94eb2c1ab5008707060561e980b6--