Results for “xle_firstparty”

8 results




Overview
Explore in AI Chat

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

Overview

The view APPS.IBY_EXT_FD_PAYER_1_0_V is a payables-related extraction view within the Oracle Payments (IBY) module of Oracle E-Business Suite. It exposes first-party payer information in a flattened, denormalized form suitable for external reporting, data warehouse extraction, and integration with third-party financial or treasury systems. The naming convention "EXT_FD" indicates it is part of the Payments Extract Foundation layer used by the Payments data model, while the "1_0" suffix denotes version 1.0 of the interface contract.

The view joins first-party legal entity information against the Oracle Trading Community Architecture (TCA) party tables to produce a payer record enriched with the decoded party type. It is one of a family of IBY_EXT_FD views that publish payer, payee, and payment data to downstream consumers. Because the party type is decoded through the party_type_lookup join, records returned by this view carry a human-readable meaning rather than only the raw lookup code.

Underlying Base Objects

Per the documented metadata, the view is defined as the join of three base objects and invokes one PL/SQL function:

  • XLE_FIRSTPARTY_INFORMATION_V (VIEW) — The first-party legal entity view from the Legal Entity (XLE) module. Supplies legal_entity_id, registration_number, name, location_id, and attribute_category. This is the driving source of the payer (first-party) records.
  • HZ_PARTIES (SYNONYM) — The TCA party master, providing party_id, party_number, party_name, party_type, and attribute_category. Joined on xle_firstparty.party_id = party.party_id.
  • AR_LOOKUPS (VIEW) — The Receivables lookup view, aliased party_type_lookup. Joined where party.party_type = party_type_lookup.lookup_code and party_type_lookup.lookup_type = 'PARTY_TYPE'. This resolves the party type code to its descriptive meaning.
  • IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — The Payments extract generation package. Its function Get_FP_TaxRegistration(legal_entity_id) derives the first-party tax registration value returned as an unaliased expression column.

Because the view spans legal entity, TCA, and lookup data, it presupposes that the first party has been created in TCA and associated with a legal entity record.

Key Columns

  • party_id — Primary key of the TCA party; the join key to first-party legal entity data.
  • party_number and party_name — Trading community identifiers for the payer.
  • party_type — Raw lookup code indicating the party category.
  • party_type_lookup.meaning (exposed as meaning) — Decoded description of the party type, resolved from AR_LOOKUPS where lookup_type='PARTY_TYPE'. This is the column commonly targeted when filtering by party type.
  • Get_FP_TaxRegistration(legal_entity_id) — Tax registration number of the first party, computed at query time by the IBY package function.
  • registration_number, legal_entity_id, name, and location_id — Legal entity attributes of the first party, including the entity name and registered location.
  • attribute_category — Appears twice: once from HZ_PARTIES and once from XLE_FIRSTPARTY_INFORMATION_V.

Common Use Cases and Queries

Typical uses include extraction of first-party payer records into an external payments or regulatory reporting store, selection of legal entities by decoded party type, and retrieval of tax registration numbers per entity.

SELECT party_id,
       party_number,
       party_name,
       party_type,
       meaning,
       registration_number,
       legal_entity_id,
       location_id
FROM   apps.iby_ext_fd_payer_1_0_v;

Filtering by the decoded value, which is the purpose of the party_type_lookup join, follows the pattern below. Note that meaning is the resolved value from AR_LOOKUPS:

SELECT party_id, party_number, party_name, meaning
FROM   apps.iby_ext_fd_payer_1_0_v
WHERE  meaning = 'Organization';

Because one of the projected columns is a PL/SQL function call, runtime cost is higher than a simple join, so queries should filter on indexed attributes such as party_id or legal_entity_id where possible.