Search Results fii_gl_je_summary_b




Overview
Explore in AI Chat

Overview

FII_GL_JE_SUMMARY_B is a base summary table owned by the FII schema within the Oracle E-Business Suite Financial Intelligence (FII) product family. It stores pre-aggregated General Ledger journal entry balances, rolled up across accounting period, company, cost center, financial category, product category, ledger, and user-defined dimension combinations. Its primary role in Oracle EBS 12.1.1 and 12.2.2 is to support revenue and expense related portlets displayed to financial users, allowing summary performance figures to be retrieved without scanning detail GL balances each time a dashboard is rendered.

The table holds 30 documented columns in the ETRM 12.1.1 schema. Mined from its foreign key structure, the heuristic Data Vault classification is standalone, meaning the table does not participate in a classic hub-link-satellite chain through its documented FKs alone. As a modeling suggestion, this classification indicates the table behaves as an independently maintained aggregate, best treated as a derived fact or summary satellite whose grain is defined by its unique business key rather than by an upstream hub reference.

Key Information Stored

The table's uniqueness is enforced by the candidate business key FII_GL_JE_SUMMARY_B_U1, defined over the tuple (PERIOD_TYPE_ID, TIME_ID, COMPANY_ID, COST_CENTER_ID, FIN_CATEGORY_ID, LEDGER_ID, USER_DIM1_ID, USER_DIM2_ID, JE_SOURCE, JE_CATEGORY, CHART_OF_ACCOUNTS_ID, PROD_CATEGORY_ID, POSTED_DATE). This composite key establishes the aggregation grain and should be treated as the logical business key rather than a single surrogate identifier.

The most significant columns fall into three groups:

Common Use Cases and Queries

The principal use case is portlet rendering for revenue and expense dashboards. A typical query filters by ledger, period and company to retrieve summarized amounts by financial or product category:

  • Period-to-period revenue and expense comparison for a given company and ledger, aggregating AMOUNT_B by PERIOD_TYPE_ID and TIME_ID.
  • Cost center variance reporting using COST_CENTER_ID with FIN_CATEGORY_ID to isolate expense categories.
  • Budget-versus-actual style reporting using COMMITTED_AMOUNT_PRIM and OBLIGATED_AMOUNT_PRIM against PRIM_AMOUNT_G.
  • Multi-currency summaries by selecting FUNCTIONAL_CURRENCY with SEC_AMOUNT_G.
  • Drill-through identification of the source journals behind a summary cell using JE_SOURCE and JE_CATEGORY.

Queries should always constrain on the leading columns of the unique index to exploit FII_GL_JE_SUMMARY_B_U1 efficiently.

Related Objects

Two foreign keys are documented on this table:

  • PN_COMPANIES_ALL — referenced via FII_GL_JE_SUMMARY_B.COMPANY_ID, providing company name and attributes for organizational roll-ups.
  • GL_MGT_SEG_UPGRADE_H — referenced via FII_GL_JE_SUMMARY_B.CHART_OF_ACCOUNTS_ID, linking summary rows to chart of accounts management segment upgrade history.

Beyond these documented relationships, the table logically integrates with GL summary and balance objects such as GL_BALANCES and GL_CODE_COMBINATIONS through the CHART_OF_ACCOUNTS_ID and ledger columns, and with FII portlet and dashboard views that consume the summarized figures for financial intelligence reporting. The absence of additional inbound foreign keys reinforces the standalone classification and indicates the table is populated by FII extraction or concurrent programs rather than through declarative referential constraints.