Search Results fv_lookup_codes




Overview
Explore in AI Chat

Overview

FV_LOOKUP_CODES is a read-only view owned by the APPS schema in Oracle E-Business Suite (12.1.1 and 12.2.2). It is a component of the FV — Federal Financials product family, which provides the compliance, funds control, and reporting extensions used by U.S. federal agencies running EBS. The view exposes federally seeded lookup codes maintained in the standard Oracle Application Object Library (AOL) lookup infrastructure, restricted to those owned by the Federal Financials application (VIEW_APPLICATION_ID = 8901). It presents a denormalized, language-aware subset of FND_LOOKUP_VALUES with the standard WHO audit columns and the full fifteen-column descriptive flexfield attribute set.

Because it resolves the current session language and security group at runtime, the view returns only the lookup rows appropriate to the calling user's language and lookup security context. This makes it suitable for reporting, concurrent programs, and integration interfaces that must enumerate valid federal lookup values without directly querying the AOL base tables, whose security and language handling must otherwise be replicated by the developer.

Underlying Base Objects

The view is defined over two documented objects:

  • FND_LOOKUP_VALUES (SYNONYM) — the AOL base table holding all lookup code values across applications, aliased LV in the view text. The view filters this table on three predicates: LV.LANGUAGE = USERENV('LANG'), LV.VIEW_APPLICATION_ID = 8901, and LV.SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID).
  • FND_GLOBAL (PACKAGE) — the AOL global context package, invoked through FND_GLOBAL.LOOKUP_SECURITY_GROUP to derive the applicable security group identifier for each lookup type. This enforces lookup-level security at query time.

The view performs no joins to other application tables; all columns are projected directly from FND_LOOKUP_VALUES, with the exception that LOOKUP_CODE and the remaining columns retain their original names while MEANING is aliased to DESCRIPTION.

Key Columns

  • LOOKUP_TYPE — the lookup type that groups related codes (for example, a federal funds-control or payment-format lookup).
  • LOOKUP_CODE — the internal code stored on transactions and used in validations.
  • DESCRIPTION — the user-facing meaning of the code, sourced from FND_LOOKUP_VALUES.MEANING.
  • ENABLED_FLAG — indicates whether the code is active for entry and validation.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date window during which the code is valid.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns for change tracking and reconciliation.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments attached to the lookup value, frequently used by federal implementations for agency-specific classification data.

Common Use Cases and Queries

Typical scenarios include populating value lists in custom forms or OAF pages, feeding reference data to downstream federal reporting extracts, and validating interface payloads against active federal codes. Because the view already resolves language and security, queries are concise. A basic listing for one lookup type:

  • SELECT lookup_code, description, enabled_flag FROM fv_lookup_codes WHERE lookup_type = :p_lookup_type AND enabled_flag = 'Y' ORDER BY lookup_code;

Filtering by effective date to exclude expired codes:

  • SELECT lookup_code, description, start_date_active, end_date_active FROM fv_lookup_codes WHERE lookup_type = :p_lookup_type AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

An audit query joining back to the base table for change history would target FND_LOOKUP_VALUES directly, since the view exposes only current, security-filtered rows. Where the metadata is limited, developers should confirm any newly added federal lookup types against FND_LOOKUP_VALUES for application 8901.