Search Results iby_bepkeys

Overview

The IBY_BEPKEYS table is a core data repository within the Oracle E-Business Suite Payments module (IBY). It functions as the master table for storing and managing payment system accounts. In the context of Oracle Payments, a payment system account represents a specific financial account configured within a Business Entity Processor (BEP), which is the software component that interfaces with an external payment system or financial network. The table's primary role is to maintain a unique registry of these accounts, linking them to their owning entity (such as an operating unit or legal entity) and their associated BEP. This central reference is critical for orchestrating payment flows, ensuring transactions are routed to the correct financial institution and account.

Key Information Stored

The table's structure is designed to enforce uniqueness and define relationships for payment accounts. The primary identifier is BEP_ACCOUNT_ID, a system-generated primary key. The table enforces a unique constraint (IBY_BEPKEYS_UK) on a combination of columns that collectively define a distinct account entry: OWNERID (the identifier of the owning entity, like an ORG_ID), OWNERTYPE (the type of owner, such as 'OPERATING_UNIT'), BEPID (a foreign key to IBY_BEPINFO identifying the payment processor), and KEY (which typically holds the account number or a unique reference for the account within the BEP). This design prevents the configuration of duplicate accounts for the same owner and processor.

Common Use Cases and Queries

A primary use case is troubleshooting payment setup or identifying the accounts configured for a specific entity. For instance, to list all payment accounts for a given operating unit (ID 204), a query would join to the BEP info table for clarity:

• SELECT bk.key AS account_number, bi.bepid, bi.name AS bep_name, bk.ownertype FROM iby.iby_bepkeys bk, iby.iby_bepinfo bi WHERE bk.bepid = bi.bepid AND bk.ownerid = 204 AND bk.ownertype = 'OPERATING_UNIT';

Another common scenario is validating the setup before a payment process request, ensuring the initiating entity has at least one valid account defined for the intended payment method. Administrators may also query this table to audit account usage across the system or to diagnose errors where a payment submission fails due to a missing or misconfigured BEP account reference.

Related Objects

As indicated by its foreign key relationships, IBY_BEPKEYS is a central hub referenced by numerous other payment setup and transaction tables. The IBY_BEPINFO table is a direct parent, providing the processor definition. Crucially, the IBY_ACCT_PMT_PROFILES_B table links payment method profiles to specific accounts in IBY_BEPKEYS. Account-specific optional settings are stored in IBY_BEP_ACCT_OPT_VALS. Default account assignments for various contexts are held in IBY_DEFAULT_BEP. Furthermore, user-level payment instrument profiles for credit cards (IBY_FNDCPT_USER_CC_PF_B), debit cards (IBY_FNDCPT_USER_DC_PF_B), and EFT (IBY_FNDCPT_USER_EFT_PF_B) all reference a BEP account, making IBY_BEPKEYS essential for both supplier and customer payment processing.