Results for “iby_xml_fndcpt_payer_1_0_v”

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

Overview

The IBY_XML_FNDCPT_PAYER_1_0_V view is a public Oracle E-Business Suite view owned by the APPS schema within the IBY (Payments) product. It is a specialized XML-generation view used by the Payments extraction and XML publishing framework to produce a canonical, versioned XML representation of a payer — the party that funds or originates a payment instruction. The FNDCPT token in its name associates it with the Funds Capture (FNDCPT) module of Oracle Payments, and the 1_0 suffix identifies the XML message schema version 1.0.

Rather than returning a flat tabular result set, the view uses Oracle XML SQL functions (XMLCONCAT, XMLELEMENT) to build a nested XMLType document. Each row returned is therefore an XML fragment conforming to the payer schema, carrying party identification, tax and legal registration numbers, flexible-field descriptors, alternative names, customer account numbers, and an optional billing address. Because the object type is a VIEW (STATUS: VALID), it is a queryable, non-materialized definition, making it well suited for on-demand generation of payment XML during extraction runs.

Underlying Base Objects

The view is defined primarily over the helper view IBY_EXT_FC_PAYER_1_0_V (aliased EXT_FC), which supplies the flattened payer attributes. It is joined in an outer-join fashion to HZ_LOCATIONS (alias HZ_LOC) on BILL_TO_ADDRESS_ID = LOCATION_ID for the address block, and to AR_LOOKUPS (alias PARTY_TYPE_LOOKUP) on PARTY_TYPE = LOOKUP_CODE restricted to LOOKUP_TYPE = 'PARTY_TYPE' to resolve the party-type meaning.

The ETRM 12.2.2 metadata documents additional referenced objects: FND_LOOKUP_VALUES, FND_TERRITORIES_VL, the IBY_EXTRACTGEN_PVT and IBY_FD_EXTRACT_GEN_PVT packages (the latter supplying the descriptive flexfield routine GET_DFFS), and the XMLTYPE datatype. The dependency on IBY_EXTRACTGEN_PVT is significant: it indicates the view participates in the standard Payments extraction generation pipeline, where addresses and DFFs are resolved at runtime.

Key Columns

The view exposes a deliberately narrow column list — PAYER, PARTY_ID, and TRXNMID — while the meaningful payer content is packed into the PAYER XMLType column. The TRXNMID (transaction identifier) is carried alongside so that each generated XML fragment can be correlated back to its originating payment transaction, and PARTY_ID provides the key party identifier for downstream joins.

The XML document itself includes elements such as PARTYINTERNALID, PARTYNUMBER, NAME, PARTYTYPE (with nested CODE and MEANING), TAXREGISTRATIONNUMBER, LEGALREGISTRATIONNUMBER, PARTYDESCRIPTIVEFLEXFIELD, ALTERNATENAME, CUSTOMERACCOUNTNUMBER, a nested ADDRESS block, and FIRSTPARTYREFERENCE. Conditional CASE expressions suppress the flexfield element when PARTY_ATTR_CAT is null, the address when BILL_TO_ADDRESS_ID is null, and FIRSTPARTYREFERENCE when PARTY_NUMBER is null.

Common Use Cases and Queries

This view is typically consumed by the Payments XML publishing process rather than by end users directly, but it is useful for diagnostics when validating payer data before an extraction run. A basic query retrieves the payer XML and its transaction identifier:

• SELECT party_id, trxnmid, payer FROM iby_xml_fndcpt_payer_1_0_v WHERE trxnmid = :p_trxnmid;
• To inspect a single XML element, use EXTRACTVALUE or XMLQUERY: SELECT EXTRACTVALUE(payer, '/PARTY/NAME') FROM iby_xml_fndcpt_payer_1_0_v WHERE party_id = :p_party_id;
• To verify address population, filter on the nested location: SELECT party_id FROM iby_xml_fndcpt_payer_1_0_v WHERE EXTRACTVALUE(payer,'/PARTY/ADDRESS/CITY') IS NOT NULL;

These queries assist in confirming that party type lookups resolve correctly, that billing addresses exist where expected, and that the generated document conforms to the version 1.0 payer schema before it is transmitted by the extraction framework.