Search Results rg_factor_v

Overview

RG_FACTOR_V is a view owned by the APPS schema within the Oracle E-Business Suite, belonging to the RG (Application Report Generator) product. The RG module provides the historical report-writing and data-definition framework that underpins various Oracle applications, and objects within this schema are frequently referenced by report definitions and lookup-driven processing logic. The ETRM documentation classifies RG_FACTOR_V as "10SC ONLY," indicating that the object was introduced specifically to support the 10SC (subledger/accounting) context and is not intended as a general-purpose reporting entity across all modules.

Functionally, RG_FACTOR_V exposes a filtered projection of display-unit definitions. It presents a two-column result set derived from the RG_LOOKUPS view, restricted to the lookup type DISPLAY_UNITS. In Oracle EBS reporting and integration scenarios, this view serves as a lightweight reference source for resolving display-unit lookup codes and their corresponding meanings, allowing concurrent programs, report definitions, and dependent views to retrieve unit-of-measure or display formatting metadata without directly querying the broader RG_LOOKUPS structure.

Underlying Base Objects

The only documented referenced base object for RG_FACTOR_V is RG_LOOKUPS, which itself is a view rather than a base table. This layered dependency means RG_FACTOR_V inherits its data characteristics from the RG_LOOKUPS view, which in turn resolves against underlying lookup tables maintained by the Application Report Generator. The view definition applies a single filter predicate on the LOOKUP_TYPE column, constraining results to rows where LK.LOOKUP_TYPE = 'DISPLAY_UNITS'.

Because RG_LOOKUPS is a view, the effective query path from RG_FACTOR_V passes through at least one additional layer of indirection before reaching physical storage. From a performance and diagnostics standpoint, this matters: troubleshooting missing rows or unexpected values in RG_FACTOR_V requires inspecting the RG_LOOKUPS definition and its own base objects, not simply the lookup tables referenced by name. The dependency also means that any change to RG_LOOKUPS — column additions, filter changes, or recompilation issues — propagates directly to RG_FACTOR_V.

Key Columns

The documented view text projects two columns, aliased through the underlying lookup view:

• DISPLAY_UNITS — Corresponds to LK.LOOKUP_CODE. This is the stored lookup code identifying a specific display unit. It functions as the effective key of the view's result set.
• FACTOR — Corresponds to LK.MEANING. In the lookup framework, MEANING typically carries the descriptive or user-facing value associated with a lookup code. In this view it is aliased as FACTOR, indicating that the meaning column carries a numeric or conversion-style factor value for each display unit.

The ETRM column listing names DISPLAY_UNITS and FACTOR, while the view text shows the source columns LOOKUP_CODE and MEANING. Consumers should treat DISPLAY_UNITS as the lookup key and FACTOR as the associated value, understanding that the alias reflects the semantic role assigned within the RG/10SC context.

Common Use Cases and Queries

Typical use cases include resolving display-unit codes to their factors during report generation, validating that a given display unit is defined before processing, and joining the view to report-definition or formatting logic. A basic retrieval of all defined display units is straightforward:

SELECT display_units, factor FROM apps.rg_factor_v ORDER BY display_units;

To resolve a single unit, filter on the exposed key column:

SELECT factor FROM apps.rg_factor_v WHERE display_units = :p_unit;

The view can also be used as a validation source in PL/SQL or as a lookup in a report query, for example joining to a staged data set to translate unit codes into factors. Given the "10SC ONLY" designation, usage should be confined to the intended 10SC context. Because the view is defined over another view, queries should be tested against production data volumes, and any diagnostic investigation should trace through RG_LOOKUPS to identify the true source of unexpected results.