Search Results iby_pmt_mthd_attrib_appl_pk

Overview

The table IBY_PMT_MTHD_ATTRIB_APPL is a core configuration table within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as a junction table that defines the valid attributes for a specific payment method within a specific payment flow. This table is essential for enforcing business rules and ensuring data integrity during the payment process setup. It acts as a master list, controlling which configurable attributes (e.g., bank account, payment format, remittance delivery method) are applicable and required when a user assigns a payment method to a payee or a payment instruction. Its primary role is to govern the setup and validation of payment methods across different payment flows, such as disbursements (outbound) or receipts (inbound).

Key Information Stored

The table's structure is defined by its composite primary key, which consists of three critical columns. The PAYMENT_FLOW column identifies the direction of the payment, typically holding values like 'DISBURSEMENTS' for outgoing payments or 'RECEIPTS' for incoming funds. The PAYMENT_METHOD_CODE column stores the internal code for a payment instrument, such as 'CHECK', 'WIRE', or 'EFT'. The ATTRIBUTE_CODE column holds the code for a specific configurable attribute that must be defined for the given payment method and flow, examples include 'BANK_ACCOUNT_ID' or 'PAYMENT_FORMAT_CODE'. Together, each unique combination in this table authorizes a single attribute for use with a specific payment method in a specific context.

Common Use Cases and Queries

A primary use case is validating and troubleshooting payment method setup. For instance, if a specific attribute is not appearing as expected during payee assignment in the Payment Manager, a query against this table can confirm if the attribute is registered for the relevant payment method and flow. System administrators and implementers use this table to understand the complete set of attributes required to make a payment method functional. A typical diagnostic query would be:

• SELECT attribute_code FROM iby_pmt_mthd_attrib_appl WHERE payment_flow = 'DISBURSEMENTS' AND payment_method_code = 'CHECK';

This returns all attributes applicable to the Check payment method for disbursements. Reporting use cases often involve joining this table to descriptive views like IBY_PAYMENT_METHODS_TL and IBY_ATTRIBUTES_TL to generate user-friendly setup documentation or validation lists for data migration.

Related Objects

This table is central to the Payments data model and has key relationships with other master tables. It references the payment method definition via the PAYMENT_METHOD_CODE column, typically joining to IBY_PAYMENT_METHODS_B. It references the attribute definition via the ATTRIBUTE_CODE column, joining to IBY_ATTRIBUTES_B. The primary purpose of these foreign key relationships is to validate that the codes stored are legitimate. Furthermore, this table is directly referenced by setup tables that store the actual values for these attributes, such as IBY_PMT_MTHD_ATTRIBUTES, which holds the specific attribute values assigned to a payee's payment method. The relationship is enforced by the primary key IBY_PMT_MTHD_ATTRIB_APPL_PK on the columns (PAYMENT_FLOW, PAYMENT_METHOD_CODE, ATTRIBUTE_CODE).