Analytics Catalog/Data dictionary/FND_LOOKUP_VALUES_TL
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

FND_LOOKUP_VALUES_TL

Common / FoundationUsed in 218 subject areas13 reporting columnsBICC incremental-ready

Foundation / Setup (FND), translation table, multi-language labels (join on the base key + LANGUAGE).

Primary key: LOOKUP_TYPE, LOOKUP_CODE, VIEW_APPLICATION_ID, SET_ID, LANGUAGE, ENTERPRISE_ID, SANDBOX_ID (Oracle's FND_LOOKUP_VALUES_TL_PK) · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DESCRIPTION●Description.
LANGUAGEPK●Language.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATEINCR●Date and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGIN●Session login of the user who last updated the row.
LOOKUP_CODEPK●Code identifying the lookup.
LOOKUP_TYPEPK●Type of lookup.
MEANING●Meaning.
SET_IDPK●Identifier for the set.
SOURCE_LANG●Source lang.
VIEW_APPLICATION_IDPK●Identifier for the view application.

4 reports read from this table

Change a column here and these are the reports that move with it, the blast radius for any change to FND_LOOKUP_VALUES_TL.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.

Need the extract + dbt staging for FND_LOOKUP_VALUES_TL?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern