Search Results prod_category_id




Overview
Explore in AI Chat

Overview

FII_GL_JE_SUMMARY_B_P_V is a reporting view owned by the APPS schema within the FII (Financial Intelligence) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes summarized General Ledger journal entry data across multiple analytical dimensions, including time, period type, product category, journal source and category, ledger, chart of accounts, company, cost center, and user-defined dimensions. The view is a thin projection over the FII_GL_JE_SUMMARY_B base table; the "_P_V" naming convention identifies it as a protected presentation-layer view that shields downstream FII reports, dashboards, and extract processes from direct dependency on the physical summary table. Because the view includes date-tracked audit columns (CREATION_DATE, LAST_UPDATE_DATE, and their user/login counterparts), it is also suitable for incremental extraction and change-detection patterns in data warehouse and reconciliation pipelines.

Underlying Base Objects

The view is defined exclusively over a single documented base object: FII_GL_JE_SUMMARY_B. Its defining text maps each base column directly to an exposed column, aliasing two of them — PRIM_AMOUNT_G becomes AMOUNT_G, and USER_DIM1_ID and USER_DIM2_ID become FUD1_ID and FUD2_ID respectively. All remaining columns (TIME_ID, PERIOD_TYPE_ID, PROD_CATEGORY_ID, JE_SOURCE, JE_CATEGORY, LEDGER_ID, CHART_OF_ACCOUNTS_ID, FUNCTIONAL_CURRENCY, AMOUNT_B, FIN_CATEGORY_ID, COMPANY_ID, and COST_CENTER_ID) are passed through unchanged. No additional joins, unions, or filter predicates are documented in the view text, so the view does not alter row cardinality relative to FII_GL_JE_SUMMARY_B. The ETRM 12.2.2 metadata records no additional referenced base objects beyond this summary table.

Key Columns

  • TIME_ID / PERIOD_TYPE_ID — Analytical time dimension identifier and the accounting period type used to group the summarized balances.
  • LEDGER_ID / CHART_OF_ACCOUNTS_ID — Identifies the ledger and its associated chart of accounts for which the summarized amounts were accumulated.
  • FUNCTIONAL_CURRENCY — The functional currency code in which amounts are expressed; this column is central to currency-filtered reporting and to the "functional_currency" search term, since it determines which ledger balances can be aggregated or compared without translation.
  • AMOUNT_B / AMOUNT_G — Entered (base) amount and the primary functional-currency amount, exposed as PRIM_AMOUNT_G in the base table and aliased to AMOUNT_G in the view.
  • JE_SOURCE / JE_CATEGORY — Journal source and journal category, enabling segregation of transactions by origin and accounting purpose.
  • FIN_CATEGORY_ID, COMPANY_ID, COST_CENTER_ID, FUD1_ID, FUD2_ID — Financial category and organizational dimensions, including two user-defined dimensions surfaced with the FUD aliases.
  • PROD_CATEGORY_ID — Product category dimension used in profitability and product-line analysis.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN supporting incremental loads and data lineage tracking.

Common Use Cases and Queries

Typical consumers include FII financial dashboards, GL summary reconciliation reports, and ETL routines that stage summarized journal activity. A common pattern filters by functional currency and ledger to isolate reporting-currency balances:

SELECT ledger_id, functional_currency, je_source, je_category,
       TIME_ID, AMOUNT_B, AMOUNT_G
  FROM APPS.FII_GL_JE_SUMMARY_B_P_V
 WHERE functional_currency = 'USD'
   AND ledger_id = :p_ledger_id;

Incremental extraction for a data warehouse relies on the audit columns:

SELECT time_id, ledger_id, chart_of_accounts_id, functional_currency,
       company_id, cost_center_id, fud1_id, fud2_id,
       amount_b, amount_g, last_update_date
  FROM APPS.FII_GL_JE_SUMMARY_B_P_V
 WHERE last_update_date >= :p_since_date;

Organizational rollups generally aggregate the dimension identifiers and both amount columns while constraining on period type and journal source, and currency-specific questions are resolved directly against FUNCTIONAL_CURRENCY, which is exposed unchanged from the base summary table.