Search Results void_date

Overview

The view FV_TREAS_CONFIRM_CHECKS_V is an Oracle EBS Federal Financials (FV) reporting object owned by the APPS schema. It presents a consolidated, treasury-facing picture of payment and check activity by joining Oracle Payables check data to Oracle Payments payment instruction data. Its name and column set indicate that it supports treasury confirmation and reconciliation processes, particularly the identification and reporting of voided payments. Because it exposes VOID_DATE directly alongside the check number, vendor name, amount, and payment reference number, the view gives treasury and federal accounting users a single query point for confirming whether a disbursement has been voided and for matching a check to its originating payment instruction.

The view is read-only and intended for reporting and integration rather than transaction entry. It does not itself enforce business rules; it simply projects columns from two core payment tables so that downstream reports, extracts, and reconciliations can operate against a stable column list.

Underlying Base Objects

The view text is defined as a join between two base objects:

• AP_CHECKS_ALL — the Oracle Payables payment/check table. It supplies ORG_ID, PAYMENT_ID, CHECK_ID, CHECK_NUMBER, VENDOR_NAME, AMOUNT, and VOID_DATE. AP_CHECKS_ALL is the authoritative source for check and payment records, including void status and void accounting date.
• IBY_PAYMENTS_ALL — the Oracle Payments payment table. It supplies PAYMENT_INSTRUCTION_ID and PAYMENT_REFERENCE_NUMBER, linking the Payables check to the payment instruction created in the Payments module.

The join condition is ACA.PAYMENT_ID = IPA.PAYMENT_ID, so each row in the view represents a payment record matched to its corresponding payment instruction. The ETRM metadata additionally lists AP_INV_SELECTION_CRITERIA_ALL, IBY_PAY_INSTRUCTIONS_ALL, and AP_CHECKS_ALL as referenced objects, reflecting the broader dependency chain of payment selection and instruction processing that feeds the joined tables.

Key Columns

• ORG_ID — the operating unit identifier, enabling multi-org filtering.
• PAYMENT_ID — the common key linking the Payables check to the Payments instruction.
• CHECK_ID — the internal identifier of the payment/check record.
• CHECK_NUMBER — the printed check or payment number used for reconciliation.
• VENDOR_NAME — the payee name associated with the disbursement.
• AMOUNT — the payment amount.
• VOID_DATE — the date the payment was voided; null for payments that remain outstanding. This is the column most relevant to the source query, since a non-null value confirms a voided disbursement.
• PAYMENT_INSTRUCTION_ID — the Payments instruction that produced the check.
• PAYMENT_REFERENCE_NUMBER — the payment reference used by Oracle Payments and by bank/treasury tracking.

Common Use Cases and Queries

Typical uses include treasury confirmation of issued and voided checks, reconciliation of Payables checks against Payments instructions, and federal reporting extracts that must distinguish live from voided disbursements.

To list voided checks for an operating unit:

• SELECT check_number, vendor_name, amount, void_date FROM fv_treas_confirm_checks_v WHERE org_id = :p_org_id AND void_date IS NOT NULL ORDER BY void_date;

To reconcile a check to its payment instruction by reference number:

• SELECT check_number, payment_reference_number, payment_instruction_id FROM fv_treas_confirm_checks_v WHERE payment_reference_number = :p_ref;

To summarize disbursements, voided versus outstanding, by payee:

• SELECT vendor_name, SUM(amount) total_amount, COUNT(*) payment_count FROM fv_treas_confirm_checks_v WHERE org_id = :p_org_id AND void_date IS NULL GROUP BY vendor_name;

Because VOID_DATE originates in AP_CHECKS_ALL, filtering on it is the standard method for isolating voided payments, and the join to IBY_PAYMENTS_ALL allows the same result set to be reported with treasury payment reference detail.