Oracle Fusion · Data dictionary
PER_ACTION_REASON_USAGES
HCMUsed in 0 subject areas15 reporting columnsBICC incremental-ready
Person / Worker (PER).
Likely primary key: ACTION_REASON_USAGE_ID (inferred from Oracle naming conventions — verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ACTION_CODE | ● | Code identifying the action. | |
| ACTION_ID | ● | Identifier for the action. | |
| ACTION_REASON_CODE | ● | Code identifying the action reason. | |
| ACTION_REASON_ID | ● | Identifier for the action reason. | |
| ACTION_REASON_USAGE_ID | PK? | ● | Identifier for the action reason usage. |
| BUSINESS_GROUP_ID | ● | Identifier for the business group. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| END_DATE | ● | End date. | |
| 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. | |
| MODULE_ID | ● | Identifier for the module. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| START_DATE | ● | Start date. |
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_ACTION_REASON_USAGES?
We ship parameterized SQL, BICC config, and dbt models you own.