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

PER_ASG_ABSENCE_RECORDING

HCMUsed in 0 subject areas14 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: ASG_ABSENCE_RECORDING_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

Columns

ColumnKeyIn reportsDescription (inferred)
ABSENCE_ATTENDANCE_ID●Identifier for the absence attendance.
ABSENCE_DAYS●Absence days.
ABSENCE_HOURS●Absence hours.
ASG_ABSENCE_RECORDING_IDPK?●Identifier for the asg absence recording.
ASSIGNMENT_ID●Identifier for the assignment.
AUTHORISING_PERSON_ID●Identifier for the authorising person.
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.
PERSON_ID●Identifier for the person.
REPLACEMENT_PERSON_ID●Identifier for the replacement 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 PER_ASG_ABSENCE_RECORDING?
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