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

HRA_CHECK_IN_MEETINGS

SharedUsed in 0 subject areas16 reporting columnsBICC incremental-ready

Talent Review (HRA).

Likely primary key: CHECK_IN_MEETING_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): REVIEW_PERIOD_ID → HRT_REVIEW_PERIODS_B

Columns

ColumnKeyIn reportsDescription (inferred)
BUSINESS_GROUP_ID●Identifier for the business group.
CHECK_IN_DATE●Check in date.
CHECK_IN_MEETING_IDPK?●Identifier for the check in meeting.
CHECK_IN_TEMPLATE_ID●Identifier for the check in template.
CREATED_BY●User who created the row.
CREATED_BY_PERSON_ID●Identifier for the created by person.
CREATION_DATE●Date and time the row was created.
DOCUMENT_NAME●Name of the document.
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.
MANAGER_PERSON_ID●Identifier for the manager person.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
REVIEW_PERIOD_ID●Identifier for the review period.
WORKER_ASSIGNMENT_ID●Identifier for the worker assignment.
WORKER_PERSON_ID●Identifier for the worker person.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Subject areas

Need the extract + dbt staging for HRA_CHECK_IN_MEETINGS?
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