Search Results payment_count

Overview

FII_AP_OPEN_PAYMT_SUMMARY_V is a reporting view belonging to the Financial Intelligence (FII) product family in Oracle E-Business Suite. FII was Oracle's earlier-generation financial analytics and dashboard offering, predating the current Oracle Financials data model and the later OBIA/BI-Apps content packs. In Oracle EBS 12.1.1 and 12.2.2, FII is classified as obsolete, meaning Oracle no longer ships or supports the product as a strategic solution and, in most installations, the underlying objects are not deployed.

The view's documented purpose is to support the Payables Open Payments Summary Drill Downs portlet. It aggregates open (unpaid) Payables transactions into an operating-unit and trading-partner summary, allowing a dashboard portlet to display a rolled-up count, value, and aging profile of open payments, and then drill down from that summary into the underlying detail rows. The view is therefore an analytics-layer construct rather than a transactional or integration object.

The user search term sch_payment_id corresponds to the SCH_PAYMENT_ID column referenced in the view definition. This is the identifier used to count open payment records within each operating-unit and trading-partner grouping, and it is the key that drives the drill-down behavior of the portlet.

Underlying Base Objects

The view is defined over a single base object, FII_AP_TRANS_BACKLOG_SUMMARY, which serves as the FII backlog summary table for Payables open transactions. The ETRM documentation records the base object as FII_AP_TRANS_BACKLOG_SUMMARY and notes that no other referenced base objects are documented. The documented implementation status for FII_AP_OPEN_PAYMT_SUMMARY_V is "Not implemented in this database," confirming that in a standard 12.1.1 or 12.2.2 environment the view and its base table are typically absent unless the FII schema was explicitly installed.

The view performs no joins to the standard AP_PAYMENT_SCHEDULES or AP_INVOICES_ALL tables directly. Instead, it depends entirely on the FII backlog summary layer, which is expected to have been populated by FII's own extraction and loading processes. This architecture means the view cannot be repointed at standard Payables tables without redesign, and any replacement reporting must be built against the native Payables data model.

Key Columns

• OPERATING_UNIT_PK_KEY / OPERATING_UNIT_NAME — The operating unit grouping key and its descriptive name; the primary organizational dimension for the summary.
• TRADING_PARTNER_PK_KEY / TRADING_PARTNER_NAME — The supplier (trading partner) grouping key and name.
• PAYMENT_COUNT — COUNT(SCH_PAYMENT_ID), the number of open payment schedule records in the group.
• PAYMENT_AMOUNT — SUM(OPEN_PAYMENT_AMOUNT), the total open payment value.
• AVG_DAYS_OUTSTANDING — AVG(DAYS_OUTSTANDING), the simple average age of open items.
• WT_DAYS_OUTSTANDING — SUM(DAYS_OUTSTANDING * OPEN_PAYMENT_AMOUNT) / SUM(OPEN_PAYMENT_AMOUNT), the amount-weighted average days outstanding, which is the more meaningful aging metric because larger liabilities carry proportionally greater weight.

Common Use Cases and Queries

The primary use case is the Payables Open Payments Summary drill-down portlet, where each row represents an operating-unit/trading-partner combination and the calculated columns drive KPI tiles and aging charts. A secondary use is ad hoc analysis of open payment concentration by supplier or operating unit.

A representative query is:

• SELECT operating_unit_name, trading_partner_name, payment_count, payment_amount, avg_days_outstanding, wt_days_outstanding FROM fii_ap_open_paymt_summary_v ORDER BY payment_amount DESC;

Because the view is obsolete and usually not implemented, teams on 12.1.1/12.2.2 should treat it as a reference design rather than a reportable object. Equivalent results are typically produced directly from AP_PAYMENT_SCHEDULES joined to AP_INVOICES_ALL, grouping by operating unit and supplier, with a weighted aging calculation substituted for the FII formula.