Hello Support:

A client has pointed out an inconsistency in costing. We have configured the PO module to allow 5 decimal places for costs. They rarely need that many but a cost of $0.525 per unit is common. It works very well.

But when they next create a new PO and add that item, the default cost (which comes from "Most Recent Cost") will appear as $0.53. This leads to the occasional error and requires constant vigilance because it's not obvious to the user that figure is a rounded cost.

This happens because the "Most Recent Cost" and related fields use the number of decimal places specified by the currency belonging to the dataset (dollars in most cases).

Request: Can the "Most Recent Cost" field track more decimal places? This would apply to a number of related fields like "Previous Most Recent" cost. This client uses Sundry items in PO but it would apply more importantly to Inventory and also to Order Entry.