CurrencyTable Object

Discussion

Use this object to set up currency records and rates.

To create a CurrencyTable object, use the Add method of the CurrencyTables collection. If you use a data source to populate a currency table, CurrencyRecord objects are automatically added to the model, as are the currency rates associated with each record.

Alternatively, you can manually add currency records to a currency table. In this case, CurrencyRate objects are automatically generated for each new CurrencyRecord object, but you must manually maintain the rates.

CurrencyRate, CurrencyRecord, CurrencyTable, and DateDimension objects are all needed for currency conversion to work.

For conversions involving non-European Monetary Union (EMU) currencies or conversions involving EMU currencies before 1999, only one table is needed, with the CurrencyTableType property set to trCurrencyTableBase. The base table initially shows the default currency, such as US dollars. This is based on the regional setting of your operating system. The setting can be changed to any other currency, including the euro.

For conversions that involve EMU currencies after 1998, you need two tables. Set the CurrencyTableType property of one table to trCurrencyTableBase and set the same property in the second table to trCurrencyTableEuro. The euro table contains the fixed conversion rates used to convert values to, or from, the national currencies of EMU countries or regions by using the euro and base currencies as intermediate values in the conversion. This process is called euro triangulation. For euro triangulation to work, sort the date levels in ascending order and set the Unique property of each date level to True. Give the date field a zero value (0) for the records of EMU members that follow January 1st, 1999.

The required multiplication, division, and rounding operations are all performed in PowerPlay®.

You can use several data sources to supply the currency data for your base table. However, all column names must match so that the information combines properly. The same requirement applies to the euro table, although you must assign different names to the columns associated with the euro table.

When you use a data source to populate a table, set the GeneratePowerCube property to trGenerationNoCreatePowerCubes and the GenerateCategories property to False. By doing so, any updates to the CurrencyTable object do not interfere with category generation in the rest of your model. You can leave these properties enabled if the names of the date columns in your base and euro currency data sources differ from the column name of your time dimension, and from each other. Otherwise, Transformer cannot differentiate between them.

To save changes to the properties of this object, use the Update method.

Related Topics

These tables list related collections, methods, and properties.

Examples

objBaseTable = objModel.CurrencyTables.Add()