Search Results formatting_payment_id




Overview
Explore in AI Chat

Overview

APPS.IBY_XML_FD_DOC_1_0_V is a dictionary-owned view in the Oracle Payments (IBY) module that exposes payment document XML payloads in the 1.0 format definition. Its primary purpose is to surface the structured XMLTYPE document (DOC_PAYABLE) generated for a formatting payment, together with the identifying keys that link that XML back to the originating payment and payment service request. The view is classified as "Oracle Internal Use Only"; Oracle Corporation does not support direct access to its data except from standard Oracle Applications programs. Consequently, it should be regarded as an internal extraction artifact rather than a public reporting interface.

Underlying Base Objects

The view is defined over several IBY and SYS objects, and its logic is not a simple join over base tables. Documented dependencies include the IBY_EXT_FD_DOC_1_0_V view, the IBY_FD_EXTRACT_GEN_PVT package, the IBY_EXTRACTGEN_PVT package, and the IBY_FD_EXTRACT_EXT_PUB package, along with FND_GLOBAL (used to resolve session and application context) and the SYS.XMLTYPE datatype. Reverse dependencies show that IBY_FD_EXTRACT_GEN_PVT references this view, indicating it participates in the payment document extraction and formatting pipeline. In short, the view is a thin access layer over the extract-generation and publish routines that materialize the payment XML, not a static snapshot of a single table.

Key Columns

  • DOC_PAYABLE (XMLTYPE) — the serialized payment document in FD 1.0 format; the core payload consumed by downstream formatting and printing programs.
  • PAYMENT_ID (NUMBER) — identifier of the payment associated with the extracted document.
  • FORMATTING_PAYMENT_ID (NUMBER) — identifier of the formatting-level payment record. This column is frequently searched because it is the join key between the formatted payment and the extracted XML document, particularly when a single payment is processed through multiple formatting runs.
  • PAYMENT_SERVICE_REQUEST_ID (NUMBER) — the payment service request that initiated processing, useful for tracing an extraction to its originating request.
  • DOCUMENT_PAYABLE_ID (NUMBER) — surrogate identifier for the payable document record.
  • DOCUMENT_STATUS (VARCHAR2) — status of the document at extraction time, indicating where it sits in the payment lifecycle.

Common Use Cases and Queries

The most common practical scenario is retrieving the XML payload for a specific formatting payment, typically when diagnosing a payment format, template, or printing issue. A minimal query follows the documented Query Text:

  • SELECT DOC_PAYABLE FROM APPS.IBY_XML_FD_DOC_1_0_V WHERE FORMATTING_PAYMENT_ID = :p_formatting_payment_id;
  • SELECT DOC_PAYABLE, PAYMENT_ID, PAYMENT_SERVICE_REQUEST_ID, DOCUMENT_STATUS FROM APPS.IBY_XML_FD_DOC_1_0_V WHERE PAYMENT_ID = :p_payment_id;

Because the view calls extraction logic at runtime (IBY_FD_EXTRACT_GEN_PVT, IBY_FD_EXTRACT_EXT_PUB), queries can be resource-intensive and should be scoped by one of the numeric keys. Given the Oracle Internal Use Only restriction, use of this view should be confined to diagnostics or Oracle-standard programs, and any custom integration should preferably rely on supported IBY public APIs rather than querying this object directly.