Search Results fin_metric_code




Overview
Explore in AI Chat

Overview

GL.GL_OASIS_FIN_METRICS_11I is an interface table in the Oracle General Ledger (GL) schema that stores computed financial metrics produced by the OASIS reporting and analytics framework. The "_11I" suffix indicates the object originated in the Oracle E-Business Suite 11i release and is retained in the 12.1.1 and 12.2.2 data models, typically for backward compatibility and for use by internal Oracle programs. In EBS 12.2.2 the table is documented with fifteen columns and a status of VALID, residing in the APPS_TS_INTERFACE tablespace — a placement consistent with its role as a staging or interface object rather than a transactional master table.

The table is explicitly flagged "Oracle Internal Use Only." Oracle Corporation does not support direct data access through this object except from standard Oracle Applications programs. Any custom read is therefore at the implementer's own risk, and the object should be treated as a read-only interface surface. From a modeling perspective, the heuristic Data Vault classification is satellite-leaning: the table records descriptive measures (quarter and year values, report metadata) that revolve around a defined key, rather than acting as a hub of independent business entities or a link resolving many-to-many relationships.

Key Information Stored

The primary key, GL_OASIS_FIN_METRICS_PK1, is composite, consisting of SET_OF_BOOKS_ID and FIN_METRIC_CODE. A separate unique index, GL_OASIS_FIN_METRICS_U1, covers the same two columns, making them the definitive business-key candidates for the row. The most significant columns include:

  • SET_OF_BOOKS_ID — the accounting books defining column; the set of books (ledger context) to which the metric belongs.
  • FIN_METRIC_CODE — a 30-character code indicating the desired financial metric; this is the attribute the user searched for.
  • EFFECTIVE_PERIOD_NUM — the effective period number of the current period for which the program was run.
  • REPORT_NAME — the name of the report associated with the metric (up to 2000 characters).
  • REPORT_PARAMETERS — the parameters used to drive that report.
  • QUARTER1_VALUE through QUARTER4_VALUE — numeric metric values for each fiscal quarter.
  • YEAR_VALUE — the year-to-date value of the metric.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns for audit and concurrency tracking.

The values columns are the analytical payload; the report columns describe how each metric is presented; the Who columns satisfy audit requirements.

Common Use Cases and Queries

Typical usage is investigative rather than production-facing. Analysts inspect populated metrics for a given ledger and period, or trace which reports are generating a metric. A representative query is:

  • SELECT FIN_METRIC_CODE, EFFECTIVE_PERIOD_NUM, YEAR_VALUE FROM GL.GL_OASIS_FIN_METRICS_11I WHERE SET_OF_BOOKS_ID = :ledger_id;
  • SELECT REPORT_NAME, REPORT_PARAMETERS FROM GL.GL_OASIS_FIN_METRICS_11I WHERE FIN_METRIC_CODE = :code;
  • SELECT FIN_METRIC_CODE, QUARTER1_VALUE, QUARTER2_VALUE, QUARTER3_VALUE, QUARTER4_VALUE FROM GL.GL_OASIS_FIN_METRICS_11I ORDER BY FIN_METRIC_CODE;

Reporting use cases include validating OASIS metric computation, reviewing quarter-to-date and year-to-date trends per ledger, and auditing which reports and parameters drive each metric definition. Because the table is an interface object, results should be treated as transient and reconciled against the standard GL reporting sources before use in external reports.

Related Objects

Documented dependency information indicates the table does not refer to other objects through declared foreign keys, and the only referenced relationship shown is SET_OF_BOOKS_ID mapping to the ledger context. Practical join candidates include:

  • GL.GL_OASIS_FIN_METRICS_11I joined to the ledger/set-of-books definition (e.g., GL_SETS_OF_BOOKS or FND_ID_FLEX_STRUCTURES context) on SET_OF_BOOKS_ID.
  • GL.GL_OASIS_FIN_METRICS_11I joined to GL_PERIODS-style calendar objects on EFFECTIVE_PERIOD_NUM to resolve the actual period name.
  • FND tables resolving CREATED_BY and LAST_UPDATED_BY to FND_USER for audit trails.
  • Standard GL report and concurrent program definitions referenced indirectly through REPORT_NAME and REPORT_PARAMETERS.

Given the interface-only status and internal-use warning, any integration should be limited to read operations and validated against the standard Oracle Applications programs that populate the table.