Dynamics Community Forum Thread Details

Moving average - Backdated transaction

Hi Experts,

I am trying to replicate the case provided in the MS docs regarding the moving average with backdated transaction.

MS Docs example - https://learn.microsoft.com/en-us/dynamics365/supply-chain/cost-management/moving-average#moving-average-with-a-backdated-transaction

Moving average with a backdated transaction

Backdated transactions are assigned the current moving average cost, and the product's physical quantity is updated, but the product's moving average cost isn't affected. In this moving average example, a backdated transaction for a moving average product is posted.

Create an inventory adjustment for the moving average product for a quantity of 1 and a cost of 20.00.
The inventory transaction history for the product would resemble the following:
- An inventory transaction of 1, a cost of 16.00, a posting date of January 15, and a transaction date of January 15.
- An inventory adjustment of 1, a cost of 20.00, a posting date of January 1, and a transaction date of January 15.
Post the adjustment.

On the Inventory transactions page, you can see that 4.00 is expensed as the current moving average for the product is 16.00. You can post in the past, but the difference in cost is expensed, so the moving average cost isn't affected.

Testing -

Item model group setup