Ways a Product Transaction date can be changed.

There are several specific issues which can cause a transaction date to change on roll records:

The product importer does not always populate the private supplier field (PRI:PrivLabelCo) - this is a required field and will be populated with a copy of the supplier if blank when edited). Products imported with the importer can be identified by viewing the cost records which will display a source of 'STANDARD IMP' or similar description.

Many costs entered into the system through EC and other importers have a large number of decimal places (e.g., 7.200011 per SY). When accessed, this cost is rounded to 3 decimal places as this is all we use. When saving this record, the cost would be modified to 7.200, which does not match the original cost and the trans date is modified.

On square foot settings, some SY prices are not interchangeable with SF prices (e.g, $5 SY = $.555555555555555... SF) - you cannot multiply this number by 9 and get back to $5 so the 3 decimal result (.556) will be multiplied by 9 yielding $5.004 which will be stored on the pricelist record as the new cost and the trans date will be updated.

Once these changes have occurred, the transdate will not be modified until cost or another field changes again.