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

PER_LOCATION_DETAILS_F_TL

HCMUsed in 62 subject areas15 reporting columnsBICC incremental-ready

Person / Worker (PER) — translation table — multi-language labels (join on the base key + LANGUAGE).

Likely primary key: LOCATION_DETAILS_ID, EFFECTIVE_START_DATE, LANGUAGE (inferred from Oracle naming conventions — verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
AC_LOCATION_CODECode identifying the ac location.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
DESCRIPTIONDescription.
EFFECTIVE_END_DATEEnd date of the effective-dated record.
EFFECTIVE_START_DATEPK?Start date of the effective-dated record.
LANGUAGEPK?Language.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEINCRDate and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGINSession login of the user who last updated the row.
LOCATION_CODECode identifying the location.
LOCATION_DETAILS_IDPK?Identifier for the location details.
LOCATION_NAMEName of the location.
OBJECT_VERSION_NUMBEROptimistic-locking version number, incremented on each update.
SOURCE_LANGSource lang.

Used by reports

No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. You can't join across them in OTBI — the owned conformed model joins them on shared keys.

Need the extract + dbt staging for PER_LOCATION_DETAILS_F_TL?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us