Search Results fnd_lookup_values_vl
Overview
FND_LOOKUP_VALUES_VL is a multilingual (translated) view in the APPS schema belonging to the FND – Application Object Library product. It exposes the descriptive and translated columns of Oracle EBS lookup values, filtering rows by the session's runtime language so that applications and reports display meanings and descriptions in the user's active language. Because lookup codes drive a large proportion of EBS configuration — statuses, types, categories, and reference lists — this view is a central access point for both inquiry screens and integration interfaces.
The object is documented as VALID in ETRM for both Oracle EBS 12.1.1 and 12.2.2. Its designation as a "_VL" view follows the standard Oracle naming convention for views that combine a base (untranslated) table with the translated "_TL" table to return language-appropriate text.
Underlying Base Objects
Per the documented metadata, FND_LOOKUP_VALUES_VL is defined exclusively over the synonym FND_LOOKUP_VALUES. The view text references this base object as alias B and applies the filter WHERE B.LANGUAGE = USERENV('LANG'), restricting output to the row set matching the current session language. The synonym resolves to the underlying lookup values entity that stores both the codes and the translated MEANING and DESCRIPTION attributes, allowing the view to present a single language-relevant projection without additional joins visible to the caller.
Because the view is built on a synonym and hidden joins, consumers should treat it as a read-only reporting and query interface. The relationship to the base object is one-to-one per lookup row for the active language; no aggregation or denormalization is applied.
p>Note the view text in the ETRM excerpt contains a trailing comma before FROM, a transcription artifact; the functional semantics remain as described above.Key Columns
- ROW_ID — ROWID of the underlying base row, usable for direct row addressing.
- LOOKUP_TYPE and LOOKUP_CODE — the lookup type and its code value; together they form the logical business key.
- MEANING and DESCRIPTION — the translated text returned for the session language, the primary reason to use the _VL view.
- ENABLED_FLAG — indicates whether the lookup code is active.
- START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the code.
- TERRITORY_CODE — territory association where applicable.
- TAG — free-form tag attribute on the lookup value.
- VIEW_APPLICATION_ID — owning application identifier.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) segments.
- SECURITY_GROUP_ID — security grouping column.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard audit columns.
Common Use Cases and Queries
Typical scenarios include populating LOVs and report parameters, validating incoming interface data, and joining lookup values to transactional tables to resolve display text.
List active values for a lookup type:
SELECT lookup_code, meaning, description, enabled_flag
FROM fnd_lookup_values_vl
WHERE lookup_type = 'INV_TRANSACTION_TYPE'
AND enabled_flag = 'Y';
Translate a stored code during reporting:
SELECT t.transaction_code, v.meaning
FROM my_transactions t, fnd_lookup_values_vl v
WHERE v.lookup_type = 'MY_TYPE'
AND v.lookup_code = t.transaction_code;
Restrict by effective dates to return only currently valid codes. Because the view filters on USERENV('LANG'), results automatically reflect the language environment of the executing session, making it suitable for concurrent programs and personalizations that must present localized meaning text without explicit language joins.
-
View: FND_LOOKUP_VALUES_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FND.FND_LOOKUP_VALUES_VL, object_name:FND_LOOKUP_VALUES_VL, status:VALID, product: FND - Application Object Library , implementation_dba_data: APPS.FND_LOOKUP_VALUES_VL ,
-
View: FND_LOOKUP_VALUES_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:FND.FND_LOOKUP_VALUES_VL, object_name:FND_LOOKUP_VALUES_VL, status:VALID, product: FND - Application Object Library , implementation_dba_data: APPS.FND_LOOKUP_VALUES_VL ,
-
View: BIS_APPR_MSGTYPE
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FND.BIS_APPR_MSGTYPE, object_name:BIS_APPR_MSGTYPE, status:VALID, product: FND - Application Object Library , implementation_dba_data: APPS.BIS_APPR_MSGTYPE ,
-
View: BIS_APPR_MSGTYPE
12.2.2
product: FND - Application Object Library , implementation_dba_data: Not implemented in this database ,
-
View: UMX_ROLE_ASSIGNMENTS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FND.UMX_ROLE_ASSIGNMENTS_V, object_name:UMX_ROLE_ASSIGNMENTS_V, status:VALID, product: FND - Application Object Library , description: Private view used by UMX to display roles and registration requests for a given user , implementation_dba_data: APPS.UMX_ROLE_ASSIGNMENTS_V ,
-
View: UMX_ROLE_ASSIGNMENTS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:FND.UMX_ROLE_ASSIGNMENTS_V, object_name:UMX_ROLE_ASSIGNMENTS_V, status:VALID, product: FND - Application Object Library , description: Private view used by UMX to display roles and registration requests for a given user , implementation_dba_data: APPS.UMX_ROLE_ASSIGNMENTS_V ,