AX2661

Conversion table requirements

This section details the requirements for conversion tables. Conversion tables hold the rates for data conversions on data tables. Before setting up conversions for a data table, you must first manually create the associated conversion table.

Table structure

Conversion tables must be data tables, and they must contain the columns detailed in the following table.

NOTE: The key columns can be named anything you like. The example names below are used in the documentation to discuss the conversion table and its columns.

Column	Key Column?	Data Type	Description
From	Yes	String	Contains identification codes for the "from" or starting point for the conversion. For example, you may want to convert United States dollars to Canadian dollars. In this case, the starting value is United States dollars, and the "from" code may be USD.
To	Yes	String	Contains identification codes for the "to" or ending point for the conversion. For example, you may want to convert United States dollars to Canadian dollars. In this case, the ending value is Canadian dollars, and the "to" code may be CAD.
Type	Yes	String	Contains identification codes for different conversion types. Each conversion type can use a different rate. For example, you may maintain two sets of conversion rates for currency conversions. One rate is the average of all the conversion rates for a particular month, whereas another rate uses the conversion rate as of the end of the month. Therefore you would have two conversion types, AVG and EOM.
Scenario	Yes	String	Contains identification codes for different conversion scenarios. Each scenario can have a different rate. For example, if you want to apply conversion rates to forecasted data, you may have several different scenarios with different rates, such as Baseline, BestCase, and WorstCase. You could also choose to store scenarios in different conversion tables rather than use different scenario codes within the same table. However, the column must still exist in each conversion table.
<Rate Columns>	No	Numeric or Integer	These columns contain the rates for the conversions, on a per period basis. The table should have one column for each period of data that you want to convert. For example, if you will be converting 12 months of data, you would have one rate column for each month. These columns should be named something like M1-M12 or P1-P12, and must be assigned to a sequence. See the following section on the conversion sequence for more information.

The conversion table must contain all four key columns, even if you do not need to use all four keys. For example, you may not need multiple rates or multiple scenarios. In this case you must still create the column, but you would place the same code in all rows. In the example screenshot, only one scenario applies, so the same code ("Actual") is used in all rows.

Conversion sequence

The rate columns in the conversion table must be assigned to a sequence. This sequence must correspond to a sequence of the same length within the data table where you want to enable conversions.

For example, imagine that you have a data table GL2019, with 12 columns of data (M1-M12) that belong to a sequence named Months. In order to configure conversions for this table, you must create a conversion table with 12 rate columns (M1-M12), and assign those columns to a sequence (say, MonthlyConversionRates).

When you configure the conversion, you associate the Months sequence in the data table to the MonthlyConversionRates sequence in the conversion table. Column M1 of the Months sequence would be converted using the rates in M1 of the MonthlyConversionRates sequence.

Rates

You can populate the rates in the rate columns manually using Open Table in Spreadsheet, or you can set up an import. For example, you might have a monthly import that brings in the actual currency conversion rates for the prior month.

The rates in the conversion table are entirely user-defined; Axiom Software does not provide any pre-populated rates for activities such as currency conversions. If you want to use different types of conversions such as AVG and EOM, your organization must obtain or calculate these rates and enter them into the conversion table.