The currency table describes the available currencies and specifies accounts, decimal places and other information about a currency. The exchange rates are stored in a separate exchange rate table, which enables the storage of historic exchange rates.

Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

This field contains the ISO currency code of the currency being set up. The currency code may be selected from the related code table for 'currency codes' by a combobox.

This combobox is used to select another currency.

This field contains an internally used alternate code of the currency. The alternate code can be freely defined.

The number of decimal places for a particular currency is defined here, and is used for all representational purposes in the system. Examples: USD: 2 decimal places JPY: 0 decimal places Any currency with a number of decimal places not equal 2 has to be listed in the TradeDesign internal parameters.

The sequence defines the row (number) where this currency appears in the exchange rate maintenance table when daily exchange rates are entered.

A value of '0' means that this currency will not appear in the table.

'3' means that the currency will appear in the third row of the table.

'-1' means that this currency has a fixed exchange rate against the system's currency. This is used for IN-currencies in the EUR region. Of course, this currency will not appear in the exchange rate maintenance table.

This account, maintained in the respective currency, is used as a transit account for currency conversions.

Example: In a transaction involving revenue in USD (debit USD) and expenditure in a local (system) currency (credit EUR), a straight debit in USD followed by a straight credit in EUR would lead to a difference between the total credits and debits. The transit account in the respective currency (USD) is used to balance the entries in the respective currency to prevent such a diference, i.e. debitting the current account in USD and crediting the transit account in USD. There is an appropriate transit account in the system currency for the system currency side.

This account, maintained in the system currency, is used as a transit account for currency conversions.

Example: In a transaction involving revenue in (debit USD) and expenditure in a local (system) currency (credit EUR), a straight debit in USD followed by a straight credit in EUR would lead to a difference between the total credits and debits. The transit account in the system currency is used to balance the entries in system currency to prevent such a difference, i.e. debitting the transit account in SYSISO, crediting the client account in SYSISO. There is an appropriate transit account for the respective currency (USD) also exist.

This field is used to set the margin from the middle rate to calculate the buying and selling rates of the currency.

This field is used to define the margin from the middle rate to calculate the squaring rate of the currency.

This field is used to define the base rate of the currency. It is used to check the rate entered against this rate plus/minus the maximum tolerance.

This field contains the maximum allowed (plus or minus) tolerance from the last valid middle rate when importing or entering daily exchange rates. Should an exchange rate entered exceed this tolerance limit, an error message is issued and the rate is not updated to the database.

This field defines the parity of this currency against the system's currency, i.e. 1 EUR x rate ⇒ USD amount but 1000 JPY x rate ⇒ USD amount, so for EUR the calculation base is 1, for JPY 1000.

The field defines the rounding unit of currency (e.g.: 0.01, 0.05, 0.10, 1) used in conversions into the currency.

Rounding is optional and, depending on the nature of the transaction and other factors, might be switched on or off.

This field is used to define the date from which a currency becomes valid. The date entered is included.

This field is used to define the date from which a currency is no longer valid. The date entered is not included in the period of validity.

Interest Days in OD-Rate (Overday)

This field is used to default the number of days to be added to the current date to calculate the value date in a debit transaction involving this currency.

This field is used to default the number of days to be added to the current date to calculate the value date in a credit transaction involving this currency.

The currency of the maximum amount has to be available in the system currency.

This field defines the maximum threshold values for the use of currency rates stored in the database. The amount is expressed in the system currency.

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.

Defines the sequence of currencies in the selection list. To prevent currencies without an explicit priority specified from being listed at the beginning of the list of currencies, the priority 0 is changed to 999.

This field holds the external key of the owning entity group to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity group are visible to the user.

Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.

Defines the time (in hours) at which the funding should run for this currency.

Defines the time (in minutes) at which the funding should run for this currency.

Defines the cut off time (in hours) after which the following day will be used for value date calculation.

Defines the cut off time (in minutes) after which the following day will be used for value date calculation.