Oracle Fusion · Data dictionary
DOO_TASK_INSTANCES
SharedUsed in 1 subject areas11 reporting columns
Order Management (DOO).
Likely primary key: TASK_INSTANCE_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ACTUAL_COMPLETION_DATE | ● | Actual completion date. | |
| ACTUAL_START_DATE | ● | Actual start date. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| JEOPARDY_REASON | ● | Jeopardy reason. | |
| JEOPARDY_SCORE | ● | Jeopardy score. | |
| PLANNED_COMPLETION_DATE | ● | Planned completion date. | |
| PLANNED_START_DATE | ● | Planned start date. | |
| SCHEDULED_COMPLETION_DATE | ● | Scheduled completion date. | |
| SCHEDULED_START_DATE | ● | Scheduled start date. | |
| STEP_ACTIVE | ● | Step active. | |
| TASK_INSTANCE_ID | PK? | ● | Identifier for the task instance. |
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 DOO_TASK_INSTANCES?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table