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_CODE●Code identifying the ac location.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DESCRIPTION●Description.
EFFECTIVE_END_DATE●End date of the effective-dated record.
EFFECTIVE_START_DATEPK?●Start date of the effective-dated record.
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.
LOCATION_CODE●Code identifying the location.
LOCATION_DETAILS_IDPK?●Identifier for the location details.
LOCATION_NAME●Name of the location.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
SOURCE_LANG●Source 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. 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 PER_LOCATION_DETAILS_F_TL?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
The report that lies quietly · Approval history vanishes · What the extract does not carry