Search Results iby_xml_fndcpt_doc_line_v




Overview
Explore in AI Chat

Overview

The IBY_XML_FNDCPT_DOC_LINE_V view belongs to the IBY (Payments) product family within Oracle E-Business Suite and is deployed in the APPS schema. It is a reporting and integration view whose purpose is to emit payment document line data in an Oracle XMLType structure. Rather than returning conventional relational rows, the view applies SQL/XML functions—XMLELEMENT, XMLFOREST, and nested element constructors—to produce a hierarchical XML document fragment for each source line. The outermost element is DOCUMENTLINE, which wraps identification, descriptive, monetary, and tax sub-elements in a format suitable for downstream consumption by payment processing, funds capture, and external system integrations.

Within the Funds Capture (FNDCPT) architecture, this view serves as the line-level counterpart used when constructing an outbound payment document payload. Applications that need a structured, transportable representation of receivables document lines—amount, currency, tax breakdown, and line attributes—can query the view and consume the resulting XMLType directly, avoiding bespoke formatting logic.

Underlying Base Objects

Per the documented metadata, the view is defined over two underlying views and draws on a supporting package and datatype:

  • AR_DOCUMENT_LINES_V — supplies the line-level source records, aliased INV_LINE, including line number, line type, description, gross amount, unit price, quantity, unit of measure, discount, and tax columns.
  • AR_DOCS_RECEIVABLES_V — supplies the header-level context, aliased INV_HEADER, principally DOC_UNIQUE_REF and the document currency code used throughout the nested amount elements.
  • ARP_TRX_LINE_UTIL (Package) — the receivables transaction line utility package referenced by the defining logic.
  • XMLTYPE (Type) — the Oracle SQL/XML datatype that forms the view's returned content.

The join is established on INV_LINE.DOC_UNIQUE_REF = INV_HEADER.DOC_UNIQUE_REF, giving one XML DOCUMENTLINE element per matching line/header pair.

Key Columns

The view exposes three documented columns:

  • DOCUMENT_LINE — the primary output, an XMLType instance containing the full DOCUMENTLINE element with nested LINEID, LINENUMBER, LINETYPE, LINEDESCRIPTION, LINEAMOUNT (with VALUE and CURRENCY/CODE), UNITRATE, QUANTITY, UNITOFMEASURE, PRODUCTCODE, COMMODITYCODE, DISCOUNT, and paired TAX elements distinguishing SALESTAX and VAT.
  • CUSTOMER_TRX_LINE_ID — the receivables transaction line identifier, providing a relational key back to the originating AR line.
  • DOC_UNIQUE_REF — the document-level unique reference linking each line back to its header, the same correlate used in the internal join.

Note that, because both the TAX and DISCOUNT amount elements carry the currency code sourced from the header, monetary values always inherit the document's transaction currency.

Common Use Cases and Queries

Typical scenarios include generating payment document payloads for external remittance or funds capture interfaces, validating tax and discount breakdowns across invoice lines, and reconstructing document structures for integration middleware.

A representative query returning the XML payload for a specific document reference:

  • SELECT l.DOC_UNIQUE_REF, l.CUSTOMER_TRX_LINE_ID, l.DOCUMENT_LINE FROM APPS.IBY_XML_FNDCPT_DOC_LINE_V l WHERE l.DOC_UNIQUE_REF = :p_doc_unique_ref;

To extract scalar values from the XMLType, callers may apply XMLTABLE or EXTRACTVALUE against DOCUMENT_LINE. Joining to the AR header views on DOC_UNIQUE_REF allows aggregation of line totals. Because the view emits XMLType, bulk extraction should be limited to scoped document references to control parsing cost.