Results for “payment_service_request_id”

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

Overview

IBY_XML_FD_PPR_1_0_V is an Oracle E-Business Suite view owned by the APPS schema within the IBY (Payments) product. It is a reporting and integration artifact that materializes a Payment Process Request (PPR) as an XML document conforming to the Oracle Payments "Payment Process Request" version 1.0 message structure. Rather than storing data itself, the view leverages Oracle SQL/XML functions — principally XMLELEMENT — to generate an XMLTYPE payload reflecting the header-level attributes of a Payment Process Request together with its associated payment aggregates and prebuilt document information.

In the Oracle EBS 12.1.1 and 12.2.2 releases, this view forms part of the extract infrastructure used by the Payments module to produce standardized XML output. It is typically consumed by the Payments file delivery and extract generation processes, where an outbound XML document describing a payment process request is assembled for downstream applications, banking partners, or internal reconciliation. Because the view is built on top of the extract view IBY_EXT_FD_PPR_1_0_V, it represents a presentation layer that wraps a well-defined extract structure with the appropriate XML tags and naming conventions required by the version 1.0 specification.

Underlying Base Objects

The view is defined over the documented base object IBY_EXT_FD_PPR_1_0_V, which supplies the core Payment Process Request columns (aliased PPR in the query). The XML generation itself relies on several PL/SQL packages referenced in the view text. IBY_FD_EXTRACT_GEN_PVT contributes the aggregation functions GET_PPR_PMTAGG, GET_PPR_PMTCOUNT, GET_PPR_PREBUILDDOCAGG, and GET_PPR_PREBUILDDOCCOUNT, which assemble payment and prebuilt-document sub-elements. IBY_EXTRACTGEN_PVT provides GET_DFFS, invoked to emit the DESCRIPTIVEFLEXFIELD element for the IBY_PAY_SERVICE_REQUESTS entity when descriptive flexfield attributes exist. The type XMLTYPE underpins the generated document, while additional packages such as IBY_FD_POST_PICP_PROGS_PVT, IBY_EXT_WRAP_PUB, and FND_GLOBAL are documented as referenced base objects that support extract generation, request context, and publication logic. The dependency on IBY_EXT_FD_PPR_1_0_V places this view at the top of a layered extract stack.

Key Columns

The view exposes two columns. PAYMENT_PROCESS_REQUEST is the XMLTYPE document produced by the nested XMLELEMENT calls. Its root element is PAYMENTPROCESSREQUEST, containing a PAYMENTPROCESSREQUESTINFO section with SOURCEPRODUCTREFERENCE, PAYMENTPROCESSREQUESTREFERENCENUMBER, SUBMISSIONDATE, PAYMENTPROCESSREQUESTSTATUS (CODE and MEANING), PROCESSTYPE (CODE and MEANING), and an optional DESCRIPTIVEFLEXFIELD. Sibling elements include payment aggregates, a PAYMENTCOUNT, and a PREBUILDDOCUMENTSPAYABLE element carrying its own DOCUMENTCOUNT. PAYMENT_SERVICE_REQUEST_ID is the numeric identifier of the Payment Process Request, retained as a relational key that links each generated XML document back to the originating request. Notably, the SUBMISSIONDATE element formats CREATION_DATE as an ISO-8601 timestamp (YYYY-MM-DD"T"HH24:MI:SS).

Common Use Cases and Queries

Typical uses include retrieving the XML payload for a single PPR, extracting payment counts for reconciliation reporting, and joining the view to request metadata. A representative query returning one document is:

• SELECT payment_process_request FROM iby_xml_fd_ppr_1_0_v WHERE payment_service_request_id = :ppr_id;
• SELECT v.payment_service_request_id, v.payment_process_request.getClobVal() xml_doc FROM iby_xml_fd_ppr_1_0_v v WHERE v.payment_service_request_id = :ppr_id;
• SELECT ppr.payment_service_request_id FROM iby_xml_fd_ppr_1_0_v ppr WHERE EXISTS (SELECT 1 FROM iby_pay_service_requests r WHERE r.payment_service_request_id = ppr.payment_service_request_id AND r.payment_service_request_status = 'COMPLETED');

These patterns support XML extract generation, status-driven reporting, and integration testing, where the standardized PAYMENTPROCESSREQUEST document is validated or routed to external systems.