Search Results payment_due_date

Overview

The view FII_AP_OPEN_PAYMT_DTL_SUM_V is a reporting and integration object within the Oracle E-Business Suite Financial Intelligence (FII) product family. Its documented purpose is to support the Payables Open Payments Detail Drill Downs Portlet, a dashboard component that allows users to navigate from aggregated Payables open-payment figures down to the underlying payment detail records associated with individual invoices. The view thus acts as a presentation-layer artifact rather than a transactional store: it exposes a denormalised, drill-ready result set that blends invoice-level attributes with payment-level attributes so that a portlet region can render summary rows without performing complex joins at runtime.

In the ETRM 12.2.2 metadata this object is flagged as belonging to an Obsolete FII module, and the implementation notes state that it is not implemented in this database. That distinction is significant: the view is a documented, historical artifact of the FII product rather than a live database object in a standard 12.1.1 or 12.2.2 instance. Its structure nonetheless remains informative for understanding how the FII Open Payments drill-down was modelled, and it is frequently referenced when troubleshooting or reconstructing legacy FII reports.

Underlying Base Objects

The ETRM metadata records the view text as a straightforward projection over a single source object: FII_AP_TRANS_BACKLOG_SUMMARY. No additional base tables, synonyms, or views are documented as referenced objects, which indicates that the summarisation and any necessary Payables joins are resolved inside the backlog summary object itself. In other words, FII_AP_OPEN_PAYMT_DTL_SUM_V is a thin selection layer: it does not itself aggregate, join to AP_INVOICES_ALL, AP_PAYMENT_SCHEDULES_ALL, or AP_CHECKS_ALL, but depends entirely on the backlog summary to have already materialised the invoice-to-payment relationships. The documented referenced base objects list is empty, consistent with the view being defined purely over the FII backlog summary.

Key Columns

• OPERATING_UNIT_PK_KEY and OPERATING_UNIT_NAME — the ledger/operating unit context for the payables transactions, used for organisational drill filtering.
• TRADING_PARTNER_PK_KEY and TRADING_PARTNER_NAME — the supplier (trading partner) identifier and display name.
• INVOICE_PK_KEY — the surrogate primary key of the invoice, which is the column most directly associated with the search term invoice_pk_key. It is the join/link key a drill-down portlet uses to navigate from the summary row to the invoice detail.
• INVOICE_NUMBER — the user-visible invoice number, aliased from INVOICE_NUM.
• INVOICE_AMOUNT — the invoiced amount associated with the row.
• PAYMENT_ID — aliased from SCH_PAYMENT_ID; identifies the payment schedule/payment record.
• PAYMENT_AMOUNT — aliased from OPEN_PAYMENT_AMOUNT; the open (unpaid) amount for that payment.
• PAYMENT_DUE_DATE — the due date used for ageing and prioritisation in the portlet.

Common Use Cases and Queries

The principal use case is powering the Open Payments Detail drill-down portlet, where INVOICE_PK_KEY serves as the link parameter. A representative query mirroring the documented view definition is:

• SELECT operating_unit_name, trading_partner_name, invoice_number, invoice_amount, payment_amount, payment_due_date FROM fii_ap_open_paymt_dtl_sum_v WHERE trading_partner_name = :supplier;
• SELECT * FROM fii_ap_open_paymt_dtl_sum_v WHERE invoice_pk_key = :invoice_pk_key; — the typical drill-down lookup for a single invoice.
• Ageing analysis of open payments: SELECT operating_unit_name, SUM(payment_amount) FROM fii_ap_open_paymt_dtl_sum_v GROUP BY operating_unit_name;

Because the object is obsolete and not implemented, these queries are best regarded as reference patterns for FII-era reporting rather than executable statements in a current 12.1.1 or 12.2.2 environment.