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

PER_PERSON_TYPES_TL

HCMUsed in 6 subject areas10 reporting columnsBICC incremental-ready

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

Likely primary key: PERSON_TYPE_CODE, LANGUAGE (inferred from Oracle naming conventions, verify against Tables & Views) · 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.
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.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
PERSON_TYPE_CODEPK?○Code identifying the person type.
PERSON_TYPE_ID●Identifier for the person type.
SOURCE_LANG●Source lang.
USER_PERSON_TYPE●Type of user person.

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