Search Results invoice_lines_count

Overview

FII_AP_OP_IND_INV_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes summarized accounts payable invoice activity, aggregated by operating unit and trading partner, and is part of the Financials Intelligence / ETRM (Enterprise Tax and Reporting Model) family of objects. The view is designed to answer a narrow but frequently requested question: which operating unit / trading partner combinations have posted supplier invoice activity, and how large is that activity in terms of invoice line count, invoice count, and monetary amount.

In the context of EBS reporting and integration, this view functions as a curated, filtered projection over a pre-aggregated summary table. It is not a transaction-level view. Because the underlying summary is already consolidated, the view is efficient for dashboards, tax and reporting extracts, and third-party integrations that need period-level operational indicators rather than individual invoice documents.

Underlying Base Objects

The view is defined over a single documented base object: the table FII_AP_OP_INDICATOR_SUMMARY. No other base tables, synonyms, or views are documented in the ETRM metadata for this object, so the relationship is a straightforward one-to-one projection with a filter applied. The base table carries pre-aggregated indicator data keyed by operating unit and trading partner. The view selects only the columns relevant to invoice-level indicators and eliminates rows where INVOICE_LINES_COUNT is zero.

The resulting relationship can be expressed simply: FII_AP_OP_IND_INV_SUMMARY_V = FII_AP_OP_INDICATOR_SUMMARY WHERE INV_LINES_COUNT > 0, with a rename of columns to report-friendly aliases. Because the view imposes no joins, there is no risk of row multiplication from fan-out joins, and query performance is governed almost entirely by the base table's indexes and the selectivity of the INV_LINES_COUNT predicate.

Key Columns

• OPERATING_UNIT_PK_KEY — Primary key of the operating unit, suitable for joins to operating unit dimension tables and secure access control.
• OPERATING_UNIT_NAME — Descriptive name of the operating unit, useful for display and grouping without an additional lookup.
• TRADING_PARTNER_PK_KEY — Primary key of the trading partner (supplier/legal entity counterparty) for which invoice activity is summarized.
• TRADING_PARTNER_NAME — Descriptive name of the trading partner, provided for report labeling.
• INVOICE_LINES_COUNT — Number of invoice lines contributing to the summary row. This column also drives the view's filter; only non-zero values are returned.
• INVOICE_COUNT (inv_count) — Number of invoices represented by the summary row. This is the column users typically reference when they search for "inv_count"; note the view aliases the base column INV_COUNT to INVOICE_COUNT.
• INVOICE_AMOUNT — Total monetary amount of the summarized invoices, in the functional currency of the operating unit.

Common Use Cases and Queries

Typical use cases include reconciling invoice counts per operating unit for tax reporting, validating trading-partner activity volumes before period close, and feeding external tax engines or data warehouses with aggregated AP indicators. Because the filter uses INV_LINES_COUNT, the view is an effective starting point for "activity exists" checks, avoiding empty summary rows.

A basic retrieval of invoice counts and amounts for all active operating unit / trading partner combinations:

• SELECT operating_unit_name, trading_partner_name, invoice_count, invoice_amount FROM apps.fii_ap_op_ind_inv_summary_v ORDER BY operating_unit_name, trading_partner_name;
• SELECT operating_unit_name, SUM(invoice_count) total_invoices, SUM(invoice_amount) total_amount FROM apps.fii_ap_op_ind_inv_summary_v GROUP BY operating_unit_name;
• SELECT * FROM apps.fii_ap_op_ind_inv_summary_v WHERE trading_partner_name = :partner ORDER BY invoice_amount DESC;

The third query illustrates a common pattern: filtering to a single trading partner and ordering by amount to identify the largest contributions. Since the view returns both key and name columns, integrations can join on the primary key columns while displaying the name columns, avoiding additional lookups.