Results for “gl_historical_rates_usage_v”

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

Overview

The view APPS.GL_HISTORICAL_RATES_USAGE_V is a lookup-driven metadata view in the Oracle E-Business Suite General Ledger module. Its purpose is to expose the set of valid "historical rates usage" options that are applicable to the currently active ledger. In Oracle EBS 12.1.1 and 12.2.2, historical rate usage determines how General Ledger translates account balances when revaluation or translation processes require an historical rate rather than a period-end or average rate.

Rather than storing transactional data, the view acts as a filtered presentation layer over the General Ledger lookup codes. It combines the lookup repository with the current set of books context so that the rows returned reflect only the usages meaningful to the active ledger. This makes it a convenience object for forms, concurrent programs, and reporting logic that must present or validate the historical rate usage choice against the enabled ledger configuration.

Underlying Base Objects

The view is defined over three referenced base objects: the FND_PROFILE package, the GL_LOOKUPS view, and the GL_SETS_OF_BOOKS view.

• GL_LOOKUPS supplies the lookup codes and their meanings where LOOKUP_TYPE = 'GL_HIST_RATES_USAGE'. This lookup type defines the permissible historical rate usage values in General Ledger.
• GL_SETS_OF_BOOKS supplies ledger configuration, specifically the ENABLE_AVERAGE_BALANCES_FLAG. The view uses this flag to suppress the AVERAGE usage when average balances are not enabled for the ledger.
• FND_PROFILE is referenced through FND_PROFILE.VALUE('GL_SET_OF_BKS_ID'), which returns the set of books identifier for the current session, ensuring the view filters against the ledger in context.

The core filter is the predicate GLU.LOOKUP_CODE <> DECODE(GLSOB.ENABLE_AVERAGE_BALANCES_FLAG, 'N', 'AVERAGE', 'DUMMY'). When average balances are disabled ('N'), the AVERAGE lookup code is excluded; otherwise the comparison targets a dummy value that matches nothing, so all lookups are returned.

Key Columns

The view exposes two columns, both originating from GL_LOOKUPS:

• LOOKUP_CODE — the internal code identifying a historical rate usage option, such as period-end, average, or a specific translated usage value.
• MEANING — the user-facing description of the lookup code, suitable for display in list of values, reports, and validation messages.

These two columns provide the code-value pair typical of Oracle lookup-backed selection lists, allowing downstream logic to store the code while presenting the meaning to users.

Common Use Cases and Queries

The view is most commonly used to populate a list of values for the historical rate usage field, to validate a submitted usage against the active ledger configuration, and to drive translation setup reporting. A representative query follows:

SELECT LOOKUP_CODE, MEANING
FROM   APPS.GL_HISTORICAL_RATES_USAGE_V
ORDER BY MEANING;

Because the result depends on FND_PROFILE.VALUE('GL_SET_OF_BKS_ID'), the calling session must be initialized with a valid ledger context. In multi-org or multi-ledger environments, the same query may return different rows for different ledgers — notably omitting the AVERAGE option where average balances are not enabled. This behavior makes the view a reliable source for ledger-sensitive validation rather than a static lookup list.