Search Results payment_process_request

Overview

The view APPS.IBY_XML_FD_PPR_1_0_V is an Oracle E-Business Suite internal view owned by the APPS schema, residing in the Payments (IBY) module. It exposes XML representations of payment process requests in a versioned format (1.0), as indicated by its suffix. Its status is VALID, and it is registered with FND Design Data under IBY.IBY_XML_FD_PPR_1_0_V. The view plays a supporting role in the Oracle Payments XML extract generation framework, where payment data is assembled into XML payloads for delivery to payment systems, banks, or external integration consumers.

The object carries the Oracle Internal Use Only designation, meaning Oracle Corporation does not support direct customer access except through standard Oracle Applications programs. It is intended for consumption by Oracle's own extraction and formatting logic, not as an end-user reporting interface. Within this framework, the view supplies a structured, query-friendly projection of payment process request XML content alongside a numeric service request identifier.

Underlying Base Objects

According to the documented dependency metadata for ETRM 12.2.2 and the view source excerpt for 12.1.1/12.2.2, IBY_XML_FD_PPR_1_0_V is built upon several base objects:

• FND_GLOBAL (Package) — supplies session context such as organization and user identifiers used in multi-org or security filtering.
• IBY_EXTRACTGEN_PVT (Package) and IBY_FD_EXTRACT_GEN_PVT (Package) — the extract generation engine that formats payment records into the XML structures consumed by the view.
• IBY_EXT_FD_PPR_1_0_V (View) and IBY_EXT_WRAP_PUB (Package) — the extension layer and wrapping public API that adapt the underlying XML payloads.
• IBY_FD_POST_PICP_PROGS_PVT (Package) — supporting logic for post-processing and format-program handling.
• XMLTYPE (Type) — the SYS datatype used for the XML payload column.

The view itself is referenced by IBY_FD_EXTRACT_GEN_PVT, confirming its position as an intermediate artifact within Oracle Payments' extraction pipeline rather than a standalone repository object.

Key Columns

The view exposes two documented columns:

• PAYMENT_PROCESS_REQUEST (XMLTYPE, length 64) — the XML representation of a payment process request. This column carries the formatted payload used for downstream consumption.
• PAYMENT_SERVICE_REQUEST_ID (NUMBER, length 15) — a numeric identifier linking the XML content to the corresponding payment service request record. This serves as the practical join and filter key.

Common Use Cases and Queries

Because the view is flagged Oracle Internal Use Only, legitimate usage is limited to troubleshooting, diagnostics, and integration testing where Oracle's own programs are involved. A typical diagnostic query retrieves the XML payload for a given service request:

• SELECT PAYMENT_SERVICE_REQUEST_ID, PAYMENT_PROCESS_REQUEST FROM APPS.IBY_XML_FD_PPR_1_0_V WHERE PAYMENT_SERVICE_REQUEST_ID = :p_request_id;

Analysts investigating extract failures may join the view to extract-run metadata, or extract XML fragments using XMLType methods such as EXTRACTVALUE or XMLQUERY to inspect header-level attributes. When inspecting XMLTYPE output in SQL*Plus, GETCLOBVAL() is commonly applied to obtain a readable character form.

In summary, IBY_XML_FD_PPR_1_0_V is an internal Oracle Payments view binding XML payment process request data to its service request identifier, serving Oracle's extraction and formatting infrastructure rather than supported end-user querying.