FrontAccounting forum — Inventory Valuation Report showing 0 (zero) on Unit Cost

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (b.popoola) — Wed, 19 Oct 2022 15:03:30 +0000

i am getting same error for transferred items for different locations

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (apmuthu) — Sat, 04 Jul 2020 10:03:14 +0000

Although the specific rep301.php has not changed in the meanwhile, some functions it directly / indirectly uses may have been changed post release in other files. No harm in putting in the post release changed files - it does not change the db in any manner and any missing sys_prefs variables entries will get auto populated. Then see if the situation changes.

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (Shenzo) — Sat, 04 Jul 2020 07:55:15 +0000

2.4.8 released in feb 4, 2020. Do i still need to integrate post release fixes released before 2.4.8 release date?

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (Shenzo) — Sat, 04 Jul 2020 07:49:41 +0000

thanks for the response. I just checked server shows the right time. I have two locations, say location A and B, for inventory. both locations have 3 units in stock for that item. when I run report 301 without location filter, it works perfectly, without zeros, and shows 6 units with correct price and correct value (price x 6). but when I apply location filter to location A, it shows zeros for price and value of that item. However applying filter to location B shows right quantity (3), unit price and value for that item. The problems is visible with only location A filter.

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (apmuthu) — Tue, 30 Jun 2020 18:57:03 +0000

Check if this was a server time zone issue at the time when you tried it. This is a very old thread. Hope you have all the post release fixes in your install. Also a latest change was reverted to await v2.5 but is in mt FA24Mods folder (2019-06-24).

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (Shenzo) — Tue, 30 Jun 2020 18:17:41 +0000

This problem still persists in report 301 (inventory valuation report). I am getting zero for unit cost and value for one of the items. When i change to_date from 30/06/2020 to 29/06/2020 the report works fine, no zeros. However report 308 is working perfectly fine with any to_date.
I am using frontaccounting 2.4.8 php 7.2 ubuntu 18.04

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (joe) — Sat, 09 Dec 2017 08:50:21 +0000

Fixed files committed. Even report 308 was having the same issue.

/Joe

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (joe) — Sat, 09 Dec 2017 08:30:17 +0000

Ok, I will.

/Joe

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (apmuthu) — Sat, 09 Dec 2017 06:44:29 +0000

The default value of the precision parameter in php.ini on a 32 bit system is 14 even when absent. In some installs it comes preset at 17. All float values that are a result of a fraction that has recurring decimals ad infinitum will generally truncate off at ini_get('precision')-3 decimals, to make up for a:
1. sign,
2. single integer to the left of the decimal point and
3. the decimal point itself.

Hence the line 356 of includes/current_user.inc:

        if ($len > $dec)

should be:

        if ($len > $dec && $len < ini_get('precision')-3)

@joe: can commit both fixes (decimals and report sql)

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (apmuthu) — Sat, 09 Dec 2017 04:17:17 +0000

The sql in the function getAverageCost() defined in the file reporting/rep301.php (Inventory Valuation Report) is like:

SELECT move.*, IF(ISNULL(supplier.supplier_id), debtor.debtor_no, supplier.supplier_id) person_id
FROM 1_stock_moves move
     LEFT JOIN 1_supp_trans credit ON credit.trans_no=move.trans_no AND credit.type=move.type
     LEFT JOIN 1_grn_batch grn ON grn.id=move.trans_no AND 25=move.type
     LEFT JOIN 1_suppliers supplier ON IFNULL(grn.supplier_id, credit.supplier_id)=supplier.supplier_id
     LEFT JOIN 1_debtor_trans cust_trans ON cust_trans.trans_no=move.trans_no AND cust_trans.type=move.type
     LEFT JOIN 1_debtors_master debtor ON cust_trans.debtor_no=debtor.debtor_no
WHERE stock_id=102
  AND move.tran_date < '2017-11-27' 
  AND standard_cost > 0.001 
  AND qty <> 0 
  AND move.type <> 16 -- ST_LOCTRANSFER
ORDER BY tran_date;

This means that when the purchase invoice is made on 2017-11-27, the sql above computes the average cost to just before the said date and not including it. If a subsequent date is used for the query, then all is well (save for the irrational value at times not obeying the decimal limit).

@joe: must we correct line 65 in it:

            AND move.tran_date < '$to_date' AND standard_cost > 0.001 AND qty <> 0 AND move.type <> ".ST_LOCTRANSFER;

to be

            AND move.tran_date <= '$to_date' AND standard_cost > 0.001 AND qty <> 0 AND move.type <> ".ST_LOCTRANSFER;

so that it takes into consideration all transaction up until the end of the day and not to just before the date?

The decimals issue can be corrected by appropriately formatting the return value at the end of the said function or where it it used in line 211 in the report although line 229 uses it without assignment when $details is present. The culprit is line 357 in includes/current_user.inc for irrational numbers with large number of decimal places ~~when the value of $dec becomes 14. It is best hard coded to 2.~~

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (joe) — Mon, 27 Nov 2017 22:28:29 +0000

I agree that this sounds strange. Maybe someone else can help us investigate this. I have only heard about problems with normal 4 decimals when huge currency rates exists.

/Joe

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (aguspajak) — Mon, 27 Nov 2017 21:29:42 +0000

It makes me confused, I tried using new COA USA, and try the same test using USD as home currency. It works fine with The end date 27-11-2017. Hmmm?

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (aguspajak) — Mon, 27 Nov 2017 21:09:56 +0000

No Joe. It is not the decimals.

Here I found just now.
I created new company and start with empty data.
I inputed Direct Supplier Invoice using date 27-11-2017.
When I access Inventory Valuation Report with end date 27-11-2017 it shows 0 (zero) on Unit Cost.
But when I put End Date 28-11-2017 or 30-11-2017 the Unit Cost shows the value.

Don't you think if I put 27-11-2017 The unit cost allready should have value?

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (joe) — Mon, 27 Nov 2017 20:54:31 +0000

Maybe even more decimals.

Joe

Re: Inventory Valuation Report showing 0 (zero) on Unit Cost

null@example.com (aguspajak) — Mon, 27 Nov 2017 20:43:28 +0000

joe wrote:

Yes it is related to the currency. Try to increase the currency decimals in user preferences, f.i. 6.
Joe

Unfortunately it doesn't help. The problem persist.
Any ideas?