Search Results fin_metric_code

Overview

GL_OASIS_FIN_METRICS_11I is a General Ledger (GL) table in the Oracle E-Business Suite database, owned by the GL schema and marked VALID in the ETRM 12.2.2 data dictionary. Its documented purpose is to store summarized financial metrics, meaning it holds pre-aggregated financial values derived from the ledger rather than raw journal balances. Rather than retaining transaction-level detail, the table persists quarterly and annual metric values keyed by set of books and metric definition, which makes it a compact reporting substrate for financial analysis and comparative reporting.

In Oracle EBS 12.1.1 and 12.2.2, the table is not part of the core posting engine. It supports financial reporting and analytical products that require metrics summarized outside the standard GL_BALANCES aggregation path. The 15 documented columns are narrow and purpose-built, and the structure is stable across both 12.1 and 12.2 releases. A heuristic Data Vault classification, mined from the foreign key structure, places this table as satellite-leaning. In modeling terms, that suggests the table behaves as a dependent satellite: the combination of SET_OF_BOOKS_ID and FIN_METRIC_CODE provides the business identity, while the period and value columns are descriptive attributes that change across reporting cycles. This classification should be treated as a modeling suggestion for warehousing initiatives rather than a statement of Oracle's internal intent.

Key Information Stored

The table's documented columns separate cleanly into identity, metric definition, and measure groups:

• SET_OF_BOOKS_ID — Identifies the ledger whose financials are being summarized. This column participates in the primary key.
• FIN_METRIC_CODE — The metric identifier. Given the user search term, this is the operative lookup column: it names the metric being stored. It is the second component of the primary key.
• EFFECTIVE_PERIOD_NUM — The accounting period to which the summarized metric applies.
• QUARTER1_VALUE, QUARTER2_VALUE, QUARTER3_VALUE, QUARTER4_VALUE — The four quarterly metric amounts, permitting fiscal-quarter comparison within a single row.
• YEAR_VALUE — The annual aggregate metric amount.
• REPORT_NAME and REPORT_PARAMETERS — Capture the report context and parameter string used to generate the metric, enabling traceability to the originating process.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard WHO audit tracking.

The surrogate primary key is GL_OASIS_FIN_METRICS_PK1, defined over (SET_OF_BOOKS_ID, FIN_METRIC_CODE). Because the primary key itself is composite over two business columns, the unique index GL_OASIS_FIN_METRICS_U1 covers the same two columns and is redundant as a uniqueness constraint; it serves as the business-key candidate rather than a distinct identifier.

Common Use Cases and Queries

Typical usage centers on retrieving pre-summarized metrics for a ledger by metric code, or comparing quarterly and annual values in a single pass. A common pattern selects all metrics for a given ledger and period:

• SELECT FIN_METRIC_CODE, EFFECTIVE_PERIOD_NUM, QUARTER1_VALUE, QUARTER2_VALUE, QUARTER3_VALUE, QUARTER4_VALUE, YEAR_VALUE FROM GL.GL_OASIS_FIN_METRICS_11I WHERE SET_OF_BOOKS_ID = :p_sob_id AND EFFECTIVE_PERIOD_NUM = :p_period ORDER BY FIN_METRIC_CODE;
• Trend reporting joins the table to itself or to period definitions on EFFECTIVE_PERIOD_NUM to plot a metric across periods for one FIN_METRIC_CODE.
• Audit and reconciliation queries filter on REPORT_NAME or REPORT_PARAMETERS to trace how a summarized value was populated.
• Extract queries for downstream warehouses select the measure columns alongside the composite key to load fact tables keyed by ledger and metric.

Related Objects

The documented foreign key references GL_OASIS_FIN_METRICS_11I.SET_OF_BOOKS_ID, indicating the ledger dimension is imposed on this table. In practice the relevant related objects include:

• GL_SETS_OF_BOOKS (or GL_LEDGERS in 12.x) — joined on SET_OF_BOOKS_ID to resolve ledger identity.
• GL_PERIODS / GL_PERIOD_SETS — used with EFFECTIVE_PERIOD_NUM to translate the numeric period into calendar context.
• GL_BALANCES — the conventional source of ledger aggregates against which summarized metric values may be validated.
• The unique index GL_OASIS_FIN_METRICS_U1 and primary key constraint GL_OASIS_FIN_METRICS_PK1 — the structural objects enforcing uniqueness on (SET_OF_BOOKS_ID, FIN_METRIC_CODE).

Because the table is a specialized reporting artifact, dependency is generally inbound: reports and extract processes read from it, while it is populated by the financial metrics summarization logic rather than by direct application DML.