eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

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

TABLE: IBY.IBY_RULE_CONDITIONS

Object Details

Object Name:	IBY_RULE_CONDITIONS
Object Type:	TABLE
Owner:	IBY
FND Design Data:	IBY.IBY_RULE_CONDITIONS
Subobject Name:
Status:	VALID

IBY_RULE_CONDITIONS stores the detail-level information for a payment method defaulting rule. Each row in the IBY_PAYMENT_RULES table has one or more rows in this table. Conditions of different types are combined with the AND logical operator. Conditions of the same type are combined with the OR logical operator. This table corresponds to the Payment Method Defaulting Rules page.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_RULE_CONDITIONS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	RULE_CONDITION_ID
IBY_RULE_CONDITIONS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PAYMENT_RULE_ID

Columns

Name	Datatype	Length	Mandatory	Comments
RULE_CONDITION_ID	NUMBER	(15)	Yes	System generated primary key
PAYMENT_RULE_ID	NUMBER	(15)	Yes	Rule header Identifier
RULE_CONDITION_TYPE_CODE	VARCHAR2	(30)	Yes	Rule condition type. Each type corresponds to one driver parameter for payment method defaulting. Lookup values of IBY_PMT_MTHD_DEFAULTING_CONDITION lookup type
OPERATOR_CODE	VARCHAR2	(30)	Yes	Rule condition operator. Lookup codes, such as EQ, GT, LE, and others, which are defined by the IBY_PMT_MTHD_DEFAULTING_OPS lookup type. Applicable operators vary depending on the condition type.
RULE_CONDITION_VALUE	VARCHAR2	(240)		Rule condition value
STRING_VALUE_FLAG	VARCHAR2	(1)		Y if the value is a string. Otherwise it is treated as a number.
RULE_CONDITION_ENTRY_SEQUENCE	NUMBER	(15)		Number that denotes the order in which the user has entered the conditions. When queried, it needs to be displayed in the same order that the user has entered the rule condition.
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		Yes	Object version number

Query Text

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


SELECT RULE_CONDITION_ID
,      PAYMENT_RULE_ID
,      RULE_CONDITION_TYPE_CODE
,      OPERATOR_CODE
,      RULE_CONDITION_VALUE
,      STRING_VALUE_FLAG
,      RULE_CONDITION_ENTRY_SEQUENCE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
FROM IBY.IBY_RULE_CONDITIONS;

Dependencies

[top of page]

IBY.IBY_RULE_CONDITIONS does not reference any database object

IBY.IBY_RULE_CONDITIONS is referenced by following:

IBY: IBY_RULE_CONDITIONS#