TIBEDI_BATCH_TX_BIN
Details for the table TIBEDI_BATCH_TX_BIN are explained in the table below.
Name | Value |
---|---|
Data Model | Physical |
Documentation |
This table stores the EDI data that has been batched. Note: Note: This table will grow based on the exchanged transactions. This table should be
added as a part of the archiving process.
A typical sample archive query for an Oracle database is shown below: Select * from TIBEDI_BATCH_TX_BIN where BININDEX in (select BININDEX from TIBEDI_BATCH_TX where STATUS like '%COMPLETED%' OR '%ERROR%' AND TS <= TO_TIMESTAMP(<from date>, 'YYYY-MM-DD HH24:MI:SS.FF') AND TS >= TO_TIMESTAMP(<to date>,'YYYY-MM-DD HH24:MI:SS.FF')) A typical sample archive query for Microsoft SQL database is shown below: Select * from TIBEDI_BATCH_TX_BIN where BININDEX in (select BININDEX from TIBEDI_BATCH_TX where STATUS like '%COMPLETED%' or '%ERROR%' and PROTOCOLNAME = '<protocol>' AND TS <= '<to date>' and TS >= '<from date>) |
User IDLast Numeric Value | 0 |
Primary Key Constraint Name | TIBEDI_BCH_TX_BIN |
DDLCLause | BININDEX NUMBER(18), COMPRESSED VARCHAR2(2) NULL, BINVAL BLOB NULL, CONSTRAINT TIBEDI_BCH_TX_BIN FOREIGN KEY (BININDEX) REFERENCES TIBEDI_BATCH_TX(BININDEX) ON DELETE CASCADE |
Columns summary for the table TIBEDI_BATCH_TX_BIN is shown in the table below:
Name | Data Type | Constraints | Nullable | Documentation |
---|---|---|---|---|
BININDEX | number(18) | No | Foreign key reference. | |
COMPRESSED | varchar2(2) | Yes | The data in this column is compressed or not. | |
BINVAL | BLOB | Yes | The actual EDI data that has to be batched. |