Results for “refund_gl_date”

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

Overview

FV_PAYABLE_REFUNDS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Federal Financials (FV) product family. Its documented purpose is to retrieve refund payment details originating from Oracle Payables. In federal accounting environments, refunds frequently arise when a vendor returns funds previously disbursed — for example, a credit or debit invoice processed against an existing payment. This view consolidates the vendor, check, invoice, and invoice-payment attributes associated with such refund transactions into a single queryable structure, allowing federal reporting and reconciliation processes to identify and analyze refund activity without joining the underlying Payables tables directly.

The view is exposed as a standard APPS view and carries a VALID status in the ETRM repository, confirming it is a supported, deployable object in both 12.1.1 and 12.2.2 environments. Because it references synonyms and other APPS views rather than tables in a private schema, it is intended for read-only consumption by reports, federal accounting extracts, and integration routines.

Underlying Base Objects

The documented base objects underlying FV_PAYABLE_REFUNDS_V are:

• AP_CHECKS_ALL (SYNONYM) — supplies payment/check header information, including check identifiers, amounts, dates, organization, and payment type flags.
• AP_INVOICES_ALL (SYNONYM) — supplies invoice header information, including invoice number, amount, GL date, and invoice type.
• AP_INVOICE_PAYMENTS_ALL (SYNONYM) — links checks to invoices and provides refund amount, GL period, set of books, and invoice payment identifiers.
• PO_VENDORS (VIEW) — supplies vendor identification, including the vendor name and the SEGMENT1 vendor number.

The joins tie vendors to checks via VENDOR_ID, checks to invoice payments via CHECK_ID and ORG_ID, and invoice payments to invoices via INVOICE_ID and SET_OF_BOOKS_ID. The view also includes an EXISTS subquery against GL_JE_LINES and AP_INVOICE_DISTRIBUTIONS_ALL, restricting output to invoices whose distributions have posted journal entries (GLJL.STATUS = 'P' and matching CODE_COMBINATION_ID). Filter conditions restrict results to credit or debit invoice types, outstanding refund payment type (PAYMENT_TYPE_FLAG = 'R'), posted payments, and non-reversed invoice payments (REVERSAL_INV_PMT_ID IS NULL).

Key Columns

• VENDOR_ID, VENDOR_NAME, VENDOR_NUM — vendor identity; VENDOR_NUM is sourced from PO_VENDORS.SEGMENT1 and is the column most commonly referenced when searching by vendor.
• VENDOR_SITE_CODE, VENDOR_SITE_ID — the vendor site associated with the refund check.
• REFUND_AMOUNT — the refunded amount from AP_INVOICE_PAYMENTS_ALL.AMOUNT.
• CHECK_ID, CHECK_NUMBER, CHECK_AMOUNT, REFUND_GL_DATE, REFUND_GL_PERIOD — payment instrument details and the accounting date/period of the refund.
• ORG_ID, SET_OF_BOOKS_ID — operating unit and ledger identifiers supporting multi-org and multi-ledger reporting.
• INVOICE_ID, INVOICE_NUM, INVOICE_AMOUNT, INVOICE_GL_DATE — the invoice associated with the refund.
• INVOICE_PAYMENT_ID — the linking key between invoice and payment, useful for drill-down.

Common Use Cases and Queries

Typical uses include federal refund reconciliation, vendor refund analysis, and ledger-level audit extracts. A frequent requirement is locating refunds for a specific vendor by vendor number:

• SELECT vendor_num, vendor_name, check_number, refund_amount, invoice_num FROM fv_payable_refunds_v WHERE vendor_num = :p_vendor_num;
• SELECT org_id, set_of_books_id, refund_gl_period, SUM(refund_amount) FROM fv_payable_refunds_v GROUP BY org_id, set_of_books_id, refund_gl_period;
• SELECT invoice_num, invoice_amount, check_number, refund_amount FROM fv_payable_refunds_v WHERE invoice_gl_date BETWEEN :from_date AND :to_date;

Because the view already enforces posted, non-reversed, refund-flagged payments, queries against it return a pre-qualified refund population, reducing the filtering logic required in downstream reports.