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

HRT_RATING_LEVELS_TL

SharedUsed in 3 subject areas13 reporting columnsBICC incremental-ready

Talent Profile (HRT), translation table, multi-language labels (join on the base key + LANGUAGE).

Likely primary key: RATING_LEVEL_ID, LANGUAGE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): RATING_LEVEL_IDHRT_RATING_LEVELS_B

Columns

ColumnKeyIn reportsDescription (inferred)
BUSINESS_GROUP_IDIdentifier for the business group.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
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.
OBJECT_VERSION_NUMBEROptimistic-locking version number, incremented on each update.
RATING_DESCRIPTIONDescription of the rating.
RATING_LEVEL_IDPK?Identifier for the rating level.
RATING_SHORT_DESCRRating short descr.
REVIEW_RATING_DESCRReview rating descr.
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 HRT_RATING_LEVELS_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