Oracle Fusion · Data dictionary
ANC_ABSENCE_REASONS_F
HCM AbsenceUsed in 0 subject areas14 reporting columnsBICC incremental-ready
Absence Management (ANC).
Likely primary key: ABSENCE_REASON_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ABSENCE_REASON_ID | PK? | ● | Identifier for the absence reason. |
| ANC_ABS_REASONS_F_ALTCD | ● | Anc abs reasons f altcd. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| EFFECTIVE_END_DATE | ● | End date of the effective-dated record. | |
| EFFECTIVE_START_DATE | PK? | ● | Start date of the effective-dated record. |
| ENTERPRISE_ID | ● | Identifier for the enterprise. | |
| 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. | |
| LEGISLATION_CODE | ● | Code identifying the legislation. | |
| MODULE_ID | ● | Identifier for the module. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| STATUS | ● | Status. |
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 ANC_ABSENCE_REASONS_F?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table