Search Results inv_line_count




Overview
Explore in AI Chat

Overview

APPS.FII_AP_INV_LINES_FCV is a denormalized reporting view within the Oracle Business Intelligence Applications (OBIA) / Financial Analytics for EBS data model. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the extract source for Payables invoice line fact and dimension loading into the FII (Financials Intelligence Infrastructure) warehouse. The view flattens the transactional Payables invoice line structure into a star-schema-friendly shape by joining invoice distribution, purchase order match, supplier, currency, and accounting flexfield context into a single row per invoice line.

The view is significant for users searching on MATCH_LINE_AMT_T, which is the transactional (entered) currency amount associated with matched invoice line quantities against a purchase order or receipt. Together with the business (_B) and global/functional (_G) currency counterparts, these amounts underpin procurement spend, price variance, and quantity variance analysis. The view's role is thus dual: it supports incremental ETL into the OBIA warehouse and can be queried directly for ad hoc reconciliation between Payables invoice lines and their matched PO commitments.

Underlying Base Objects

The ETRM metadata documents the view as defined entirely by its SQL SELECT text over a set of joined Payables and purchasing entities rather than exposing a single underlying base table. No base objects are separately documented in the ETRM record, so the lineage must be inferred from the column names and the FII naming conventions. The column set — including INV_LINE_PK, PO_DISTRIBUTION_ID, INV_FK, SUPPLIER_FK, and the FK-suffixed foreign keys (ORG_FK, SOB_FK, ITEM_FK, ACCOUNTING_DATE_FK) — indicates joins across AP invoice headers and lines, AP invoice distributions, PO distributions, and supplier master data. The naming convention _FCV denotes a fact-collector view, distinguishing it from dimension views and from the base staging tables populated during the ETL run. Because the metadata documents no referenced base objects, the exact join graph should be confirmed against the view's DDL in the target instance; the documented view text, however, confirms that it projects both keys and measures from these joined sources.

Key Columns

Common Use Cases and Queries

A primary use case is reconciling matched invoice line amounts against PO commitments in transactional currency, often by supplier and period. A second use case is variance analysis, comparing invoice and PO unit prices or isolating quantity variances. A third is tracking unmatched lines to identify accrual or receipt-matching exceptions.

Sample query isolating matched amounts by supplier site:

  • SELECT supplier_site_id, org_fk, SUM(match_line_amt_t) matched_amt, SUM(unmatch_line_amt_t) unmatched_amt, SUM(inv_line_count) line_cnt FROM apps.fii_ap_inv_lines_fcv WHERE accounting_date BETWEEN :p_start AND :p_end AND match_status_flag IS NOT NULL GROUP BY supplier_site_id, org_fk;

Sample query for price variance detail:

  • SELECT inv_num, po_number, inv_unit_price_t, po_unit_price_t, inv_price_var_amt_t, qty_var_amt_t, total_var_amt_t FROM apps.fii_ap_inv_lines_fcv WHERE total_var_amt_t <> 0 ORDER BY ABS(total_var_amt_t) DESC;

Because the view is a fact-collector construct, queries should generally be restricted by accounting date and organization to limit scan volume, and joined to FII dimension views via the exposed FK columns rather than re-joining to EBS base tables.