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
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ABSENCE_ATTENDANCE_ID | ● | Identifier for the absence attendance. | |
| ABSENCE_DAYS | ● | Absence days. | |
| ABSENCE_HOURS | ● | Absence hours. | |
| ASG_ABSENCE_RECORDING_ID | PK? | ● | 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_DATE | INCR | ● | 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.