Search Results fii_ap_inv_paymts_fcv

Overview

FII_AP_INV_PAYMTS_FCV is an internal Oracle E-Business Suite view owned by the APPS schema and classified under the FII (Financial Intelligence) product family. Its documented purpose is warehouse data extraction, meaning it serves as a flattened staging layer that feeds the Financial Intelligence data warehouse rather than as an end-user inquiry screen. The view exposes Accounts Payable invoice and payment activity in a denormalized form, combining invoice-level attributes, payment-level attributes, currency and exchange rate information, and accounting flexfield components into a single row-per-transaction shape. Because the Financial Intelligence product is designed for analytical reporting and dimensional modeling, this view abstracts the join logic normally required across AP invoices, payments, and accounting distributions, and presents surrogate foreign keys such as INV_FK, PAYMENT_FK, SUPPLIER_FK, SOB_FK, and GEOGRAPHY_FK for downstream ETL.

Underlying Base Objects

The ETRM metadata records no documented base objects for this view; the view text is defined as a direct SELECT against a set of columns rather than an explicit join list in the excerpt provided. In practice, a view of this shape and naming convention in FII is defined over AP base tables including AP_INVOICES_ALL, AP_INVOICE_PAYMENTS_ALL, AP_PAYMENT_SCHEDULES_ALL, AP_CHECKS_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and the GL daily conversion and accounting flexfield structures. The columns SEQ_ID, INV_PK-style identifiers, and the INV_PAYMENT_PK primary key column indicate the grain is the invoice-payment intersection, with one row representing a payment applied to an invoice. The B, G, and T column suffixes follow the standard FII convention of Base, Global, and Transaction (entered) currency amounts.

Key Columns

• INV_EXCHANGE_RATE / INV_EXCHANGE_DATE / INV_EXCHANGE_RATE_TYPE — the exchange rate, effective date, and rate type applied at invoice entry, populated from the invoice header.
• PAYMENT_EXCHANGE_RATE / PAYMENT_EXCHANGE_DATE / PAYMENT_EXCHANGE_RATE_TYPE — the corresponding rate, date, and type applied at payment time.
• GLOBAL_CURRENCY_RATE — the reporting or global currency conversion rate used to translate base amounts into the warehouse global currency.
• INV_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, BASE_CURRENCY_CODE — the invoice, payment, and functional (set of books) currencies.
• PAYMENT_AMT_B / PAYMENT_AMT_G / PAYMENT_AMT_T — payment amount expressed in base, global, and transaction currency.
• DISC_AMT_TAKEN_B / _G / _T and DISC_AMT_LOST_B / _G / _T — discounts taken versus discounts lost, segmented by currency basis.
• INV_FK, PAYMENT_FK, SUPPLIER_FK, SOB_FK, ORG_FK, GEOGRAPHY_FK, PAYMENT_TERM_FK, CHART_OF_ACCOUNTS_ID — warehouse dimension foreign keys.
• GL_ACCT1_FK through GL_ACCTn_FK — derived accounting flexfield segments built by decoding the GL_SEG concatenated string, with the NA_EDW token preserved for unmapped segments.
• ACCRUAL_POSTED_FLAG, CASH_POSTED_FLAG, POSTED_FLAG, FUTURE_PAY_POSTED_FLAG — accounting and posting status indicators.

Common Use Cases and Queries

The view is primarily consumed by Financial Intelligence ETL processes and by analysts reconciling AP invoice and payment data across currencies. A typical query retrieving exchange rate context for a settlement follows.

• Invoice-to-payment rate comparison: SELECT INV_NUM, INV_EXCHANGE_RATE, PAYMENT_EXCHANGE_RATE, PAYMENT_AMT_T, PAYMENT_AMT_B FROM FII_AP_INV_PAYMTS_FCV WHERE INV_EXCHANGE_RATE_TYPE = 'Corporate';
• Discount analysis by currency basis: SELECT SUPPLIER_FK, SUM(DISC_AMT_TAKEN_B), SUM(DISC_AMT_LOST_B) FROM FII_AP_INV_PAYMTS_FCV GROUP BY SUPPLIER_FK;
• Warehouse extraction by period: SELECT SEQ_ID, ACCOUNTING_DATE, INV_FK, PAYMENT_FK, SOB_FK FROM FII_AP_INV_PAYMTS_FCV WHERE ACCOUNTING_DATE BETWEEN :start_date AND :end_date;
• Unposted cash validation: SELECT INV_NUM, PAYMENT_FK, CASH_POSTED_FLAG FROM FII_AP_INV_PAYMTS_FCV WHERE CASH_POSTED_FLAG = 'N';

As an undocumented internal object with no declared base tables in ETRM, the view should be treated as subject to change between 12.1.1 and 12.2.2; direct dependency in custom code is discouraged in favor of the supported FII public interfaces.