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

HRT_PROFILES_B

SharedUsed in 3 subject areas14 reporting columnsBICC incremental-ready

Talent Profile (HRT), base table, language-neutral data (paired with _TL labels and the _VL view).

Likely primary key: PROFILE_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): PARTY_ID → HZ_PARTIES

Columns

ColumnKeyIn reportsDescription (inferred)
BUSINESS_GROUP_ID●Identifier for the business group.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
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.
OWNER_PERSON_ID●Identifier for the owner person.
PARTY_ID●Identifier for the party.
PERSON_ID●Identifier for the person.
PROFILE_CODE●Code identifying the profile.
PROFILE_IDPK?●Identifier for the profile.
PROFILE_TYPE_ID●Identifier for the profile type.
PROFILE_USAGE_CODE●Code identifying the profile usage.

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 HRT_PROFILES_B?
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