Search Results oe_gl_daily_conversion_types_v




Overview
Explore in AI Chat

Overview

The OE_GL_DAILY_CONVERSION_TYPES_V view is a validation view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ONT - Order Management product family. Its documented purpose is to validate the conversion type code used within Order Management processing. In Oracle EBS, currency conversion types (such as Spot, Corporate, User-defined, or the EMU fixed-rate types) are defined in General Ledger and consumed by subledger applications whenever foreign currency amounts must be converted into the functional currency. Rather than querying the General Ledger base table directly, Order Management and its dependent validation logic reference this view, which presents a controlled projection of the GL conversion type definitions.

Because the object is a view rather than a table, it holds no data of its own and introduces no redundant storage. Its role is to expose a consistent, secured interface for validation and reporting. The view is marked VALID in the ETRM 12.2.2 metadata, confirming that it compiles successfully against its underlying synonyms at that release level, and the same definition is delivered in 12.1.1.

Underlying Base Objects

The view is defined over a single referenced base object: GL_DAILY_CONVERSION_TYPES, accessed through a synonym in the APPS schema. The view text performs a direct, unfiltered projection of that table:

  • Every row in GL_DAILY_CONVERSION_TYPES is exposed; no WHERE clause filters the result set.
  • The column list is passed through one-to-one, including all fifteen descriptive flexfield attribute columns and the CONTEXT column.
  • No joins, aggregations, or computed expressions are present, so the view is a straightforward SELECT projection.

Consequently, any row inserted, updated, or disabled in the GL base table is immediately visible through the view, and there is no materialization or caching to reconcile. Access is governed by grants on the view rather than direct privileges on the underlying GL table.

Key Columns

  • CONVERSION_TYPE — the internal, system-level code that uniquely identifies the conversion type; this is the key against which Order Management validates user-entered or interface-supplied values.
  • USER_CONVERSION_TYPE — the user-facing name of the conversion type displayed in LOVs and reports.
  • DESCRIPTION — the descriptive text maintained on the GL conversion type definition.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns, useful for change tracking and data lineage analysis.
  • ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segment columns carried from GL, available for any context-sensitive information configured on the source record.
  • CONTEXT — the descriptive flexfield context value that determines which attribute segments are meaningful.

Common Use Cases and Queries

The primary practical use is validating that a conversion type supplied by an order, an interface table, or a conversion-rate reference exists and is active before currency conversion is attempted. A second common use is building LOV-driven selection lists in custom concurrent programs or reports, and a third is audit or reconciliation reporting that compares conversion types referenced by Order Management data against their GL definitions.

Typical queries include a simple lookup by code:

  • SELECT conversion_type, user_conversion_type, description FROM oe_gl_daily_conversion_types_v WHERE conversion_type = :p_conversion_type;
  • SELECT conversion_type, user_conversion_type FROM oe_gl_daily_conversion_types_v ORDER BY user_conversion_type;
  • SELECT conversion_type, last_update_date, last_updated_by FROM oe_gl_daily_conversion_types_v WHERE last_update_date >= :p_since_date;

Because the view is a direct projection of GL, results always reflect the current GL configuration; disabling a conversion type in GL immediately removes it from valid selections through this view. On upgrade from 12.1.1 to 12.2.2 the definition remains unchanged, and the view stays VALID.