Oracle Fusion · Data dictionary
PAY_ELEMENT_ENTRY_VALUES_F
PayrollUsed in 0 subject areas14 reporting columnsBICC incremental-ready
Payroll (PAY).
Likely primary key: ELEMENT_ENTRY_VALUE_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): ENTRY_USAGE_ID → PAY_ENTRY_USAGES
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| 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. |
| ELEMENT_ENTRY_ID | ● | Identifier for the element entry. | |
| ELEMENT_ENTRY_VALUE_ID | PK? | ● | Identifier for the element entry value. |
| ENTERPRISE_ID | ● | Identifier for the enterprise. | |
| ENTRY_USAGE_ID | ● | Identifier for the entry usage. | |
| INPUT_VALUE_ID | ● | Identifier for the input value. | |
| 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. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| SCREEN_ENTRY_VALUE | ● | Screen entry value. |
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 PAY_ELEMENT_ENTRY_VALUES_F?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table