Results for “iby_external_payers_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_EXTERNAL_PAYERS_ALL is the Payments (IBY) module table that registers external payers — parties, customer accounts, or account site uses that are authorized to act as the paying entity for a funds capture transaction. In Oracle EBS Release 12.1.1 and 12.2.2, this table underpins externally initiated payment instruments such as direct debits, bank transfers, and debit-advice driven collections processed through Oracle Payments. Each row associates a payer identity from the Trading Community Architecture (HZ) model with a payment function and, optionally, the operational context (operating unit organization and organization type) that governs how that payer participates in a funding instruction.

The primary key of the table is IBY_EXTERNAL_PAYERS_ALL_PK, defined on EXT_PAYER_ID, which matches the user's search term. Based on the foreign-key topology documented in the ETRM metadata, a heuristic Data Vault classification of this object is a link: it connects reference hubs (HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL) to a payment-function context, rather than functioning as a standalone hub or descriptive satellite.

Key Information Stored

The table is documented with 18 columns. The most significant are:

• EXT_PAYER_ID — surrogate primary key and the unique identifier for an external payer record (unique index IBY_EXTERNAL_PAYERS_ALL_U1).
• PAYMENT_FUNCTION — the functional role of the external payer within funds capture processing.
• PARTY_ID — foreign key to HZ_PARTIES, identifying the party that serves as the payer.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS, identifying the customer account tied to the payer.
• ACCT_SITE_USE_ID — foreign key to HZ_CUST_SITE_USES_ALL, identifying the specific site use (for example, a bill-to or statement site) associated with the payer.
• ORG_TYPE and ORG_ID — the organization type and operating unit context that qualify the payer relationship.
• BANK_CHARGE_BEARER_CODE — indicates which party (payer, payee, or shared) bears bank charges.
• DIRDEB_INSTRUCTION_CODE — the direct debit instruction code governing collection behavior.
• DEBIT_ADVICE_DELIVERY_METHOD, DEBIT_ADVICE_EMAIL, and DEBIT_ADVICE_FAX — the delivery method and contact endpoints for debit advices issued to the payer.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard Who-column audit and optimistic-locking attributes.

The unique index IBY_EXTERNAL_PAYERS_ALL_U2 on (PARTY_ID, PAYMENT_FUNCTION, ORG_ID, ORG_TYPE, CUST_ACCOUNT_ID, ACCT_SITE_USE_ID) is the documented business-key candidate, confirming that a given payer identity cannot be duplicated for the same payment function and organizational context.

Common Use Cases and Queries

Typical scenarios include validating that a direct debit authorization maps to a registered external payer, reporting all payers configured for a given customer, and diagnosing funds capture failures caused by missing or misconfigured payer records.

• Resolving a payer identifier to its HZ identity: join EXT_PAYER_ID to PARTY_ID, CUST_ACCOUNT_ID, and ACCT_SITE_USE_ID to retrieve party, account, and site details.
• Auditing debit advice configuration: select DEBIT_ADVICE_DELIVERY_METHOD, DEBIT_ADVICE_EMAIL, and DEBIT_ADVICE_FAX for each external payer to verify notification routing.
• Reporting by operating unit: filter and group on ORG_ID and ORG_TYPE to produce payer counts per business unit and payment function.
• Detecting duplicates or overlaps: query on the U2 column set (PARTY_ID, PAYMENT_FUNCTION, ORG_ID, ORG_TYPE, CUST_ACCOUNT_ID, ACCT_SITE_USE_ID) to confirm business-key uniqueness before data loads or conversions.
• Cross-referencing transaction extensions: join to IBY_FNDCPT_TX_EXTENSIONS on EXT_PAYER_ID to determine which funds capture transactions were associated with each payer.

A representative query pattern is: select p.EXT_PAYER_ID, p.PAYMENT_FUNCTION, p.PARTY_ID, p.CUST_ACCOUNT_ID, p.ORG_ID from IBY_EXTERNAL_PAYERS_ALL p where p.PARTY_ID = :party_id. Because the table name carries the _ALL suffix, it follows the multi-org convention and queries should honor the appropriate ORG_ID security context in 12.1.1 and 12.2.2 environments.

Related Objects

• HZ_PARTIES — referenced via IBY_EXTERNAL_PAYERS_ALL.PARTY_ID; supplies the payer's party identity.
• HZ_CUST_ACCOUNTS — referenced via IBY_EXTERNAL_PAYERS_ALL.CUST_ACCOUNT_ID; supplies the customer account context.
• HZ_CUST_SITE_USES_ALL — referenced via IBY_EXTERNAL_PAYERS_ALL.ACCT_SITE_USE_ID; supplies the specific site use.
• IBY_FNDCPT_TX_EXTENSIONS — references IBY_EXTERNAL_PAYERS_ALL.EXT_PAYER_ID; links funds capture transactions to their external payer.
• IBY_EXTERNAL_PAYERS_ALL_PK / U1 / U2 — the primary and unique indexes enforcing record identity and business-key integrity on EXT_PAYER_ID and the composite business key.

Together these objects form the reference framework through which Oracle Payments resolves external payers during funds capture processing.