DOO_PROCESS_INSTANCES
This table stroes the information about process instance
Details
-
Schema: FUSION
-
Object owner: DOO
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
DOO_PROCESS_INSTANCES_PK |
DOO_PROCESS_INSTANCE_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| DOO_PROCESS_INSTANCE_ID | NUMBER | 18 | Yes | Unique identifier of the orchestration process instance. | |
| LINE_COUNT | NUMBER | 18 | Needed for branching logic in step manager based on number of lines in the group. | ||
| ORCHESTRATION_APPLICATION_ID | NUMBER | 18 | Reference to the unique identifier of the orchestration application | ||
| DOO_PROCESS_ID | NUMBER | 18 | Yes | Reference to the unique identifier of an orchestration process | |
| PARENT_PROCESS_INSTANCE_ID | NUMBER | 18 | Parent process identifier to which this instance is a subprocess. | ||
| ROOT_PROCESS_INSTANCE_ID | NUMBER | 18 | Root parent process identifier to which this instance is a subprocess. | ||
| DOO_PROCESS_VERSION | NUMBER | 18 | Yes | Version of the orchestration process. | |
| STATUS_CODE | VARCHAR2 | 30 | State or condition of a process | ||
| PROCESS_ACTIVE | VARCHAR2 | 30 | Signifies whether the process state is active or not | ||
| PLANNED_COMPLETION_DATE | DATE | Planned Completion date of the orchestration process. | |||
| REQUIRED_FULFILL_DATE | DATE | Date when a fulfillment line is required to be fulfilled (Shipped/Installed) by, in order to meet the promised date of the order. | |||
| PLANNED_FULFILL_DATE | DATE | Planned Fulfillment Date of Orchestration Process | |||
| ACTUAL_START_DATE | DATE | The date that work commenced on an orchestration process. | |||
| ACTUAL_FULFILL_DATE | DATE | The date when a orchestration process is considered completed. | |||
| ACTUAL_COMPLETION_DATE | DATE | The date when orchestration process is completed. | |||
| JEOPARDY_SCORE | NUMBER | Jeopardy score calculated at the orchestration process level. This is highest of the jeopardy scores amongst all the tasks in a orchestration process. | |||
| JEOPARDY_REASON | VARCHAR2 | 128 | Indicates why a part of the fulfillment process is running behind schedule. | ||
| JEOPARDY_REASON_TASK_INST_ID | NUMBER | 18 | Stores the task Instance that caused the orchestration process to be in jeopardy. | ||
| REFERENCE_PROCESS_INSTANCE_ID | NUMBER | 18 | Used by change processing framework for storing the previous process instance. | ||
| BPEL_INSTANCE_ID | NUMBER | 18 | Reference to the unique identifier for BPEL instance | ||
| COMPLETED_STEPS | NUMBER | 18 | Used by change processing framework for tracking number of completed steps | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| PROCESS_NUMBER | VARCHAR2 | 50 | Process number used for display in the runtime UI. | ||
| PAUSE_FOR_CHANGE_FLAG | VARCHAR2 | 1 | Flag that allows orchestration to pause an ongoing process and wait for change request thread to complete processing | ||
| PROCESS_BITSET | NUMBER | 4 | Bitset that contains information on certain process attributes. | ||
| CHANGE_ORIGINATOR | VARCHAR2 | 64 | This column records who originates the change requests that are processed by this process instance. The process instance is the one that does the required compensations for the change. | ||
| ORCHESTRATION_APP_ATTRIBUTE1 | NUMBER | 18 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE2 | NUMBER | 18 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE3 | VARCHAR2 | 256 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE4 | VARCHAR2 | 256 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE5 | VARCHAR2 | 256 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE6 | VARCHAR2 | 256 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE7 | VARCHAR2 | 256 | This is the Custom columns to store product specific information. | ||
| ORCHESTRATION_APP_ATTRIBUTE8 | DATE | This is the Custom columns to store product specific information. | |||
| ORCHESTRATION_APP_ATTRIBUTE9 | DATE | This is the Custom columns to store product specific information. | |||
| ORCHESTRATION_APP_ATTRIBUTE10 | DATE | This is the Custom columns to store product specific information. | |||
| ORCHESTRATION_APP_ATTRIBUTE11 | DATE | This is the Custom columns to store product specific information. | |||
| SPLIT_FROM_STEP_ID | NUMBER | 18 | Stores the split from step id | ||
| PRIOR_SPLIT_FROM_STEP_ID | NUMBER | 18 | Stores the prior split from step id | ||
| SPLIT_FROM_STEP_STATUS | NUMBER | 18 | Stores the Split from Step status as a bit map. For an example. Step could be Complete | ||
| EXECUTE_ALLSTEPS_SPLITS_FLAG | VARCHAR2 | 32 | To inducate if orch should start from top instead of where split happended. For an example, split could happen at shipping step, if this flag is set AND the first step of the process is scheduling, then the new split line will start from scheduling step. | ||
| LINKED_PROCESS_INSTANCE_ID | NUMBER | 18 | Identifier of the Process instance used to cancel the set of fulfill lines, in cancel-create pattern. | ||
| SPLIT_LINE_PROCESSING_MODE | VARCHAR2 | 30 | Identifies the processing mode of a split fulfillment line. The change processing framework uses this value to determine whether an orchestration process instance can update the line when the fulfillment system splits the line. Here are some example values: CANCEL_CREATE means the orchestration process can cancel the existing line and recreate the line because fulfillment hasn't yet shipped it. UPDATE means an upstream application updated the line. NO_UPDATE means fulfillment already shipped the line so the orchestration process can't update it. |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| DOO_PROCESS_INSTANCES | doo_orchestration_applications | ORCHESTRATION_APPLICATION_ID |
| DOO_PROCESS_INSTANCES | doo_process_definitions_b | DOO_PROCESS_ID |
| doo_orchestration_groups | doo_process_instances | DOO_PROCESS_INSTANCE_ID |
| doo_process_step_instances | doo_process_instances | DOO_PROCESS_INSTANCE_ID |
| doo_task_instances | doo_process_instances | DOO_PROCESS_INSTANCE_ID |
| doo_process_bpel_instances | doo_process_instances | PROCESS_INSTANCE_ID |
| doo_order_states | doo_process_instances | DOO_PROCESS_INSTANCE_ID |
| doo_jeopardy_score_history | doo_process_instances | DOO_PROCESS_INSTANCE_ID |
| doo_error_recovery_instances | doo_process_instances | PROCESS_INSTANCE_ID |
| doo_task_status_history | doo_process_instances | DOO_PROCESS_INSTANCE_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| DOO_PROCESS_INSTANCES_FK1 | Non Unique | Default | DOO_PROCESS_ID |
| DOO_PROCESS_INSTANCES_N1 | Non Unique | Default | PROCESS_NUMBER |
| DOO_PROCESS_INSTANCES_N2 | Non Unique | Default | REQUIRED_FULFILL_DATE |
| DOO_PROCESS_INSTANCES_N3 | Non Unique | Default | LAST_UPDATE_DATE |
| DOO_PROCESS_INSTANCES_PK | Unique | Default | DOO_PROCESS_INSTANCE_ID |