Results for “currency_conversion_type_code”

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

Overview

GLBV_GL_CONVERSION_TYPES is a read-only view owned by the APPS schema within the Oracle General Ledger (GL) module of Oracle E-Business Suite. It exposes the set of daily currency conversion types that are defined and enabled in the ledger application, providing a stable, presentation-oriented interface over the underlying GL_DAILY_CONVERSION_TYPES table. Conversion types in Oracle General Ledger represent the named rate relationships used when translating amounts between currencies — examples include Spot, Corporate, User-defined, and other rate categories maintained by the treasury or accounting function. By surfacing these definitions through a dedicated view, EBS provides a controlled access point for reporting, integration, and inquiry against conversion type metadata without requiring direct reads from the base transaction table. The object is documented as VALID in the ETRM repository and forms part of the standard APPS schema object inventory for release 12.2.2, with equivalent behavior in 12.1.1.

Underlying Base Objects

The view is defined over a single base table, GL_DAILY_CONVERSION_TYPES, referenced through the alias GL_CONVERSION_TYPE. The defining query selects three columns from that table and applies the WITH READ ONLY clause, which explicitly prevents DML operations through the view and reinforces its role as a query-only reporting artifact. The ETRM metadata lists no other referenced base objects, confirming that GLBV_GL_CONVERSION_TYPES is a straightforward projection rather than a join or aggregation view. Because it maps almost directly onto its parent table, any row visible in GL_DAILY_CONVERSION_TYPES appears in the view, subject only to the column list defined in the view text.

Key Columns

The view exposes the following columns. Note that the ETRM "Columns" listing records CURRENCY_CONVERSION_TYPE_CODE, CURRENCY_CONVERSION_TYPE, and DESCRIPTION, while the documented view text selects CONVERSION_TYPE, USER_CONVERSION_TYPE, and DESCRIPTION; these refer to the same conceptual attributes of a conversion type.

• CONVERSION_TYPE / CURRENCY_CONVERSION_TYPE_CODE — the internal code identifying the conversion type, used as the key value stored on transactions and rate definitions.
• USER_CONVERSION_TYPE / CURRENCY_CONVERSION_TYPE — the user-facing name of the conversion type as displayed in forms and reports.
• DESCRIPTION — the descriptive text explaining the purpose or usage of the conversion type.

Common Use Cases and Queries

Typical uses include validating conversion type codes during data conversion, driving LOV-style listings in custom concurrent programs, and joining conversion type attributes onto daily rates for reporting. The following examples illustrate standard patterns.

• List all defined conversion types: SELECT conversion_type, user_conversion_type, description FROM glbv_gl_conversion_types ORDER BY user_conversion_type;
• Resolve a code to its display name: SELECT user_conversion_type FROM glbv_gl_conversion_types WHERE conversion_type = :p_code;
• Join to daily rates: SELECT r.conversion_date, r.from_currency, r.to_currency, c.user_conversion_type, r.conversion_rate FROM gl_daily_rates r, glbv_gl_conversion_types c WHERE r.conversion_type = c.conversion_type AND r.conversion_date = :p_date;

Because the view is read-only, it should be used strictly for query and integration purposes; maintenance of conversion types must be performed against the base table through the standard General Ledger setup forms.