Search Results inv_lines_count

Overview

FII_AP_OP_IND_INV_SUMMARY_V is a Financial Intelligence (FII) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is purpose-built to support the Payables Invoice Summary Drill Downs Portlet, which forms part of the Oracle Financial Intelligence dashboards delivered through the EBS HTML interface. The view narrows the broader FII_AP_OP_INDICATOR_SUMMARY dataset down to trading partner and operating unit combinations that have payable invoice activity, exposing invoice volume and monetary aggregates in a form suited for dashboard display and drill-down navigation.

Because the object is a view rather than a table, it stores no data of its own. It is a lightweight, metadata-driven projection over an FII summary structure and is regenerated on query. For users searching on the term inv_amount, the relevant point is that the underlying column INV_AMOUNT is aliased to INVOICE_AMOUNT in this view; consumers must reference INVOICE_AMOUNT, not INV_AMOUNT, when selecting from the view.

Underlying Base Objects

The ETRM metadata documents the view text as selecting from FII_AP_OP_INDICATOR_SUMMARY, filtered to rows where INV_LINES_COUNT > 0. No additional referenced base objects are documented, and the view is a single-level projection with no joins, unions, or analytic functions. This means all aggregation logic — invoice counts, line counts, and the INV_AMOUNT sum — resides in FII_AP_OP_INDICATOR_SUMMARY, which is itself an FII indicator summary object likely populated by concurrent programs or materialization logic from Payables transaction tables such as AP_INVOICES_ALL and AP_INVOICE_LINES_ALL. From a dependency standpoint, FII_AP_OP_IND_INV_SUMMARY_V inherits the refresh characteristics of its parent summary; its results are only as current as the last population of FII_AP_OP_INDICATOR_SUMMARY.

Key Columns

• OPERATING_UNIT_PK_KEY — Surrogate primary key identifying the operating unit dimension, used for drill-down navigation and joins to operating unit lookups.
• OPERATING_UNIT_NAME — Descriptive name of the operating unit, presented in the portlet for readability.
• TRADING_PARTNER_PK_KEY — Surrogate key for the trading partner (supplier or party) dimension.
• TRADING_PARTNER_NAME — Display name of the trading partner associated with the summarized invoices.
• INVOICE_LINES_COUNT — Number of invoice lines aggregated for the operating unit and trading partner combination. Source column is INV_LINES_COUNT.
• INVOICE_COUNT — Number of invoices aggregated. Source column is INV_COUNT.
• INVOICE_AMOUNT — Total monetary value of the summarized invoices. This is the aliased form of the source column INV_AMOUNT and is the field most commonly sought by users searching on "inv_amount".

Common Use Cases and Queries

The primary use case is driving the Payables Invoice Summary Drill Downs Portlet, where each row represents an operating unit and trading partner pairing and the portlet displays invoice counts and amounts. Analysts also query the view directly to reconcile invoice totals by operating unit or to feed downstream reporting extracts. Because only rows with INV_LINES_COUNT greater than zero are included, the view is already filtered to active invoice activity, which simplifies most reporting logic.

A basic query retrieving invoice totals by operating unit and trading partner:

• SELECT operating_unit_name, trading_partner_name, invoice_count, invoice_lines_count, invoice_amount FROM fii_ap_op_ind_inv_summary_v ORDER BY invoice_amount DESC;
• SELECT operating_unit_name, SUM(invoice_amount) total_amount FROM fii_ap_op_ind_inv_summary_v GROUP BY operating_unit_name;
• SELECT trading_partner_name, invoice_count, invoice_amount FROM fii_ap_op_ind_inv_summary_v WHERE operating_unit_name = :p_operating_unit;

When troubleshooting, note that the view cannot return INV_AMOUNT by name; invalid identifier errors on that column indicate the query was written against the base summary rather than this view. Access is granted through the APPS schema, and responsibility-level security on the parent FII summary determines which operating units are visible to the querying user.