http://www.magentocommerce.com/bug-tracking/ en MagentoCommerce Copyright {gmt_date format="%Y"} {gmt_date format="%Y-%m-%dT%H:%i:%s%Q"} http://www.magentocommerce.com/bug-tracking/issue?issue=3668 Posted: 2008-10-14 06:41:02
Category: Configuration
Version: 1.1.6
Priority: high
Status: closed
Reported By: joolsr

Hi

This is related to previous bug 4848.

I am in the UK, and Magento has my CurrencyCode set to GBP. But now app/code/core/Mage/Usa/Model/Shipping/Carrier/Fedex.php uses the Magento CurrencyCode from its own entry previously set in the database. This is good, but with GBP set to the Magento Currency Code, no rates are returned, just an error. Hardwiring line 289 so that I use USD instead fixes the issue.

$declaredValue->addChild('CurrencyCode', 'USD');
// $declaredValue->addChild('CurrencyCode', Mage::app()->getBaseCurrencyCode());

Of course this is not ideal, as the rates we are using are in US Dollars not UK Sterling. I believe the fault is really that FedEx do not accept certain countries' CurrencyCode, see bug 4848, but there should be some check for this in Magento, rather than having to do in the code. CAN and EUR work for Canadian Dollars and Euros, but surprisingly not UK Sterling, ie GBP.

Confusingly, if you change hardwired CurrencyCodes as above, the rates are NOT changed by the usual exchange rate levels, but by only a few %, ie setting to AUS, gives a rate of £58.14 for a package to France, USA £62.01, EUR £63.95 for same package and destination. So I think the differences may be down to exchange rate fluctuations.

If you want any more info, please contact me my PM.

---

]]> #1 / Comment by joolsr

After checking the codecreturned from Fedex, it seems they use UKL as the GBP Country Code !!! This is an ancient terminology used about 30 yeras ago, as far as we can remember.

Using UKL in the CurrencyCode now works and gives back pricing.]]> #2 / Comment by Magento Team

All currency codes correspondence was done.]]> #3 / Comment by Magento Team

Hello joolsr,

This issue was fixed. The changes will be available in the next bugfix release.

Thank you.]]>