Results for “currency_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_ENTERED_CURRENCIES_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite General Ledger (GL). It is registered as a VALID object in both 12.1.1 and 12.2.2. The view presents a consolidated, filtered list of currency codes drawn from the currencies and lookups that are relevant to entered-currency processing in General Ledger. Rather than returning every code held in FND_CURRENCIES, the view classifies each row with a currency type indicator and restricts the result set to those codes that GL treats as valid for entry.

The central purpose of the view is to expose the CURRENCY_TYPE attribute, which is the column most frequently cited in searches relating to this object. The view is used wherever GL or dependent modules must differentiate between a standard entered currency ('E'), the Statistical currency ('STAT', type 'S'), and the literal placeholder 'N/A' (type 'T') drawn from GL lookups. Because it is a view rather than a base table, it carries no data of its own and requires no maintenance; it is a read-only projection over its source objects.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects: FND_CURRENCIES (referenced through a SYNONYM) and GL_LOOKUPS (itself a VIEW). Both are owned or accessed within the APPS schema.

• FND_CURRENCIES — the Oracle Application Object Library currency definition table. It supplies the set of enabled currency codes and is the source for the 'E' and 'S' rows of the view.
• GL_LOOKUPS — the General Ledger lookup view. It supplies the 'N/A' literal code, restricted to LOOKUP_TYPE = 'LITERAL'.

The view text composes three branches joined with UNION: standard currencies (type 'E') where the code is not 'STAT'; the single statistical currency (type 'S') where the code equals 'STAT'; and the literal lookup code 'N/A' (type 'T') from GL_LOOKUPS. This UNION structure guarantees a single, non-duplicated row per code with an unambiguous type classification, which simplifies downstream filters and reporting.

Key Columns

• CURRENCY_TYPE — a single-character classification applied to each currency row. 'E' denotes a standard entered currency, 'S' denotes the Statistical currency, and 'T' denotes the literal 'N/A' placeholder. This column is the primary selection discriminator used by callers.
• CURRENCY_CODE — the currency or literal identifier itself. For types 'E' and 'S' this is a value from FND_CURRENCIES; for type 'T' it is the LOOKUP_CODE 'N/A' sourced from GL_LOOKUPS. Note that the view aliases LOOKUP_CODE to CURRENCY_CODE in the third branch so that both branches share a common column name.

Common Use Cases and Queries

Typical applications include currency-of-entry selection lists, validation of an entered currency before posting, and reporting that must separate the Statistical currency from ordinary currencies. Because the view already carries the classification, queries avoid complex inline logic.

• Listing only standard entered currencies:
  SELECT CURRENCY_CODE FROM GL_ENTERED_CURRENCIES_V WHERE CURRENCY_TYPE = 'E' ORDER BY CURRENCY_CODE;
• Isolating the statistical currency:
  SELECT CURRENCY_CODE FROM GL_ENTERED_CURRENCIES_V WHERE CURRENCY_TYPE = 'S';
• Retrieving the literal placeholder used for non-currency entry:
  SELECT CURRENCY_CODE FROM GL_ENTERED_CURRENCIES_V WHERE CURRENCY_TYPE = 'T';
• Grouping counts by type to audit the available entry set:
  SELECT CURRENCY_TYPE, COUNT(*) FROM GL_ENTERED_CURRENCIES_V GROUP BY CURRENCY_TYPE;

All queries are read-only and incur no locking. When integrating with external systems, the CURRENCY_TYPE value should be preserved so that the Statistical and literal cases are not mistaken for ordinary currencies.