Results for “ece_tp_location_code”

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

Overview

The IBY_EXTERNAL_PAYEES_V view is a reporting and integration layer owned by the APPS schema within the Oracle Payments (IBY) module. It exposes a single-row-per-payee projection of the external payee configuration that drives payment processing in Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, Oracle Payments acts as the central payment engine shared by Payables, Receivables, Payroll, and other subledgers; the external payee record captured here defines how a trading partner is paid, including the payment function, the default payment method, delivery channel, payment format, bank charge bearer, and settlement priority. Because the view is delivered as a standard APPS object, it is safe to query directly from SQL*Plus, Oracle Reports, BI Publisher data templates, and custom concurrent programs without requiring the caller to hold privileges on the underlying transactional table. It is treated as a read-only reporting object: the view performs no transformation beyond column selection, so it faithfully represents the row as stored, and it inherits the multi-org (ORG_ID) security context of its base object.

Underlying Base Objects

The view is defined over the synonym IBY_EXTERNAL_PAYEES_ALL. The _ALL suffix confirms that the base object is an Oracle Multi-Org (partitioned) table, keyed in part by ORG_ID. The view text is a straightforward projection: it selects PAYEE.EXT_PAYEE_ID, PAYEE.PAYEE_PARTY_ID, and the remaining payee attributes directly from the synonym, aliased as PAYEE. No joins, filters, or functions are applied, so the view returns exactly the rows present in the base table, restricted only by any row-level security that the _ALL synonym and the Multi-Org views layered beneath it enforce. Internally, IBY_EXTERNAL_PAYEES_ALL references the TCA party model (HZ_PARTIES, HZ_PARTY_SITES) through the party and party-site identifiers it carries, and it links to supplier sites in the Payables schema via SUPPLIER_SITE_ID. Because the view contains no DISTINCT or aggregate, expected cardinality is one row per external payee (per operating unit where the base object is org-partitioned).

Key Columns

• EXT_PAYEE_ID — Primary identifier for the external payee record; the join key to downstream payment and payee-usage tables.
• PAYEE_PARTY_ID, PARTY_SITE_ID, SUPPLIER_SITE_ID — Party, party-site, and supplier-site identifiers linking the payee to TCA and Payables entities.
• ORG_ID, ORG_TYPE — Operating unit and its classification, establishing the Multi-Org context.
• PAYMENT_FUNCTION — The role the payee plays for payment purposes (for example, payee, payer, or both).
• DEFAULT_PAYMENT_METHOD_CODE, PAYMENT_FORMAT_CODE, DELIVERY_CHANNEL_CODE — The default disbursement method, the payment instruction format, and the delivery channel used to transmit payment instructions.
• BANK_CHARGE_BEARER, BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE, BANK_INSTRUCTION_DETAILS — Bank charge allocation and free-format bank instructions passed to the payment system.
• SETTLEMENT_PRIORITY — The ordering attribute that governs the sequence in which payments for the payee are settled; it is the column most frequently targeted in searches on this object and is central to payment-batching and settlement-ordering logic.
• PAYMENT_REASON_CODE, PAYMENT_REASON_COMMENTS, PAYMENT_TEXT_MESSAGE1–3 — Reason and remittance text carried onto the payment.
• EXCLUSIVE_PAYMENT_FLAG, INACTIVE_DATE, ECE_TP_LOCATION_CODE — Exclusivity indicator, deactivation date, and the e-commerce trading-partner location code respectively.

Common Use Cases and Queries

Typical uses include auditing payee payment setup, identifying inactive or expiring payees, and sorting/grouping payees by settlement priority before settlement runs. A common query filters on SETTLEMENT_PRIORITY to review the settlement ordering assigned to active payees:

• SELECT ext_payee_id, payee_party_id, payment_function, default_payment_method_code, settlement_priority FROM iby_external_payees_v WHERE inactive_date IS NULL ORDER BY settlement_priority;
• SELECT p.ext_payee_id, p.party_site_id, p.supplier_site_id, p.settlement_priority, p.bank_charge_bearer FROM iby_external_payees_v p WHERE p.org_id = :org_id AND p.settlement_priority IS NOT NULL;
• SELECT payment_function, COUNT(*) FROM iby_external_payees_v GROUP BY payment_function;

These patterns support reconciliation against payment process requests, data conversion validation, and ad-hoc extracts for integration with external payment systems. Because the view underpins the Oracle Payments payee model, joins are usually made back to IBY_EXTERNAL_PAYEES_ALL for write operations and to IBY_PAYMENTS_ALL and IBY_PAY_INSTRUCTIONS_ALL for payment history. All queries should be restricted by operating unit to respect Multi-Org security. Oracle Proprietary, Confidential Information — Legal Notices apply.