Search Results bsc_sys_init




Overview
Explore in AI Chat

Overview

BSC_SYS_INIT is a system configuration table belonging to the Oracle Balanced Scorecard (BSC) product family, which is classified as obsolete in Oracle E-Business Suite release 12.1.1 and 12.2.2. The table's documented description is "System Properties," indicating that it stores application-level settings and initialization parameters used by the Balanced Scorecard module. In the EBS architecture, tables of this type function as reference or control repositories that govern runtime behavior, defaults, and feature toggles for the owning application.

The ETRM metadata records a clear caveat: "Not implemented in this database." This signifies that BSC_SYS_INIT is documented in the data model but is not physically created in the environment from which the metadata was extracted. Its presence in the ETRM repository is therefore of historical and structural interest, reflecting the schema as it was shipped or catalogued for the BSC product rather than an active, queryable object in current installations. Because BSC is obsolete, the table is unlikely to appear in supported configurations of 12.1.1 or 12.2.2.

From a heuristic Data Vault modeling perspective, the metadata classifies BSC_SYS_INIT as standalone. This suggests the table be modeled as a hub or reference satellite in its own right, with no mined foreign-key links to other entities. The absence of relationship data confirms that it does not participate in the referential fabric of the BSC schema and should be treated as an independent configuration entity.

Key Information Stored

The documented physical schema assigns ownership to the BSC schema and lists seven columns. The most significant are:

  • PROPERTY_CODE — the business identifier for each system property; this is both the primary key column (via BSC_SYS_INIT_PK) and the unique business-key candidate (via BSC_SYS_INIT_U1). It defines the semantic name of the setting.
  • PROPERTY_VALUE — the stored value corresponding to each property code, holding the actual configuration data consumed by the application.
  • CREATED_BY — the user or process that inserted the row.
  • CREATION_DATE — the timestamp of initial insertion.
  • LAST_UPDATED_BY — the user or process responsible for the most recent modification.
  • LAST_UPDATE_DATE — the timestamp of the most recent modification.
  • LAST_UPDATE_LOGIN — the login context associated with the last update, used for audit traceability.

The five audit columns follow the standard EBS WHO-column convention and support change tracking and lineage. The surrogate primary key is BSC_SYS_INIT_PK on PROPERTY_CODE; the unique index BSC_SYS_INIT_U1 also enforces uniqueness on PROPERTY_CODE, meaning the business key and the surrogate key coincide in this design — a common pattern for simple property tables without a separate numeric identifier.

Common Use Cases and Queries

Where present and populated, BSC_SYS_INIT supports administrative inspection and configuration validation. Typical query patterns include retrieving a specific setting and reviewing recent configuration changes:

  • Point lookup: SELECT PROPERTY_VALUE FROM BSC_SYS_INIT WHERE PROPERTY_CODE = :code;
  • Change audit: SELECT PROPERTY_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM BSC_SYS_INIT ORDER BY LAST_UPDATE_DATE DESC;
  • Configuration inventory: SELECT PROPERTY_CODE, PROPERTY_VALUE FROM BSC_SYS_INIT ORDER BY PROPERTY_CODE;

Because the object is marked obsolete and not implemented, these queries will fail with ORA-00942 in most environments; they are relevant primarily for migration analysis, legacy data-model documentation, or upgrade assessment exercises where the historical BSC schema must be reconciled against current releases.

Related Objects

The ETRM metadata reports no foreign-key relationships for BSC_SYS_INIT and classifies it as standalone. Consequently, no documented join columns exist between this table and other objects. In the wider BSC schema, related configuration tables would typically include BSC system parameter and preference tables, along with the BSC application schema objects and the FND profile option infrastructure that frequently governed similar settings. However, since BSC_SYS_INIT is obsolete and unimplemented, and no FK evidence was mined, these associations are contextual rather than structural; the table should be regarded as an isolated reference entity with no enforced dependencies on other documented objects.