Results for “bm_group_id”

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

Overview

BSC_SYS_BM_GROUPS is a table owned by the BSC schema within the Oracle E-Business Suite product family BSC — Balanced Scorecard. Its documented purpose is to hold benchmark groups information. In practice, this table functions as a small associative structure that maps benchmark identifiers to the groups into which those benchmarks are organized, allowing the Balanced Scorecard application to cluster benchmarks for scoring, comparison, and display purposes.

The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. From a heuristic Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification, though the pure two-column composition with a composite primary key is equally consistent with a link-style association between benchmarks and their grouping. Either interpretation is a modeling suggestion only; the table is a conventional relational table with a composite primary key named BSC_SYS_BM_GROUPS_PK.

Key Information Stored

The documented physical schema is intentionally narrow: only two columns are recorded, and both participate in the primary key. The essential content is as follows:

• BM_GROUP_ID — Identifies the benchmark group to which a benchmark is assigned. This is the grouping attribute that organizes benchmarks into logical clusters.
• BM_ID — Identifies the individual benchmark record. This column also serves as the foreign key reference to BSC_SYS_BENCHMARKS_B.BM_ID.

The composite primary key BSC_SYS_BM_GROUPS_PK is defined over (BM_GROUP_ID, BM_ID). A unique index, BSC_SYS_BM_GROUPS_U1, is documented over the same column pair, confirming that the combination of group and benchmark is enforced as a business-key candidate: a given benchmark may appear only once within a given group. Because the documented column set is limited to these two attributes, there is no separate surrogate key; the business key and the primary key are effectively the same, and no descriptive or auditing attributes are exposed in the ETRM documentation.

Common Use Cases and Queries

The primary use case is resolving the many-to-many relationship between benchmarks and groups. Reporting queries typically join this table to BSC_SYS_BENCHMARKS_B to list all benchmarks belonging to a given group, or to determine which groups a benchmark participates in.

• Listing benchmarks for a group: SELECT bm.* FROM bsc.bsc_sys_bm_groups g, bsc.bsc_sys_benchmarks_b bm WHERE g.bm_id = bm.bm_id AND g.bm_group_id = :group_id
• Counting benchmarks per group for coverage analysis: SELECT bm_group_id, COUNT(*) FROM bsc.bsc_sys_bm_groups GROUP BY bm_group_id
• Detecting ungrouped benchmarks by outer-joining from BSC_SYS_BENCHMARKS_B and filtering for NULL BM_GROUP_ID.
• Validating load integrity by comparing distinct BM_ID values in this table against the benchmark base table.

Because the table carries no effective-dating or language columns in the documented schema, queries are straightforward and require no date or language filters. Access should observe standard BSC security and responsibility constraints.

Related Objects

The documented FK relationship anchors this table to the benchmark base table. The most significant related objects are:

• BSC_SYS_BENCHMARKS_B — Referenced via BSC_SYS_BM_GROUPS.BM_ID → BSC_SYS_BENCHMARKS_B.BM_ID. This is the principal parent object; joins on BM_ID are the standard access path.
• BSC_SYS_BENCHMARKS_TL — The translated benchmark definitions, typically joined to the base table for multilingual reporting.
• BSC_SYS_BM_GROUPS_PK — The composite primary key constraint enforcing uniqueness of (BM_GROUP_ID, BM_ID).
• BSC_SYS_BM_GROUPS_U1 — The unique index over the same column pair, supporting the business-key candidate interpretation.
• Benchmark group definition and scorecard presentation objects in the BSC schema, which consume BM_GROUP_ID when rendering grouped benchmark results.

No views, APIs, or additional child tables referencing BSC_SYS_BM_GROUPS are documented in the available ETRM metadata.