Search Results operating_unit_pk_key




Overview
Explore in AI Chat

Overview

The view APPS.FII_AP_DISC_LOST_TOP_SUMMARY_V is a reporting object belonging to the Oracle Financials Intelligence (FII) family of database objects shipped with Oracle E-Business Suite. In release 12.1.1 and 12.2.2, this view exposes aggregated information about discounts lost on supplier invoices, summarized at the level of the operating unit and the trading partner. It is part of the Oracle EBS Trade Management / Financials Intelligence analytical layer that supports payables performance reporting, notably the analysis of early payment discounts that were not captured.

The view carries the suffix _TOP and _SUMMARY, indicating that it presents only the highest-level grouping of discount-lost data rather than invoice-level or line-level detail. It is functionally aligned with the family of objects referenced by the trading_partner_name column, which is one of the principal descriptive attributes exposed for drill-down and grouping in trade-related reporting. Because the object is a database view rather than a table, it does not store data; it derives its result set at runtime from the underlying summary table.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over a single base object: the summary table FII_AP_DISCOUNTS_SUMMARY. No other base tables or views are documented as referenced by this definition. The view definition applies a restrictive filter on the source table with the predicate record_type = 'L', which selects only the "lost" discount records from the summary table and excludes other record types that may be stored in the same table (for example, discounts taken or available). This filter is the mechanism by which FII_AP_DISCOUNTS_SUMMARY, which may hold mixed record types, is narrowed to the discount-lost subset.

The relationship between the view and its base object is therefore one of projection and aggregation: the view reads the granular summary rows held in FII_AP_DISCOUNTS_SUMMARY, restricts them to lost-discount records, and rolls them up by operating unit and trading partner. No joins are documented, so the view is a pure select-filter-group construct over the summary table.

Key Columns

  • OPERATING_UNIT_PK_KEY — The primary key surrogate identifying the operating unit to which the summarized discount data belongs.
  • OPERATING_UNIT_NAME — The descriptive name of the operating unit, presented alongside its key for reporting convenience.
  • TRADING_PARTNER_PK_KEY — The surrogate key identifying the trading partner (supplier/vendor) associated with the lost-discount activity.
  • TRADING_PARTNER_NAME — The name of the trading partner. This is the column most directly associated with the search term, and it serves as the principal human-readable grouping attribute for supplier-level analysis.
  • INVOICE_COUNT — The count of distinct invoices (COUNT(DISTINCT INVOICE_UNIQUE_IDENTIFIER)) contributing to the summarized discount-lost amount, providing an indication of invoice volume.
  • INVOICE_AMOUNT — The summed invoice amount (SUM(INVOICE_AMOUNT)) for the grouped invoices, giving the monetary base against which the lost discount occurred.
  • DISCOUNT_LOST — The summed value of discounts lost (SUM(DISCOUNT_LOST)) for the grouping, the primary measure of analytical interest.

Common Use Cases and Queries

The view is typically consumed in payables and treasury reporting where the objective is to quantify forgone early-payment discounts and identify the trading partners or operating units responsible for the largest losses. A representative query retrieving the top trading partners by lost discount amount is shown below.

SELECT trading_partner_name,
       operating_unit_name,
       invoice_count,
       invoice_amount,
       discount_lost
FROM   apps.fii_ap_disc_lost_top_summary_v
ORDER BY discount_lost DESC;

Analysts frequently filter on a specific trading partner name to isolate a supplier's discount-lost exposure:

SELECT operating_unit_name,
       invoice_count,
       invoice_amount,
       discount_lost
FROM   apps.fii_ap_disc_lost_top_summary_v
WHERE  trading_partner_name = :p_trading_partner_name;

Because the view pre-aggregates by operating unit and trading partner, it is well suited to dashboard tiles, trend summaries, and exception reports highlighting suppliers with material lost discounts. It is not intended for invoice-level reconciliation, which should be performed against the underlying FII_AP_DISCOUNTS_SUMMARY table or the payables transaction tables themselves. Standard Oracle EBS security applies: access is granted through the APPS schema and typically via a responsibility using the FII reporting menus.