Search Results iby_account_owners

Overview

The IBY_ACCOUNT_OWNERS table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as a critical junction table that establishes and manages the relationship between external bank accounts and the legal entities or parties that own them. This table is fundamental to the payment processing architecture, enabling the system to correctly attribute bank accounts to specific business entities, such as operating units, legal entities, or suppliers, for payment initiation, receipt application, and bank account validation. Its integrity is essential for ensuring payments are sourced from and directed to the appropriate, authorized accounts.

Key Information Stored

The table's primary function is to link a bank account identifier with a party identifier. The key columns, as indicated by its foreign key relationships, are EXT_BANK_ACCOUNT_ID and ACCOUNT_OWNER_PARTY_ID. The ACCOUNT_OWNER_ID column serves as the table's unique primary key. While the provided metadata does not list all columns, the structure implies the table stores the association record itself, likely including control columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY for auditing purposes. The ACCOUNT_OWNER_PARTY_ID typically references a record in the HZ_PARTIES table, which represents a legal entity, organization, or person within the Trading Community Architecture (TCA).

Common Use Cases and Queries

A primary use case is validating and reporting on bank account ownership during payment setup or inquiry. For instance, when configuring a payment process profile, the system validates that the specified disbursement bank account is owned by the correct legal entity. Common queries involve joining to related tables to retrieve a comprehensible list of bank accounts and their owners. A typical reporting pattern would be:

• Identifying all bank accounts owned by a specific legal entity for audit purposes.
• Listing party details for all owners of a given external bank account.
• Troubleshooting payment failures related to invalid account-party associations.

A sample SQL pattern to retrieve account and owner information is:
SELECT iao.account_owner_id, eba.bank_account_name, hp.party_name
FROM iby_account_owners iao,
iby_ext_bank_accounts eba,
hz_parties hp
WHERE iao.ext_bank_account_id = eba.ext_bank_account_id
AND iao.account_owner_party_id = hp.party_id;

Related Objects

The IBY_ACCOUNT_OWNERS table maintains defined relationships with other key EBS tables, as per the provided metadata. Its foreign keys establish its role as a dependent entity linking two master data sources.

• IBY_EXT_BANK_ACCOUNTS: Linked via the column IBY_ACCOUNT_OWNERS.EXT_BANK_ACCOUNT_ID. This is the master table storing detailed bank account information (account number, currency, bank branch, etc.).
• HZ_PARTIES: Linked via the column IBY_ACCOUNT_OWNERS.ACCOUNT_OWNER_PARTY_ID. This is the central TCA table storing information about all parties (organizations, people, groups) known to the system.

The table itself is referenced by its primary key, ACCOUNT_OWNER_ID, though the specific dependent tables are not listed in the provided excerpt. In a typical Payments implementation, this ownership record is crucial for downstream processes in Payables (AP), Receivables (AR), and Treasury.