Results for “gl_lookups_rate_type_v”

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

Overview

GL_LOOKUPS_RATE_TYPE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered against the General Ledger (GL) product family. The view presents a filtered projection of the GL_LOOKUPS lookup repository, restricted to the lookup type RATE_TYPE. Its documented description designates it as "10SC ONLY," indicating the object is scoped to a specific deployment or localization context rather than being a generally applicable GL component. Consistent with this restricted scope, the view is marked VALID in ETRM 12.2.2 and remains documented for both the 12.1.1 and 12.2.2 releases.

Functionally, the view exposes the rate type lookup set in a simplified, two-column form that maps the internal lookup code to its user-facing meaning. This makes it useful for reporting and integration scenarios where a rate type code stored on a transaction or conversion record must be resolved to a descriptive label without navigating the broader, multi-purpose LOOKUP_TYPE namespace of GL_LOOKUPS.

Underlying Base Objects

The view is defined over a single documented base object: the GL_LOOKUPS view. The defining view text is:

• SELECT L.LOOKUP_CODE RATE_TYPE, L.MEANING SHOW_RATE_TYPE FROM GL_LOOKUPS L WHERE L.LOOKUP_TYPE = 'RATE_TYPE'

Because GL_LOOKUPS is itself implemented as a view rather than a base table, the objects presented by GL_LOOKUPS_RATE_TYPE_V are effectively one layer removed from the physical lookup storage. The defining query applies a fixed predicate on LOOKUP_TYPE, so the row set is determined entirely by the presence and current state of records in GL_LOOKUPS where the lookup type equals 'RATE_TYPE'. Any change to those underlying records — the addition of a new rate type, a change to a meaning string, or a change in enabled/disabled state — is reflected in this view on the next query, with no materialization or snapshot semantics.

Key Columns

The view exposes exactly two columns, both derived from GL_LOOKUPS through column aliasing:

• RATE_TYPE — The alias assigned to GL_LOOKUPS.LOOKUP_CODE. It carries the internal, machine-readable identifier for a rate type, and is the value typically stored on transactions and conversion records that reference a rate type.
• SHOW_RATE_TYPE — The alias assigned to GL_LOOKUPS.MEANING. It carries the descriptive, user-facing label for the same rate type, suitable for display in reports, concurrent program output, and user interfaces.

No additional attributes from GL_LOOKUPS — such as description, enabled flag, or tag columns — are projected by this view, so consumers requiring those attributes must query GL_LOOKUPS directly and apply the equivalent LOOKUP_TYPE filter.

Common Use Cases and Queries

The principal use case is the resolution of rate type codes to their display meanings in reporting and data-extraction queries. Because the view carries the LOOKUP_TYPE filter internally, queries against it are simpler and less error-prone than equivalent joins against GL_LOOKUPS. A typical listing query is:

• SELECT rate_type, show_rate_type FROM apps.gl_lookups_rate_type_v ORDER BY rate_type;

A common integration pattern joins the view to transaction or conversion data to append the descriptive rate type label:

• SELECT t.rate_type, v.show_rate_type FROM some_gl_table t, apps.gl_lookups_rate_type_v v WHERE t.rate_type = v.rate_type;

That pattern is equally valid as a subquery or inline view when the translation is needed for a single column rather than a full join. A validation query confirms that a given code is a defined rate type:

• SELECT COUNT(*) FROM apps.gl_lookups_rate_type_v WHERE rate_type = :p_rate_type;

Because the object is documented as "10SC ONLY," adoption should be preceded by confirming its presence and validity in the target instance, particularly in 12.1.1 environments. Where the view is unavailable, an equivalent result is obtained directly from GL_LOOKUPS with an explicit LOOKUP_TYPE = 'RATE_TYPE' predicate. In all cases the view should be treated as read-only reference data, not as a target for DML.