Search Results iby_xml_fndcpt_doc_lines_v




Overview
Explore in AI Chat

Overview

The IBY_XML_FNDCPT_DOC_LINES_V view is a Payments (IBY) module database object owned by the APPS schema. It is a valid, aggregation-oriented view whose purpose is to consolidate multiple payment document line records into a single XML fragment per document. This makes it a key utility for Oracle Payments when constructing XML payloads that are exchanged with payment system counterparts or external financial institutions.

Whereas the underlying IBY_XML_FNDCPT_DOC_LINE_V view exposes one row per document line, IBY_XML_FNDCPT_DOC_LINES_V collapses those rows into a single aggregated XML document per unique document reference. This aggregation is achieved through the XMLAGG SQL/XML function, producing an XMLType value that can be embedded directly into larger XML generation routines. In Oracle EBS 12.1.1 and 12.2.2, this view supports the Oracle Payments XML document generation framework and the formatting of payment instruction documents.

Underlying Base Objects

The view is defined at runtime over a small set of documented base objects:

  • IBY_XML_FNDCPT_DOC_LINE_V (VIEW): the primary source of row-level document line data that is aggregated.
  • XMLAGG (SYNONYM): the SQL/XML aggregation function that concatenates line-level XMLType values into a single node set.
  • AGGXMLIMP (TYPE) and XMLTYPE (TYPE): Oracle types providing the internal aggregation implementation and the resulting XML datatype.
  • ARP_TRX_LINE_UTIL (PACKAGE): a Receivables utility package referenced in the broader lineage that supplies supporting line-level logic and attribute derivation.

The defining query groups IBY_XML_FNDCPT_DOC_LINE_V by DOC_UNIQUE_REF and applies XMLAGG(DOCUMENT_LINE) to each group. Consequently, the view carries no storage of its own; it is a virtual aggregation layer that depends on the row-level view remaining valid and populated.

Key Columns

The view exposes two columns of interest as documented in the ETRM metadata:

  • DOCUMENT_LINES: the XMLType value produced by XMLAGG(DOCUMENT_LINE). It contains the concatenated XML fragment representing all lines belonging to a given document. Each constituent fragment corresponds to one row from IBY_XML_FNDCPT_DOC_LINE_V.
  • DOC_UNIQUE_REF: the unique document reference that identifies the parent payment document. This is the grouping key; one output row exists per distinct DOC_UNIQUE_REF.

The DOCUMENT_LINE element aggregated into DOCUMENT_LINES is sourced from the row-level view and typically carries line detail such as line identifiers, amounts, and payment attributes relevant to the enclosing document.

Common Use Cases and Queries

Typical scenarios include generating XML payment files, validating aggregated line payloads, and troubleshooting document assembly where line counts or content appear incorrect. A representative query to retrieve the aggregated lines for a specific document is:

  • SELECT DOC_UNIQUE_REF, DOCUMENT_LINES FROM APPS.IBY_XML_FNDCPT_DOC_LINES_V WHERE DOC_UNIQUE_REF = :p_doc_unique_ref;
  • SELECT x.DOC_UNIQUE_REF FROM APPS.IBY_XML_FNDCPT_DOC_LINES_V x WHERE EXISTSNODE(x.DOCUMENT_LINES, '/lines/line') = 1;

Because the view performs aggregation, queries should generally filter by DOC_UNIQUE_REF or another selective predicate to avoid full scans of the underlying document line data. The XMLType output can be further transformed with standard SQL/XML functions such as EXTRACT, XMLQUERY, or XMLSERIALIZE to render the aggregated lines as CLOB or VARCHAR2 for downstream file generation. Integration developers should note that the view is read-only and that any change to the row-level view or to the ARP_TRX_LINE_UTIL package may affect the aggregated output.