The Moving Average correction process due to a transaction date error that exceeds the current date

(0) Share

Report

Posted on by Community Member

Please Help,

How to correct the Moving Average value by mistake when entering a transaction date that exceeds the current date.

example : Create issue transaction in inventory with date 'Dec/24/2018'

This transaction causes the moving average value for its inventory to remain unchanged.

Note : this item using all dimension group 

Regards

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Guy Terry 28,970 Moderator on at

Like (0)

Report
Copy link

Link copied!

I don't understand. Issue transaction do not cause the moving average value to change, no matter when they are posted. Can you share a scenario, and what you expect to happen?

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello Sudiarta,

Did you enter a transaction by mistake on 24 Dec 2018 with a wrong price/quantity or what happened exactly?

Can you share some additional details/screenprints?

Best regards,

Ludwig

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Actually I have made a transaction date mistake. Refer to the MA whitepaper, This error will result in the moving average value of the transaction (specifically this item) being made will not change until the date of December 24, 2018 (AX will read the transaction as backdate).

Regards

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Anybody help?

Was this reply helpful? Yes No