Search Results payee_subkey_id

Overview

The IBY_PAYEE_SUBKEYS table is a core data object within the Oracle E-Business Suite Payments (IBY) module. It functions as a repository for subkey values associated with payees, which are typically financial institutions. In the context of electronic funds transfer (EFT) and other automated payment methods, a subkey provides an additional, often mandatory, identifier beyond a standard account number. This identifier is frequently used to specify a particular branch, location, or department within a payee's financial institution. The table's primary role is to store and manage these critical routing or qualifying details, ensuring accurate and successful payment processing by linking subkey definitions to their corresponding master payee records in the IBY_PAYEE table.

Key Information Stored

The central piece of information stored is the subkey value itself, linked to its parent payee. While the provided metadata does not list all columns, the documented primary and foreign keys reveal the essential structural data. The PAYEE_SUBKEY_ID column serves as the unique primary key for each subkey record. The MPAYEE_ID column is a foreign key that establishes the critical link to the IBY_PAYEE table, identifying the master payee to which this subkey belongs. Additional columns, typical for such a table, would store the actual subkey value, its type or format, and control attributes like start and end dates to manage its validity period.

Common Use Cases and Queries

This table is central to payment setup and transaction validation. A common operational use case is the validation of payment instructions during payment process request submission, where the system verifies that a provided subkey is valid and active for the specified payee. For reporting and troubleshooting, queries often join this table to the master payee information. A fundamental query pattern retrieves all active subkeys for a specific payee or financial institution:

• SELECT p.party_name, ps.subkey_value FROM iby_payee_subkeys ps, iby_payee p WHERE ps.mpayee_id = p.payee_id AND p.party_id = :supplier_party_id AND SYSDATE BETWEEN ps.start_date AND NVL(ps.end_date, SYSDATE);

Another critical use case involves investigating payment transactions, requiring a join to the IBY_TRXN_SUMMARIES_ALL table to see which specific transactions utilized a given subkey.

Related Objects

The IBY_PAYEE_SUBKEYS table sits at the center of a key relationship hierarchy within the Payments data model, as confirmed by the provided foreign key metadata.

• IBY_PAYEE: This is the parent table. The MPAYEE_ID column in IBY_PAYEE_SUBKEYS references the IBY_PAYEE table, linking each subkey to its master payee definition.
• IBY_TRXN_SUMMARIES_ALL: This is a child table. The SUB_KEY_ID column in IBY_TRXN_SUMMARIES_ALL references the PAYEE_SUBKEY_ID in IBY_PAYEE_SUBKEYS. This relationship documents which subkey was used for an individual payment transaction summary, making it vital for payment audit trails and reconciliation.