Search Results bis_weighted_measure_weights

Overview

BIS.BIS_WEIGHTED_MEASURE_WEIGHTS is a configuration and definition table within the Oracle EBS Business Intelligence System (BIS) product family. It stores the weight allocations applied to dependent measures that participate in a weighted parameter calculation. In practice, the table answers the question: "when a weighted measure parameter is evaluated, how much influence does each contributing dependent measure have on the composite result?" Each row binds a weighted parameter to one dependent measure and records the numeric weight assigned to that pairing.

The table is owned by the BIS schema and holds VALID status in both the 12.1.1 and 12.2.2 releases, with a documented physical schema of nine columns. Heuristic Data Vault mining classifies this object as standalone, meaning no foreign-key lineage outside the table's single outbound reference was detected. In Data Vault modeling terms, this suggests treating the table as a link that connects a weighted parameter to its dependent measures, with the WEIGHT column acting as the link's descriptive attribute. This classification is a modeling suggestion only; the object is not formally registered as a Data Vault construct.

Key Information Stored

The nine documented columns separate cleanly into surrogate identification, business keys, and audit fields.

• WEIGHT_ID — the surrogate primary key for each weight assignment. It is also the target of the single documented foreign key on the table.
• WEIGHTED_PARAMETER_ID — identifies the parent weighted measure parameter being configured.
• DEPENDENT_MEASURE_ID — identifies the source measure whose value contributes to the weighted parameter.
• WEIGHT — the numeric coefficient applied to the dependent measure during evaluation.
• CREATED_BY, CREATION_DATE — standard EBS who/when audit columns capturing row origin.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing the most recent change and the login session that produced it.

Two unique indexes define business-key candidates. BIS_WEIGHTED_MEASURE_WEIGHT_U1 is a single-column unique index on WEIGHT_ID, reinforcing its role as a surrogate primary key. BIS_WEIGHTED_MEASURE_WEIGHT_U2 is a composite unique index on WEIGHTED_PARAMETER_ID, DEPENDENT_MEASURE_ID, and WEIGHT. The composite index is the more informative business key: it enforces that a given parameter cannot reference the same dependent measure with the same weight more than once, ensuring deterministic composite calculations.

Common Use Cases and Queries

Typical usage centers on reviewing and auditing weighted measure definitions.

• List all dependent measures feeding a parameter, ordered by weight:
  SELECT dependent_measure_id, weight FROM bis.bis_weighted_measure_weights WHERE weighted_parameter_id = :p_param ORDER BY weight DESC;
• Detect parameters whose weights do not sum to a normalized total:
  SELECT weighted_parameter_id, SUM(weight) FROM bis.bis_weighted_measure_weights GROUP BY weighted_parameter_id HAVING SUM(weight) <> 1;
• Trace the load-balance weight source for reconciliation:
  SELECT w.*, l.* FROM bis.bis_weighted_measure_weights w, cs.cs_sr_load_balance_wt l WHERE w.weight_id = l.weight_id;
• Audit recent configuration drift using LAST_UPDATED_BY and LAST_UPDATE_DATE.

Reporting against this table is generally read-only; rows are maintained through the BIS configuration and administration layer rather than direct DML.

Related Objects

• CS_SR_LOAD_BALANCE_WT — referenced by the outbound foreign key BIS_WEIGHTED_MEASURE_WEIGHTS.WEIGHT_ID → CS_SR_LOAD_BALANCE_WT. This is the sole documented foreign-key relationship and ties weighted measure rows back to load-balance weight definitions.
• BIS_WEIGHTED_MEASURE_WEIGHT_U1 / U2 — the unique indexes enforcing surrogate and composite business keys.
• Weighted parameter and dependent measure dimension objects in the BIS schema — joined through WEIGHTED_PARAMETER_ID and DEPENDENT_MEASURE_ID respectively — complete the definition chain.