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

PER_ASSIGNMENT_DAY_ABSENCES

HCMUsed in 0 subject areas18 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: ASSIGNMENT_DAY_ABSENCE_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): ABSENCE_ATTENDANCE_ID → PER_ABSENCE_ATTENDANCES · ASG_ABSENCE_RECORDING_ID → PER_ASG_ABSENCE_RECORDING

Columns

ColumnKeyIn reportsDescription (inferred)
ABSENCE_ATTENDANCE_ID●Identifier for the absence attendance.
ABSENCE_DATE●Absence date.
ABSENCE_DURATION_DAYS●Absence duration days.
ABSENCE_DURATION_HOURS●Absence duration hours.
ASG_ABSENCE_RECORDING_ID●Identifier for the asg absence recording.
ASSIGNMENT_DAY_ABSENCE_IDPK?●Identifier for the assignment day absence.
ASSIGNMENT_ID●Identifier for the assignment.
CALENDAR_EVENT_DURATION●Calendar event duration.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DAY_TYPE●Type of day.
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_ID●Identifier for the person.
SCHEDULE_WORK_DURATION●Schedule work duration.
WORK_SCHEDULE_UNIT●Work schedule unit.

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