Search Results doc_unique_ref




Overview
Explore in AI Chat

Overview

The view APPS.IBY_XML_FNDCPT_DOC_LINES_V is a payment-related XML aggregation view within the Oracle Payments (IBY) module of Oracle E-Business Suite. It presents document line data for funds capture documents in an XML-typed format, aggregating individual line records into a single XML document per document unique reference. The view's defining characteristic is its use of the SQL XMLAgg aggregate function combined with a GROUP BY doc_unique_ref clause, which consolidates the multiple line-level rows produced by the underlying base view into one aggregated XMLType value per document.

This view plays a specific role in Oracle EBS reporting and integration: it serves as a formatting and consolidation layer that transforms flat relational line data into structured XML payloads. Such payloads are typically consumed by payment processing engines, funds capture workflows, or outbound integration interfaces that require complete document line detail packaged as a single hierarchical XML entity rather than as separate rows. The doc_unique_ref column acts as the grouping key and is the attribute most commonly referenced by consumers searching for this object, since it uniquely identifies each aggregated document within the result set.

Underlying Base Objects

According to the documented ETRM metadata for release 12.2.2, the view is owned by APPS and is defined over the following referenced base objects:

  • IBY_XML_FNDCPT_DOC_LINE_V (VIEW) — the immediate source view from which line-level rows are drawn. This view supplies the document_line XML fragments and the doc_unique_ref grouping column.
  • XMLAGG (SYNONYM) — the SQL/XML aggregate function used to concatenate the per-line XML fragments into a single aggregated document.
  • AGGXMLIMP (TYPE) — the Oracle internal type supporting XML aggregation implementation.
  • XMLTYPE (TYPE) — the Oracle native XML datatype in which the aggregated document_line result is returned.
  • ARP_TRX_LINE_UTIL (PACKAGE) — an Oracle Receivables transaction line utility package referenced within the broader document line processing chain, reflecting the linkage between funds capture document lines and underlying AR transaction line logic.

The view therefore sits at the top of a two-tier stack: the base view IBY_XML_FNDCPT_DOC_LINE_V produces individual line records, and IBY_XML_FNDCPT_DOC_LINES_V aggregates those records by document reference.

Key Columns

The view definition exposes a deliberately minimal column set, reflecting its narrow aggregation purpose:

  • DOC_UNIQUE_REF — the unique reference identifying a funds capture document. This is the grouping key in the GROUP BY clause and the primary means by which consumers correlate an aggregated XML payload to its originating document.
  • DOCUMENT_LINE (aggregated) — the result of XMLAgg(document_line), returned as an XMLType. It contains the concatenated XML fragments representing all lines belonging to the corresponding doc_unique_ref.

Because the view is an aggregation, it does not expose individual line attributes such as line number, amount, or description directly; those attributes reside within the XML structure of the DOCUMENT_LINE value and are inherited from the base view.

Common Use Cases and Queries

The principal use case is retrieving a single consolidated XML document of all lines for a given funds capture document. A representative query is:

  • SELECT doc_unique_ref, document_line FROM apps.iby_xml_fndcpt_doc_lines_v WHERE doc_unique_ref = :p_ref;

Additional scenarios include bulk extraction of all aggregated documents for downstream XML processing, and integration with payment or reporting engines that expect XMLType output:

  • SELECT doc_unique_ref, XMLQuery('$d/doc' PASSING document_line AS "d" RETURNING CONTENT) FROM apps.iby_xml_fndcpt_doc_lines_v;
  • SELECT COUNT(*) FROM apps.iby_xml_fndcpt_doc_lines_v; — to determine the number of distinct documents with aggregated lines.

Consumers should note that filtering on doc_unique_ref is the most efficient access path, since it aligns with the view's grouping key.