IBY_TRANSACTION_ERRORS
IBY_TRANSACTION_ERRORS stores any errors encountered during payment processing validations.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
IBY_TRANSACTION_ERRORS_PK |
TRANSACTION_ERROR_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| TRANSACTION_ERROR_ID | NUMBER | 18 | Yes | System generated primary key | |
| TRANSACTION_TYPE | VARCHAR2 | 30 | Yes | Transaction type. Values from the lookup IBY_TRANSACTION_TYPES include DOCUMENT_PAYABLE, PAYMENT, and PAYMENT_INSTRUCTION. | |
| TRANSACTION_ID | NUMBER | 18 | Yes | Transaction Identifier | |
| ERROR_CODE | VARCHAR2 | 30 | Yes | Error code for failed transaction. If ERROR_TYPE is BANK, this is a bank-specific error code. | |
| ERROR_DATE | DATE | Yes | Date on which the error occurred | ||
| ORIGINATOR_CODE | VARCHAR2 | 80 | Status reason code sent from bank or payment systems | ||
| ORIGINATOR_MESSAGE | VARCHAR2 | 1024 | Status reason message sent from bank or payment systems | ||
| ERROR_STATUS | VARCHAR2 | 30 | Yes | Whether the error is still active, that is, the error still applies, passed, or overridden. Values from the lookup IBY_TRANSACTION_ERROR_STATUSES include ACTIVE, PASSED, and OVERRIDDEN. The last two values only apply to validation errors. | |
| OVERRIDE_ALLOWED_ON_ERROR_FLAG | VARCHAR2 | 1 | Yes | Y or N flag specifying whether this validation error can be overridden by the payment administrator. Some validation errors are fatal and the condition causing the error must be corrected so the payment instruction can be validated successfully. By default, this flag is Y. For fatal errors, the Create Payment Instructions program sets this flag to N. | |
| DO_NOT_APPLY_ERROR_FLAG | VARCHAR2 | 1 | Yes | Y or N flag which only applies to errors on payment instructions. The value is N by default and only changes to Y if an administrator overrides the error. When a payment instruction is resubmitted to the Create Payment Instructions program and validations are applied, this error is not applied when the value is Y. | |
| 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. | ||
| 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. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| CALLING_APP_ID | NUMBER | 18 | Source product Identifier | ||
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | 100 | Payment processing transaction type striped by application | ||
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | 100 | Source product''s first unique document payable Identifier | ||
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | 100 | Source product''s second unique document payable Identifier | ||
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | 100 | Source product''s third unique document payable Identifier | ||
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | 100 | Source product''s fourth unique document payable Identifier | ||
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | 100 | Source product''s fifth unique document payable Identifier | ||
| ERROR_TYPE | VARCHAR2 | 30 | Type of error. Values from the lookup IBY_TRANSACTION_ERROR_TYPES include VALIDATION and BANK. | ||
| ERROR_MESSAGE | VARCHAR2 | 255 | Error message for failed transaction. If ERROR_TYPE is BANK, this is a bank-specific error code. | ||
| VALIDATION_SET_CODE | VARCHAR2 | 30 | Identifier of the validation set that was violated if ERROR_TYPE is VALIDATION. | ||
| PASS_DATE | DATE | Date on which the validation set that gave rise to this error was passed. This column is not be populated if the DO_NOT_APPLY_ERROR_FLAG is Y. | |||
| OVERRIDE_JUSTIFICATION | VARCHAR2 | 255 | Justification for overriding validation error. This column is only populated if the DO_NOT_APPLY_ERROR_FLAG is Y. | ||
| OVERRIDE_DATE | DATE | Date on which the error was overridden. This column is only populated if the DO_NOT_APPLY_ERROR_FLAG is Y. | |||
| STATUS_ORGINATOR_ID | VARCHAR2 | 100 | ID of the status originator. | ||
| STATUS_ORIGINATOR_ID_TYPE | VARCHAR2 | 30 | Type of the status originator ID. I.e., BIC, CHIPS, ABA Routing number, ISO20022 clearing system member ID, etc. | ||
| STATUS_ORGINATOR_NAME | VARCHAR2 | 240 | Name of the status originator - a financial institution on the payment chain that initated the status such as rejection | ||
| LOAD_REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the interface load job that created the row. | ||
| TOKEN_REQUEST_FORMAT_CODE | VARCHAR2 | 30 | Message format for creating outbound request to launch hosted payment page owned by payment gateway to create credit card token. | ||
| TOKEN_RESPONSE_FORMAT_CODE | VARCHAR2 | 30 | Message format for reading and processing inbound response received from payment gateway for credit card token creation using hosted payment page. | ||
| TOKEN_REQUEST_ERROR_MESSAGE | VARCHAR2 | 360 | Error raised while initiating outbound request for credit card token creation. | ||
| TOKEN_RESPONSE_ERROR_MESSAGE | VARCHAR2 | 360 | Error raised while reading and processing inbound response received from payment gateway for token creation request. | ||
| QUERY_REQUEST_FORMAT_CODE | VARCHAR2 | 30 | Message format for creating outbound request to query the payment gateway. | ||
| QUERY_RESPONSE_FORMAT_CODE | VARCHAR2 | 30 | Message format for reading and processing inbound response received from payment gateway for transaction query. | ||
| QUERY_REQUEST_ERROR_MESSAGE | VARCHAR2 | 360 | Error raised while initiating outbound request to query the payment gateway. | ||
| QUERY_RESPONSE_ERROR_MESSAGE | VARCHAR2 | 360 | Error raised while reading and processing inbound response received from payment gateway for payment query. | ||
| OAUTH_PERFORMED_FLAG | VARCHAR2 | 1 | Indicates whether the transaction supports Oauth. | ||
| BEPID | NUMBER | 18 | The payment system identifier that will issue the payment instrument token. | ||
| BEP_ACCOUNT_ID | NUMBER | 18 | Payment system account that contains the merchant identifier parameters of the payment system that will issue the payment instrument token. | ||
| USER_PROFILE_CODE | VARCHAR2 | 30 | Funds capture process profile code related to payment instrument token. |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| IBY_TRANSACTION_ERRORS | iby_trxn_types_b | CALLING_APP_ID, PAY_PROC_TRXN_TYPE_CODE |
| iby_trxn_error_tokens | iby_transaction_errors | TRANSACTION_ERROR_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_TRANSACTION_ERRORS_N1 | Non Unique | Default | CALLING_APP_ID, PAY_PROC_TRXN_TYPE_CODE |
| IBY_TRANSACTION_ERRORS_N2 | Non Unique | Default | TRANSACTION_ID, TRANSACTION_TYPE |
| IBY_TRANSACTION_ERRORS_N3 | Non Unique | Default | ERROR_DATE |
| IBY_TRANSACTION_ERRORS_U1 | Unique | Default | TRANSACTION_ERROR_ID |