Oracle Fusion · Data dictionary
PJO_PLANNING_ELEMENTS
ProjectsUsed in 2 subject areas8 reporting columns
Projects Planning (PJO).
Primary key: PLANNING_ELEMENT_ID
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| 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. | |
| PLANNING_ELEMENT_ID | PK | ○ | Identifier for the planning element. |
| PLANNING_END_DATE | ● | Planning end date. | |
| PLANNING_START_DATE | ● | Planning start date. | |
| RATE_BASED_FLAG | ● | Indicator (Y/N) for the rate based. |
Used by reports
No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.
- ,
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_PLANNING_ELEMENTS?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table