Search Results invoice_source

Overview

FII_BIS_APIPY_DRILL_V is an internal database view shipped with the Oracle Financial Intelligence (FII) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support Accounts Payable (AP) Invoice Payments Drill Down reports consumed through the PM Viewer (Page Manager Viewer) reporting framework. The view presents summarized AP invoice payment activity at the line level, comparing current-year figures against prior-year figures across period-to-date (PTD), quarter-to-date (QTD), and year-to-date (YTD) reporting horizons. It is not a user-facing reporting object and is not exposed in the standard EBS navigation; it is invoked internally by the BI Publisher report definition FII_PARAMETER_FIIAPIPY.

The view is classified as "not implemented in this database," meaning it is created dynamically by the FII report generation process rather than pre-installed in the APPS schema during standard installation. It materializes during report execution, is read by the report layout, and is subsequently cleaned up.

Underlying Base Objects

The view is defined exclusively over FII_BIS_APIPY_TEMP, a temporary staging table populated by the FII extraction programs for the AP Invoice Payments report. The ETRM 12.2.2 metadata records no other referenced base objects, and the view text confirms that all thirteen columns derive from this single source table.

Notably, the view filters the staging table with WHERE ATTRIBUTE4 = 'LINES' and REPORT_NAME = 'FII_PARAMETER_FIIAPIPY', so only line-level rows belonging to that specific report run are surfaced. This filter also explains why the column REPORTING_LEVEL, which is physically stored in ATTRIBUTE4, is always the constant value 'LINES' in the view output — a point of confusion for users searching on "reporting_level." The mapping of ATTRIBUTE4 to REPORTING_LEVEL is a hard-coded alias in the SELECT list, not a general hierarchical reporting dimension.

Key Columns

• ICX_SESSION_ID — Session identifier from ICX_SESSION, used to isolate rows belonging to a single concurrent request or viewer session.
• REPORT_NAME — Always 'FII_PARAMETER_FIIAPIPY' in this view.
• REPORTING_LEVEL — Sourced from ATTRIBUTE4; fixed to 'LINES' by the view predicate.
• REPORT_DATE — Execution date of the report.
• TRANSACTION_TYPE / INVOICE_SOURCE — Aliases of ATTRIBUTE2 and ATTRIBUTE3 respectively, providing the drill-down dimensions.
• PERIOD_NUMBER / PERIOD_NAME — Derived from DIMENSION1 (cast to NUMBER) and DIMENSION2.
• REPORT_PERIOD — From DIMENSION3; reconciles the row to PTD, QTD, YTD, PY PTD, PY QTD, or PY YTD buckets.
• CY_AMOUNT / CY_COUNT — Current-year amount and transaction count, decoded from MEASURE1–MEASURE3 based on REPORT_PERIOD.
• PY_AMOUNT / PY_COUNT — Prior-year comparatives decoded from MEASURE4–MEASURE6.

Common Use Cases and Queries

Because the view is internal, direct SQL use is generally limited to diagnostics and troubleshooting of the FII AP Invoice Payments drill-down. A typical diagnostic query compared prior-year and current-year payment volumes by period:

SELECT PERIOD_NAME, REPORT_PERIOD, SUM(CY_AMOUNT) CY_AMT, SUM(PY_AMOUNT) PY_AMT FROM FII_BIS_APIPY_DRILL_V WHERE ICX_SESSION_ID = :session_id GROUP BY PERIOD_NAME, REPORT_PERIOD ORDER BY PERIOD_NUMBER, REPORT_PERIOD;

Analysts may also isolate a single transaction type or invoice source to validate that the report totals match the underlying AP payment data, or to investigate variance between PTD and YTD figures. Because rows carry only a fixed REPORTING_LEVEL of 'LINES', any requirement for aggregate or header-level reporting must be derived by aggregating the view's measures rather than by filtering on REPORTING_LEVEL.

Oracle does not support customization of this view; all queries should be treated as read-only and tied to a valid ICX_SESSION_ID to avoid mixing data from concurrent report runs.