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

TABLE: IBY.IBY_VAL_ASSIGNMENTS

Object Details
Object Name: IBY_VAL_ASSIGNMENTS
Object Type: TABLE
Owner: IBY
FND Design Data: TableIBY.IBY_VAL_ASSIGNMENTS
Subobject Name:
Status: VALID


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.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
IBY_VAL_ASSIGNMENTS_VAID_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnVALIDATION_ASSIGNMENT_ID
ColumnZD_EDITION_NAME
IBY_VAL_ASSIGNMENTS_N1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnVAL_ASSIGNMENT_ENTITY_TYPE
ColumnASSIGNMENT_ENTITY_ID
IBY_VAL_ASSIGNMENTS_N2 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnPAYMENT_METHOD_CODE
IBY_VAL_ASSIGNMENTS_N3 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnTERRITORY_CODE
Columns
Name Datatype Length Mandatory Comments
VALIDATION_ASSIGNMENT_ID NUMBER (15) Yes System generated primary key
VALIDATION_SET_CODE VARCHAR2 (30) Yes Validation set code
VAL_ASSIGNMENT_ENTITY_TYPE VARCHAR2 (30) Yes 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) Yes Identifier of the appropriate entity, for example, payment method, payment format.
INACTIVE_DATE DATE

Inactive date
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)
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.
TERRITORY_CODE VARCHAR2 (2)
Country to which the validation is applicable
PAYMENT_METHOD_CODE VARCHAR2 (30)
Payment method to which the validation is applicable
ZD_EDITION_NAME VARCHAR2 (30) Yes
Query Text

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


SELECT VALIDATION_ASSIGNMENT_ID
,      VALIDATION_SET_CODE
,      VAL_ASSIGNMENT_ENTITY_TYPE
,      ASSIGNMENT_ENTITY_ID
,      INACTIVE_DATE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      TERRITORY_CODE
,      PAYMENT_METHOD_CODE
,      ZD_EDITION_NAME
FROM IBY.IBY_VAL_ASSIGNMENTS;

Dependencies

[top of page]

IBY.IBY_VAL_ASSIGNMENTS does not reference any database object

IBY.IBY_VAL_ASSIGNMENTS is referenced by following:

SchemaIBY
ViewIBY_VAL_ASSIGNMENTS#