Results for “weight_id”

34 results




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

Overview

BIS_WEIGHTED_MEASURE_SCORES is a configuration and lookup table within the Oracle E-Business Suite Applications BIS (Business Intelligence System) product family. It stores the scoring bands that translate a numeric measure value into a weighted score, driving the composite scoring logic used by the BIS balanced scorecard and performance-management framework. Each row defines a range (from LOW_RANGE to HIGH_RANGE) and the discrete score assigned to a measure value that falls within that range, grouped under a weight definition identified by WEIGHT_ID. In effect, the table implements the mapping function between raw measure outcomes and the normalized points that feed weighted aggregations across scorecard measures.

The ETRM metadata describes the object physically as owned by the BIS schema with nine documented columns in release 12.1.1. The metadata note "Not implemented in this database" reflects that the object is created and populated only when the relevant BIS scoring functionality is configured; in environments where weighted measure scoring is not enabled, the table may exist as an empty structure or be absent from the physical schema.

A heuristic Data Vault classification, mined from the foreign-key structure, places BIS_WEIGHTED_MEASURE_SCORES as standalone. It is therefore best modeled as a reference or lookup satellite (or, where range bands are versioned, a satellite over a weight-definition hub) rather than as a transactional hub or link. This classification is a modeling suggestion derived from the relationship metadata and should be validated against the specific implementation.

Key Information Stored

The column set documented in ETRM 12.1.1 comprises the following significant attributes:

  • WEIGHT_ID — The foreign key to the weight definition. It joins to CS_SR_LOAD_BALANCE_WT and is the primary grouping key for all score bands belonging to a given weight.
  • LOW_RANGE — The lower boundary of the measure-value interval to which the score applies. Together with HIGH_RANGE and WEIGHT_ID, it forms unique index BIS_WEIGHTED_MEASURE_SCORES_U1, making the range a business-key candidate.
  • HIGH_RANGE — The upper boundary of the interval. The pair LOW_RANGE / HIGH_RANGE must not overlap for a given weight.
  • SCORE — The weighted score awarded when a measure value falls inside the band. It is paired with WEIGHT_ID in unique index BIS_WEIGHTED_MEASURE_SCORES_U2, confirming that scores are unique per weight definition.
  • CREATED_BY, CREATION_DATE — Standard EBS who-columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns recording the most recent modification and the login that performed it.

No separate surrogate primary key column is documented; attribution relies on the composite business keys enforced by the two unique indexes, supported by the standard EBS audit columns.

Common Use Cases and Queries

Typical usage involves resolving a measure value to its score and validating that score bands are contiguous and non-overlapping. A representative query returns all bands for a weight, ordered by range:

  • SELECT weight_id, low_range, high_range, score FROM bis_weighted_measure_scores WHERE weight_id = :p_weight_id ORDER BY low_range;
  • Scoring lookup: SELECT score FROM bis_weighted_measure_scores WHERE weight_id = :p_weight_id AND :p_value BETWEEN low_range AND high_range;
  • Gap/overlap validation: compare HIGH_RANGE of one row against LOW_RANGE of the next using an analytic LEAD function to detect missing or overlapping intervals.
  • Audit reporting: filter on LAST_UPDATE_DATE to identify recently reconfigured scoring bands.

These patterns support scorecard configuration review, migration verification between environments, and troubleshooting of unexpected composite scores.

Related Objects

  • CS_SR_LOAD_BALANCE_WT — The referenced weight definition table, joined on WEIGHT_ID. This is the only documented foreign-key relationship.
  • BIS_WEIGHTED_MEASURE_SCORES_U1 — Unique index on (WEIGHT_ID, LOW_RANGE, HIGH_RANGE).
  • BIS_WEIGHTED_MEASURE_SCORES_U2 — Unique index on (WEIGHT_ID, SCORE).
  • Other BIS scorecard and measure-attribute tables within the same schema that consume WEIGHT_ID as a scoring reference.
  • Standard EBS concurrent programs and scorecard reports that read these bands to compute weighted results.

Because the object is documented as standalone with a single FK, broader relationships should be confirmed against the deployed BIS schema.