DBA Data[Home] [Help] [Dependency Information]

TABLE: IBY.IBY_VALIDATION_SETS_TL

Object Details
Object Name: IBY_VALIDATION_SETS_TL
Object Type: TABLE
Owner: IBY
FND Design Data: TableIBY.IBY_VALIDATION_SETS_TL
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.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
IBY_VALIDATION_SETS_TL_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnLANGUAGE
ColumnVALIDATION_SET_CODE
ColumnZD_EDITION_NAME
IBY_VALIDATION_SETS_TL_VSID_N1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnVALIDATION_SET_CODE
Columns
Name Datatype Length Mandatory Comments
VALIDATION_SET_CODE VARCHAR2 (30) Yes User entered primary key
LANGUAGE VARCHAR2 (4) Yes Language code
SOURCE_LANG VARCHAR2 (4) Yes Language code of the record's current language
VALIDATION_SET_DISPLAY_NAME VARCHAR2 (100) Yes Validation set name
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.
ZD_EDITION_NAME VARCHAR2 (30) Yes
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT VALIDATION_SET_CODE
,      LANGUAGE
,      SOURCE_LANG
,      VALIDATION_SET_DISPLAY_NAME
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      ZD_EDITION_NAME
FROM IBY.IBY_VALIDATION_SETS_TL;

Dependencies

[top of page]

IBY.IBY_VALIDATION_SETS_TL does not reference any database object

IBY.IBY_VALIDATION_SETS_TL is referenced by following:

SchemaIBY
ViewIBY_VALIDATION_SETS_TL#