IBY_ROUTINGINFO_
IBY_ROUTINGINFO stores information that maps payment method to the payment system and funds capture process profile via conditions.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
IBY_ROUTINGINFO_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, PAYMENTMETHODID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| PAYEEID | VARCHAR2 | 80 | Payee Identifier passed by electronic commerce application | ||
| BEPID | NUMBER | 18 | Payment system Identifier | ||
| PAYMENTMETHODID | NUMBER | 18 | Yes | System-generated identifier of the payment method | |
| CONFIGURED | NUMBER | 2 | Indicates whether payment method is active or not. 1 is active and 0 is inactive. | ||
| PRIORITY | NUMBER | 18 | Order in which the payment methods are selected | ||
| PAYMENTMETHODNAME | VARCHAR2 | 80 | Name of the payment method | ||
| MPAYEEID | NUMBER | 18 | Payee Identifier | ||
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of 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. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| CREATION_DATE | TIMESTAMP | Who column: indicates the date and time of the creation of the row. | |||
| CREATED_BY | VARCHAR2 | 64 | Who column: indicates the user who created the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | |||
| INSTR_TYPE | VARCHAR2 | 30 | Instrument type for which this routing rule applies. One of CREDITCARD, PURCHASECARD, or BANKACCOUNT | ||
| INSTR_SUB_TYPE | VARCHAR2 | 30 | If INSTR_TYPE is BANKACCOUNT, subtype can be either ACH or BR | ||
| BEPKEY | VARCHAR2 | 80 | Merchant account Identifier associated with this routing rule | ||
| HITCOUNTER | NUMBER | 18 | Count of the number of times the routing rule was chosen | ||
| INACTIVE_DATE | DATE | Inactive Date | |||
| FNDCPT_USER_PROFILE_CODE | VARCHAR2 | 30 | Funds capture process profile | ||
| PAYMENT_CHANNEL_CODE | VARCHAR2 | 30 | Payment method | ||
| BEP_ACCOUNT_ID | NUMBER | 18 | Payment system account | ||
| START_DATE | DATE | Date from which the routing rule is available for use | |||
| END_DATE | DATE | Date until which the routing rule is available for use | |||
| AUDIT_ACTION_TYPE_ | VARCHAR2 | 10 | Action Type - have values like INSERT, UPDATE and DELETE. | ||
| AUDIT_CHANGE_BIT_MAP_ | VARCHAR2 | 1000 | Used to store a bit map of 1s and 0s for each column in the table. | ||
| AUDIT_IMPERSONATOR_ | VARCHAR2 | 64 | Original Impersonator User. | ||
| TOKENIZATION_ROUTING_FLAG | VARCHAR2 | 1 | Determines whether the routing rule is for transaction or payment instrument tokenization. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_ROUTINGINFON1_ | Non Unique | Default | PAYMENTMETHODID, LAST_UPDATE_DATE |
| IBY_RTINFO_PAYMENTMETHODID_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, PAYMENTMETHODID |