Search Results days_outstanding

Overview

APPS.FII_AP_OPEN_PAYMT_SUMMARY_V is a reporting view in the Oracle E-Business Suite Financials Intelligence (FII) schema, part of the Oracle Financial Services Accounting Hub and EBS financial analytics layer. It presents an aggregated snapshot of open accounts payable payments, summarized by operating unit and trading partner. In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as a semantic abstraction over the AP transaction backlog data, delivering pre-computed payment counts, open payment amounts, and aging metrics that analysts and reporting tools can consume without recomputing aggregations at query time.

Because the view performs the GROUP BY and summation internally, it is well suited for dashboards, payables aging reports, and integration extracts that require a consolidated view of outstanding liabilities by operating unit and trading partner. The name itself reflects its purpose: it is a summary of open payment amounts.

Underlying Base Objects

The view is defined over a single documented base object: FII_AP_TRANS_BACKLOG_SUMMARY. This base table stores transaction backlog summary records, including scheduled payment identifiers, open payment amounts, and days-outstanding measures. The view does not introduce joins to other tables in its documented definition; instead, it applies grouping and aggregation logic directly on the backlog summary table.

Conceptually, the backlog summary table is derived from upstream payables transaction data (invoice and payment distributions), and this view exposes that data at the operating unit / trading partner grain. Because the view is a simple aggregate projection, it inherits the refresh characteristics of FII_AP_TRANS_BACKLOG_SUMMARY — data reflects whatever state the underlying backlog table currently holds, typically populated by FII concurrent programs or ETL processes.

Key Columns

• OPERATING_UNIT_PK_KEY — Surrogate primary key identifying the operating unit; used for joins to operating unit dimensions.
• OPERATING_UNIT_NAME — Descriptive name of the operating unit, carried through the GROUP BY for readability.
• TRADING_PARTNER_PK_KEY — Surrogate key for the trading partner (supplier/vendor entity in AP context).
• TRADING_PARTNER_NAME — Descriptive trading partner name.
• PAYMENT_COUNT — COUNT(SCH_PAYMENT_ID); the number of scheduled payments in the group.
• PAYMENT_AMOUNT — SUM(OPEN_PAYMENT_AMOUNT); the total open (unpaid) amount for the group. This column directly answers the "open_payment_amount" search term.
• AVG_DAYS_OUTSTANDING — AVG(DAYS_OUTSTANDING); simple average aging of open payments.
• WT_DAYS_OUTSTANDING — Weighted average days outstanding, computed as SUM(DAYS_OUTSTANDING * OPEN_PAYMENT_AMOUNT) / SUM(OPEN_PAYMENT_AMOUNT). This weights aging by open amount and is the preferred metric for true aging analysis.

Common Use Cases and Queries

The view is typically queried to produce payables aging and exposure reports by operating unit and trading partner. A common scenario is identifying trading partners with the largest open balances or the longest weighted aging.

Total open payments by operating unit:

• SELECT operating_unit_name, SUM(payment_amount) total_open FROM apps.fii_ap_open_paymt_summary_v GROUP BY operating_unit_name ORDER BY total_open DESC;

Top trading partners by weighted days outstanding:

• SELECT trading_partner_name, payment_amount, wt_days_outstanding FROM apps.fii_ap_open_paymt_summary_v WHERE payment_amount > 0 ORDER BY wt_days_outstanding DESC;

Because the view aggregates at operating unit and trading partner level, it should not be joined to detail-level AP tables without accounting for the summarization grain. It is best consumed directly by BI Publisher reports, OBIEE repositories, or ad hoc SQL where consolidated open-payment exposure is required.