Thanks for your suggestion. I debugged the x++ code and discovered that the rounding is applied when activating the pending prices. If the source price is calculated then the price precision remains, otherwise its rounded to 2dp. This is done in the InventItemPriceSim table method "moveSimulatedToCurrent()"
My options are to review the need for rounding to be applied to prices of type 'Cost' and amend the code accordingly
------------------------------
Paul Fildes
AX Technical Support Consultant
Steelite International Ltd
Stoke-On-Trent
------------------------------
Original Message:
Sent: Mar 03, 2023 02:43 AM
From: Steven Eland
Subject: Activating a Static Cost Price in Costing Versions
More of a workaround than a solution but could you use the per series option to effectively increase the dp?
Would ideally be on both sites.
Original Message:
Sent: 3/2/2023 11:33:00 AM
From: Paul Fildes
Subject: Activating a Static Cost Price in Costing Versions
Hi all,
In our AX 2012 R3 CU10 environment I have a costing version in one site with calculated costs. These are calculated with a precision of 6 decimal places. With introducing a new site and warehouse, I'm copying the costs from my original costing version to a new one in the new site. I'm finding that the values are being copied exactly as pending prices, so no precision is lost, however when these pending prices are activated the value is being rounded to 2 decimal places.
This has become apparent when transferring stock between the warehouses and sites. Its creating GL variances which we've attributed to the difference between the activated costs.
Can anybody offer any advise as to what I could be doing wrong?
#AX2012
------------------------------
Paul Fildes
AX Technical Support Consultant
Steelite International Ltd
Stoke-On-Trent
------------------------------