When we want to import model data in different local currencies, we need to ensure that our models are saved with currency conversion enabled. In this case, our model has the default currency set to USD, and the maximum number of currency conversions that can be displayed simultaneously in tables based on the model is set to four. In the dimension that contains the model’s currency information, all of the regions also have USD as the local currency, apart from Overseas. Its sub regions, EMEA and Asia Pacific, use the Euro and the Yuan respectively. In a table based on the model, initially, all of the values display in the model’s default currency of USD. To display additional currencies, we first need to add the Cross Calculations dimension to the table. A Cross Calculations column is added, which indicates that all values are converted to the model’s default currency. To add rows that display values in each region’s local currency, we need to modify filter for the Cross Calculations dimension… and add the Currency member. Additional rows are added to display the local currency value for each region. Note that the EMEA and Asia Pacific values display in Euros and Yuan, respectively, as configured in the model. Also note that several of the local currency rows display no values. This is because the members of the hierarchy do not share the same local currency, and no currency conversion is taking place. We see only the amount that was originally imported for each leaf member. We can add rows to display values in other currencies by adding Currency Conversion calculations to the Cross Calculations dimension. In this case, we will add a cross calculation to display values in Euros. First, we’ll enter a name for the currency conversion calculation. Next, we need to specify the currency. Note that the currencies we can choose from are those that are available in the model’s currency conversion table. In the Category area… we can specify a Rate Category from the currency conversion table if desired, or choose Dynamic to automatically use the rate category that’s currently specified for each category in the model. We can also specify a Rate Version if named Rate Versions are available in the conversion table for the currency we have specified. Note that we need to choose Specific in the Category area before we can choose a rate version. In the Date area, we can use the booking date, set a booking date of plus or minus a year quarter or month, or set a fixed date. In this case, we will use the booking date. This means that currency conversion rates will be used based on each record’s transaction date. Rows are added to display the values in Euros. Note that because these rows are based on a currency conversion calculation, there are no empty cells. Values imported in any currency are converted into Euros. We have added several additional currency conversion cross calculations to the table. Note that when the number of currency conversions available exceeds the maximum value we set in the model, which in this case was four… a Select Conversions options displays. We need to remove one of the four currency conversions that is currently selected…. before we can choose an additional currency. Thanks for watching!