[Home] [Help] [Dependency Information]
Object Name: | IBY_VALIDATION_SETS_B |
---|---|
Object Type: | TABLE |
Owner: | IBY |
FND Design Data: | IBY.IBY_VALIDATION_SETS_B |
Subobject Name: | |
Status: | VALID |
IBY_VALIDATION_SETS stores links to payment validations. These validations must be performed before submitting transactions to a payment system. Validations may be required for many reasons, including bank account restrictions or the countries, currencies, or payment systems involved in a transaction. Payment validations are currently implemented in code, rather than in metadata. Thus, each validation in this table should be accompanied by a pointer to the code in which the validation is implemented. Validations can be further defined by specifying the entity with which they are associated. This determines when the validation should take place. Payment method validations are done immediately when a calling application submits a payment process request to Oracle Payments, and in some cases earlier as well. Other validations are done later, after Oracle Payments assigns the appropriate entities, such as payment format, to the payment. This division is done in the IBY_VAL_ASSIGNMENTS table.
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
IBY_VALIDATION_SETS_B_VSCID_U1 | NORMAL | UNIQUE | APPS_TS_TX_IDX | VALIDATION_SET_CODE |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
VALIDATION_SET_CODE | VARCHAR2 | (30) | Yes | User entered primary key |
PAYMENT_FLOW | VARCHAR2 | (30) | Lookup Type: IBY_PAYMENT_FLOW Lookup Values: DISBURSEMENTS, FUND_CAPTURE | |
VALIDATION_LEVEL_CODE | VARCHAR2 | (30) | Yes | Level at which this validation should apply. Values, from the IBY_VALIDATION_LEVELS lookup, include DOCUMENT, PAYMENT, and INSTRUCTION |
VALIDATION_CODE_PACKAGE | VARCHAR2 | (255) | Yes | Package where the validation is defined; in PL/SQL this corresponds to a package name, in Java a class name |
VALIDATION_CODE_ENTRY_POINT | VARCHAR2 | (255) | Yes | Entry point of the code that implements the validation set. For example, this could be in the form of a PL/SQL package and procedure, or a Java class and method. |
VALIDATION_CODE_LANGUAGE | VARCHAR2 | (30) | Yes | Language of the code that implements the validation set. Possible values are PLSQL and JAVA. |
CREATED_BY | NUMBER | (15) | Yes | Standard Who column |
CREATION_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard Who column |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
OBJECT_VERSION_NUMBER | NUMBER | (15) | Yes | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
Cut, paste (and edit) the following text to query this object:
SELECT VALIDATION_SET_CODE
, PAYMENT_FLOW
, VALIDATION_LEVEL_CODE
, VALIDATION_CODE_PACKAGE
, VALIDATION_CODE_ENTRY_POINT
, VALIDATION_CODE_LANGUAGE
, CREATED_BY
, CREATION_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
, OBJECT_VERSION_NUMBER
FROM IBY.IBY_VALIDATION_SETS_B;
IBY.IBY_VALIDATION_SETS_B does not reference any database object
IBY.IBY_VALIDATION_SETS_B is referenced by following:
|
|
|