Search Results iby_ext_fd_ppr_1_0_v




Overview
Explore in AI Chat

Overview

IBY_EXT_FD_PPR_1_0_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the IBY (Payments) product and serves as an external-facing reporting and integration interface over the Payment Service Request (PPR) data model. The "EXT_FD" naming convention indicates that the view is intended for external consumption and formatted data extraction, allowing reporting tools, extracts, and downstream interfaces to query Payment Service Request records without directly joining the underlying transactional and lookup tables.

The view flattens the core Payment Service Request header data (identified by PAYMENT_SERVICE_REQUEST_ID) and enriches it with decoded, human-readable descriptions sourced from Oracle Applications lookups and the applications registry. Rather than returning raw lookup codes and application IDs, the view exposes descriptive meanings and application names, which makes it well suited for operational reporting, reconciliation extracts, and integration payloads that must be consumed by external systems or business users.

Underlying Base Objects

The view is defined over the following documented base objects:

All joins are inner-equality joins on code-to-lookup and ID-to-registry relationships, meaning rows are returned only where corresponding lookup definitions and application registrations exist.

Key Columns

The view exposes the following columns, listed as they appear in the view text and documented structure:

  • PAYMENT_SERVICE_REQUEST_ID — primary identifier of the Payment Service Request row.
  • CALLING_APP_ID — application ID of the product that initiated the service request.
  • APPLICATION_NAME — decoded name of the calling application from FND_APPLICATION_VL.
  • CALL_APP_PAY_SERVICE_REQ_CODE — the calling application's own reference code for the request.
  • CREATION_DATE — timestamp when the request record was created.
  • PAYMENT_SERVICE_REQUEST_STATUS — raw status code of the request.
  • PPR_STATUS_MEANING — decoded status meaning from the 'IBY_REQUEST_STATUSES' lookup.
  • PROCESS_TYPE — raw process type code.
  • PPR_ATTR_CAT — attribute category associated with the request.
  • PPR_PROCESS_TYPE_MEANING — decoded process type meaning from the 'IBY_PROCESS_TYPES' lookup.

Common Use Cases and Queries

This view is typically used for monitoring request status distribution, auditing requests by calling application, and feeding external payment integration extracts. A representative query is:

SELECT payment_service_request_id, application_name, call_app_pay_service_req_code, creation_date, ppr_status_meaning, ppr_process_type_meaning FROM iby_ext_fd_ppr_1_0_v WHERE creation_date >= SYSDATE - 30 ORDER BY creation_date DESC;

Analysts can group by ppr_status_meaning or ppr_process_type_meaning to summarize volumes, and filter by application_name to isolate requests originating from a specific Oracle module.