POI_RULE_RUN_HIST
This table contains information about the rules and their run history. Rules are used to change the classification results. They can also be used to normalize the data before or after the classification process.
Details
-
Schema: FUSION
-
Object owner: POI
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
POI_RULE_RUN_HIST_PK |
RULE_ID, BATCH_ID, TXN_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
RULE_ID | NUMBER | 18 | Yes | Identifies the rule applied on the batch. | |
BATCH_ID | NUMBER | 18 | Yes | Identifies the batch when processing the transactional data batch. | |
RUN_DATE | DATE | Yes | Batch execution date when the rule is applied. | ||
STATUS | VARCHAR2 | 30 | Status of the rule run against the batch. | ||
MESSAGE | VARCHAR2 | 2000 | Status or error message of the rules run against batch. | ||
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. | ||
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. | |
TXN_ID | NUMBER | 18 | Yes | Uniquely identifies the transaction data. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
POI_RULE_RUN_HIST_U1 | Unique | Default | RULE_ID, BATCH_ID, TXN_ID |