Search Results iby_pmtmthd_conditions




Overview
Explore in AI Chat

Overview

The IBY_PMTMTHD_CONDITIONS table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the repository for conditional logic rules that govern the dynamic selection of payment methods during the payment process execution. The table's primary role is to store the granular criteria—composed of a parameter, an operator, and a comparison value—that the Payments engine evaluates at runtime. This evaluation determines whether a specific payment method is applicable for a given transaction, enabling sophisticated, rule-based payment routing and method assignment based on real-time business data.

Key Information Stored

The table stores each condition as a discrete record, uniquely identified by a composite primary key. The most critical columns define the condition's logic and its association with a specific payment method rule. The PAYMENTMETHODID column is a foreign key that links the condition to its parent payment method definition in the IBY_ROUTINGINFO table. The ENTRY_SEQUENCE allows for ordering multiple conditions within a single rule. The core of the condition is defined by three columns: PARAMETER_CODE (the data element being evaluated, such as payment amount or invoice currency), OPERATION_CODE (the logical operator, such as 'EQUALS' or 'GREATER_THAN'), and VALUE (the target value for comparison). Together, these columns form the executable rule that the Payments engine processes.

Common Use Cases and Queries

A primary use case is troubleshooting payment method assignments. For instance, if a payment is unexpectedly assigned an incorrect method, a consultant would query the conditions tied to the involved payment methods to verify the logic. Common reporting needs include documenting the complete set of payment rules for audit purposes or analyzing conditions for potential conflicts. A typical diagnostic query would join to the routing information table to get a readable summary of all conditions for a specific payment method.

SELECT r.payment_method_code,
       c.entry_sequence,
       c.parameter_code,
       c.operation_code,
       c.value
FROM   iby.iby_pmtmthd_conditions c,
       iby.iby_routinginfo r
WHERE  c.paymentmethodid = r.paymentmethodid
AND    r.payment_method_code = 'CHECK'
ORDER BY c.entry_sequence;

This query helps validate that conditions like "Payment Currency equals USD" and "Payment Amount less than 10000" are correctly configured for the 'CHECK' payment method.

Related Objects

  • IBY_ROUTINGINFO: This is the primary parent table. The foreign key relationship IBY_PMTMTHD_CONDITIONS.PAYMENTMETHODID → IBY_ROUTINGINFO ensures every condition is associated with a valid payment method rule. This table holds the high-level definition of the payment method, which the conditions further qualify.
  • The table's integrity is enforced by the primary key constraint IBY_PMTMTHD_CONDITIONS_UK on the columns (PAYMENTMETHODID, ENTRY_SEQUENCE, PARAMETER_CODE, OPERATION_CODE). This guarantees the uniqueness of each condition component within a payment method rule.