Oracle Fusion · Data dictionary
PER_JOBS_F_TL
HCMUsed in 8 subject areas12 reporting columnsBICC incremental-ready
Person / Worker (PER), translation table, multi-language labels (join on the base key + LANGUAGE).
Primary key: JOB_ID, EFFECTIVE_START_DATE, LANGUAGE · Incremental key: LAST_UPDATE_DATE
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. |
| JOB_ID | PK | ● | Identifier for the job. |
| LANGUAGE | PK | ● | Language. |
| 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. | |
| NAME | ● | Name. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| SOURCE_LANG | ● | Source lang. |
2 reports read from this table
Change a column here and these are the reports that move with it, the blast radius for any change to PER_JOBS_F_TL.
Where this surfaces in OTBI
The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.
- Maintenance Management - Purchased Item Usage Real Time
- Manufacturing - Purchased Item Usage Real Time
- Procurement - Procure To Pay Real Time
- Project Billing - Revenue Real Time
- Project Costing - Actual Costs Real Time
- Project Costing - Assets Real Time
- Project Costing - Expenditure Item Performance - Real Time
- Project Costing - Unprocessed Transactions Real Time
Need the extract + dbt staging for PER_JOBS_F_TL?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table