Search Results fa_rx_lov_u2

Overview

FA.FA_RX_LOV is a seed data table within the Oracle E-Business Suite Fixed Assets (FA) schema that stores definitions for List of Values (LOV) constructs used by the FA Reports eXtension (RX) reporting and parameter framework. In Oracle EBS 12.1.1 and 12.2.2, this table functions as a configuration repository for the runtime generation of selection lists presented to users when running fixed asset reports and concurrent programs. Each record binds a logical LOV name to an underlying value set and, where applicable, an embedded SQL SELECT statement that populates the list dynamically.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as seeded reference data rather than transactional data. It is classified as standalone by the heuristic Data Vault analysis mined from its foreign key structure. Under a Data Vault modeling suggestion, FA_RX_LOV would reasonably be treated as a hub-style reference entity keyed on LOV_ID, with descriptive attributes (LOV_NAME, VALIDATE_FLAG, SELECT_STATEMENT) forming a satellite. This classification is a modeling heuristic only; the physical table does not implement Data Vault constructs.

Key Information Stored

FA_RX_LOV contains eleven documented columns. The most significant are:

• LOV_ID (NUMBER(15), mandatory): Surrogate primary key enforced by the FA_RX_LOV_PK constraint. It uniquely identifies each LOV definition and is the column referenced by dependent tables.
• LOV_NAME (VARCHAR2(30)): The business-key candidate for the LOV. A unique index, FA_RX_LOV_U2, is defined on LOV_NAME (in the 12.2.2 schema documented with ZD_EDITION_NAME as a secondary column), making this the natural identifier used by application code and report parameters.
• VALUE_SET_ID (NUMBER): Foreign key to FRM_PART_VALUE_SETS, linking the LOV to the Oracle EBS value set that governs validation and available values.
• VALIDATE_FLAG (VARCHAR2): Controls whether user input against the LOV is validated against the referenced value set.
• SELECT_STATEMENT (LONG): Stores the query text used to dynamically populate the LOV at runtime, allowing reporting parameters to draw from arbitrary data sources.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN capture standard Oracle EBS who-did-what auditing, supporting change tracking and compliance reporting.
• ZD_EDITION_NAME: Editioning column present in the 12.2.2 schema, part of Oracle's Edition-Based Redefinition support and included in both unique indexes (FA_RX_LOV_U1 on LOV_ID and FA_RX_LOV_U2 on LOV_NAME).

Common Use Cases and Queries

Typical scenarios include identifying the value set behind a report parameter, auditing dynamic SQL used in LOVs, and joining LOV definitions to report parameter configurations. A representative query resolves a LOV name to its value set:

• SELECT l.LOV_ID, l.LOV_NAME, l.VALUE_SET_ID, l.VALIDATE_FLAG FROM FA.FA_RX_LOV l WHERE l.LOV_NAME = :lov_name;
• SELECT p.PARAMETER_ID, p.LOV_ID, l.LOV_NAME, l.SELECT_STATEMENT FROM FA.FA_RX_REP_PARAMETERS p JOIN FA.FA_RX_LOV l ON l.LOV_ID = p.LOV_ID WHERE p.PARAMETER_ID = :param_id;
• SELECT LOV_NAME, VALUE_SET_ID FROM FA.FA_RX_LOV WHERE VALIDATE_FLAG = 'Y' ORDER BY LOV_NAME;

Because SELECT_STATEMENT is a LONG datatype, it cannot be manipulated with standard string functions; extraction for inspection generally requires PL/pgSQL-style procedural handling or a tool capable of reading LONG columns.

Related Objects

The documented dependency graph is narrow but well defined:

• FA.FA_RX_REP_PARAMETERS: References FA_RX_LOV through the LOV_ID column. This is the principal consumer, binding LOV definitions to report parameters.
• FA.FRM_PART_VALUE_SETS: Referenced by FA_RX_LOV.VALUE_SET_ID; supplies the value set definition used for validation and value resolution.
• APPS.FA_RX_LOV: The APPS-layer synonym or view through which the table is accessed by application code and concurrent programs.
• FA_RX_LOV_PK / FA_RX_LOV_U1 / FA_RX_LOV_U2: The primary key and unique indexes (on LOV_ID and LOV_NAME respectively) that enforce row identity and business-key uniqueness.

No additional database objects are documented as being referenced by this table, confirming its role as a bounded seed configuration entity within the Fixed Assets reporting framework.