Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
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 TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
While doing Foreign currency revaluation in Ap module im getting the below error.
Account number for transaction type exchange rate gain does not exist
Posting has been cancelled.
I have setup exchange rate gain and loss account under GL/posting/accounts for automatic transcations
under gl/currency/currency revaluation accounts.
But still am getting the same error.
Can you check your your currency setup and verify whether or not ledger accounts have been setup for the different currencies used? Probably one of those is missing the gain account.
Has the currency revaluation actually worked before or is it the first time your experience this error?
Currency setup has been setup for different currencies used and currency revaluation worked earlier.
Can you check whether all revaluation accounts are setup for the different currencies that you use.
It seems that for one of those currencies an account is missing.
Which exact version of AX 2012 are you using? There is a hotfix available on LCS for AX 2012 RTM and R2.
As moderator I have removed the word "Urgent" from the title. It has no use on a forum.
Currently we are using R2 version.
Earlier reporting and accounting currency was same and later I changed from Zar to Usd.
Once after changing this setup, will I get this error?
I'm not sure as I haven't done such change in the past, but it could indeed cause your error. Did you change the accounting or the reporting currency? How did you change this?
Possibly the hotfix mentioned above could be helpful.
Hi, could you solve the problem?
Interested in knowing if this ever got resolved, we're facing the same issue.
Please be informed that i am also getting same error and i have setup
1 GL >> Posting >> accounts for automatic transactions
2. GL >> setup >>Ledger >> realized gain/loss and unrealized loss/gain accounts
Here i need to know whether we need to select realized gain/loss and unrealized loss/gain accounts for related currencies also or not
since we have selected same accounts at ledger as specified above point # 2 so i think we no need to specify accounts for each currency
We would request you all please check and clarify above clarification
suppose it is a bug please let us know the hotfix for the same and do the needful.
You responded to a 2 year old thread.
Can you please create a new one and provide information about the system version you operate?
Also, please attach some supporting screenprints that illustrate the issue in more detail.
Many thanks and best regards,
Dear Mr, Ludwig
Thank you so much for your quick reply
As your email please find the source information of the erro
We would request you to check and do the needful on this
I can confirm we solved this by installing hotfix 2912586, we're running AX 2012 R2
Are you operating AX2012 R2 as Alexander mentioned?
Does the hotix apply?
Were you able to apply 2912586 on it's own? Or did you have to apply a larger, cumulative hotfix? If the latter, do you have an archived version of that hotfix? I am looking to find that hotfix to fix this very issue.
Business Applications communities