Results for “iby_xml_fndcpt_doc_headers_v”

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

Overview

The IBY_XML_FNDCPT_DOC_HEADERS_V view is a dictionary object owned by the APPS schema within the Oracle Payments (IBY) module of Oracle E-Business Suite. It is delivered with a VALID status in both release 12.1.1 and 12.2.2. The view does not represent transactional data in the conventional relational sense; rather, it aggregates XML document header fragments into a single XMLType instance per tangible identifier, making it a purpose-built integration artifact for the Payments XML messaging framework.

Functionally, the view serves as the collection layer for payment document headers that are consumed by Oracle Payments when constructing outbound XML payloads, such as payment instruction files transmitted to banks or payment systems. Its design confirms its integration role rather than a pure reporting role: the grouping mechanism collapses many document header rows into one consolidated XML document, which is the representation required by the downstream XML generation logic.

Underlying Base Objects

The view text is defined as SELECT XMLAGG(DOCUMENT_HEADER), TANGIBLEID FROM IBY_XML_FNDCPT_DOC_HEADER_V GROUP BY TANGIBLEID. Its documented dependencies are:

• IBY_XML_FNDCPT_DOC_HEADER_V (VIEW) — the single source row set. Each row supplies an XML fragment in DOCUMENT_HEADER plus the TANGIBLEID used for grouping.
• XMLAGG (SYNONYM) — the SQL/XML aggregate function that concatenates the header fragments into one XMLType value per TANGIBLEID.
• AGGXMLIMP (TYPE) and XMLTYPE (TYPE) — Oracle's implementation types supporting XML aggregation and the XMLType datatype used to hold the result.
• ARP_TRX_LINE_UTIL (PACKAGE) — an AR utility package referenced within the dependency chain, reflecting the lineage of the underlying document header data derived from receivables transaction structures.

The documented dependency on ARP_TRX_LINE_UTIL indicates that the header content originates in contexts linked to AR transaction data, where Oracle Payments builds the tangible/document header hierarchy used for XML output.

Key Columns

The view exposes only two columns:

• DOCUMENT_HEADERS (XMLType) — the aggregated XML document containing all document header fragments for a given tangible identifier. It is produced by XMLAGG over the DOCUMENT_HEADER column of the base view.
• TANGIBLEID — the grouping key. It identifies the tangible (the physical or logical payment artifact, such as a check, draft, or electronic payment object) with which the aggregated headers are associated. One row is returned per distinct TANGIBLEID.

Because the output is XMLType, consumers typically apply XMLType methods (for example getClobVal()) to materialize readable markup.

Common Use Cases and Queries

This view is principally used by the Oracle Payments XML generation and diagnostic paths. A representative query to inspect the aggregated headers for a tangible is:

• SELECT TANGIBLEID, DOCUMENT_HEADERS.getClobVal() AS HEADER_XML FROM APPS.IBY_XML_FNDCPT_DOC_HEADERS_V WHERE TANGIBLEID = :tangible_id;
• SELECT COUNT(*), COUNT(DISTINCT TANGIBLEID) FROM APPS.IBY_XML_FNDCPT_DOC_HEADERS_V; to profile aggregation cardinality.
• SELECT TANGIBLEID FROM APPS.IBY_XML_FNDCPT_DOC_HEADERS_V WHERE DOCUMENT_HEADERS IS NULL; to detect tangibles lacking header fragments.

These queries support troubleshooting XML payload assembly, validating that each tangible receives a well-formed header block, and auditing the collision count where multiple fragments collapse into one aggregate.