Search Results vendor_address_line3




Overview
Explore in AI Chat

Overview

FV_ECS_PAYMENT_V is a Federal Financials (FV) reporting view that exposes payment batch records formatted for the ECS (Electronic Certification System) NCR payment format process. It consolidates agency identification, agency banking, and payee (vendor) payment detail into a single flattened result set so that an ECS payment file — or a supporting report — can be produced without joining the underlying Oracle Payables selection tables at runtime. The view presents one row per selected payment check, qualified by OK_TO_PAY_FLAG = 'Y' on both the invoice selection and the selected check, and by a checkrun name common to AP_SELECTED_INVOICES and AP_INVOICE_SELECTION_CRITERIA.

Its principal purpose is output formatting rather than transactional inquiry. Column expressions apply UPPER and SUBSTR with fixed field widths (25, 35, 16, 12, 8, 3) that correspond to the positional record layout expected by the NCR payment format, so the view can be consumed directly by a concurrent program, a BI Publisher data template, or an outbound interface extract.

Underlying Base Objects

The view is defined over six joined base objects, all standard Oracle EBS Payables and HR tables:

  • HR_ORGANIZATION_UNITS — the agency organization, joined to FV_SYSTEM_PARAMETERS_V on LE_ORGANIZATION_ID.
  • FV_SYSTEM_PARAMETERS_V — Federal Financials system parameters; supplies the agency ALC (agency location code) and the legal entity context.
  • HR_LOCATIONS — the agency address and telephone, joined through HR_ORGANIZATION_UNITS.LOCATION_ID.
  • AP_SELECTED_INVOICES — the payment batch checkrun header and set of books linkage.
  • AP_SELECTED_INVOICE_CHECKS — payee/vendor name, number, and remit-to address lines for each selected check.
  • AP_INVOICE_SELECTION_CRITERIA and AP_BANK_ACCOUNTS / AP_BANK_BRANCHES — checkrun selection criteria and the disbursement bank account/branch used to derive the agency bank account type.

Joins are driven by SET_OF_BOOKS_ID, PAY_SELECTED_CHECK_ID, CHECKRUN_NAME, BANK_ACCOUNT_ID, and BANK_BRANCH_ID. The view text uses a DISTINCT, which suppresses duplicate rows produced when an invoice selection criteria row fans out across multiple selected invoices or checks in the same checkrun.

Key Columns

Common Use Cases and Queries

The primary use case is generating or validating ECS NCR payment format output for a specific checkrun. A typical query filters on the checkrun and orders by check identifier:

  • SELECT checkrun_name, agency_alc, vendor_number, vendor_name, vendor_address_line1, vendor_address_line2, vendor_address_line3, vendor_address_line4, vendor_check_amt FROM fv_ecs_payment_v WHERE checkrun_name = :checkrun ORDER BY vendor_check_id;
  • Address completeness review: SELECT checkrun_name, vendor_number, vendor_name FROM fv_ecs_payment_v WHERE vendor_address_line3 IS NULL; — useful because the view substitutes a single space for null address components, so line-3 validation should test for the blank rather than a true null.
  • Batch totals and reconciliation against the Payables payment register: SELECT checkrun_name, SUM(vendor_check_amt) FROM fv_ecs_payment_v GROUP BY checkrun_name;

Because all text output is upper-cased and width-limited, the view should be treated as a presentation layer; drill-back to invoice or payment detail should be performed against AP_SELECTED_INVOICES and AP_SELECTED_INVOICE_CHECKS directly.