IBY_PMT_SYS_TRANSMISSIONS_
IBY_BEP_TRANSMISSIONS links payment systems to the transmission protocols they support. When a user creates a payment process profile, this table gives him or her the correct choice of protocols to use with a given payment system.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
Name | Columns |
---|---|
IBY_PMT_SYS_TRANSMISSIONS_PK_ |
LAST_UPDATE_DATE, TRANSMIT_PROTOCOL_CODE, BEPID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
TRANSMIT_PROTOCOL_CODE | VARCHAR2 | 240 | Yes | Transmission protocol identifier | |
BEPID | NUMBER | 18 | Yes | Payment system identifier | |
CREATED_BY | VARCHAR2 | 64 | Who column: indicates the user who created the row. | ||
CREATION_DATE | TIMESTAMP | Who column: indicates the date and time of the creation of the row. | |||
LAST_UPDATED_BY | VARCHAR2 | 64 | 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 | 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. | ||
AUDIT_ACTION_TYPE_ | VARCHAR2 | 10 | Actione Type - have values like INSERT, UPDATE and DELETE. | ||
AUDIT_CHANGE_BIT_MAP_ | VARCHAR2 | 1000 | Used to store a bit map of 1's and 0s for each row. 1 will be stored if the value has changed and 0 will be stored if the value hasn't. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
IBY_PMT_SYS_TRANSMISSIONS_PK_ | Unique | Default | LAST_UPDATE_DATE, TRANSMIT_PROTOCOL_CODE, BEPID |
IBY_PMT_SYS_TRANSMISSI_N1_ | Non Unique | Default | TRANSMIT_PROTOCOL_CODE, BEPID |