Map Object Values to Currency Types
- Currency Codes - Defines what currencies should be available in the installation, System administration
- Currency Pairs - Defines what cross currency rates should be possible to define (USD<->EUR)
- Currency Types - Defines different currency types and calculation methods
- Currency Rates - Maintains currency rates for each period
After defining currency types and their calculation methods, you must also 'connect' these calculation methods to one or many object values. In a normal consolidation scenario, you would like to define one currency type (and calculation method) for balance sheet accounts, and one for profit and loss accounts. This information is used by the built in consolidation logic in Datastore. For more information, see Currency Types.
Access Map Object Values to Currency Types by selecting Client administration > Currencies > Map object values to currency types.
To create a new mapping of currency types to an object and associated object values, select the New button.
Edit the settings and select Save.
Below is a list of available fields:
Field | Description | Example | Note |
|---|---|---|---|
Currency Type ID | The currency type to map. | BS Balance Sheet Currency Type | |
Object ID | The dimension/object that should be used as the base for assigning currency types and the currency calculation. | ACCOUNT Chart of account | |
Time unit ID | The time unit (month, quarter, etc) that should be used by the calculation. | ISOMONTH | The build in consolidation functionality in Datastore is based on ISOMONTH, the consolidation is executed on a monthly basis. |
From object value | The first object value (account) in the range for which the currency type should be used. | 1000 | |
To object value | The last object value (account) in the range for which the currency type should be used | 2999 | |
From time value | Defines from what place in time this mapping rule should be applied. | 200001 | |
To time value | Defines to what place in time this mapping rule should be applied. | 202912 |
Additional Information
The ranges for two mappings must be mutual exclusive. For example, if you define two currency types, one for BS accounts and one for P&L accounts, the account range for the BS currency type mapping should not overlap the account range of the P&L currency type mapping.