Search Results bsc_db_tables_rels_pk

Overview

The BSC_DB_TABLES_RELS table is a metadata repository object within the Oracle E-Business Suite (EBS) Balanced Scorecard (BSC) module, which is documented as obsolete. Its primary role is to store information defining relationships between database tables that are relevant to the BSC application's data model. This table functions as a central catalog for understanding how different data entities within the BSC module are linked, which is essential for data integrity, application logic, and potentially for generating dynamic queries or reports. The provided ETRM metadata explicitly states that this table is "Not implemented in this database," indicating it may have been part of a design or installation artifact that was not deployed in standard instances of EBS 12.1.1 or 12.2.2, despite its definition existing in the data dictionary.

Key Information Stored

The table's structure is designed to capture a directed relationship between two tables. Based on the primary key and foreign key definitions, the critical columns are SOURCE_TABLE_NAME and TABLE_NAME. Together, these form the primary key (BSC_DB_TABLES_RELS_PK), suggesting that each unique combination of source and target table defines a distinct relationship record. The column names imply that the table stores a parent-child or foreign key relationship where the SOURCE_TABLE_NAME is likely the referencing table (the table containing the foreign key), and the TABLE_NAME is the referenced table (the primary key table). This metadata would be crucial for applications that need to navigate or validate the BSC data model programmatically.

Common Use Cases and Queries

Given its status as a metadata table for an obsolete module and its noted non-implementation, direct operational use in a live EBS environment is improbable. Historically, its intended use cases would have included application features that required dynamic discovery of table relationships, such as building ad-hoc query interfaces, generating data lineage reports, or enforcing data consistency rules within the BSC module. A typical query to retrieve all defined relationships would be a simple SELECT statement on the key columns. For example, to find all tables related to a specific primary table, one might use: SELECT source_table_name FROM bsc_db_tables_rels WHERE table_name = 'BSC_KPI_DATA';. However, administrators should verify the table's existence and content in their specific database before relying on it.

Related Objects

The ETRM documentation specifies two foreign key relationships, both pointing to the BSC_DB_TABLES table. This indicates that BSC_DB_TABLES_RELS is a child table of BSC_DB_TABLES, and both the SOURCE_TABLE_NAME and TABLE_NAME columns must exist as valid table names in the BSC_DB_TABLES master list. The documented relationships are:

• BSC_DB_TABLES_RELS.TABLE_NAME references BSC_DB_TABLES (ensures the referenced table is defined in the system).
• BSC_DB_TABLES_RELS.SOURCE_TABLE_NAME references BSC_DB_TABLES (ensures the source/referencing table is defined in the system).

This structure creates a tightly coupled metadata subsystem where BSC_DB_TABLES acts as the master list of recognized tables, and BSC_DB_TABLES_RELS defines the permissible relationships between them.