1. Administering Planning
  2. Accessing More Administrative Tasks
  3. Administering Dimensions
  4. Setting Up Currencies
  5. Enabling Multiple Currencies
  6. Working with Currencies in a Standard Multicurrency Application

Working with Currencies in a Standard Multicurrency Application

Note:

This topic assumes the Standard multiple currency option was selected during application creation. If the Simplified multiple currency option was selected, see About Simplified Multicurrency.

If multiple currencies are enabled, users can see values converted from the local currency to a reporting currency and can override a cell’s base currency.

Note:

  • When the local currency is selected on forms, the default stored and displayed currency for cells is the entity’s base currency (which you specify). Users can enter data values only into local currency members. If the local currency member is selected, all currencies specified for the application are available as input types.

  • You can set dimension properties for each currency in the Edit Currency dialog box. In preferences, users can select different display options, and can select Currency Setting to apply the properties set by the Service Administrator.

  • Currencies can be converted only to reporting currencies. Users can't enter data into cells displayed in reporting currencies. The application’s main currency is by default a reporting currency. You can change which currencies are reporting currencies.

  • Currencies defined for the application are valid currencies for data entry. Valid currencies for data entry are displayed in a list that users access by clicking the Currency link during data entry.

  • To get meaningful results, roll up values in one common reporting currency. If members of a subtotal have mixed currencies, the currency type is blank and the currency symbol doesn't display. For example, adding 10 US dollars and 10 Japanese yen to a value of 20 makes no sense.

  • An application with 500 time periods can successfully run currency conversion calculation scripts only if the time periods have default names, TP 1 through 500. Otherwise, the conversion calculation script you try to create exceeds the 64K limit.

  • User-defined currency conversion calculation scripts created when a database is created or refreshed may be available in Oracle Smart View for Office, depending on user access. When using user-defined currency conversion calculation scripts, Oracle recommends changing the order so the currency conversion calculation script is first, before Calculate Form.

  • Currency codes associated with input values are stored as numeric values. These codes are calculated in dimension formulas, calculation scripts, and business rules. The calculated values of these currency codes may translate to currency codes that are incorrect or invalid. Where there are children with mixed currencies, review calculated results on the upper levels.

  • If a parent has multiple children, of whom only one child has an overridden currency, the parent inherits the overridden currency code (which isn't displayed on forms).

  • In certain cases, parent entities display #MISSING when trying to convert to a selected currency. Ensure that a currency rate is entered for each combination of local currencies and selected currencies on forms or reports. Currency combinations must exist for all mixed-currency children entities and parent members.

  • Input of multiple currencies to one entity isn't supported in Smart View. If worksheets include mixed currency types, users could inadvertently enter values in the wrong currency.