Results for “iby_ext_fd_payee_1_0_v”

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

Overview

IBY_EXT_FD_PAYEE_1_0_V is a seeded Oracle EBS database view owned by the APPS schema and shipped as part of the IBY (Payments) product. It exists to support external payment formatting and extraction flows — the naming convention EXT_FD designates it as an outbound feed view used by the Payments extract framework to publish payee (supplier/party) details in a flat, integration-ready shape. The view consolidates payment, supplier, and trading-partner attributes into a single denormalized row per payment, so that downstream payment files, XML messages, or bank-format extracts can be produced without joining the underlying transactional tables directly.

In both 12.1.1 and 12.2.2 the object carries a VALID status, and its documented dependencies confirm that it is a reporting and integration facade rather than a base data store. The inclusion of the ALTERNATE_NAME column is significant for searches on that term: it is the view's derived "doing-business-as" or phonetic alternate representation of the payee name, and it is computed at runtime rather than stored in any single base table.

Underlying Base Objects

The view is defined over a fixed join graph documented in the ETRM 12.2.2 metadata:

• IBY_PAYMENTS_ALL (synonym) — the driving table, supplying PAYMENT_ID, SUPPLIER_SITE_ID, PARTY_SITE_ID, PAYEE_PARTY_ID, and REMIT_TO_LOCATION_ID.
• PO_VENDORS (view) — supplies VENDOR_ID, SEGMENT1, CUSTOMER_NUM, and the vendor-level fallback for tax/legal registration.
• PO_VENDOR_SITES_ALL (view) — supplies VENDOR_SITE_CODE, VENDOR_SITE_CODE_ALT, and COUNTRY.
• HZ_PARTIES (synonym) — the Trading Community Architecture (TCA) party record, source of PARTY_NUMBER, PARTY_NAME, PARTY_TYPE, the phonetic name attributes, and ATTRIBUTE_CATEGORY.
• HZ_PARTY_SITES (synonym) — supplies PARTY_SITE_NAME for the site display value.
• AR_LOOKUPS (view) — restricted to LOOKUP_TYPE = 'PARTY_TYPE' to translate the party type code into a meaning.
• IBY_FD_EXTRACT_GEN_PVT (package) — invoked through GET_PAYEE_TAXREGISTRATION and GET_PAYEE_LEGALREGISTRATION to derive regulatory registration numbers at query time.
• FND_GLOBAL (package) — referenced for session/application context resolution within the extract framework.

The join to PO_VENDOR_SITES_ALL and PO_VENDORS is outer (+), reflecting the design assumption that a payee party may exist with more than one vendor, so the vendor is reached through the supplier site rather than directly from the party. This is explicitly noted in the view text comment attributed to the original development team.

Key Columns

• PAYMENT_ID — primary linkage to the payment record in IBY_PAYMENTS_ALL.
• PARTY_ID, PARTY_NUMBER, PARTY_NAME — TCA party identity of the payee.
• ALTERNATE_NAME — derived via DECODE on PARTY_TYPE: for organizations it returns ORGANIZATION_NAME_PHONETIC; for persons it concatenates PERSON_FIRST_NAME_PHONETIC and PERSON_LAST_NAME_PHONETIC.
• VENDOR_ID, VENDOR_SITE_ID, SUPPLIER_NUMBER — the AP supplier identity associated with the payment.
• SITE_NAME / ALTERNATE_SITE_NAME — NVL of the party site name or vendor site code, plus the vendor site alternate code.
• PARTY_TYPE / PARTY_TYPE_MEANING — coded and decoded party classification (e.g., ORGANIZATION, PERSON).
• TAX_REGISTRATION_NUMBER / LE_REGISTRATION_NUMBER — values returned by the extract private package functions.
• PARTY_ATTR_CAT, PAYMENT_LOCATION_ID, CUSTOMER_NUM — supporting context for formatting and bank routing.

Common Use Cases and Queries

The view is typically consumed to build payment output files and to audit the payee details that will appear on those files. A representative query retrieving payee identity and alternate name is:

• SELECT payment_id, party_name, alternate_name, supplier_number FROM apps.iby_ext_fd_payee_1_0_v WHERE payment_id = :p_payment_id;
• SELECT party_id, party_name, alternate_name FROM apps.iby_ext_fd_payee_1_0_v WHERE UPPER(alternate_name) LIKE UPPER(:p_search || '%'); — used when searching payees by their phonetic or alternate name.
• SELECT vendor_id, supplier_number, site_name, tax_registration_number FROM apps.iby_ext_fd_payee_1_0_v WHERE supplier_site_id = :p_site_id; — for validating regulatory registration data before payment file generation.

Because ALTERNATE_NAME and the registration numbers are computed through DECODE logic and PL/SQL package calls, filtering on them is best done after the extract framework has produced rows, and the view should be treated as read-only reference data for reconciliation and troubleshooting rather than as a transactional source.