Search Results invoice_unique_identifier




Overview
Explore in AI Chat

Overview

The view APPS.FII_AP_DISC_LOST_DTL_SUMMARY_V is a reporting object within the Oracle E-Business Suite Financials Intelligence (FII) product family, which underpins the Oracle Financial Analytics (OFA) application. It exposes summarized information about discounts lost on Oracle Payables invoices, presented at the granularity of operating unit, trading partner, and individual invoice. The view is defined as a filtered and aggregated projection over the underlying summary table FII_AP_DISCOUNTS_SUMMARY, restricting output to rows where RECORD_TYPE = 'L' (the designation for "lost" discount records) and rolling amounts up by the invoice-level grouping keys.

Because it collapses lower-level summary detail into a predictable invoice-oriented grain, the view serves as a convenient source for analytical reports, dashboard queries, and extract routines that must reconcile discount-loss amounts to a specific invoice within a specific business unit. The same definition is valid across both Oracle EBS 12.1.1 and 12.2.2, since the FII schemas and the Financials Intelligence database objects remain consistent between these releases and are not affected by the Online Patching (adopting) architecture introduced in 12.2.

Underlying Base Objects

The view is defined over a single base object, FII_AP_DISCOUNTS_SUMMARY, which stores pre-aggregated payable discount metrics. The relationship is direct and non-join-based: no additional tables, lookup views, or external references are documented for this definition. The FROM clause references only FII_AP_DISCOUNTS_SUMMARY, and the WHERE clause applies the single predicate RECORD_TYPE = 'L' to isolate lost discounts.

Key attributes of the relationship are:

  • Filtering: only records flagged as lost discounts (RECORD_TYPE = 'L') are surfaced; earned or other record types present in the base table are excluded.
  • Aggregation: the view applies SUM to INVOICE_AMOUNT and DISCOUNT_LOST, so multiple underlying summary rows for the same invoice are consolidated into one output row.
  • Grouping: aggregation occurs over the full set of non-measure columns, producing one row per operating unit, trading partner, invoice identifier, invoice number, and invoice date.
  • Audit ownership: the ETRM metadata records no documented referenced base objects beyond the summary table, and no owner-specific comments are supplied.

Key Columns

  • OPERATING_UNIT_PK_KEY — Surrogate primary key of the operating unit, used for organizational partitioning.
  • OPERATING_UNIT_NAME — Descriptive name of the operating unit for display and grouping in reports.
  • TRADING_PARTNER_PK_KEY — Surrogate key of the supplier or trading partner associated with the discount.
  • TRADING_PARTNER_NAME — Descriptive name of the trading partner.
  • INVOICE_PK_KEY — The invoice unique identifier. In the view definition this column is selected from the base column INVOICE_UNIQUE_IDENTIFIER and aliased to INVOICE_PK_KEY. This aliasing is significant for users searching on "invoice_unique_identifier," since the searchable name is at the base-table level while the exposed view column is labeled INVOICE_PK_KEY.
  • INVOICE_NUMBER — The human-readable invoice number, sourced from INVOICE_NUM.
  • INVOICE_DATE — Accounting or invoice date used as part of the grouping key.
  • INVOICE_AMOUNT — Aggregated invoice amount (SUM(INVOICE_AMOUNT)).
  • DISCOUNT_LOST — Aggregated discount amount forfeited (SUM(DISCOUNT_LOST)).

Common Use Cases and Queries

Typical applications include supplier-level discount-loss analysis, operating-unit performance reporting, and reconciliation of forfeited discounts back to invoice records. Because the invoice identifier is exposed as INVOICE_PK_KEY, queries that were written against the base table's INVOICE_UNIQUE_IDENTIFIER must reference the alias when targeting this view.

  • Retrieving lost discounts for one invoice:
SELECT operating_unit_name,
       trading_partner_name,
       invoice_number,
       invoice_date,
       invoice_amount,
       discount_lost
FROM   apps.fii_ap_disc_lost_dtl_summary_v
WHERE  invoice_pk_key = :p_invoice_pk_key;
  • Summarizing lost discounts by trading partner across an operating unit:
SELECT trading_partner_name,
       SUM(discount_lost) total_discount_lost
FROM   apps.fii_ap_disc_lost_dtl_summary_v
WHERE  operating_unit_name = :p_operating_unit
GROUP  BY trading_partner_name
ORDER  BY total_discount_lost DESC;
  • Period-based reporting of forfeited discounts using the invoice date for time bucketing.

Because the view performs aggregation and exposes only summarized measures, it should be used for reporting and analytics rather than transactional inquiry; detail-level reconciliation should reference the underlying FII_AP_DISCOUNTS_SUMMARY table directly.