Results for “iby_external_payees_all”

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

Overview

IBY_EXTERNAL_PAYEES_ALL is a core Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the payment disposition and disbursement attributes of external payees. An external payee is any party outside the deploying organization—typically a supplier, supplier site, or third-party recipient—for which the Payments infrastructure must record default disbursement instructions. Rows are populated automatically by source products such as Payables when a supplier or supplier site is created or updated; the table is not normally maintained through direct user entry in the Payments screens.

The object is owned by the IBY schema and holds 32 documented columns. Its structure reflects a single payee record with multiple instructional attributes. Based on the foreign key topology, the ETRM metadata classifies IBY_EXTERNAL_PAYEES_ALL as satellite-leaning in a Data Vault model. This is a heuristic classification: the table functions primarily as an attribute-bearing satellite keyed by a single surrogate identifier, with no many-to-many resolution behavior typical of a link table. Consumers modeling this object should treat it as a descriptive satellite attached to a payment-party hub.

Key Information Stored

• EXT_PAYEE_ID — the surrogate primary key (IBY_EXTERNAL_PAYEES_ALL_PK) and the unique business-key candidate (IBY_EXTERNAL_PAYEES_ALL_U1). It is referenced widely by downstream payment and payable tables.
• PAYEE_PARTY_ID and PARTY_SITE_ID — identify the underlying trading party and party site supplied by TCA.
• SUPPLIER_SITE_ID — links the payee to the corresponding supplier site in the Payables model.
• ORG_ID and ORG_TYPE — establish the operating unit and entity type context, supporting multi-org security.
• PAYMENT_FUNCTION and EXCLUSIVE_PAYMENT_FLAG — define the payee's role in payment run selection and whether the payee is restricted to a single payment function.
• DEFAULT_PAYMENT_METHOD_CODE — the default disbursement method, constrained by a foreign key to IBY_PAYMENT_METHODS_B.
• BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE, and BANK_INSTRUCTION_DETAILS — supplementary banking instructions carried on the payment.
• PAYMENT_REASON_CODE and PAYMENT_REASON_COMMENTS — standard reason and free-text commentary for the payment.
• PAYMENT_FORMAT_CODE, DELIVERY_CHANNEL_CODE, and SETTLEMENT_PRIORITY — govern output formatting, routing, and settlement sequencing.
• REMIT_ADVICE_DELIVERY_METHOD, REMIT_ADVICE_EMAIL, and REMIT_ADVICE_FAX — control remittance advice distribution.

Standard auditing columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and INACTIVE_DATE round out the structure.

Common Use Cases and Queries

The table supports payment run selection, remittance processing, and supplier payment setup auditing. A typical query retrieves disbursement attributes for a supplier site:

• SELECT p.EXT_PAYEE_ID, p.SUPPLIER_SITE_ID, p.DEFAULT_PAYMENT_METHOD_CODE, p.PAYMENT_FORMAT_CODE FROM IBY_EXTERNAL_PAYEES_ALL p WHERE p.ORG_ID = :org_id AND p.INACTIVE_DATE IS NULL;

Reporting uses include identifying payees with incomplete payment setup (missing method or format), analyzing payees by delivery channel or settlement priority, and reconciling payment records back to their payee definition by joining IBY_PAYMENTS_ALL on EXT_PAYEE_ID. Integration teams frequently query this table when troubleshooting why a payment selected an unexpected format or remittance method.

Related Objects

• IBY_PAYMENTS_ALL and IBY_PAYMENTS_H — join on EXT_PAYEE_ID to associate issued payments with their payee definition.
• IBY_DOCS_PAYABLE_ALL and IBY_DOCUMENTS_PAYABLE_H — join on EXT_PAYEE_ID to link payable documents to the external payee.
• FV_TPP_ASSIGNMENTS_ALL — join on EXT_PAYEE_ID for third-party payment assignments.
• IBY_EXT_PARTY_PMT_MTHDS — linked via EXT_PMT_PARTY_ID for payee payment method detail.
• IBY_PAYMENT_METHODS_B, IBY_DELIVERY_CHANNELS_B, and IBY_BANK_INSTRUCTIONS_B — referenced through DEFAULT_PAYMENT_METHOD_CODE, DELIVERY_CHANNEL_CODE, and the BANK_INSTRUCTION codes respectively.

These relationships confirm the table's central role as the payment-attribute satellite for external payees across Payables and Payments processing.