Results for “fv_ach_ctx_vendor_v”

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

Overview

FV_ACH_CTX_VENDOR_V is a reporting view delivered within the Federal Financials (FV) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its purpose is to present payment and vendor information in the flat, positional layout required for NACHA ACH CTX (Corporate Trade Exchange) vendor payment files. CTX formatting differs from simpler ACH formats in that it embeds remittance data and requires the payment record to be accompanied by carefully truncated originator, receiver, and financial-institution fields. The view assembles these fields — agency identity, agency banking details, vendor identity, vendor banking details, and the individual check/payment amount — into a single denormalized result set that an outbound payment program or report can consume without further joining.

The view is documented as "not implemented in this database" in the ETRM metadata, meaning its definition is shipped but the underlying objects may not exist in every environment; it becomes available only when the relevant Federal Financials and Payables components are installed. Because it draws on Human Resources organization and location tables in addition to Payables tables, it is only valid where those modules are licensed and configured.

Underlying Base Objects

The view is defined over a join of the following documented base objects: HR_ORGANIZATION_UNITS (HRORG), FV_SYSTEM_PARAMETERS_V (FVS), HR_LOCATIONS (HRLOC), AP_SELECTED_INVOICES (APSI), PO_VENDORS (POV), PO_VENDOR_SITES (POVS), AP_BANK_ACCOUNTS (APBA, used for the vendor bank account and joined to a bank-branch source via AP_BANK_BRANCHES), and ASIC, the ACH selected-invoice/check source that supplies the payment-level vendor name, address, and check amount. The join correlates each selected invoice with its vendor, vendor site, vendor bank account, and the paying agency's organization unit, location, and ALC code from the FV system parameters. The AP_BANK_BRANCHES table is the source of the bank branch number that supplies the nine-position routing field through APBB.BANK_NUM and the branch type through APBB2.BANK_BRANCH_TYPE.

Key Columns

• CHECKRUN_NAME, SELECTED_CHECK_ID, VENDOR_CHECK_ID, VENDOR_CHECK_AMT, CHECK_NUM — payment run and individual payment identifiers and amounts.
• AGENCY_NAME, AGENCY_ALC_CODE, AGENCY_ADDRESS_LINE_1/2, AGENCY_CITY_STATE_ZIP, AGENCY_TELEPHONE_NUMBER_1 — originating agency identity and contact data, upper-cased and length-truncated.
• AGENCY_BANK_ACCOUNT_TYPE — three-character branch/account type derived from AP_BANK_BRANCHES.BANK_BRANCH_TYPE.
• VENDOR_NUM, VENDOR_NAME, VENDOR_NUM_1099, VENDOR_NAME1, VENDOR_NUMBER1 — vendor identifiers, including the 1099 tax number and the remittance-level name/number.
• VENDOR_BANK_ACCOUNT_NUM, CHECK_DIGITS, VENDOR_BANK_ACCOUNT_TYPE, VENDOR_BANK_NUM — receiver deposit account and nine-digit zero-padded routing number.
• INVOICE_NUM, PAYMENT_AMOUNT — invoice-level reference and amount.
• VENDOR_ADDRESS_LINE1–4 — remittance address fields taken from the ACH check source.

Character fields are consistently wrapped in UPPER and SUBSTR or RPAD to enforce fixed-width ACH positioning.

Common Use Cases and Queries

Typical use is to feed an ACH CTX payment file generator or to audit vendor disbursements by bank. A representative query is:

SELECT checkrun_name, vendor_num, vendor_name, vendor_bank_num, vendor_bank_account_num, vendor_check_amt FROM fv_ach_ctx_vendor_v WHERE checkrun_name = :checkrun;

To reconcile payments against the AP_BANK_BRANCHES routing number, filter on vendor_bank_num. Because the view is not implemented in all databases, the first validation step is to confirm the object exists and compiles. Where it is unavailable, the same data can be reconstructed by joining AP_SELECTED_INVOICES, PO_VENDORS, AP_BANK_ACCOUNTS, and the HR organization and location tables directly.