Oracle Fusion · Data dictionary
PER_LOC_ADDRESS_USAGES_F
HCMUsed in 0 subject areas14 reporting columnsBICC incremental-ready
Person / Worker (PER).
Likely primary key: LOC_ADDRESS_USAGE_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) |
|---|---|---|---|
| ACTION_OCCURRENCE_ID | ● | Identifier for the action occurrence. | |
| ADDRESS_ID | ● | Identifier for the address. | |
| ADDRESS_USAGE_TYPE | ● | Type of address 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. | |
| EFFECTIVE_END_DATE | ● | End date of the effective-dated record. | |
| EFFECTIVE_START_DATE | PK? | ● | Start date of the effective-dated record. |
| 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. | |
| LOCATION_ID | ● | Identifier for the location. | |
| LOC_ADDRESS_USAGE_ID | PK? | ● | Identifier for the loc address usage. |
| 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_LOC_ADDRESS_USAGES_F?
We ship parameterized SQL, BICC config, and dbt models you own.