Search Results bsc_db_reserved_words

Overview

BSC_DB_RESERVED_WORDS is a reference table that belongs to the BSC (Balanced Scorecard) product family in Oracle E-Business Suite. Within the documented ETRM metadata for releases 12.1.1 and 12.2.2, this object is explicitly classified as part of an Obsolete module, and the implementation note states that it is "Not implemented in this database." The table therefore serves primarily as a historical or residual schema artifact rather than an active operational object in a standard EBS installation.

Conceptually, the table represents a catalog of reserved words, segmented by type, that would have been used to validate identifiers, prevent naming collisions, or enforce syntactic constraints during the creation or import of Balanced Scorecard content such as scorecards, perspectives, objectives, or database-level object names. Despite its obsolete status, ETRM documents a complete physical definition, indicating that the object may still be present in certain legacy or customized environments where the BSC schema was deployed.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. Because no inbound or outbound FK relationships are documented, the table is best modeled as an independent reference or lookup set, functioning neither as a hub, link, nor satellite connected to a broader integration model. It holds static enumeration data rather than transactional or historical state.

Key Information Stored

The documented physical schema for BSC_DB_RESERVED_WORDS in ETRM 12.1.1 contains just two columns, and both participate in the primary key and in a unique index. The most important elements are:

• TYPE — Categorizes each reserved word into a logical group or namespace (for example, a category of identifier, keyword class, or naming context). It forms the leading component of the composite primary key and helps scope validation rules.
• WORD — The actual reserved word or token value stored in the catalog. It is the second component of the composite key and the attribute against which candidate identifiers would be checked.

The surrogate identifier for this table is the composite primary key BSC_DB_RESERVED_WORDS_PK (TYPE, WORD). A separate unique index, BSC_DB_RESERVED_WORDS_U1 (TYPE, WORD), duplicates the same column pair as a business-key candidate, confirming that the natural key is the TYPE/WORD combination and that no additional surrogate sequence column is documented. Because both columns are consumed by the primary key, there are no non-key attributes; the row represents an atomic reserved-word assertion rather than an entity with descriptive payload.

Common Use Cases and Queries

Because the object is marked obsolete and not implemented in the database, direct production use is unlikely. Nonetheless, in environments where the table persists, typical scenarios include auditing legacy scorecard metadata, migrating or archiving retired BSC configuration, and confirming that customizations do not conflict with reserved tokens. A representative lookup query is:

• SELECT TYPE, WORD FROM BSC.BSC_DB_RESERVED_WORDS WHERE TYPE = :p_type ORDER BY WORD;
• SELECT COUNT(*), TYPE FROM BSC.BSC_DB_RESERVED_WORDS GROUP BY TYPE;
• SELECT WORD FROM BSC.BSC_DB_RESERVED_WORDS WHERE UPPER(WORD) = UPPER(:candidate);

These patterns support validation of user-supplied names, generation of a reserved-word list for import routines, and reporting on the composition of each reserved-word type. When the table is absent, equivalent logic is typically embedded in application code or handled by other validation mechanisms.

Related Objects

The ETRM metadata documents no foreign-key relationships, and the heuristic classification is standalone, so no dependent tables, views, or APIs are formally linked through referential constraints. Any references that exist are therefore conventional rather than enforced, and the table should be treated as an isolated reference set within the BSC schema. Where BSC components such as scorecard definition or objective metadata tables historically performed name validation, they would reference BSC_DB_RESERVED_WORDS only in application logic, not through database constraints. Given its obsolete status, administrators should verify object presence before relying on it and should consult the corresponding 12.2.2 repository definitions, which may omit the object entirely.