Oracle Fusion · Data dictionary
PAY_REQUESTS
PayrollUsed in 0 subject areas13 reporting columnsBICC incremental-ready
Payroll (PAY).
Likely primary key: PAY_REQUEST_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): FLOW_TASK_INSTANCE_ID → PAY_FLOW_TASK_INSTANCES
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| CALL_ID | ● | Identifier for the call. | |
| CALL_TYPE | ● | Type of call. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| FLOW_INSTANCE_ID | ● | Identifier for the flow instance. | |
| FLOW_TASK_INSTANCE_ID | ● | Identifier for the flow task instance. | |
| 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. | |
| PARAM_NAME_VALS | ● | Param name vals. | |
| PAY_REQUEST_ID | PK? | ● | Identifier for the pay request. |
| PAY_TASK_ACTION_ID | ● | Identifier for the pay task action. |
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_REQUESTS?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table