Results for “gl_das_rate_types”

10 results




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

Overview

APPS.GL_DAILY_RATES_V is a supplementary view in the Oracle E-Business Suite (EBS) General Ledger schema, documented as VALID at release 12.1.1 / 12.2.2 with FND Design Data reference SQLGL.GL_DAILY_RATES_V. It presents daily currency conversion rate information, combining the stored rate attributes of the GL_DAILY_RATES table with conversion type descriptions from GL_DAILY_CONVERSION_TYPES and with function security checks resolved through FND_GLOBAL and FND_DATA_SECURITY. The view exposes privileged views of rate data by deriving VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE columns, alongside the raw conversion figures.

Oracle explicitly classifies this object as a view type "used to simplify forms coding," with the stated warning that Oracle does not recommend querying or altering data using this view because it "may change dramatically in subsequent minor or major releases." Its principal role is therefore internal to the EBS forms layer (notably the daily rates maintenance form) rather than as a published integration interface. Reporting teams that require stable access to conversion rates should reference GL_DAILY_RATES directly or use the supported GL_DAILY_RATES_API.

Underlying Base Objects

The view is defined over the following documented objects:

  • GL_DAILY_RATES (SYNONYM) — the base table holding currency conversion rates keyed by from-currency, to-currency, conversion date, and conversion type. It supplies CONVERSION_RATE, INVERSE_CONVERSION_RATE, STATUS_CODE, ROW_ID, and the descriptive flexfield columns.
  • GL_DAILY_CONVERSION_TYPES (SYNONYM) — provides the user-defined conversion type name exposed as USER_CONVERSION_TYPE and the internal CONVERSION_TYPE code.
  • FND_GLOBAL (PACKAGE) — supplies the runtime session context (user, responsibility, login) used to evaluate privileges for the current session.
  • FND_DATA_SECURITY (PACKAGE) — resolves function and data security so the view returns only records the current user may view, use, or modify.

Because privilege evaluation depends on session context, results from this view are user- and responsibility-dependent, unlike the base table.

Key Columns

  • FROM_CURRENCY / TO_CURRENCY — the currency pair being converted.
  • CONVERSION_DATE — effective date of the rate.
  • USER_CONVERSION_TYPE / CONVERSION_TYPE — user-facing name and internal code of the conversion type (e.g., Corporate, Spot).
  • CONVERSION_RATE / INVERSE_CONVERSION_RATE — the rate and its reciprocal.
  • SHOW_CONVERSION_RATE / SHOW_INVERSE_CON_RATE — numeric presentation columns used by the maintenance form.
  • ROW_ID / INVERSE_ROW_ID — ROWID values identifying the rate row and its inverse, used by forms for row-level updates.
  • STATUS_CODE — status flag of the rate record.
  • VIEW_PRIVILEGE / USE_PRIVILEGE / MODIFY_PRIVILEGE — function security indicators controlling read, use, and change access.
  • ATTRIBUTE1–15, CONTEXT — descriptive flexfield segments and the context column.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

The view is primarily consumed by the daily rates form to render rates with the correct privilege flags. For diagnostic or investigative SQL, administrators may query it as follows:

  • Retrieve the current effective rate for a currency pair:
    SELECT from_currency, to_currency, conversion_date, user_conversion_type, conversion_rate FROM apps.gl_daily_rates_v WHERE from_currency = 'USD' AND to_currency = 'SAR' AND conversion_date <= SYSDATE ORDER BY conversion_date DESC;
  • Check whether a user session has modify capability before attempting an update through the form.
  • Audit historical rates for a specific conversion type using the CONVERSION_TYPE column.

Given the documented deprecation warning, production reporting and interfaces should be built against GL_DAILY_RATES or the supported API instead of this view, and any ad hoc use should be confined to read-only diagnostics.