Oracle Fusion · Data dictionary
PER_POSITION_LEG_F
HCMUsed in 0 subject areas14 reporting columnsBICC incremental-ready
Person / Worker (PER).
Likely primary key: POSITION_LEG_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): ACTION_OCCURRENCE_ID → PER_ACTION_OCCURRENCES
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ACTION_OCCURRENCE_ID | ● | Identifier for the action occurrence. | |
| ATTRIBUTE_CATEGORY | ● | Descriptive flexfield context (structure definition). | |
| 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. |
| INFORMATION_CATEGORY | ● | Information category. | |
| 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. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| POSITION_ID | ● | Identifier for the position. | |
| POSITION_LEG_ID | PK? | ● | Identifier for the position leg. |
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_POSITION_LEG_F?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table