Search Results iby_payee_pk

Overview

The IBY_PAYEE table is a core data object within the Oracle E-Business Suite Payments (IBY) module, specifically in versions 12.1.1 and 12.2.2. It serves as the master repository for payee information. A payee is defined as any external entity to which the organization makes payments, such as suppliers (billers), merchants, or stores. Each row in this table uniquely identifies a payee at the installation site. The table's primary role is to centralize payee definitions, enabling their association with various payment methods, risk configurations, and transaction processing rules across the Payments module. It is a foundational table that supports the configuration and execution of electronic and printed payment processes.

Key Information Stored

While the provided metadata does not list all columns, the primary and unique key structures reveal critical identifiers. The table uses two key identifiers: the MPAYEEID and the PAYEEID. The MPAYEEID column is the primary key (IBY_PAYEE_PK), serving as the main internal, system-generated identifier for the payee record. The PAYEEID column is governed by a unique key constraint (IBY_PAYEE_UK), representing a distinct business identifier for the payee, likely used for integration and external reference. Another documented column is ECAPPID, which is a foreign key to the IBY_ECAPP table, linking the payee to an Electronic Commerce Application for specific payment processing contexts.

Common Use Cases and Queries

This table is central to payment setup and inquiry operations. Common use cases include configuring payee-specific payment instructions, defining default banking details, and setting up fraud detection rules (IBY Risk Management) for specific merchants. For reporting, it is frequently joined to transaction tables to analyze payment history by payee. A typical query pattern involves joining IBY_PAYEE to transaction summary tables. For example, to list payees with recent payment activity, one might use:

SELECT ip.PAYEEID, ip.MPAYEEID, COUNT(its.TRANSACTION_ID) AS TXN_COUNT
FROM IBY.IBY_PAYEE ip
JOIN IBY.IBY_TRXN_SUMMARIES_ALL its ON ip.MPAYEEID = its.MPAYEEID
WHERE its.TRANSACTION_DATE > SYSDATE - 30
GROUP BY ip.PAYEEID, ip.MPAYEEID;

Another common scenario is querying payee details along with their associated accepted payment methods from the IBY_ACCPPMTMTHD table using the MPAYEEID as the join key.

Related Objects

The IBY_PAYEE table has extensive relationships within the Payments schema, as evidenced by its foreign key constraints. Key related objects include:

• IBY_ECAPP: Linked via IBY_PAYEE.ECAPPID.
• IBY_ACCPPMTMTHD: References IBY_PAYEE.MPAYEEID to define payment methods accepted by a payee.
• IBY_BATCHES_ALL: References IBY_PAYEE.MPAYEEID to associate payment batches with a payee.
• IBY_DEFAULT_BEP: References IBY_PAYEE.MPAYEEID to store a payee's default payment instruction (Bank Account).
• IBY_ROUTINGINFO: References IBY_PAYEE.MPAYEEID for payee-specific payment routing details.
• IBY_TRXN_SUMMARIES_ALL: References IBY_PAYEE.MPAYEEID to summarize transactions per payee.
• Risk Management Objects: Multiple tables (e.g., IBY_RISK_FORMULAS, IBY_IRF_PMT_AMOUNT) reference IBY_PAYEE.PAYEEID to attach fraud detection rules to specific payees.
• IBY_PAYEE_SUBKEYS: References IBY_PAYEE.MPAYEE_ID for storing additional payee identifiers.
• IBY_MAPPINGS: References IBY_PAYEE.PAYEEID for mapping payees to internal entities.