Increase standard cost decimal places precision to 8 #873
Replies: 4 comments 1 reply
-
|
I'm happy with the change to costs. I may be missing something, but I don't see the case for prices though. However I'm ready to be convinced :) Tim |
Beta Was this translation helpful? Give feedback.
-
|
OK, then. I will take care of the costs first. Regarding prices: I have not thought it in detail, but in the same scenario of financial products (that can be managed in webERP as inventory items with PO and SO), if the cost is to be measured with 8-digit precision, probably the price too. Example: Bought 100 shares of XYZ at average price of 321.12345678 (as most times purchases are not done at once by the trading company; thus the average price could be with a long decimal queue), I agree it can be handled as a second step. R |
Beta Was this translation helpful? Give feedback.
-
|
PurchData.php, line 301 reads:
so, linking purchasing price precision to the Standard Cost decimal places, Then, purchdata column price should also be changed to decimal(24,8). |
Beta Was this translation helpful? Give feedback.
-
|
I'm thinking financial resolution and and calculation precision should be listed in the webERP features list https://weberp.org/Features.html. Units of Measure conversion is another factor when using units other than "each". Going completely off-track, there are probably quite a few "specifications" that might be convenient to find on the Features page (or quasi-product-datasheet) e.g. Stock ID (text 64 char) and Stock Description (text 255 char). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, we can choose any decimal places for standard cost from 0 to 4 in SystemParameters.php
Would it be OK for anybody to increase it to max 8 decimal places?
For physical items (earrings, bolts, flour, etc.) costs it won't change anything and probably is not required, but it does make sense in financial products where the cost price might be something like 321.12345678 USD.
stockmaster, lastcostrollup cost columns should be changed from decimal (20,4) to decimal (24,8) with
Should prices and allocations also be changed accordingly?
R
Beta Was this translation helpful? Give feedback.
All reactions