Results for “accomplished_date”

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

Overview

FV_PAYMENT_MASTER_V is a Federal Financials (FV) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to retrieve payment details in the form of a Document Cross-Reference. In practice, this view presents a simplified, denormalized projection of payment and disbursement information drawn from Oracle Payables. It is intended primarily for inquiry, reporting, and integration scenarios where consumers require a stable read-only representation of a payment record without joining the full PAYABLES base tables themselves. Because the view is defined only over AP_CHECKS, it can be treated as a thin, upward-compatible abstraction layer over the payment header. This makes it suitable for Federal Financials cross-reference reporting, where a payment must be reconciled against treasury disbursement attributes and, in the retrieved form, against accompanying document identifiers.

Underlying Base Objects

Per the ETRM metadata, FV_PAYMENT_MASTER_V is defined exclusively over the base object AP_CHECKS, which is referenced as a synonym in the APPS schema. The documented view text confirms this relationship directly:

• AP_CHECKS (synonym): the single underlying base table. The SELECT statement joins no other table; all columns are sourced from AP_CHECKS.
• Alias: the view text aliases AP_CHECKS as AC, and every projected column is qualified with that alias.
• Filtering: the documented statement contains no WHERE clause, so the view exposes all payment rows visible to the querying user's data access, without additional row-level restriction at the view definition itself.

Because there is a one-to-one, single-table relationship, the view carries no aggregation or join fan-out risk. Row counts and key uniqueness mirror AP_CHECKS, and ordinary Payables security applied to AP_CHECKS propagates to consumers of this view.

Key Columns

The view text and documented column list are not perfectly aligned, and this discrepancy is significant for anyone searching on “accomplished_date.” The SELECT statement projects CHECK_DATE, whereas the documented column list includes both CHECK_DATE and ACCOMPLISHED_DATE, along with VOID_STATUS. Practitioners should therefore verify the runtime column set in their target instance rather than relying solely on either list. The principal exposed columns are:

• ORG_ID: operating unit identifier, supporting multi-org querying.
• CHECK_ID: surrogate key of the payment record in AP_CHECKS.
• VENDOR_ID / VENDOR_SITE_ID: supplier and supplier site identifiers.
• TREASURY_PAY_NUMBER / TREASURY_PAY_DATE: Treasury disbursement reference and date, central to Federal cross-reference.
• AMOUNT: payment amount.
• CHECKRUN_NAME / CHECK_NUMBER / CHECK_DATE: payment run name, instrument number, and payment date. ACCOMPLISHED_DATE is documented as the date the payment was accomplished; where exposed, it is the effective accounting/payment date.
• STATUS_LOOKUP_CODE / VOID_STATUS / VOID_DATE: payment status, void indicator, and void date.

Common Use Cases and Queries

This view is used for Federal payment cross-reference reporting, treasury reconciliation, and lookups keyed on payment identifiers. A typical query joining the view back to AP_CHECKS to retrieve the accomplished date (where the column is present at runtime) follows:

• Payment cross-reference lookup: SELECT check_id, treasury_pay_number, treasury_pay_date, amount, status_lookup_code FROM fv_payment_master_v WHERE org_id = :p_org_id AND check_date BETWEEN :p_from AND :p_to;
• Accomplished-date oriented extract: SELECT check_id, check_number, accomplished_date, amount FROM fv_payment_master_v ORDER BY accomplished_date;
• Void review: SELECT check_number, void_status, void_date FROM fv_payment_master_v WHERE void_date IS NOT NULL;
• Treasury reconciliation: SELECT treasury_pay_number, treasury_pay_date, check_number FROM fv_payment_master_v WHERE treasury_pay_number IS NOT NULL;

Consumers should confirm the presence of ACCOMPLISHED_DATE versus CHECK_DATE at runtime, apply ORG_ID predicates for multi-org security, and treat the view as read-only. No DML should be issued against it, and its single-table basis means performance is effectively that of querying AP_CHECKS.