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

PER_CALENDAR_EVENTS

HCMUsed in 0 subject areas16 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: CALENDAR_EVENT_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): TREE_VERSION_ID → FND_TREE_VERSION_VL

Columns

ColumnKeyIn reportsDescription (inferred)
BUSINESS_GROUP_ID●Identifier for the business group.
CALENDAR_EVENT_IDPK?●Identifier for the calendar event.
CATEGORY●Category.
COVERAGE_TYPE●Type of coverage.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
END_DATE_TIME●End date time.
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.
SHORT_CODE●Code identifying the short.
START_DATE_TIME●Start date time.
TREE_CODE●Code identifying the tree.
TREE_STRUCTURE_CODE●Code identifying the tree structure.
TREE_VERSION_ID●Identifier for the tree version.

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