Search Results iby_fd_payments_v




Overview
Explore in AI Chat

Overview

IBY_FD_PAYMENTS_V is a dictionary view owned by the APPS schema within the Oracle E-Business Suite Payments (IBY) module. It exposes payment records in a form suitable for funds disbursement and payment extraction reporting. The view is part of the Oracle Payments funds capture and disbursement infrastructure, and it is referenced primarily by the payment instruction and extract generation logic. Its status is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, although certain structural details are introduced or extended in 12.2.2.

Functionally, the view consolidates payment-level attributes—payment amounts, currencies, methods, statuses, stop and void details, and descriptive flexfield columns—into a single queryable interface. It serves as a reporting and integration surface for developers and analysts who need to interrogate payment state without navigating the full normalized payment tables. Because it is a view and not a table, it carries no storage of its own and reflects the current state of the underlying payment data at query time.

Underlying Base Objects

The documented base objects referenced by IBY_FD_PAYMENTS_V are:

  • IBY_PAYMENTS_ALL (synonym) — the principal payment table holding one row per payment, including status, amount, currency, method, stop/void fields, and flexfield attribute columns.
  • IBY_PAY_INSTRUCTIONS_ALL (synonym) — the payment instruction table providing bank instruction and settlement context associated with payments.
  • IBY_FD_EXTRACT_GEN_PVT (package) — the funds disbursement extract generation package that consumes payment data for creating payment files and related extract records.

The view is therefore defined over the payment entity (aliased IBY_PAY in the view text), joined or filtered against payment instruction and extract-related logic. The synonym IBY_PAYMENTS_ALL resolves to the underlying transaction table that holds the authoritative payment rows, while IBY_FD_EXTRACT_GEN_PVT represents the procedural dependency used during extraction rather than a relational source of rows. This distinction is important: although the package is listed as a referenced base object, the physical rows are drawn from the payment and instruction tables.

Key Columns

Common Use Cases and Queries

Typical uses include payment reconciliation reports, exception monitoring for stopped or voided payments, and integration extracts for treasury or banking systems.

SELECT payment_id,
       payment_amount,
       payment_currency_code,
       payment_status,
       payment_date
  FROM apps.iby_fd_payments_v
 WHERE payment_status = 'ISSUED'
   AND org_id = :p_org_id;

To identify stopped or voided payments for audit purposes:

SELECT payment_id, void_date, void_reason, stop_confirm_reason
  FROM apps.iby_fd_payments_v
 WHERE void_date IS NOT NULL
    OR stop_confirmed_flag = 'Y';

Because the view exposes flexfield and legal entity columns, it is also suitable for multi-org reporting and analytical extracts joining to supplier and legal entity master data.