Results for “iby_xml_trxn_extendlist_v”

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

Overview

The IBY_XML_TRXN_EXTENDLIST_V view is a reporting and integration object within the Oracle Payments (IBY) module of Oracle E-Business Suite. Its purpose is to present the extensibility attributes associated with a payment transaction as a single, aggregated XML document, keyed by transaction identifier. Rather than exposing the individual extensibility rows stored in the underlying table, the view collapses all extension name/value pairs belonging to a given transaction into one XML fragment. This makes it directly consumable by XML-based integration layers, such as payment instruction generation, bank communication formatting, and outbound interface processing, where extensibility data must be embedded within a larger XML payload.

The defining characteristic of this view is its use of the SQL/XML aggregation function XMLAGG, combined with XMLELEMENT, to construct the output. The view produces a well-formed XML structure in which each transaction is represented by a set of nested <EXTEND> elements, each containing a <NAME> and a <VALUE> child element.

Underlying Base Objects

The view is owned by the APPS schema and is defined over a single base object: IBY_TRXN_EXTENSIBILITY, which is referenced in the ETRM metadata as a synonym. This table stores the individual extensibility records that attach user-defined or system-defined attribute names and values to a given transaction, identified by the TRXNMID key. The view groups these rows by TRXNMID and aggregates the related records into one XML value per transaction.

In addition to the base table, the view relies on database-supplied XML infrastructure. The metadata lists XMLAGG as a synonym (the aggregate function used to concatenate XML fragments), along with the types AGGXMLIMP and XMLTYPE. These SQL/XML features are part of the Oracle XML DB stack and are available in both Oracle EBS 12.1.1 and 12.2.2 environments, provided the standard XML database components are installed. The view text confirms the definition: it selects XMLAGG(XMLELEMENT("EXTEND", XMLELEMENT("NAME", EXTEND_NAME), XMLELEMENT("VALUE", EXTEND_VALUE))) grouped by TRXNMID.

Key Columns

• EXTEND_LIST — The aggregated XML document produced by XMLAGG. It contains zero or more <EXTEND> elements, each holding a <NAME> and <VALUE> pair derived from the underlying extensibility rows. This column provides all extension metadata for a transaction in a single value.
• TRXNMID — The transaction identifier used as the grouping key. Each row of the view corresponds to one distinct TRXNMID value from IBY_TRXN_EXTENSIBILITY, allowing the aggregated extension list to be joined back to transaction-level data.

Note that the source attributes EXTEND_NAME and EXTEND_VALUE are not projected as standalone columns; they are embedded within EXTEND_LIST. The user search term "extend_name" maps to the XML element name generated from the source column EXTEND_NAME, which appears as <NAME> in the output.

Common Use Cases and Queries

This view is typically joined to transaction or payment instruction headers when building outbound XML messages that must carry transaction extensibility attributes. Typical usage retrieves the aggregated extension list for a specific transaction or range.

• Retrieving the extension XML for a single transaction:

SELECT TRXNMID, EXTEND_LIST
FROM   APPS.IBY_XML_TRXN_EXTENDLIST_V
WHERE  TRXNMID = :p_trxnmid;

• Joining the aggregated extensions to a transaction-level query to enrich reporting output.
• Extracting a specific extension name from the aggregated list using XMLTABLE or EXTRACTVALUE for filtering or validation.

Because the view returns an XMLTYPE-based aggregate, consumers can apply standard SQL/XML functions to parse or transform the EXTEND_LIST content. The view is read-only and is best treated as a presentation layer over IBY_TRXN_EXTENSIBILITY.