Results for “fv_ecs_ach_vendor_v”

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

Overview

The view FV_ECS_ACH_VENDOR_V is a Federal Financials (FV) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to obtain the data required for the ECS (Electronic Certification System / payment-file) ACH Vendor format. In practical terms, it assembles a flat, denormalized record set suitable for generating an ACH vendor payment file, presenting payee bank details, agency banking identifiers, and pay-run selection data in a single row per selected payment.

The view joins payment-selection data (AP_SELECTED_INVOICES, AP_SELECTED_INVOICE_CHECKS) with vendor and vendor-site banking information (PO_VENDORS, PO_VENDOR_SITES), disbursement bank account details (AP_BANK_ACCOUNTS), and agency identity/location attributes (HR_ORGANIZATION_UNITS, HR_LOCATIONS, FV_SYSTEM_PARAMETERS_V). The result is a compliant, fixed-width-oriented projection of ACH vendor remittance data.

Underlying Base Objects

The view is defined over eight documented base objects:

• AP_SELECTED_INVOICES (APSI) — selected invoice/payment records for a check run.
• AP_SELECTED_INVOICE_CHECKS (ASIC) — check-level selection detail.
• AP_INVOICE_SELECTION_CRITERIA (APISC) — pay-run criteria linking check run to bank account.
• PO_VENDORS (POV) — vendor master records, including TIN/1099 number.
• PO_VENDOR_SITES (POVS) — vendor site banking attributes such as bank number.
• AP_BANK_ACCOUNTS (APBA) — internal disbursement bank account type.
• HR_ORGANIZATION_UNITS (HRORG) — agency organization identity.
• HR_LOCATIONS (HRLOC) — agency address and telephone.
• FV_SYSTEM_PARAMETERS_V (FVS) — Federal agency ALC code and legal entity linkage.

The joins are keyed on set of books, vendor, vendor site, check run name, bank account, and selected check, with filtering restricted to records whose OK_TO_PAY_FLAG = 'Y'. At execution, the view depends on the HR and AP schemas and returns no data where no qualifying selected payments exist.

Key Columns

• CHECKRUN_NAME — pay-run identifier.
• INVOICE_NUM — invoice number (substr 50).
• SELECTED_CHECK_ID / PAYMENT_AMOUNT — payment identifiers and amount.
• AGENCY_NAME, AGENCY_ALC_CODE, AGENCY_BANK_ACCOUNT_TYPE, AGENCY_ADDRESS_LINE_1/2, AGENCY_CITY_STATE_ZIP, AGENCY_TELEPHONE_NUMBER_1 — agency/remitter header data; ALC code is RPAD to 8.
• VENDOR_NUM, VENDOR_NAME, VENDOR_NUM_1099 — payee identity.
• VENDOR_BANK_ACCOUNT_NUM and VENDOR_BANK_ACCOUNT_TYPE — the payee ACH account and its one-character account type.
• VENDOR_BANK_NUM — routing/ABA number, left-padded to 9 with zeros.

Notably, VENDOR_BANK_ACCOUNT_TYPE is derived from APSI.BANK_ACCOUNT_TYPE, truncated to one character — the column most relevant to the user query term vendor_bank_account_type. Field sizes are explicitly constrained to fit the ACH flat-file layout.

Common Use Cases and Queries

Typical use is to extract ACH vendor payment data for a specific check run, then format to the required fixed-width ECS layout.

• Reviewing ACH account types for a run to validate payee setup.
• Feeding downstream payment-file generation for Federal ECS processing.
• Auditing selected payments by vendor and bank account.

Sample query:

SELECT checkrun_name, vendor_num, vendor_name, vendor_bank_account_num,
vendor_bank_account_type, vendor_bank_num, payment_amount
FROM fv_ecs_ach_vendor_v
WHERE checkrun_name = :p_checkrun_name
ORDER BY vendor_num;

Because the view restricts to OK_TO_PAY_FLAG = 'Y', it returns only payments cleared for disbursement, making it suitable for both reporting and payment-file integration.