Results for “iby_rejected_docs_xml_v”

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

Overview

The IBY_REJECTED_DOCS_XML_V view is a reporting and integration object within the Oracle E-Business Suite Payments (IBY) module. It exposes rejected or non-validated payment documents in an XML-structured, aggregated form, grouping them by payment service request. Rather than presenting flat rows, the view concatenates relational data into a single XML document per payment service request, which is a pattern frequently used for outbound integration payloads, error notification messages, and diagnostic reporting against the Payments document pipeline.

The view is owned by the APPS schema and carries a VALID status in both EBS 12.1.1 and 12.2.2. Its design reflects the ETRM description: it collects documents whose lifecycle has not reached the 'VALIDATED' state and whose PAYMENT_ID remains null, meaning no disbursement record has been created. This makes the view a natural lens for surfacing rejected or pending documents requiring attention.

Underlying Base Objects

The view is defined over two core transactional tables, accessed through synonyms: IBY_DOCS_PAYABLE_ALL and IBY_PAY_SERVICE_REQUESTS. The XML aggregation is performed using the XMLAGG synonym and the AGGXMLIMP aggregate type, with the output materialized as an XMLTYPE. The join is on PAYMENT_SERVICE_REQUEST_ID, linking each document to the service request that governs its processing.

The row set is filtered by two predicates: DOCUMENT_STATUS must not equal 'VALIDATED', and PAYMENT_ID must be null. Results are grouped by REQ.CALLING_APP_ID, REQ.PAYMENT_SERVICE_REQUEST_ID, and REQ.PAYMENT_SERVICE_REQUEST_STATUS, producing one concatenated XML document per service request. The header element carries FNDAPPLICATIONID derived from CALLING_APP_ID, and each rejected document is emitted as a REJECTEDDOCUMENTS node built with XMLFOREST.

Key Columns

• DOCUMENT_CONTENT — The CL/XMLTYPE payload built by XMLCONCAT and XMLAGG. It contains a DOCUMENTGROUP root with a FNDAPPLICATIONID element and one or more REJECTEDDOCUMENTS elements. Each rejected document carries PAYMENTPROCESSTRXNTYPECODE, CALLINGAPPID, and up to five CALLINGAPPDOCUNIQUEREF values.
• PAY_REQ_ID — Projects REQ.PAYMENT_SERVICE_REQUEST_ID, the identifier of the payment service request grouping the rejected documents. This is the column most often used to join back to IBY_PAY_SERVICE_REQUESTS and is the term users search on.
• REQUEST_STATUS — Projects REQ.PAYMENT_SERVICE_REQUEST_STATUS, indicating the processing state of the originating service request and providing context for why documents sit in a rejected state.

Common Use Cases and Queries

Typical scenarios include auditing failed document submissions, feeding error-handling workflows, and troubleshooting why a payment was never created. The following retrieves the XML payload and status for a specific service request:

• SELECT pay_req_id, request_status, document_content FROM apps.iby_rejected_docs_xml_v WHERE pay_req_id = :p_req_id;
• SELECT pay_req_id, request_status FROM apps.iby_rejected_docs_xml_v WHERE request_status = 'REJECTED';
• SELECT pay_req_id, EXTRACTVALUE(document_content, '//CALLINGAPPDOCUNIQUEREF1') ref1 FROM apps.iby_rejected_docs_xml_v;

Because the view aggregates by service request, joining directly to IBY_DOCS_PAYABLE_ALL requires care: extract the unique reference values from the XML rather than expecting one row per document. This view is best used where an XML message is required; for row-level document diagnostics, query IBY_DOCS_PAYABLE_ALL directly with the same DOCUMENT_STATUS and PAYMENT_ID predicates.