Results for “gl_oasis_fin_metrics”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_OASIS_FIN_METRICS is a General Ledger (GL) table in Oracle E-Business Suite that stores summarized financial metrics. Within the ETRM documentation set it is described simply as "the new table stores the summarized financial metrics," positioning it as a consolidation or staging structure that holds pre-aggregated financial measures rather than transactional journal detail. Its role in Oracle EBS is to expose derived, book-level financial indicators that downstream reporting, analysis, or OASIS-related processing can consume without repeatedly aggregating high-volume subledger and GL activity.

The table is scoped to the ledger by way of a foreign key to GL_SETS_OF_BOOKS on SET_OF_BOOKS_ID, and its primary key (GL_OASIS_FIN_METRICS_PK1) is a composite of SET_OF_BOOKS_ID and FIN_METRIC_CODE. Based on the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning: it is best modeled as descriptive, measure-bearing data attached to the ledger hub, rather than as an independent hub or a link resolving many-to-many relationships. Note that the ETRM metadata marks this object as "Not implemented in this database," so any deployment relies on customer-specific configuration of the OASIS financial metrics feature.

Key Information Stored

The documented metadata identifies a narrow but meaningful column set. The most important elements are:

• SET_OF_BOOKS_ID — Ledger identifier and part of the composite primary key. It serves as the foreign key to GL_SETS_OF_BOOKS and establishes the ledger-level scope of every summarized metric row.
• FIN_METRIC_CODE — The metric discriminator and the other half of the composite primary key. It uniquely identifies which summarized financial metric a given row represents for a given ledger.
• Primary key — GL_OASIS_FIN_METRICS_PK1 (SET_OF_BOOKS_ID, FIN_METRIC_CODE) — The composite key is the structural backbone of the table. Because the PK is composed of these two columns, the pairing of ledger and metric code is the natural business key; there is no separately documented surrogate sequence column in the metadata.

The metadata does not enumerate the remaining value columns. In practice, a "summarized financial metrics" satellite of this shape typically carries the metric amount or value, the period or date context, a currency or unit qualifier, and audit columns (creation/update stamps and the user or program that produced the row). Those columns should be confirmed against the actual deployed table definition before being used in code, since the ETRM record treats them as implementation detail.

Common Use Cases and Queries

Because the table stores summarized metrics keyed by ledger and metric code, it supports fast retrieval of book-level indicators without touching GL_BALANCES or journal line tables. Typical scenarios include executive and management reporting, ledger-to-ledger comparisons, and feeding external analytics or OASIS-specific dashboards. A canonical lookup retrieves all metrics for one ledger:

• SELECT fin_metric_code, <metric value column> FROM gl_oasis_fin_metrics WHERE set_of_books_id = :ledger_id;
• Ledger-level joining to obtain context: SELECT m.fin_metric_code, b.name AS ledger_name FROM gl_oasis_fin_metrics m JOIN gl_sets_of_books b ON b.set_of_books_id = m.set_of_books_id WHERE m.fin_metric_code = :code;
• Cross-ledger comparison for a single metric: SELECT set_of_books_id, fin_metric_code, <metric value column> FROM gl_oasis_fin_metrics WHERE fin_metric_code = :code ORDER BY set_of_books_id;

Reverse-engineering queries joining ALL_TAB_COLUMNS and ALL_CONS_COLUMNS for GL_OASIS_FIN_METRICS are advisable before relying on any column not named in the ETRM metadata. Reporting tools (BI Publisher, Oracle Financials reporting, or custom extracts) can treat the table as a small dimension-plus-measure source, provided the metric code values are documented and stable.

Related Objects

The documented relationship set is intentionally compact. The principal related objects are:

• GL_SETS_OF_BOOKS — The only documented foreign key target. GL_OASIS_FIN_METRICS.SET_OF_BOOKS_ID references GL_SETS_OF_BOOKS, supplying ledger name, currency, chart of accounts, and accounting calendar context for every metric row.
• GL_OASIS_FIN_METRICS_PK1 — The composite primary key index over (SET_OF_BOOKS_ID, FIN_METRIC_CODE), which also enforces uniqueness and drives efficient point lookups.

Beyond these, related objects are inferred by function rather than documented: GL_BALANCES and GL_JE_LINES represent the upstream transaction-level sources from which the summarized metrics are presumably derived, and GL_JE_HEADERS supplies journal context. Any OASIS-specific concurrent programs or APIs that populate the table would constitute additional dependencies, but they are not identified in the ETRM metadata and should be confirmed in the deployed environment.