Results for “iby_pmt_failed_docs_xml_v”

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

Overview

The IBY_PMT_FAILED_DOCS_XML_V view is an Oracle Payments (IBY) reporting and integration object owned by the APPS schema. Its purpose is to aggregate payment documents that did not reach a terminal processed state, packaging the identifying attributes of those rejected or unprocessed documents into a single XML document per application and payment identifier. In the Oracle EBS 12.1.1 and 12.2.2 data models, Payments processing moves source documents from feeder applications (Payables, Receivables, and other calling modules) through payment service requests. Documents that are successfully converted into payments are stamped with the document status value PAYMENTS_CREATED. Any document whose DOCUMENT_STATUS is not equal to PAYMENTS_CREATED is treated as a failure or an outstanding exception and is surfaced by this view.

The view sits above the standard IBY transaction tables and does not persist data itself; it is a query-time projection that joins documents, payments, and service requests. The XML payload makes it suitable for message-based handoff to the calling application, so the originating module can be notified of which of its submitted documents were rejected and why, keyed by the documents it originally supplied.

Underlying Base Objects

The documented definition of the view is built on three synonyms over the base Payments tables:

• IBY_DOCS_PAYABLE_ALL — the document layer, supplied as alias DOCS. It carries the payment service request linkage, the calling application document unique references 1 through 5, the payment process transaction type code, and the document status used by the filter.
• IBY_PAYMENTS_ALL — the payment layer, alias PMTS, providing PAYMENT_ID and PAYMENT_STATUS.
• IBY_PAY_SERVICE_REQUESTS — the service request layer, alias REQ, providing CALLING_APP_ID and the payment service request identifier and status.

The join is driven on PAYMENT_SERVICE_REQUEST_ID across all three objects, with a further equality on DOCS.PAYMENT_ID = PMTS.PAYMENT_ID. The aggregation rounds are performed with XMLAGG and the resulting fragments are wrapped by XMLELEMENT and XMLFOREST into a DOCUMENTGROUP element. XMLCONCAT and XMLTYPE support types (AGGXMLIMP) are referenced as supporting objects. The defining predicate DOCS.DOCUMENT_STATUS <> 'PAYMENTS_CREATED' is the discriminating condition that gives the view its name.

Key Columns

• DOCUMENT_CONTENT — the generated XMLTYPE document containing the DOCUMENTGROUP element, the FNDAPPLICATIONID, and one REJECTEDDOCUMENTS element per unpaid document.
• CALLING_APP_ID — the application identifier that submitted the payment service request.
• PAYMENT_ID — the payment identifier from IBY_PAYMENTS_ALL.
• PAYMENT_STATUS — the current status of the payment row.
• PAY_REQ_ID — the payment service request identifier, exposed in the view as the grouping key for the service request.
• REQUEST_STATUS — the status of the payment service request.

Common Use Cases and Queries

The principal use case is exception reporting and outbound notification of rejected documents to calling applications. The view groups by calling application, payment, and service request, so a single row represents the failed document set for one payment within one request. Note that the underlying document status PAYMENTS_CREATED is commonly associated with a successful payment creation; a user search for "payments_created" typically resolves to this same data set because the view is defined as the complement of that status.

A basic query returns the XML payload and the identifying keys:

SELECT calling_app_id, pay_req_id, payment_id, payment_status, request_status
FROM apps.iby_pmt_failed_docs_xml_v;

For a targeted reconciliation, the XML can be parsed to isolate the failing document references:

SELECT payment_id, request_status, x.document_content.getClobVal() AS xml_payload
FROM apps.iby_pmt_failed_docs_xml_v x
WHERE x.calling_app_id = :app_id;

Because the view executes XML aggregation at query time, it is best used for narrow, filtered extracts rather than large scans. It is commonly consumed by concurrent programs, dashboard extracts, or interface processes that route rejected documents back to the originating application for correction and resubmission.