Here's an even weirder one: average cost item that was backordered (qtyshipped = 0, unitcost = 0) has an extended cost of .65 (which is not its average cost - that is .42) in the item transaction record, and that amount posted to GL.
I often wonder how much of this kind of thing goes on and 99% of customers never reconcile anything to notice it...
It also shows up how often Sage 100 data structures break the "one version of the truth" concept...
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------
Original Message:
Sent: 08-21-2019 16:50
From: Phil McIntosh
Subject: Extended cost doesn't match
The item is average cost and there are still more in stock...
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------
Original Message:
Sent: 08-21-2019 16:32
From: Kevin Moyes
Subject: Extended cost doesn't match
Valuation has a cost tier? If you are consuming the final quantity of a tier, Sage should now add the total extended value in... (recent bug fix to avoid tier value without quantity).
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
Original Message:
Sent: 08-21-2019 16:09
From: Phil McIntosh
Subject: Extended cost doesn't match
In SQL Manager it is 23.610000
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
Original Message:
Sent: 08-21-2019 15:47
From: Brett Zimmerman
Subject: Extended cost doesn't match
Take a look at the file(s) via DFDM. Maybe you'll find that 23.610000 is actually stored differently (e.g. 23.61333) and is the cause of the round-up.
------------------------------
- Brett