Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Nicole Rockey]

We recently updated the currency decimals on inventory items so they were set to five (most items were already set to five decimals, but some were set to two prior to this change). The update was done through SQL. When the change was completed, we started seeing issues with some item costs showing as rounded costs (rounded to the nearest 10). I can see (in a smartlist) that the original cost is still in the system, it seems to just be displaying as a rounded cost. Has anyone seen this before or does anyone have a recommended fix?

Any guidance is appreciated. Thanks in advance!

——————————
Nicole Rockey

——————————

[Wassim Rahme]

Hi Nicole,

It is not advisable to change the inventory decimals in SQL.  Better use the ‘Change Decimal Places’ window (Inventory>>Utilities).

Now that you’ve done it, try to run the process ‘Reconcile Inventory Quantities’ (again under Utilities) and see if that corrects the issue.

Regards

——————————
Wassim Rahme
Consulting Manager
Computel
Westmount QC
——————————
——————————————-

[Nicole Rockey]

Thank you! I will try that. The utility would not work for us as we have thousands of items on open POs and open sales orders, so we had to use SQL instead.

——————————
Nicole Rockey
Precision Planting
Tremont IL
——————————
——————————————-

[Blair Christensen]

You are correct in that the utility requires that there be no open PO’s referencing the item and that is for good reason: the calculations on inventory depend on the item card definitions.  Changing them with SQL just bypasses a safeguard built into the system so that the calculations remain correct and consistent.

We have to use this utility often because of some idiosyncracies with one of our business relationships.  We find that in general in GP, there is usually a good reason to use the provided utilities as they maintain consistency in the system.  Manipulations via SQL should be a last-ditch effort and only conducted after a thorough investigation with a Partner/Microsoft to determine fallout and testing in a test environment.  The other thing that I would strongly advise is to get backups before doing back-end manipulation through SQL.  I’ve never been sorry to take that backup.

——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise ID
——————————
——————————————-