Search Results simulate_flag

Overview

BSC.BSC_KPI_TREE_NODES_B is a base table in the Oracle EBS Balanced Scorecard (BSC) schema that stores the definition of simulation tree nodes associated with individual key performance indicators (KPIs). In ETRM 12.1.1 and 12.2.2, this table underpins the graphical strategy map and KPI tree rendering facilities that allow administrators to lay out indicator nodes on a simulation canvas. Each row binds a tree node to an indicator, carrying its position coordinates, color treatment, number formatting, and behaviour flags such as trend navigation and autoscaling.

Because the primary key is a composite of INDICATOR and NODE_ID, the table behaves as a dependent child of the KPI definition rather than an independent entity. Under a heuristic Data Vault classification this object leans toward a satellite: its identity is inherited from BSC_KPIS_B, and its non-key attributes are descriptive configuration rather than referenced business entities. Treat it accordingly when modelling — as an attribute-bearing satellite hanging off the KPI hub, not as a hub or link in its own right.

Key Information Stored

The most significant columns are:

• INDICATOR — Indicator code; part of the composite primary key and a foreign key to BSC_KPIS_B.
• NODE_ID — Tree node identifier; the second component of the composite primary key.
• SIMULATE_FLAG — Flag indicating whether the node participates in simulation. This is the column most frequently sought when users search for simulate_flag.
• FORMAT_ID — Number format identifier, foreign key to BSC_SYS_FORMATS; controls how the indicator value is displayed.
• COLOR_FLAG and COLOR_METHOD — Govern node colouring and the method used to derive it.
• NAVIGATES_TO_TREND — Indicates whether the node links through to a trend chart.
• TOP_POSITION, LEFT_POSITION, WIDTH, HEIGHT — Canvas geometry for rendering the node.
• AUTOSCALE_FLAG — Determines whether the associated graph scale is automatic.

The surrogate primary key is BSC_KPI_TREE_NODES_B_PK (INDICATOR, NODE_ID). A unique index, BSC_KPI_TREE_NODES_B_U1, covers the same column pair and serves as the business-key candidate. A non-unique index, BSC_KPI_TREE_NODES_B_N1, supports lookups by FORMAT_ID.

Common Use Cases and Queries

Typical usage includes auditing which KPI nodes are configured for simulation, reproducing tree layouts for a given indicator, and validating that every node carries a valid format reference.

• Identify simulation-enabled nodes:

  SELECT INDICATOR, NODE_ID, SIMULATE_FLAG
  FROM   BSC.BSC_KPI_TREE_NODES_B
  WHERE  SIMULATE_FLAG = 1;

• List all nodes for a specific indicator:

  SELECT NODE_ID, FORMAT_ID, COLOR_METHOD, NAVIGATES_TO_TREND
  FROM   BSC.BSC_KPI_TREE_NODES_B
  WHERE  INDICATOR = :indicator_id;

• Detect orphaned format references:

  SELECT n.INDICATOR, n.NODE_ID, n.FORMAT_ID
  FROM   BSC.BSC_KPI_TREE_NODES_B n
  WHERE  NOT EXISTS (SELECT 1 FROM BSC.BSC_SYS_FORMATS f
                     WHERE f.FORMAT_ID = n.FORMAT_ID);

These queries support migration validation, layout regression testing, and operational reporting on scorecard configuration.

Related Objects

The following objects participate in the dependency chain around this table:

• BSC.BSC_KPIS_B — Parent KPI definition; joined on INDICATOR.
• BSC.BSC_SYS_FORMATS — Number format lookup; joined on FORMAT_ID.
• BSC.BSC_KPI_TREE_NODES_TL — Translation table referencing this base table on INDICATOR; supplies language-specific node text.
• APPS.BSC_KPI_TREE_NODES_B — The APPS synonym through which application code and concurrent programs access the base table.

The table references no other database objects beyond BSC_KPIS_B and BSC_SYS_FORMATS, and is itself referenced by the translation layer, which preserves multilingual node labels alongside the base configuration held here.