Search Results display_units




Overview
Explore in AI Chat

Overview

APPS.RG_FACTOR_V is a lightweight Oracle E-Business Suite view that exposes the display unit lookup values maintained within the Oracle Assets (Fixed Assets) module. Its entire definition is a single filtered query against the RG_LOOKUPS table, restricting rows to the lookup type DISPLAY_UNITS. In effect, the view presents the lookup codes and their corresponding user-facing meanings that describe the units used for displaying depreciation or asset-related factors.

The object resides in the APPS schema and is therefore accessible to any responsibility or reporting tool that connects with the standard APPS credentials, provided the underlying RG_LOOKUPS object is also readable. Within Oracle EBS 12.1.1 and 12.2.2, the view's role is to abstract the lookup mechanism so that forms, concurrent programs, and custom reports can retrieve a clean list of display-unit values without hardcoding the lookup type filter themselves. The view is read-only in practice and contains no data of its own; it is a convenience layer over the lookup repository. Because its name carries the "RG_" prefix, it belongs to the Oracle Assets table family (RG_ tables correspond to Fixed Assets internals), and it is generally consumed as a reference source rather than a transactional data source. The inclusion of display_unit values is primarily informational — supporting the presentation of factor or rate values with a unit qualifier.

Underlying Base Objects

According to the documented metadata, RG_FACTOR_V references exactly one base object: RG_LOOKUPS, which itself is a view in the APPS schema. RG_LOOKUPS is the Fixed Assets lookup view commonly used to centralize lookup codes and meanings across the module. The view performs no joins, aggregations, or expressions; it simply selects LOOKUP_CODE and MEANING from RG_LOOKUPS where LOOKUP_TYPE = 'DISPLAY_UNITS'.

Because the dependency chain is view-over-view, the actual physical lookup records originate from the underlying lookup tables that RG_LOOKUPS sources. Consequently, querying RG_FACTOR_V implicitly traverses that chain. If the site has customized or translated lookup meanings, those changes surface through this view automatically. The dependency is narrow: only two columns and one lookup type are projected, so the view is stable and inexpensive to query.

Key Columns

  • LOOKUP_CODE — The internal code value identifying a display unit. This is the value typically stored in or compared against other tables that reference a display unit.
  • MEANING — The descriptive, user-facing text associated with the lookup code. This is the value presented to end users on forms and reports.

No other columns are exposed. The view deliberately omits lookup metadata such as enabled flags, descriptions, or ordering, so consumers requiring those attributes must query RG_LOOKUPS directly.

Common Use Cases and Queries

RG_FACTOR_V is most useful when building lookups for display units in custom reports, LOVs, or integrations, and when validating values submitted through interfaces. A typical query retrieves all valid display units:

  • SELECT lookup_code, meaning FROM apps.rg_factor_v ORDER BY meaning;
  • SELECT meaning FROM apps.rg_factor_v WHERE lookup_code = :p_code;
  • SELECT lookup_code FROM apps.rg_factor_v WHERE meaning = :p_meaning;

These patterns are common in fixed-asset reporting where a factor figure must be presented alongside its unit of measure, and in interface validation where an incoming display unit must be checked against enabled lookup values. Because the view filters to a single lookup type, it simplifies SQL and removes the need to remember the DISPLAY_UNITS literal.

Performance is generally excellent given the small result set and the indexed access path characteristic of lookup tables. Standard EBS security applies: grant access to the APPS synonym and ensure the calling schema can read RG_LOOKUPS. When troubleshooting, confirm that the DISPLAY_UNITS lookup type is populated and enabled, as an empty lookup set will yield no rows from this view.