Inventory Transactions Interface FBDI Incoming Transaction Cost truncated at 2 decimal places?

Summary:

We're noticing that when importing Miscellaneous Receipt transactions via the 'InventoryTransactionImportTemplate.xlsm' FBDI file with the Use Current Cost set to 'No' on the 'INV_TRANSACTIONS_INTERFACE' tab that the values we on the 'CST_I_INCOMING_TXN_COSTS' are truncated at 2 decimal places in the resulting CSV file generated by the zipping process. In this scenario we're importing quantities and thus costs to a FIFO cost profile and there are several items where the cost is 3 or more decimal places out. The truncation in the CSV file has thus casued the transaction cost to come in at 0. Is this expected