Oracle Fusion · Data dictionary
PJO_PLAN_LINE_DETAILS
ProjectsUsed in 2 subject areas12 reporting columns
Projects Planning (PJO) — detail-level data.
Primary key: PLAN_LINE_DETAIL_ID
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| 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 | ● | 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. | |
| PLAN_LINE_DETAIL_ID | PK | ○ | Identifier for the plan line detail. |
| TC_BILL_RATE_OVERRIDE | ● | Tc bill rate override. | |
| TC_BRDND_COST_RATE_OVERRIDE | ● | Tc brdnd cost rate override. | |
| TC_RAW_COST_RATE_OVERRIDE | ● | Tc raw cost rate override. | |
| TC_STD_BILL_RATE | ● | Tc std bill rate. | |
| TC_STD_BRDND_COST_RATE | ● | Tc std brdnd cost rate. | |
| TC_STD_RAW_COST_RATE | ● | Tc std raw cost rate. |
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 PJO_PLAN_LINE_DETAILS.
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.
Need the extract + dbt staging for PJO_PLAN_LINE_DETAILS?
We ship parameterized SQL, BICC config, and dbt models you own.