End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Why FIFO recalculation repeat many times for same transactions in AX 2012 ? Can someone please tell reason for this.
It depends on your related and matched outgoing transactions, I.e. the issue transactions that the inventory close or recalculation finds.
Have you used the trace feature to see the related issue transactions?
Inventory transactions will be recalculated until you perform a closing (e.g. once a month). Then it will get a closed flag and will not be considered anymore for new recalculations.
So i understand from your post that AX re calculates and repeats until the closing is performed.
Can u explain the reason why does AX do it that way, meaning why does it repeats transaction during recalculation
is it because any adjustment should be allowed ?
Until transactions are 'closed' by the inventory close changes are allowed and are possible.
That is the reason why.
I would not recommend making an adjustment to this process.
It is complex and involves a lot of areas in AX.
You might do more harm than good.
As the adjustments are all on the same date , I assume you ran recalculation only once- or are these vouchers the result of running it many times? The adjustments are all + and = 0.01 so it seems to be be an unusual rounding iteration. What settinfs do you have for Maximum throughputs and Minimum adjustment?
Transactions wouldn't be neccessarily posted in the correct order. Sometimes a purchase invoice will be posted after a late approval. Then it might be the case that a certain recalculation was not valid anymore and there will be a new outcome.
If that issue of multiple lines generation is due to closing not done, then why not the same does not repeat on other items but only on item given in screen shot ?
Good Morning Vinesh,
Can you please check the inventory transaction via the 'trace' button to see how and why those transactions where posted/adjusted and what their origin is.
Many thanks and best regards,
Let's understand first how system works ::
I have used the date format as : MM/DD/YYYY and all the amount in USD. Assuming Item001.
1. Date = 04/01/2019 :: Purchase :: Qty = 10 :: Unit Price = $10 :: total = $100 :: Value Open = Yes
Moving Average = $ ( 100 / 10 ) = $ 10.
cost amt posted = 10 * 10 = $100
2. Date = 04/02/2019 :: Purchase :: Qty = 10 :: Unit Price = $15 :: total = $150 :: Value Open = Yes
Moving Average = $( 150 + 100 ) /20 = $12.5
Cost Amount showing against transaction = 10*12.5 = $ 125
3. Date = 04/02/2019 :: Sales :: Qty = -5 :: Unit Price = $12.5 ( based on moving average as of last transactions ) :: total = $ -62.5 :: Value Open = Yes
Moving Average = $( 150 + 100 -62.5 ) /15 = $12.5
Cost Amount showing against transaction = -5*12.5 = - $62.5
4. Date = 04/10/2019 :: Sales :: Qty = -8 :: Unit Price = $12.5 ( based on moving average as of last transactions ) :: total = $ -100 :: Value Open = Yes
Moving Average = $( 150 + 100 -62.5 -100 ) /7 = $12.5
Cost Amount showing against transaction = -8*12.5 = - $100.00
5. Date = 04/12/2019 :: Purchase :: Qty = 20 :: Unit Price = $25 :: total = $500 :: Value Open = Yes
Moving Average = $( 150 + 100 -62.5 -100 + 500 ) /27 = $21.76
Cost Amount showing against transaction = 20*21.76 = $435.2
6. Date = 04/12/2019 :: Sales :: Qty = -18 :: Unit Price = $21.76 ( based on moving average as of last transactions ) :: total = $ -391.68 :: Value Open = Yes
Moving Average = $( 150 + 100 -62.5 -100 +500 -391.68 ) /9 = $21.76
Cost Amount showing against transaction = -18*21.76 = - $391.68
When u run the recalculation ::: All the issue transactions will be proposed with a new line with proper adjustment to meet the required inventory method per item which is attached in the item model group per item like FIFO , LIFO or Weighted average etc .
based on FIFO -- the first item which will be issued will be at the cost of first purchase price of the item ...
lets see them :
3. Qty = -5 should be issued at the price of $10. so total = -$50.
so adjustment to this line = + $12.5
to make -62.5 usd back to 50 USD. ( Recalculation is proposing thsi line )
1.Value open = YES
2.Value open = YES
5.Value open = YES
4. Qty = -8 should be issued as below : first -5 qty at $10 and next -3 qty at $15.
so total = (-5*10) + ( -3*15) = - $95
so adjustment should be : + $5
to make -100 usd to -95 usd . ( the same recalculation run is proposing another adjustment in separate line with the same item but different issue transaction )
1. Value Open =NO , which is proposed by recalculation . this will change to No after running the inventory close but proposed by inventory recalculation .As this receipt is knocked off in the issue transaction of 3 and 4 .
2. Value Open = Yes.
== after no 6.
6. Qty = -18 should be issued as below :
first -7 qty at $15 = - $105
second -11 qty at $25 = - $275
total = -( $105 + $275) = - $380
initial posted = - $391.68
adjustment required = + $11.68
1. Value open = NO
2. Value Open = No
3. Value Open = Yes ( as still 9 purchased qty are yet to be knocked off )
No issue with the item .. the same item can have multiple issues and while closing r inventory recalculation :: the system proposes the adjustment for all issue related transactions if there is any difference for applied inventory methods like fifo here ..
these issue transactions can be on same date or multiple dates .. the duty of the system is to knock all issues against the purchase and knocking off with the correct amount
Verified Solution :
The item used for the sales was reserved from a transfer order directly but somehow the marking was not properly set.
So system was not able to realize the actual cost of the item when it was received and whenever there is a recalculation run, it picked up the 0.01 cent and posted to adjustment account.
After we set the marking and we run the recalculation, and system is not posting anymore adjustment for the order.
Thanks for your feedback.
Business Applications communities