Search Results bsc_sys_init_u1

Overview

BSC.BSC_SYS_INIT is a system-level configuration table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the BSC schema. As its name and documented purpose indicate, the table stores system properties consumed by the BSC application modules, which are most commonly associated with Oracle's Balanced Scorecard and related enterprise performance management functionality. The table operates as a straightforward key/value property store: each row captures a single named configuration property and its associated value, allowing the application to retrieve runtime and administrative settings without hard-coding them into forms, concurrent programs, or PL/SQL packages. Resident in the APPS_TS_TX_DATA tablespace, the object follows standard EBS transactional data conventions, including the five mandatory "Who" audit columns that record creation and last-update context for every row.

From a data modelling perspective, the metadata does not declare any foreign key relationships, and the object is classified heuristically as standalone. It is best understood as a reference/lookup structure rather than a transactional fact. Under Data Vault modelling conventions, this object would be a candidate hub keyed on PROPERTY_CODE, with PROPERTY_VALUE and the audit columns modeled as satellite attributes; because no parent or child dependencies exist, it should not be modeled as a link.

Key Information Stored

The table contains seven documented columns. The most important are:

• PROPERTY_CODE (VARCHAR2, 15) — The business key and the sole component of the primary key BSC_SYS_INIT_PK. It names the system property being configured and is the column on which all lookups are performed.
• PROPERTY_VALUE (VARCHAR2, 90) — The value assigned to the corresponding property code. Values are stored as character strings and are interpreted by the consuming application logic.
• CREATED_BY (NUMBER, 15) — Standard Who column identifying the application user who inserted the row.
• CREATION_DATE (DATE) — Standard Who column recording the row insertion timestamp.
• LAST_UPDATED_BY (NUMBER, 15) — Standard Who column identifying the user who most recently modified the row.
• LAST_UPDATE_DATE (DATE) — Standard Who column recording the most recent modification timestamp.
• LAST_UPDATE_LOGIN (NUMBER, 15) — Standard Who column capturing the login session associated with the last update.

The unique index BSC_SYS_INIT_U1, defined on PROPERTY_CODE in the APPS_TS_TX_IDX tablespace, enforces the uniqueness of the business key and is the physical structure most frequently probed during property retrieval. Note that PROPERTY_CODE serves simultaneously as the primary key (BSC_SYS_INIT_PK) and as the unique business-key candidate; there is no separate surrogate identifier column in this table.

Common Use Cases and Queries

The principal use case is runtime configuration lookup: application code, concurrent programs, and personalizations issue single-row queries against BSC_SYS_INIT filtering on PROPERTY_CODE to obtain an operational setting. A typical pattern is:

• SELECT PROPERTY_VALUE FROM BSC.BSC_SYS_INIT WHERE PROPERTY_CODE = :p_code; — the standard point lookup, satisfied by the unique index BSC_SYS_INIT_U1.
• SELECT PROPERTY_CODE, PROPERTY_VALUE FROM BSC.BSC_SYS_INIT ORDER BY PROPERTY_CODE; — an administrative review of all configured properties.
• Audit and change-tracking reports selecting LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN to determine when a configuration value was last changed and by whom.

Because the table is small and fully indexed on its key, it is also useful as a reference source in reporting queries, joining PROPERTY_CODE back to application logic that interprets the value. Administrators should treat direct DML with caution; updates to system properties can affect application behaviour across the BSC module, and the Who columns should be maintained consistently with EBS conventions.

Related Objects

The ETRM dependency data records that BSC.BSC_SYS_INIT does not reference any database object through foreign keys; the relationship classification is standalone. It is referenced only by the APPS synonym BSC_SYS_INIT, which is the public name through which application code and ad hoc queries normally access the table in the APPS schema context. Consequently, the most significant related objects are:

• APPS.BSC_SYS_INIT — the synonym exposing the table to the APPS schema; the standard access path for forms, reports, and SQL sessions.
• BSC_SYS_INIT_PK — the primary key constraint on PROPERTY_CODE.
• BSC_SYS_INIT_U1 — the unique index on PROPERTY_CODE in APPS_TS_TX_IDX, the object referenced in the original search term "bsc_sys_init_u1".

Other BSC configuration and parameter tables may be consulted alongside this object by the consuming application, but per the documented dependency data, no enforced relational joins exist. Any association with other BSC or Oracle Performance Management tables is logical rather than declarative and must be validated against the specific application logic in use.