Search Results iby_payment_rules




Overview
Explore in AI Chat

Overview

The IBY_PAYMENT_RULES table is a core data object within the Oracle E-Business Suite Payments (IBY) module. It serves as the primary repository for the header-level definition of payment method defaulting rules. In the context of Oracle EBS 12.1.1 and 12.2.2, these rules are a critical configuration component that automates the selection of a default payment method (e.g., Check, Electronic Funds Transfer) for a transaction. The rule engine evaluates multiple contextual factors of a transaction, such as the originating application, payee, and payment amount, against defined conditions to determine the appropriate payment method, thereby streamlining payment processing and enforcing business policies.

Key Information Stored

The table stores the metadata that defines a rule's identity, scope, and target. Its primary key, PAYMENT_RULE_ID, uniquely identifies each rule. Essential columns include APPLICATION_ID, which links the rule to a specific Oracle EBS application (e.g., Payables, Receivables) via FND_APPLICATION, establishing the rule's operational context. The PAYMENT_METHOD_CODE column stores the code for the default payment method (from IBY_PAYMENT_METHODS_B) that the rule assigns when its conditions are satisfied. Other significant columns typically include fields for the rule's name, description, effective dates (START_DATE, END_DATE), and an indicator for the rule's status (e.g., active or inactive), enabling temporal control over rule applicability.

Common Use Cases and Queries

A primary use case is troubleshooting payment method defaulting behavior or auditing rule configurations. For instance, to list all active payment method defaulting rules for the Payables application, a query would join IBY_PAYMENT_RULES with FND_APPLICATION. Another common scenario is identifying which rules default to a specific payment method code. Sample SQL to find rules defaulting to the 'CHECK' method would filter on PAYMENT_METHOD_CODE. Reporting often involves joining with IBY_RULE_CONDITIONS to see the full rule definition, including its detailed conditional logic. Administrators may also query this table to deactivate rules by updating their status or end date.

Related Objects

The IBY_PAYMENT_RULES table has defined relationships with several key EBS objects, as documented in the ETRM metadata. It references two tables via foreign keys: IBY_PAYMENT_METHODS_B (on PAYMENT_METHOD_CODE) to validate the assigned payment method, and FND_APPLICATION (on APPLICATION_ID) to define the rule's owning application. Crucially, it is referenced by the IBY_RULE_CONDITIONS table, where the PAYMENT_RULE_ID foreign key links each rule header to its detailed conditional lines. This one-to-many relationship is fundamental; the rule header in IBY_PAYMENT_RULES is meaningless without the specific conditions stored in IBY_RULE_CONDITIONS that define its triggering logic.

  • Table: IBY_PAYMENT_RULES 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_RULES,  object_name:IBY_PAYMENT_RULES,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_RULES stores 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 ,  implementation_dba_data: IBY.IBY_PAYMENT_RULES , 

  • Table: IBY_PAYMENT_RULES 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_RULES,  object_name:IBY_PAYMENT_RULES,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_PAYMENT_RULES , 

  • Table: IBY_RULE_CONDITIONS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_RULE_CONDITIONS,  object_name:IBY_RULE_CONDITIONS,  status:VALID,  product: IBY - Payments ,  description: 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 operat ,  implementation_dba_data: IBY.IBY_RULE_CONDITIONS , 

  • Table: IBY_RULE_CONDITIONS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_RULE_CONDITIONS,  object_name:IBY_RULE_CONDITIONS,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_RULE_CONDITIONS , 

  • Table: IBY_PAYMENT_METHODS_B 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_B , 

  • Table: IBY_PAYMENT_METHODS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_B ,