Results for “formatting_payment_id”

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

Overview

IBY_XML_FD_DOC_1_0_V is a database view owned by the APPS schema within the Oracle Payments (IBY) module. It is a component of the Payments XML extract infrastructure that Oracle E-Business Suite uses to generate Payment Format documents, specifically the "Document Payable" payload associated with the FD (Foreign Draft / Funds Disbursement) XML message family. The view constructs an XMLType instance whose root element is DOCUMENTPAYABLE, assembling document identifiers, payment status, dates, amounts, and formatted error aggregation into a single hierarchical XML structure. In EBS 12.1.1 and 12.2.2 this view participates in the Payment Process Request (PPR) pipeline, where the formatted output drives the outgoing payment instruction file delivered to a payment system, clearing house, or bank. It is a read-only presentation layer: the XML is generated on the fly by SQL/XML functions rather than persisted in a table.

Underlying Base Objects

The view is not defined directly over base tables. Instead it resolves through the ETRM-documented dependency chain consisting of IBY_EXT_FD_DOC_1_0_V (the extract view that supplies DOC), together with the packages APPS.IBY_FD_EXTRACT_GEN_PVT, IBY_EXTRACTGEN_PVT, IBY_EXT_WRAP_PUB, and FND_GLOBAL, plus the built-in XMLTYPE type and the SYS XMLELEMENT/XMLEXTEND family of SQL functions. The alias DOC in the view text refers to the row source produced by the underlying extract view, meaning IBY_XML_FD_DOC_1_0_V applies the XML envelope and element naming conventions to the already-joined extract data. IBY_FD_EXTRACT_GEN_PVT is invoked inline through GET_DOC_DOCERRAGG(DOC.DOCUMENT_PAYABLE_ID), which supplies the DOCTMENT error aggregation fragment, and FND_GLOBAL is typically used to resolve runtime context such as user or application identity. Because all of these are packaged procedures and views, the dependency tree is essential when performing validation or troubleshooting in a cloned environment.

Key Columns

Although the view exposes an XMLType payload rather than conventional relational columns, the principal logical fields are:

• DOCUMENTNUMBER — a nested structure of five DOCUMENTINTERNALIDSEGMENTn values sourced from CALLING_APP_DOC_UNIQUE_REF1 through REF5, plus APPLICATIONINTERNALID, APPLICATIONDOCUMENTSUBTYPE, APPLICATIONUNIQUEINTERNALID, and REFERENCENUMBER.
• BANKASSIGNEDREFCODE — conditionally emitted when BANK_ASSIGNED_REF_CODE is not null.
• UNIQUEREMITTANCEIDENTIFIER — carries the UR number and URI_CHECK_DIGIT for structured remittance matching.
• DOCCATEGORY, SEQUENCENAME, SEQUENCEVALUE — document classification and sequential numbering.
• PONUMBER, DOCUMENTSTATUS, DOCUMENTDATE, DOCUMENTCREATIONDATE, PAYMENTDUEDATE — purchase order reference, status code and meaning, and the key lifecycle dates.
• DOCUMENTTYPE, DOCUMENTDESCRIPTION, TOTALDOCUMENTAMOUNT — document type code/meaning, free-text description, and the amount with its CURRENCY element.

Common Use Cases and Queries

Typical usage includes verifying that the XML envelope for a payment is well formed, diagnosing a Payment Process Request that failed to produce an outbound file, and supporting Oracle Payments troubleshooting or custom bank format extension work. A representative query follows:

SELECT X.* FROM APPS.IBY_XML_FD_DOC_1_0_V X WHERE X.DOCUMENTPAYABLE IS NOT NULL;

Because the extract view generally requires runtime bind parameters (payment process request ID and related identifiers), direct ad-hoc queries frequently raise an unbound-variable condition. Users should therefore test the view inside the Oracle Payments "Create Payment Instructions" or XML extract validation flows, or wrap the call within the standard extract program, and inspect the resulting XMLTYPE with EXTRACTVALUE or XMLTABLE for specific element values.