Define and Run a Map that Copies the Exchange Rates from HACPM_ExchangeRates to Your Model

The map defines the rules for connecting your model to the exchange rates model, HACPM_ExchangeRates.

You must include at least one row in the map for each of the dimensions in HACPM_ExchangeRates and rows for any additional dimensions in your model.

HACPM_ExchangeRates uses 4 dimensions:

• CurrencyType: contains the types of currency rates, such as AVG (average monthly), EOM (end of month), or HistAvg (historical average).

• Currency: contains the names of all the currencies, such as USD, CAD, EUR, and AUD.

• Scenario: contains the full list of possible scenarios used in Planful applications.

• Time: contains multiple years, quarters, and months.

The Target Model is your model.

The Type of map must be set to Data.

The Source Model is HACPM_ExchangeRates.

The Transfer option is Leaf.

There is no option to write back data from your model.

Under Source Dimension, list the four dimensions in HACPM_ExchangeRates and decide where to use them:

• The scenario must map to an equivalent Scenario dimension in your model.

• Time must map to an equivalent Time dimension in your model.

• Currency can be mapped to a dimension (if you plan to use multiple currencies), or to a member (if you plan to take one exchange rate at a time), or can be filtered out (if you want only one currency).

• CurrencyType can be mapped to a dimension (if you plan to use multiple currency types), or to a member (if you plan to take one currency type at a time), or can be filtered out (if you want only one currency type).

The examples below show ways to design the map.

• Example Map with Variables and Currency Dimension

• Example Map for a Model that Uses Multiple Currencies

• Example Map with Currency Mapped to One Member

• Example Map with Currency Filtered Out

You then run the map by creating a calculation that executes the map. See Define and Run a Calculation that Runs the Map and Executes the Currency Formula.

Example Map with Variables and Currency Dimension

This example shows how to use variables for Scenario and Time, plus multiple currencies in your model.

The following map uses a target model with 5 dimensions:

• Scenario: contains Actual and Budget members for 2016.

• Time: includes years, quarters, and months for 2016, 2017, and 2018.

• Account: includes revenue and expense accounts.

• Reporting: includes common currency, local currency, and exchange rate members.

• Currency: includes a list of currencies to be used, copied from HACPM_ExchangeRates.

Scenario and Time are variables that can be set before running the calculation.

Currency in HACPM_ExchangeRates is mapped to Currency in the target model, and one currency is mapped. You could add rows for multiple currencies.

CurrencyType in HACPM_ExchangeRates is filtered to not appear in the target model. The AVG member from the source model is the one that will be copied into the intersection of all the other dimensions listed in the map.

With Scenario set to 2016 Budget and Time set to 2016, after loading this data, it appears in the model as follows:

Example Map for a Model that Uses Multiple Currencies

If you plan to use multiple currencies in your model, the best practice is to create a Currency dimension and include all the currencies you plan to use. If you use the same member names as are in HACPM_ExchangeRates, the map is easier to create.

The following map uses a target model with 7 dimensions:

• Scenario: contains Actual, Budget, and Forecast members for 2016 and 2017.

• Time: includes years and quarters only, not months.

• Currencies: includes the same list of currencies as are in HACPM_ExchangeRates.

• Dim1 - Dim4: miscellaneous dimensions for your reporting needs.

Scenario and Time are mapped one-to-one.

Currency in HACPM_ExchangeRates is mapped to Currencies in the target model.

CurrencyType in HACPM_ExchangeRates is filtered to not appear in the target model. The AVG member from the source model is the one that will be copied into the intersection of all the other dimensions listed in the map.

After loading this data, it appears in the model as follows. In this case, you can see that USD is the local currency because it has an exchange rate of 1.

Example Map with Currency Mapped to One Member

If you plan to use a small number of currencies in your model, you do not have to create a Currency dimension in your model. For example, if you are newly expanding to only one international market, you only need to have one member to store the new local currency.

The following map uses a target model with 6 dimensions:

• Scenario: contains Actual, Budget, and Forecast members for 2016 and 2017.

• Time: includes years and quarters only, not months.

• Dim1 - Dim4: miscellaneous dimensions for your reporting needs.

Scenario and Time are mapped one-to-one.

A particular Currency in HACPM_ExchangeRates is mapped to one member in the target model.

CurrencyType in HACPM_ExchangeRates is filtered to not appear in the target model. The AVG member from the source model is the one that will be copied into the intersection of all the other dimensions listed in the map.

After loading this data, it appears in the model as follows:

Example Map with Currency Filtered Out

If you plan to use only one other currency in your model, you can filter out the Currency dimension entirely.
The following map uses a target model with 6 dimensions:

• Scenario: contains Actual, Budget, and Forecast members for 2016 and 2017.

• Time: includes years and quarters only, not months.

• Dim1 - Dim4: miscellaneous dimensions for your reporting needs.

Scenario and Time are mapped one-to-one.

A particular Currency in HACPM_ExchangeRates is filtered to not appear in the target model. The EUR member from the source model is the one that will be copied into the intersection of all the other dimensions listed in the map.

CurrencyType in HACPM_ExchangeRates is filtered to not appear in the target model. The AVG member from the source model is the one that will be copied into the intersection of all the other dimensions listed in the map.

After loading this data, it appears in the model as follows: