Search Results graph_key

Overview

BSC.BSC_KPI_GRAPHS is a transactional configuration table within the Oracle EBS Balanced Scorecard (BSC) application schema. It stores the mapping between a responsibility, an indicator, and the graph definition used to render that indicator visually inside a portlet. In practical terms, the table answers the question: "For this responsibility and this KPI indicator, which graph should be displayed?" The related dependency notes confirm that BSC_KPI_GRAPHS "stores information about the indicator graph that are used by portlet," positioning the object as the presentation-layer control for KPI dashboards and scorecard portlets.

The object resides in the BSC schema (FND Design Data reference: BSC.BSC_KPI_GRAPHS) and is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its unique index, BSC_KPI_GRAPHS_U1, is housed separately in the APPS_TS_TX_IDX tablespace. Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as standalone — it neither references nor is referenced by other database objects through declared foreign keys. From a warehouse-modeling perspective, the table behaves as a satellite-style configuration store keyed by a natural composite of responsibility and indicator, rather than as a hub or link participating in a broader relational network.

Key Information Stored

The table contains nine documented columns. The most significant are the following:

• RESPONSIBILITY_ID (NUMBER, 15) — The EBS responsibility identifier. This is the first component of both the primary key and the unique index, scoping every graph definition to a specific responsibility.
• INDICATOR (NUMBER) — The KPI indicator code. This is the second component of the primary key and unique index.
• GRAPH_KEY (VARCHAR2, 100) — The graph key that identifies the graphical representation associated with the indicator. This is the column most commonly searched for and is the primary payload of the record.
• IMAGE_ID (NUMBER, 15) — The image identifier linked to the graph rendering.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The five standard "Who" audit columns maintained automatically by EBS, capturing row creation and last-modification metadata.

The surrogate primary key is documented as BSC_KPI_GRAPHS_PK, consisting of (RESPONSIBILITY_ID, INDICATOR). The unique index BSC_KPI_GRAPHS_U1 covers the same two columns (RESPONSIBILITY_ID, INDICATOR), meaning the business-key candidate and the primary key coincide on this composite. This enforces one graph configuration per responsibility-indicator pair.

Common Use Cases and Queries

Typical uses center on resolving which graph is configured for a given responsibility and indicator, troubleshooting blank or incorrect portlet rendering, and auditing graph configuration changes. A representative query retrieves the graph configuration for a responsibility-indicator pair:

• SELECT RESPONSIBILITY_ID, INDICATOR, GRAPH_KEY, IMAGE_ID FROM BSC.BSC_KPI_GRAPHS WHERE RESPONSIBILITY_ID = :resp_id AND INDICATOR = :indicator;
• SELECT RESPONSIBILITY_ID, INDICATOR, GRAPH_KEY FROM BSC.BSC_KPI_GRAPHS WHERE GRAPH_KEY = :graph_key;
• SELECT RESPONSIBILITY_ID, INDICATOR, GRAPH_KEY, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM BSC.BSC_KPI_GRAPHS ORDER BY LAST_UPDATE_DATE DESC;

The third pattern supports change auditing, since the "Who" columns record the last modification. Because the table is standalone with no foreign keys, joins must be inferred from the meaning of RESPONSIBILITY_ID and IMAGE_ID rather than from declared constraints.

Related Objects

The dependency metadata states that BSC.BSC_KPI_GRAPHS does not reference any database object and is referenced by the synonym/view APPS.BSC_KPI_GRAPHS. Note that APPS is entirely a synonym layer rather than a distinct physical schema, so any tool that resolves APPS.BSC_KPI_GRAPHS to the BSC schema will transparently reference the same physical table. Because the table is classified as standalone with no documented foreign keys, related-object joins are semantic rather than enforced. Joins should therefore be constructed on the shared columns present in the metadata:

• BSC_KPI_GRAPHS.RESPONSIBILITY_ID — links to the responsibility definition used to scope the portlet.
• BSC_KPI_GRAPHS.INDICATOR — links to the KPI indicator definition that the graph represents.
• BSC_KPI_GRAPHS.IMAGE_ID — links to the stored image referenced by the graph rendering.
• APPS.BSC_KPI_GRAPHS — the application-facing reference to this table.

Analysts extracting data should always qualify the table as BSC.BSC_KPI_GRAPHS to avoid ambiguity, and should treat RESPONSIBILITY_ID and INDICATOR as the reliable business key for the object.