If you trade with different countries you might want to look at how you setup prices by currency in the trade agreements. This example shows how to setup set the price by a different current and the effect if you don’t have it setup when you enter a sales order as an example in a different currency.
In this example I just took the default exchange rate conversion of the price. In reality this is likely not valid because you might want to adjust for operation differences and would depend how you handle fright and other charges.
This video was recorded with AX2012 R3 but the same concepts apply to any AX2012 release.
Hi, I think the way that AX R3 use to convert a currency to another is really bad, usually any ERP and POS, takes the sale agreement in any currency, and automaticly converts the amount to the sale currency using the up to date rate of exchange, and thats all!. In AX for example in the POS, if your sale currency is MXN and the sale agreement is in USD, the product is not converted, you have to make a SQL statement to convert it! awful!
Understand the process you are outlining. As it relates to trade agreements in AX the price is a listed prices in that currency and AX just uses the currency to find if you have listed a price. The conversion isn’t done because most times if you are listing the product in another currency you might apply other factors beyond the simple exchange rate conversion. So the normal practice would be if you allow a currency to be used to sell a product then you should a record in the trade agreements to reflect each of those currency.