Search Results na_edw




Overview
Explore in AI Chat

Overview

APPS.FII_AP_SCH_PAYMTS_FCV is a Financial Intelligence (FII) flexfield-composed view exposed under the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The _FCV suffix denotes a "flexfield-composed view," a construct introduced by the Oracle Financials Intelligence/ETRM (Enterprise Territory and Resource Management) data model to flatten and denormalize key flexfield segments and descriptive attributes into discrete, reporting-friendly columns. The view surfaces scheduled payment records for Oracle Payables, presenting a consolidated picture of invoice payment scheduling across payment terms, discounts, currencies, and accounting contexts.

Its principal role is to serve as a semantic layer for analytics and integration. Rather than requiring downstream consumers to resolve key flexfield combinations (in this case, the GL account segments), the view pre-splits the GL_SEG concatenated flexfield string into individual account segment columns (GL_ACCT1_FK, GL_ACCT2_FK, etc.), each carrying a special-case sentinel value of NA_EDW where the underlying segment is not applicable or is a defined placeholder. This design makes the view well suited to extract-transform-load pipelines and dimensional modeling in a data warehouse context.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and the view text provided is a direct column projection rather than a join definition. In practice, FII_AP_SCH_PAYMTS_FCV is defined over the AP scheduled payments fact structure — conceptually the AP_SCHEDULED_PAYMENTS / AP_INVOICE_PAYMENTS family of tables and their FII-derived fact equivalent. The view is a thin transformation layer: it selects named columns from a generalized fact and applies the flexfield-splitting logic to GL_SEG to produce the account segment foreign keys. Because the base objects are not explicitly documented, consumers should treat the view as the authoritative interface and avoid deriving dependencies from the view text alone.

Key Columns

Common Use Cases and Queries

Typical uses include cash-flow forecasting, days-payable-outstanding analytics, discount-capture performance reporting, and supplier balance dashboards. Because the view exposes translated and accounted amounts alongside account segment keys, it is frequently the target of financial data warehouse loads. A representative query returning scheduled payments at risk of discount loss for a given ledger is:

SELECT invoice_num, supplier_fk, due_date, disc_date_fk, remaining_inv_amt_at_risk_g
FROM apps.fii_ap_sch_paymts_fcv
WHERE set_of_books_id = :sob_id
AND hold_flag = 'N'
AND remaining_inv_amt_at_risk_g > 0
ORDER BY disc_date_fk;

For account-segment level reporting, consumers filter on the decomposed keys using the NA_EDW sentinel to isolate placeholder segments. Care should be exercised when joining to GL_CODE_COMBINATIONS, since the decomposed segments reflect the flexfield composition logic rather than a simple substring split.