Oracle Fusion · Data dictionary
PER_ABS_ATTENDANCE_REASONS
HCMUsed in 0 subject areas11 reporting columnsBICC incremental-ready
Person / Worker (PER).
Likely primary key: ABS_ATTENDANCE_REASON_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): LEGISLATIVE_DATA_GROUP_ID → PER_LEGISLATIVE_DATA_GROUPS
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ABSENCE_ATTENDANCE_TYPE_ID | ● | Identifier for the absence attendance type. | |
| ABS_ATTENDANCE_REASON_ID | PK? | ● | Identifier for the abs attendance reason. |
| BUSINESS_GROUP_ID | ● | Identifier for the business group. | |
| 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. | |
| LEGISLATIVE_DATA_GROUP_ID | ● | Identifier for the legislative data group. | |
| NAME | ● | Name. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. |
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_ABS_ATTENDANCE_REASONS?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table