Results for “iby_xml_fd_payer_1_0_v”

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

Overview

The view APPS.IBY_XML_FD_PAYER_1_0_V is a Payments (IBY) module database object that generates an XML representation of payer information for use in Oracle Payments funds capture and funds disbursement processing. It is one of the standard XML extraction views delivered with Oracle E-Business Suite Releases 12.1.1 and 12.2.2, and it is used to produce structured payer payloads that conform to the ISO 20022 / XML payment message format defined within the Payments architecture.

The view's principal role is to assemble payer-related data — party identity, legal entity identity, address, tax and legal registration numbers, contact information, and descriptive flexfield content — into a single XMLTYPE value per payer. Downstream Payment Instruction and Payment Process Request processing consumes this XML to transmit payer details to payment systems, banks, or external clearing networks. A recurring search term associated with this view is xle_entity_profiles_b, which reflects that the view depends on the legal entity definition stored in that table when generating the legal entity descriptive flexfield fragment.

Underlying Base Objects

The documented base objects referenced by IBY_XML_FD_PAYER_1_0_V are:

• IBY_EXT_FD_PAYER_1_0_V (VIEW) — the primary extraction view supplying payer and legal entity attributes used in the outer SELECT.
• IBY_XML_HR_ADDR_1_0_V (VIEW) — joined on PAYER.LE_LOCATION_ID = XML_HR_ADDR.LOCATION_ID to supply the formatted address XML fragment.
• IBY_EXTRACTGEN_PVT (PACKAGE) — provides the GET_DFFS function used to render descriptive flexfield content for both HZ_PARTIES and XLE_ENTITY_PROFILES_B.
• IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — provides GET_PAYERCONTACT(PARTY_ID), which returns the payer contact information fragment.
• XMLTYPE (TYPE) — the datatype of the generated payer XML document.

Notably, the flexfield extraction path references XLE_ENTITY_PROFILES_B as the source entity for legal entity DFF attributes, linking the Payments XML output directly to the Legal Entity (XLE) configuration stored in that table. This confirms the view's position at the intersection of Payments, Trading Community Architecture (HZ), and Legal Entity (XLE) data models.

Key Columns

The view exposes a narrow set of structural columns over which the XML document is built:

• PAYER — the inline alias for the joined IBY_EXT_FD_PAYER_1_0_V rowset, the source of all payer/legal entity attributes.
• PARTY_ID — the HZ_PARTIES party identifier of the payer; used as the key for descriptive flexfield extraction and contact information lookup.
• LEGAL_ENTITY_ID — the identifier of the legal entity associated with the payer; used for the XLE_ENTITY_PROFILES_B DFF extraction.

Within the generated XML document, the element structure comprises PAYERINTERNALID, PARTYNUMBER, NAME, PARTYTYPE (CODE and MEANING), TAXREGISTRATIONNUMBER, LEGALREGISTRATIONNUMBER, PARTYDESCRIPTIVEFLEXFIELD, LEGALENTITYINTERNALID, LEGALENTITYNAME, ADDRESS, CONTACTINFO, and LEDESCRIPTIVEFLEXFIELD. Each element is conditionally emitted, and the DFF elements are suppressed when the corresponding attribute category is null.

Common Use Cases and Queries

This view is typically queried to inspect or debug the XML payload produced for a given payer, particularly during implementation of funds capture or disbursement formats. A representative query is:

• SELECT PAYER.PARTY_ID, PAYER.LEGAL_ENTITY_ID FROM APPS.IBY_XML_FD_PAYER_1_0_V — to list payers with their legal entities.
• Filtering by a specific party: SELECT * FROM APPS.IBY_XML_FD_PAYER_1_0_V WHERE PARTY_ID = :p_party_id.
• Extracting the XML for validation against the target payment format by selecting the XMLTYPE result and applying XMLTYPE.getClobVal().

Because the view relies on packaged functions for DFF and contact generation, performance-sensitive queries should minimise row counts and avoid unnecessary function invocations. The view is not intended for high-volume direct reporting but rather as an internal extraction component of the Payments XML generation pipeline.