Results for “end_period”

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

Overview

BSC_SYS_PERIODS is a reference table within the Balanced Scorecard (BSC) product family of Oracle E-Business Suite. Its documented purpose is to hold "Periods information" — that is, the calendar definitions that the Balanced Scorecard module uses to align scorecards, measures, and targets to discrete time buckets. Each row describes a period belonging to a named periodicity (for example, a month, quarter, or year) and anchors that period to concrete start and end dates.

The ETRM metadata records BSC as "Obsolete" and explicitly notes that the table is "Not implemented in this database." In 12.1.1 and 12.2.2 environments, BSC_SYS_PERIODS therefore typically exists only as a legacy artifact; it may be present in schemas upgraded from earlier releases, or it may be absent entirely depending on whether Balanced Scorecard was ever licensed or initialized. The object is useful primarily for understanding historical data models, for migration or cleanup analysis, and for interpreting older customizations that still reference BSC tables.

From a data-modeling perspective, the metadata records a heuristic Data Vault classification of standalone, meaning no foreign-key dependencies to other documented tables were mined. Under Data Vault conventions, this pattern is best treated as a hub candidate: a business-key-bearing entity (periodicity plus period plus year) whose descriptive date attributes would normally be split into a satellite. This classification is a modeling suggestion, not a documented constraint.

Key Information Stored

The table is documented with 13 columns in the ETRM 12.1.1 physical schema, owned by the BSC schema. The most significant columns are:

• PERIODICITY_ID — Identifier of the periodicity (period set) to which the row belongs; the coarsest component of the primary key.
• PERIOD_ID — Identifier of the individual period within the periodicity; a period number or sequence value used for ordered reporting.
• YEAR — The calendar or fiscal year the period falls into.
• START_DATE / END_DATE — The concrete boundary dates of the period, used to map transactions, facts, and scorecard results into the correct bucket.
• START_PERIOD / END_PERIOD — Period-boundary indicators, typically used to flag whether the row is the first or last period in a range or fiscal construct.
• TIME_FK — A foreign-key-style reference into a time dimension, used to relate the period to a general time hierarchy.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle EBS WHO-column audit set recording row creation and last modification.

The primary key is documented as BSC_SYS_PERIODS_PK (PERIODICITY_ID, PERIOD_ID, YEAR). A second unique index, BSC_SYS_PERIODS_U1 (PERIODICITY_ID, YEAR, PERIOD_ID), covers the same three columns in a different order. Because both constraints span the same attribute set, the three columns function jointly as the business key, and no separate single-column surrogate key is documented.

Common Use Cases and Queries

In historical or upgraded instances, the table is typically queried to resolve which calendar period a scorecard fact belongs to, or to enumerate the periods defined for a given periodicity. A representative join pattern maps facts to their period boundaries by periodicity and year:

• Enumerating periods: SELECT period_id, year, start_date, end_date FROM bsc_sys_periods WHERE periodicity_id = :p_id ORDER BY year, period_id
• Filtering by date: SELECT * FROM bsc_sys_periods WHERE start_date <= :as_of AND end_date >= :as_of
• Joining scorecard results to period metadata on periodicity_id, year, and period_id.

Typical reporting uses include period-over-period variance analysis, aligning balanced scorecard measures to fiscal boundaries, and validating that fact rows fall within a defined start_date/end_date range. Before any such use in 12.2.2, verify that the table exists and contains rows; given the "not implemented" status, static SQL against BSC_SYS_PERIODS should be guarded or replaced with the successor time/period structures used by the reporting stack.

Related Objects

The metadata classifies BSC_SYS_PERIODS as standalone, with no mined foreign-key relationships beyond its own primary and unique keys. Related objects are therefore inferred from the BSC schema and from the join attributes named above:

• BSC_SYS_PERIODICITIES (or equivalent periodicity definition table) — supplies the PERIODICITY_ID parent values.
• Time dimension table — referenced through TIME_FK; the precise target depends on the site's warehouse configuration.
• Balanced Scorecard fact tables (measure and scorecard result tables in the BSC schema) — related via PERIODICITY_ID, YEAR, and PERIOD_ID.
• BSC_SYS_PERIOD sets / calendar setup objects — configure and populate period rows during initial setup.
• FND standard WHO columns — CREATED_BY and LAST_UPDATED_BY resolve to FND_USER.

Because the documented relationship data is minimal and the product is obsolete, integrators should confirm actual key usage directly against the target database rather than relying on the inherited model.