DOO_ORCHESTRATION_TRX_DETAILS
The table stores entites that a Process or Group is working on.
Details
-
Schema: FUSION
-
Object owner: DOO
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
DOO_ORCH_TRX_DETAILS_PK |
ORCHESTRATION_TRX_DETAIL_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
ORCHESTRATION_TRX_DETAIL_ID | NUMBER | 18 | Yes | Primary Key of this table. | |
TRX_HEADER_ID | VARCHAR2 | 400 | Header Id of the related Application transaction. | ||
TRX_HEADER_NAME | VARCHAR2 | 120 | Header type of the related Application Entity. In SFO case, it would be document_type. In DOO it will be DOO_HEADERS_ALL. | ||
ORCHESTRATION_TRX_ID | VARCHAR2 | 400 | Yes | Unique ID of the related Application Transaction Entity. For DOO case, this can be fulfillLineId. In SFO case, this can be eventId. | |
ORCHESTRATION_TRX_NAME | VARCHAR2 | 400 | Yes | Type of the related Application Transaction Entity. In DOO case, this can be FULFILLMENT_LINE for an example. In SFO case, this would be event_type. | |
TRX_SOURCE_SYSTEM | VARCHAR2 | 400 | Yes | Source system of the related Application Transaction Entity. In SFO case, this would be event_system. | |
TRANSACTION_DATE | TIMESTAMP | Date of the Transaction Entity. | |||
PARENT_TRX_ID | VARCHAR2 | 400 | Unique ID of the related Application Parent Transaction Entity. For DOO case, this can be LineId. In SFO case, this can be a parent eventId. | ||
PARENT_TRX_NAME | VARCHAR2 | 400 | Type of the related Application parent Transaction Entity. In DOO case, this can be DOO_LINE for an example. In SFO case, this would be a parent event_type. | ||
PARENT_TRX_SOURCE_SYSTEM | VARCHAR2 | 400 | Source system of the related Application Parent Transaction Entity. In SFO case, this would be parent_event_system. | ||
GROUP_ID | NUMBER | 18 | The ID of the group which groups some transaction entities. FK to Group table. If null, it means we did not start the flow. This indicates the current runtime status of a transaction entity. In SFO case, this could have a value something like either consumed or not-yet-consumed. | ||
GROUP_SEQ_ID | NUMBER | 18 | Yes | Foreign Key Reference from Groups table. | |
AGGREGATED_GROUP_ID | NUMBER | 18 | Identifies the Group of Groups that optimizes the request to TaskLayer. | ||
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. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created 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. | ||
TRX_HEADER_SOURCE_SYSTEM | VARCHAR2 | 400 | Source system of the related Application Header Transaction Entity. In SFO case, this would be document_source_system. | ||
TRANSACTION_CATEGORY | VARCHAR2 | 7 | Flow type of the related Application Transaction Entity.Example, in SFO case, this would have a value of either FORWARD or RETURN. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
DOO_ORCHESTRATION_TRX_DETAILS | doo_orchestration_groups | GROUP_SEQ_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
DOO_ORCH_TRX_DETAILS_FK1 | Non Unique | Default | GROUP_SEQ_ID |
DOO_ORCH_TRX_DETAILS_N1 | Non Unique | Default | AGGREGATED_GROUP_ID |
DOO_ORCH_TRX_DETAILS_PK | Unique | Default | ORCHESTRATION_TRX_DETAIL_ID |