Oracle Fusion · Data dictionary
PJO_PLAN_VERSIONS_B
ProjectsUsed in 2 subject areas16 reporting columns
Projects Planning (PJO), base table, language-neutral data (paired with _TL labels and the _VL view).
Primary key: not yet catalogued for PJO_PLAN_VERSIONS_B, reference Oracle Tables & Views guide.
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| BASELINED_DATE | ● | Baselined date. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| CURRENT_PLAN_STATUS_FLAG | ● | Indicator (Y/N) for the current plan status. | |
| 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. | |
| ORIGINAL_FLAG | ● | Indicator (Y/N) for the original. | |
| PLANNED_FOR_CODE | ● | Code identifying the planned for. | |
| PLAN_CLASS_CODE | ● | Code identifying the plan class. | |
| PLAN_STATUS_CODE | ● | Code identifying the plan status. | |
| REJECTED_BY | ● | Rejected by. | |
| REJECTION_DATE | ● | Rejection date. | |
| SUBMITTED_BY | ● | Submitted by. | |
| SUBMITTED_DATE | ● | Submitted date. | |
| VERSION_NUMBER | ● | Version number. |
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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.
Need the extract + dbt staging for PJO_PLAN_VERSIONS_B?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table