IBY_VAL_ASSIGNMENTS_
IBY_VAL_ASSIGNMENTS links validation sets to the appropriate validation entity. Through this table, individual validation sets are assigned to the payment method, payment format, or other entity that requires the validation encoded in that validation set. Payment method validation sets are those that should be evaluated as soon as possible once a transaction is assigned a payment method. Since each transaction is required to have a payment method assigned, these validations are evaluated immediately upon submission to Oracle Payments. All other types of validations are done offline, once the appropriate format or other entity has been assigned to the transaction. The determination of what type of entity a validation set should be associated with is based on the deploying company's business rules, the rules of the countries that have jurisdiction over the transaction, and ease-of-use. Typically, validations should be performed as early as possible, so users have immediate feedback and opportunity to modify invalid transactions.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
IBY_VAL_ASSIGNMENTS_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, VALIDATION_ASSIGNMENT_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| VALIDATION_ASSIGNMENT_ID | NUMBER | 18 | Yes | System-generated primary key. | |
| FIELD_NAME_CODE | VARCHAR2 | 30 | Field name lookup code of user-defined validation. This column can be null for predefined validation. | ||
| VALIDATION_SET_CODE | VARCHAR2 | 30 | Validation set code | ||
| VAL_ASSIGNMENT_ENTITY_TYPE | VARCHAR2 | 30 | Type of entity to which this validation is assigned. Values, from the lookup IBY_VALIDATION_ASSIGN_ENTITIES, include METHOD, FORMAT, BANK, TRANSPROTOCOL, and INTBANKACCOUNT | ||
| ASSIGNMENT_ENTITY_ID | VARCHAR2 | 30 | Identifier of the appropriate entity, for example, payment method, payment format. | ||
| INACTIVE_DATE | DATE | Inactive date | |||
| 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 | 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 | 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. | ||
| TERRITORY_CODE | VARCHAR2 | 2 | Country to which the validation is applicable | ||
| PAYMENT_METHOD_CODE | VARCHAR2 | 30 | Payment method to which the validation is applicable | ||
| START_DATE | DATE | Date when the assignment of a validation set to the payment method or format becomes active. | |||
| END_DATE | DATE | Date when the assignment of a validation set to the payment method or format becomes inactive. | |||
| SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
| 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. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_VAL_ASSIGNMENTSN1_ | Non Unique | Default | VALIDATION_ASSIGNMENT_ID, LAST_UPDATE_DATE |
| IBY_VAL_ASSIGNMENTS_VAID_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, VALIDATION_ASSIGNMENT_ID |