645
Ideas? It shows up when I sign the contract then it asks if I want to create the invoice, I say yes, and then this error appears. I click OK and the contact goes back to being unsigned.
*This post is locked for comments
[quote user="Tharanga Chandrasekara"]
This happens because you do not have currency exchange rate define for the given period.
2 ways to do this,
1. Remove currency code from the customer.( If your customer is define as a USD customer in his master card then this problem occurs.)
2. Provide the exchange rate for the given period in the exchange rate table.
Jens has covered all the pros and cons about the solutions.
[/quote]
Also refer: http://msdn.microsoft.com/en-us/library/hh169066(v=nav.71).aspx
About Using Additional Reporting Currencies
How to: Allow for Application of Customer Ledger Entries in Different Currencies
How to: Assign Currency Codes to Vendors
How to: Set Up the Additional Reporting Currency
How to: Define EMU Currencies
How to: Allow for Rounding Differences When You Apply Entries in Different Currencies
How to: Set Up Rounding Rules for Foreign Currency
How to: Update Exchange Rates
This happens because you do not have currency exchange rate define for the given period.
2 ways to do this,
1. Remove currency code from the customer.( If your customer is define as a USD customer in his master card then this problem occurs.)
2. Provide the exchange rate for the given period in the exchange rate table.
Jens has covered all the pros and cons about the solutions.
Hi Rebekah,
do you have customers with currency code USD? Is the customer in the service contract one of these?
If yes, I would recommend that you remove the currency code from the customer. Currency shouldn't be in the contract, if yes, then please remove it there, too. Assuming that your local currency code is USD, this would be the right way to fix it. You could go further and delete the USD code from the currency table entirely. Here's why.
One of the more puzzling effects in NAV is, that you shouldn't create the local currency code in the currency table, likewise not the local country code in the country table. Because strange things happen if you use them... Doesn't make life easier, but it's required to cater for a coding principle left from the "small company" days. In the business logic you have a lot of tests like:
Share
Report
All responses (
Answers (
if "Currency Code" <> '' then
{do currency handling}
This is to handle foreign currencies, meaning all currencies except the local one. If the local currency is set up in the currency table, and used in master data or documents, you get effects like yours. It will handle your local currency (USD) as if it were a foreign currency, for which you need an exchange rate, different amount rounding, and suchlike. That's why you get the error message.
Similar things can happen with country code. Usually there are setup fields in G/L Setup and Company Information to define the local currency.
It would be possible to fix the business logic of NAV or make it support both setups, but it would be tedious and probably error-prone. Definitely a job for Microsoft to do, IMO.
OTOH, if your local currency is not USD, I would recommend to set up a currency exchange rate for USD. :)
with best regards
Jens
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156