Results for “calculation_type”

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

Overview

BSC_DB_CALCULATIONS is a configuration table within the Oracle E-Business Suite Balanced Scorecard (BSC) module, owned by the BSC schema. Its documented purpose is "Calculation configuration by table," meaning it stores the parameters that govern how calculated measures are derived for scorecard data sources. In Oracle EBS 12.1.1 and 12.2.2, this table supports the Balanced Scorecard database administration layer, where administrators define how metrics are computed against underlying scorecard tables registered in BSC_DB_TABLES.

The table contains 12 documented columns: TABLE_NAME, CALCULATION_TYPE, and ten generic parameter slots (PARAMETER1 through PARAMETER10). Structurally, its single documented foreign key relationship is BSC_DB_CALCULATIONS.TABLE_NAME referencing BSC_DB_TABLES. Based on this foreign key pattern, the heuristic Data Vault classification is satellite-leaning: the table describes attributes and configuration detail attached to a parent entity (the table registration in BSC_DB_TABLES) rather than representing an independent hub or a many-to-many link. This classification should be treated as a modeling suggestion, not a documented constraint.

Key Information Stored

The most significant columns are:

• TABLE_NAME — The business-key column identifying the scorecard table to which the calculation configuration applies. It is the documented foreign key to BSC_DB_TABLES and the principal join column for relating configuration to table metadata.
• CALCULATION_TYPE — The discriminator that identifies which calculation or aggregation logic applies to the referenced table, such as a summation, average, or other derived-measure method.
• PARAMETER1 through PARAMETER10 — Ten generic parameter columns that carry the operands, column references, thresholds, or formula components required by the calculation type. Their meaning is contextual: the semantics of each parameter slot depend on the value stored in CALCULATION_TYPE.

The metadata does not document a surrogate primary key column or a unique index for this table. TABLE_NAME is the documented business-key candidate and the only column participating in a defined foreign key. Because the parameters are generically named, the effective key is likely the combination of TABLE_NAME and CALCULATION_TYPE, but this should be confirmed against the physical schema before being relied upon in production queries.

Common Use Cases and Queries

Typical uses center on auditing and reproducing scorecard calculation behavior. Administrators and developers query this table to determine how a given scorecard table produces its calculated measures, to compare configurations across environments after a clone or patch, and to troubleshoot discrepancies in reported Balanced Scorecard results.

A representative query joins the configuration to its parent table registration:

• SELECT c.TABLE_NAME, c.CALCULATION_TYPE, c.PARAMETER1, c.PARAMETER2 FROM BSC.BSC_DB_CALCULATIONS c WHERE c.TABLE_NAME = :table_name;
• SELECT t.TABLE_NAME, c.CALCULATION_TYPE, c.PARAMETER1 FROM BSC.BSC_DB_TABLES t JOIN BSC.BSC_DB_CALCULATIONS c ON c.TABLE_NAME = t.TABLE_NAME;

Additional reporting patterns include listing all calculation types in use (SELECT CALCULATION_TYPE, COUNT(*) FROM BSC.BSC_DB_CALCULATIONS GROUP BY CALCULATION_TYPE) and extracting parameter values for a specific calculation type to document formula logic during migration or regression testing.

Related Objects

• BSC_DB_TABLES — The documented parent table; join on BSC_DB_CALCULATIONS.TABLE_NAME = BSC_DB_TABLES.TABLE_NAME. This is the only foreign key relationship recorded in the ETRM metadata.
• BSC_DB_COLUMNS — Column registrations for scorecard tables, typically consulted alongside calculations to map PARAMETER values to physical columns.
• BSC_DB_DIMENSIONS and related dimension tables — Provide the dimensional context for which calculated measures are evaluated.
• BSC_DB_INDICATORS and scorecard indicator definitions — Consume calculated results as the basis for KPI display.
• BSC_DB_VIEWS — View registrations that may reference tables whose calculations are configured here.
• BSC_DB_MEASURES — Measure definitions that depend on the calculation configuration.
• BSC_DB_OBJECTS — General object registry underlying the BSC database administration layer.

These related objects should be confirmed against the target instance, as the ETRM metadata documents only the BSC_DB_TABLES foreign key explicitly.