Results for “user_level0”

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

Overview

BSC_KPI_PERIODICITIES is a table within the BSC (Balanced Scorecard) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Indicator periodicity information, meaning it defines which reporting periodicities apply to a given KPI indicator. The table acts as a configuration map linking indicators to standardized periodicities (for example, weekly, monthly, quarterly, or annual reporting windows), and it also controls presentation attributes such as display ordering, historical year scope, and viewport sizing.

From a Data Vault modeling perspective, the heuristic classification for this object is satellite-leaning. Reading this as a suggestion rather than a fixed rule, the table behaves like a satellite keyed to its parent indicator, capturing descriptive periodicity attributes rather than acting as a standalone hub or an associative link between independent entities. Its composite primary key, BSC_KPI_PERIODICITIES_PK on (INDICATOR, PERIODICITY_ID), reinforces the parent-child context.

Key Information Stored

The table contains 15 documented columns. The most significant are listed below; the remaining columns are largely presentation and maintenance attributes.

• INDICATOR — Reference to the parent KPI indicator defined in BSC_KPIS_B. Part of the composite primary key.
• PERIODICITY_ID — Reference to the standardized periodicity defined in BSC_SYS_PERIODICITIES. Also part of the composite primary key.
• DISPLAY_ORDER — Controls the sequence in which periodicity entries are presented for an indicator.
• PREVIOUS_YEARS — Indicates whether prior years of data are considered for the periodicity.
• NUM_OF_YEARS — Number of years of history or scope associated with the periodicity.
• VIEWPORT_FLAG — Determines whether a viewport (windowed display) is applied.
• VIEWPORT_DEFAULT_SIZE — Default size of the viewport when enabled.
• CURRENT_PERIOD — Identifies the currently active reporting period for the indicator.
• TARGET_LEVEL — Level at which targets are applied within the periodicity.
• USER_LEVEL0, USER_LEVEL1, USER_LEVEL2 — Hierarchical user-level settings for aggregation or drill within the periodicity.
• USER_LEVEL1_DEFAULT, USER_LEVEL2_DEFAULT — Default selections for the corresponding user levels.
• LAST_UPDATE_DATE — Standard audit column tracking the most recent modification.

The business-key candidate is captured by the unique index BSC_KPI_PERIODICITIES_U1 (INDICATOR, PERIODICITY_ID), which mirrors the primary key. In this table the surrogate primary key and the business key are effectively the same composite pair.

Common Use Cases and Queries

Typical usage centers on determining which periodicities are configured for a KPI and how history and display are scoped.

• Listing all periodicities for a specific indicator, ordered for display:

  SELECT p.PERIODICITY_ID, p.DISPLAY_ORDER, p.NUM_OF_YEARS, p.VIEWPORT_FLAG
FROM BSC.BSC_KPI_PERIODICITIES p
WHERE p.INDICATOR = :indicator_id
ORDER BY p.DISPLAY_ORDER;

• Joining to BSC_SYS_PERIODICITIES to resolve the periodicity name or type for reporting labels.
• Joining to BSC_KPI_DATA_TABLES on (INDICATOR, PERIODICITY_ID) to align configured periodicities with their underlying fact data tables.
• Auditing configuration drift by comparing entries against BSC_KPI_PERIODICITIES_USER, which carries the same key structure for user-specific overrides.
• Reviewing recent changes using LAST_UPDATE_DATE for governance reporting.

Related Objects

• BSC_KPIS_B — Parent indicator table; joined on INDICATOR.
• BSC_SYS_PERIODICITIES — System periodicity definitions; joined on PERIODICITY_ID.
• BSC_KPI_DATA_TABLES — Fact data tables referencing this table via (INDICATOR, PERIODICITY_ID).
• BSC_KPI_PERIODICITIES_USER — User-level counterpart referencing the same key pair.
• The unique index BSC_KPI_PERIODICITIES_U1 and primary key constraint BSC_KPI_PERIODICITIES_PK enforce integrity on the composite key.