Search Results bsc_kpi_graphs

Overview

BSC_KPI_GRAPHS is a table owned by the BSC schema within the Oracle E-Business Suite Balanced Scorecard module. It stores indicator graph files generated for display in scorecard portlets. Each row associates a specific Key Performance Indicator (KPI) with a graph image and binds that combination to a responsibility, allowing different users — segmented by responsibility — to view responsibility-specific graphical renditions of the same indicator. The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and it contains nine columns in the documented physical schema.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone, with no documented foreign-key dependencies into other tables. In Data Vault terms, this suggests modeling it as a satellite (or, more loosely, an independent hub) rather than as a link table, since it carries its own business key and descriptive attributes without participating in a documented many-to-many relationship. This classification is a modeling suggestion only; the actual referential integrity is not exposed in the documented metadata.

Key Information Stored

The documented primary key and unique index together define the row identity for this table:

• Primary Key — BSC_KPI_GRAPHS_PK (RESPONSIBILITY_ID, INDICATOR): The composite surrogate/primary key. RESPONSIBILITY_ID identifies the EBS responsibility under which the graph is displayed, and INDICATOR identifies the KPI whose graph is stored. A unique index, BSC_KPI_GRAPHS_U1, enforces the same (RESPONSIBILITY_ID, INDICATOR) combination, confirming these two columns act as the business-key candidates.
• INDICATOR: The KPI identifier referencing the scorecard indicator definition; the primary business attribute of the row.
• RESPONSIBILITY_ID: The EBS responsibility that scopes the graph to a particular user group or portal context.
• GRAPH_KEY: A key or handle identifying the graph rendering associated with the indicator, likely used to locate or regenerate the stored chart.
• IMAGE_ID: Reference to the stored image or file object representing the graph; this is the artifact ultimately displayed in the portlet.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN: Standard Oracle EBS WHO columns capturing creation and last-modification audit information.

The absence of a documented organization or language column reinforces the table's role as a lightweight configuration/render artifact rather than a transactional ledger.

Common Use Cases and Queries

Typical usage centers on portal rendering, auditing graph coverage, and back-office maintenance of stale images. A common retrieval pattern locates the graph for a given responsibility and indicator:

• Resolve the image for a portlet: SELECT image_id, graph_key FROM bsc.bsc_kpi_graphs WHERE responsibility_id = :resp_id AND indicator = :indicator;
• Enumerate all graphs configured for a responsibility: SELECT indicator, graph_key, image_id FROM bsc.bsc_kpi_graphs WHERE responsibility_id = :resp_id ORDER BY indicator;
• Audit recently regenerated graphs: SELECT indicator, last_update_date, last_updated_by FROM bsc.bsc_kpi_graphs WHERE last_update_date > SYSDATE - 30;
• Find indicators not yet graphed for a responsibility: compare the set of indicators in the scorecard definition against the rows here, surfacing gaps in portlet coverage.
• Housekeeping: identify orphaned or superseded image rows for cleanup, since the table is standalone and may accumulate images across regenerations.

Related Objects

The documented metadata exposes no foreign keys; the table is standalone. The following related objects are the most significant by functional context and join expectation, keyed on the documented columns:

• BSC_KPI_GRAPHS_PK / BSC_KPI_GRAPHS_U1 — the primary key and unique index enforcing (RESPONSIBILITY_ID, INDICATOR).
• FND_RESPONSIBILITY — join on RESPONSIBILITY_ID to resolve responsibility names and contexts.
• BSC indicator/scorecard definition tables — join on INDICATOR to obtain indicator metadata and descriptions.
• Image/file repository objects — resolved via IMAGE_ID for the underlying graph artifact.
• BSC portlet configuration objects — consume GRAPH_KEY and RESPONSIBILITY_ID when rendering scorecard portlets.

Because referential integrity is not documented, joins should be validated against a specific 12.1.1 or 12.2.2 instance before being relied upon in reporting.