Results for “iby_xml_fndcpt_payee_1_0_v”

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

Overview

IBY_XML_FNDCPT_PAYEE_1_0_V is a PL/SQL-based XML view owned by the APPS schema in Oracle E-Business Suite, belonging to the IBY (Payments) product family. It exposes structured payee information as an XMLType document, generated at query time through Oracle SQL/XML functions. The view operates in conjunction with FNDCPT (Funds Capture) payment processing, where payee details are consumed by outbound XML generation and integration flows.

The view produces one row per payee, with each row carrying a concatenated XML document (XML_PAYEE) alongside two scalar identifiers: PARTY_ID and LEGAL_ENTITY_ID. The presence of the "1_0" suffix indicates the version 1.0 XML schema for the Funds Capture payee message; the corresponding object name IBY_XML_FNDCPT_PAYEE_1_0_V makes this explicit.

The view is marked VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. It belongs to the family of IBY XML extraction views that support funds capture, payment settlement, and payee communication with external payment systems and banks.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following documented base objects:

• IBY_EXT_FD_PAYER_1_0_V — the primary driving view, supplying party, legal entity, tax registration, and address location attributes. Joined by PAYEE.LE_LOCATION_ID = XML_HR_ADDR.LOCATION_ID.
• IBY_XML_HR_ADDR_1_0_V — supplies the formatted HR address XML fragment via XML_HR_ADDR.ADDRESS.
• IBY_EXTRACTGEN_PVT — package invoked to resolve descriptive flexfields via GET_DFFS for HZ_PARTIES and XLE_ENTITY_PROFILES_B.
• IBY_FD_EXTRACT_GEN_PVT — Funds Capture extraction generator package linked to the extract framework.
• XMLTYPE — Oracle built-in type used to materialize the concatenated XML document.

The view text uses XMLCONCAT and nested XMLELEMENT calls to assemble the payee XML structure from these sources. Conditional CASE expressions suppress party and legal entity flexfield elements when the corresponding attribute category is null.

Key Columns

• XML_PAYEE (XMLTYPE) — the assembled payee XML document. Contains the elements PARTYINTERNALID, PARTYNUMBER, NAME, PARTYTYPE (with nested CODE and MEANING), TAXREGISTRATIONNUMBER, LEGALREGISTRATIONNUMBER, optional PARTYDESCRIPTIVEFLEXFIELD, LEGALENTITYINTERNALID, LEGALENTITYNAME, ADDRESS, and optional LEDESCRIPTIVEFLEXFIELD.
• PARTY_ID — the internal identifier of the payee party, sourced from PAYEE.PARTY_ID and echoed as a top-level scalar for relational joins.
• LEGAL_ENTITY_ID — the identifier of the legal entity associated with the payee, echoed as a scalar for filtering and joins.

The scalar columns allow reference without parsing the XMLType, which is useful when joining to HZ_PARTIES or XLE_ENTITY_PROFILES_B.

Common Use Cases and Queries

Typical scenarios include: generating Funds Capture payee messages for transmission to payment processors, extracting payee party and legal entity data for reconciliation, and pulling payee descriptive flexfield content into downstream XML payloads.

Sample query retrieving the XML and identifiers for a specific payee:

• SELECT party_id, legal_entity_id, XML_PAYEE FROM apps.iby_xml_fndcpt_payee_1_0_v WHERE party_id = :p_party_id;

Sample query extracting individual XML element values:

• SELECT x.party_id, EXTRACTVALUE(t.column_value, '//NAME') name FROM apps.iby_xml_fndcpt_payee_1_0_v x, TABLE(XMLSEQUENCE(EXTRACT(x.XML_PAYEE, '/PAYEE'))) t;

Because the view invokes IBY_EXTRACTGEN_PVT.GET_DFFS, queries returning flexfield elements can be more expensive; filtering by PARTY_ID or LEGAL_ENTITY_ID before projecting XML_PAYEE is recommended for performance.