Search Results derive_factor




Overview

OE_FND_CURRENCIES_V is a view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Order Management (ONT) product family. As documented in the ETRM metadata for both release 12.1.1 and 12.2.2, the view is defined directly over FND_CURRENCIES and carries a status of VALID. Its stated description is concise: the view "is based on fnd_currencies."

The view presents the complete set of Oracle General Ledger currency definitions to Order Management code and to external reporting consumers, while deliberately masking a small number of source attributes. The most consequential of these is the NAME column, which the view text explicitly hard-codes as a NULL literal. This design means that any consumer relying on OE_FND_CURRENCIES_V must use CURRENCY_CODE as the sole descriptive identifier; the human-readable currency name is not projected through this interface. The remaining columns, including all descriptive, precision, date-ranged, DFF, and derivation attributes, pass through unchanged from the base table.

Because it is a thin, read-only projection, the view serves primarily as a stable integration and reporting contract: it allows Order Management modules and custom extensions to resolve currency attributes without reading FND_CURRENCIES directly, insulating them from changes at the source and enforcing a consistent column list.

Underlying Base Objects

The documented referenced base object is FND_CURRENCIES, accessed through a SYNONYM in the APPS schema. The view text confirms a straightforward single-table SELECT with no joins, no WHERE clause, no aggregation, and no DISTINCT. The only transformation applied is the substitution of NULL for the NAME column; every other attribute is selected verbatim.

All standard FND_CURRENCIES bookkeeping columns are inherited, including LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, together with the CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns and the GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20 global flexfield columns. Because the view is query-only, it cannot be used as a DML target in normal application code paths.

Key Columns

CURRENCY_CODE is the effective primary key for consumers of this view and, since NAME is NULL, the primary display identifier. ENABLED_FLAG and CURRENCY_FLAG control whether a currency may be selected and transacted. PRECISION and EXTENDED_PRECISION govern rounding and extended amounts in Order Management pricing and totals, while MINIMUM_ACCOUNTABLE_UNIT establishes the smallest accountable increment. SYMBOL, DESCRIPTION, and ISO_FLAG supply presentation and standards information; ISSUING_TERRITORY_CODE ties the currency to a territory.

START_DATE_ACTIVE and END_DATE_ACTIVE implement the date-effective window that governs whether a currency is selectable on a given order date. The columns most relevant to the "derive_effective" search term are DERIVE_EFFECTIVE, DERIVE_TYPE, and DERIVE_FACTOR. These control derived currency behaviour, meaning whether a currency is derived from another, and with what factor. Because OE_FND_CURRENCIES_V exposes all three, it is a practical source for queries investigating how effective derived currency logic is configured.

Common Use Cases and Queries

Typical uses include validating that a currency is enabled for a given order date, populating currency-of-record lookups in custom Order Management reports, and auditing derived currency configuration. Sample SQL follows.

  • List active currencies: SELECT currency_code, precision, symbol FROM oe_fnd_currencies_v WHERE enabled_flag = 'Y' AND currency_flag = 'Y';
  • Date-effective validation: SELECT currency_code FROM oe_fnd_currencies_v WHERE currency_code = 'USD' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));
  • Derived currency audit: SELECT currency_code, derive_effective, derive_type, derive_factor FROM oe_fnd_currencies_v WHERE derive_effective = 'Y';
  • Rounding and minimum unit check: SELECT currency_code, precision, extended_precision, minimum_accountable_unit FROM oe_fnd_currencies_v ORDER BY currency_code;

When querying from a non-APPS schema, ensure synonyms and grants are in place or fully qualify as APPS.OE_FND_CURRENCIES_V.