IBY_RULE_CONDITIONS_
IBY_PAYMENT_RULES_ is the audit table for IBY_PAYMENT_RULES. Table IBY_PAYMENT_RULES contains the header-level information for a payment method defaulting rule. A defaulting rule enables the user to define the default payment method with respect to multiple factors of a transaction context. A defaulting rule has one or more rule conditions stored in the IBY_RULE_CONDITIONS table. Each rule has a priority value. Rules are evaluated in the order of their priority. Higher priority ones with smaller integer values are evaluated first. If a match is found, the lower priority ones are not evaluated. This table corresponds to the Payment Method Defaulting Rules page.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
IBY_RULE_CONDITIONS_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, RULE_CONDITION_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| RULE_CONDITION_ID | NUMBER | 18 | Yes | System generated unique primary key. | |
| PAYMENT_RULE_ID | NUMBER | 18 | Payment method defaulting rule identifier. | ||
| RULE_CONDITION_TYPE_CODE | VARCHAR2 | 30 | 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 | 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 | Payment method defaulting 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 | 18 | 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 | 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. | ||
| 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_RULE_CONDITIONS_N1_ | Non Unique | Default | RULE_CONDITION_ID |
| IBY_RULE_CONDITIONS_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, RULE_CONDITION_ID |