Search Results sch_payment_id

Overview

APPS.FII_AP_OPEN_PAYMT_DTL_SUM_V is a reporting view in the Oracle E-Business Suite Financial Intelligence (FII) product family. It exposes open (unpaid) payables invoice and payment detail at a summarized grain, joining invoice-level attributes to their corresponding scheduled payment records. The view is intended to support subledger-level integration and analytical reporting, particularly for flows that track trading partner activity, operating unit context, and payment due dates across the Payables subledger.

Its naming convention (FII_AP_...) places it alongside other Financial Intelligence for Payables objects, which are typically consumed by Oracle Financial Services offerings, transfer pricing and intercompany engines, and custom operational reports that need a consolidated view of open liabilities. Because the view is defined over a backlog summary table rather than the base AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES_ALL tables directly, it provides a denormalized, reporting-optimized projection rather than a normalized operational view.

Underlying Base Objects

According to the documented view text, FII_AP_OPEN_PAYMT_DTL_SUM_V is defined exclusively over a single underlying object: FII_AP_TRANS_BACKLOG_SUMMARY. No other base tables, joins, or synonyms are documented in the ETRM metadata for this view. This is significant because it means the view is a straightforward column projection and rename, not a complex multi-table join.

The defining query selects columns such as operating_unit_pk_key, trading_partner_pk_key, invoice_pk_key, invoice_amount, sch_payment_id, open_payment_amount, and payment_due_date from FII_AP_TRANS_BACKLOG_SUMMARY, aliasing several of them to more descriptive reporting names (for example INVOICE_NUM to INVOICE_NUMBER, SCH_PAYMENT_ID to PAYMENT_ID, and OPEN_PAYMENT_AMOUNT to PAYMENT_AMOUNT). The ETRM metadata lists no documented base objects beyond this summary table, and the owner is not recorded, though in practice the view resides in the APPS schema.

Key Columns

• OPERATING_UNIT_PK_KEY / OPERATING_UNIT_NAME — The primary key and descriptive name of the operating unit, providing the organizational context for each open liability.
• TRADING_PARTNER_PK_KEY / TRADING_PARTNER_NAME — The primary key and name of the trading partner, supporting intercompany and transfer pricing analysis.
• INVOICE_PK_KEY — Surrogate primary key identifying the invoice.
• INVOICE_NUMBER — The human-readable invoice number, sourced from INVOICE_NUM.
• INVOICE_AMOUNT — The total invoice amount, exposed here as the basis for matching against open payment balances. This is the column users most frequently search for.
• PAYMENT_ID — The scheduled payment identifier, sourced from SCH_PAYMENT_ID, linking the invoice to its payment schedule row.
• PAYMENT_AMOUNT — The open (unpaid) amount for the scheduled payment, sourced from OPEN_PAYMENT_AMOUNT.
• PAYMENT_DUE_DATE — The due date of the open payment, enabling aging and cash-flow analysis.

Common Use Cases and Queries

Typical consumption centers on open liability balances by operating unit or trading partner. A common query aggregates open payment amounts and reconciles them against invoice amounts:

• Open balance by trading partner: SELECT TRADING_PARTNER_NAME, SUM(PAYMENT_AMOUNT) FROM APPS.FII_AP_OPEN_PAYMT_DTL_SUM_V GROUP BY TRADING_PARTNER_NAME.
• Invoice-to-payment reconciliation: SELECT INVOICE_NUMBER, INVOICE_AMOUNT, PAYMENT_ID, PAYMENT_AMOUNT FROM APPS.FII_AP_OPEN_PAYMT_DTL_SUM_V WHERE INVOICE_AMOUNT <> PAYMENT_AMOUNT.
• Aging analysis: SELECT INVOICE_NUMBER, PAYMENT_DUE_DATE, PAYMENT_AMOUNT FROM APPS.FII_AP_OPEN_PAYMT_DTL_SUM_V WHERE PAYMENT_DUE_DATE < SYSDATE.

Because the view is a thin projection over FII_AP_TRANS_BACKLOG_SUMMARY, filters and joins should be pushed to the underlying summary table where possible. The view is version-agnostic across EBS 12.1.1 and 12.2.2, though column availability and content depend on the FII backlog population process.