Search Results fa_rx_lov




Overview
Explore in AI Chat

Overview

FA_RX_LOV is a table in the OFA (Oracle Assets) product module, owned by the FA schema. It stores the definitions used to build List of Values (LOV) components that appear on RX reports generated within Oracle E-Business Suite. RX reports are the report-definition and parameter-driven outputs produced by the Oracle Assets reporting engine; each parameter presented to a user for selection can be backed by a value set and rendered through an LOV. FA_RX_LOV records how each such LOV is constructed, named, validated, and populated, thereby decoupling report parameter presentation from the underlying value set definitions.

The table is documented as VALID in both EBS 12.1.1 and 12.2.2. Its heuristic Data Vault classification, mined from the foreign key structure, is standalone — meaning no parent hub or link dependency is embedded in the table's own key topology. In a Data Vault 2.0 model, this object would most naturally be modeled as a standalone reference or lookup satellite; a hub-and-link decomposition is not warranted because the only outbound reference (VALUE_SET_ID) points to a value-set master rather than a core business entity.

Key Information Stored

The documented physical schema contains 11 columns. The most significant are:

  • LOV_ID — surrogate primary key, enforced by the FA_RX_LOV_PK constraint and also part of the unique index FA_RX_LOV_U1. It uniquely identifies each LOV definition.
  • LOV_NAME — the business-facing identifier of the LOV, exposed to users on report parameter screens and included in the unique index FA_RX_LOV_U2.
  • VALUE_SET_ID — foreign key to FRM_PART_VALUE_SETS, linking the LOV to the Oracle Forms value set that supplies its selectable values.
  • VALIDATE_FLAG — controls whether the value returned from the LOV is validated against the value set before being accepted.
  • SELECT_STATEMENT — the SQL text or reference used to populate the LOV's candidate list at runtime.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit and concurrency information.
  • ZD_EDITION_NAME — the editioning column introduced for EBS 12.2 online patching; it participates in both unique indexes (FA_RX_LOV_U1 and FA_RX_LOV_U2).

The documented unique indexes therefore establish two business-key candidates: the combination (LOV_ID, ZD_EDITION_NAME) and the combination (LOV_NAME, ZD_EDITION_NAME), confirming that LOV names are unique per edition.

Common Use Cases and Queries

Typical uses include auditing which value sets back a given set of RX report LOVs, diagnosing why a report parameter shows no values, and producing an inventory of custom versus seeded LOV definitions. A representative join query is:

SELECT l.LOV_ID, l.LOV_NAME, l.VALUE_SET_ID,
       l.VALIDATE_FLAG, l.SELECT_STATEMENT
FROM   FA.FA_RX_LOV l
WHERE  l.ZD_EDITION_NAME = 'RUN'
ORDER  BY l.LOV_NAME;

To reconcile LOVs against their value sets:

SELECT l.LOV_NAME, v.VALUE_SET_NAME
FROM   FA.FA_RX_LOV l, FRM_PART_VALUE_SETS v
WHERE  l.VALUE_SET_ID = v.VALUE_SET_ID;

Reverse-lookup reporting (which report parameters consume a given LOV) joins through FA_RX_REP_PARAMETERS on LOV_ID.

Related Objects

  • FRM_PART_VALUE_SETS — referenced via FA_RX_LOV.VALUE_SET_ID; supplies the value set master that each LOV is bound to.
  • FA_RX_REP_PARAMETERS — references FA_RX_LOV.LOV_ID; defines the report parameters that surface each LOV to users.
  • FA_RX_REP_PARAMETERS.LOV_ID — the FK column establishing the child relationship from parameters back to the LOV definition.
  • FA_RX_LOV_PK / FA_RX_LOV_U1 / FA_RX_LOV_U2 — primary key and unique indexes that enforce identity and business-key uniqueness per edition.
  • FA_RX_REP_GROUPS / FA_RX_MASTER — the surrounding report and parameter-group objects that form the broader RX reporting framework.