Microsoft Dynamics AX (Archived)

Why FIFO recalculation repeat many times for same transactions in AX 2012 ?

(0) Share

Report

Posted on by RajeshE

Why FIFO recalculation repeat many times for same transactions in AX 2012 ? Can someone please tell reason for this.

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (1)

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi,

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?

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Rajesh,

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.

Was this reply helpful? Yes No
Vinesh Tandel 590 on at

Like (0)

Report

Hi Andre,

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 ?

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Vinesh,

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.

Best regards,

Ludwig

Was this reply helpful? Yes No
guk1964 10,888 on at

Like (0)

Report

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?

Was this reply helpful? Yes No
André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Vinesh,

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.

Was this reply helpful? Yes No
Vinesh Tandel 590 on at

Like (0)

Report

Hey Andre,

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 ?

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (1)

Report

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,

Ludwig

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

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

and then

1. Value open = NO

2. Value Open = No

3. Value Open = Yes ( as still 9 purchased qty are yet to be knocked off )

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

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

Was this reply helpful? Yes No