Results for “iby_xml_fndcpt_order_1_0_v”

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

Overview

IBY_XML_FNDCPT_ORDER_1_0_V is a valid APPS-owned XML generation view within the Oracle Payments (IBY) module. It produces an XMLType document rooted at the FUNDSCAPTUREORDER element, conforming to the Funds Capture Order 1.0 schema used by Oracle E-Business Suite payment integrations. Rather than storing data, the view assembles payment transaction attributes into a hierarchical XML structure that external payment processors, gateways, and fund-capture service providers consume during authorization and settlement flows.

The view is central to Payment Process Request (PPR) execution and to the Funds Capture extraction process. When a payment is dispatched to a processor, the underlying engine selects from this view to emit the standardized XML payload. Because it is defined as a view over transactional and extensibility objects, it reflects live payment state without requiring separate materialization, which keeps outbound messages consistent with the recorded transaction.

Its role spans both reporting and integration. As a reporting artifact, it exposes structured transaction content for diagnostics and reconciliation. As an integration artifact, it is the canonical source for the order-level XML transmitted to processors, coupling order identity, amount, payer, payee, and instrument data into a single envelope. The same view is referenced during retries, voids, credits, and reversals, since the action type is derived dynamically from the transaction type identifier.

Underlying Base Objects

The view is defined over a broad set of synonymous base objects and packaged PL/SQL routines. Core transactional columns (amount, currency, transaction type, update date, payment channel) originate from IBY_TRXN_CORE, IBY_TRXN_SUMMARIES_ALL, IBY_TANGIBLE, and IBY_TRANSACTIONCC_PKG. Extensibility attributes are drawn from IBY_TRXN_EXTENSIBILITY, while XML fragments are composed by nested helper views including IBY_XML_FNDCPT_PAYER_1_0_V, IBY_XML_FNDCPT_PAYEE_1_0_V, IBY_XML_FNDCPT_CREDITCARD_V, IBY_XML_FNDCPT_DEBITCARD_V, IBY_XML_FNDCPT_BANKACCOUNT_V, and IBY_XML_FC_PRBA_1_0_V.

Supporting packages such as IBY_CREDITCARD_PKG, IBY_SECURITY_PKG, IBY_UTILITY_PVT, IBY_EXTRACTGEN_PVT, IBY_FNDCPT_EXTRACT_GEN_PVT, IBY_FD_EXTRACT_GEN_PVT, IBY_EXT_BANKACCT_PUB, IBY_AR_UTILS, HZ_FORMAT_PUB, and FND_GLOBAL supply formatting, security, and value-generation logic. Application identity is resolved through FND_APPLICATION. The XML is constructed natively using SQL/XML functions XMLELEMENT, XMLFOREST, XMLCONCAT, and XMLAGG against the XMLTYPE and AGGXMLIMP types. This dependency chain means the view inherits the availability of the IBY transaction, tangible, and extensibility data model.

Key Columns

Attributes are emitted as XML elements rather than conventional relational columns. The principal output elements include:

• FUNDSCAPTUREORDER — the root container for the entire payload.
• APPLICATIONINTERNALID and APPLICATIONNAME — identify the source application.
• PAYMENTMETHOD — derived from the payment channel code.
• PAYEEORDERNUMBER, PAYEEORDERMEMO, PAYEEORDERREFID, and ORDERMEDIUM — payee-side order identity and reference data.
• ORDERAMOUNT — with nested VALUE and CURRENCY/CODE elements.
• ACTIONTYPE — DECODE of the transaction type into AUTH, AUTH_CAPTURE, CAPTURE, CREDIT, or VOID.
• TRANSACTIONDATE — the update date formatted as ISO-8601.
• TRACENUMBER, AUTHCODE, VOICEAUTHFLAG, and optional POSDATA — core settlement and point-of-sale details.
• ORIGINALCCTRANSACTION — populated when the reference transaction differs from the current one.

Common Use Cases and Queries

Typical uses include extracting outbound processor payloads, troubleshooting failed fund captures, and auditing authorization histories. A simple inspection query returns the generated XML for a given transaction:

• SELECT * FROM IBY_XML_FNDCPT_ORDER_1_0_V WHERE ROWNUM <= 10;
• SELECT x.* FROM IBY_XML_FNDCPT_ORDER_1_0_V WHERE EXTRACTVALUE(... ) = :transaction_id;

Because the view nests numerous dependent objects, query performance depends on selective filters against the core transaction sources. It is most commonly invoked internally by the funds capture extraction packages rather than queried directly, but direct queries remain valuable for validating the XML that a processor will receive.