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

HR_ORGANIZATION_UNITS_F_TL

HCMUsed in 172 subject areas13 reporting columnsBICC incremental-ready

HR / Workforce (HR), translation table, multi-language labels (join on the base key + LANGUAGE).

Primary key: ORGANIZATION_ID, EFFECTIVE_START_DATE, LANGUAGE · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): ORGANIZATION_IDINV_ORGANIZATION_DEFINITIONS_V

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
EFFECTIVE_END_DATEEnd date of the effective-dated record.
EFFECTIVE_START_DATEPKStart date of the effective-dated record.
LANGUAGEPKLanguage.
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.
NAMEName.
OBJECT_VERSION_NUMBEROptimistic-locking version number, incremented on each update.
ORGANIZATION_IDPKIdentifier for the organization.
SOURCE_LANGSource lang.
TITLETitle.

3 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 HR_ORGANIZATION_UNITS_F_TL.

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 HR_ORGANIZATION_UNITS_F_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