Search Results bne_stylesheets_tl_uk1

Overview

BNE.BNE_STYLESHEETS_TL is the translation table for Oracle E-Business Suite stylesheets. It stores the translated user-facing names and descriptions of the stylesheets whose base (non-translatable) definitions reside in BNE_STYLESHEETS_B. Because interface text in EBS must appear in each installed language, the TL table carries one row for every stylesheet for every language installed in the instance. The row is uniquely identified by the combination of APPLICATION_ID, STYLESHEET_CODE, and LANGUAGE, ensuring that each stylesheet has exactly one translated name per language. The object is owned by the BNE (Business Intelligence/Applications Technology) schema and is a standard seed-data companion table for the base table.

The heuristic Data Vault classification for this object is standalone. From a modeling perspective, it behaves as a satellite-like structure attached to a business key (APPLICATION_ID, STYLESHEET_CODE, LANGUAGE), with no documented foreign-key links to other Data Vault hubs or links. It should be treated as a dependent descriptive table rather than a hub or a link. The translation columns (USER_NAME, DESCRIPTION) are the descriptive payload that changes over time by language.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• APPLICATION_ID (NUMBER(15), mandatory) — application identifier, foreign key to FND_APPLICATIONS.APPLICATION_ID. Identifies the EBS application that owns the stylesheet.
• STYLESHEET_CODE (VARCHAR2(30), mandatory) — unique code identifying the stylesheet for the given APPLICATION_ID. Joins back to BNE_STYLESHEETS_B.
• LANGUAGE (VARCHAR2, mandatory) — the language for which this row provides translated text.
• SOURCE_LANG (VARCHAR2) — the language that non-translated text mirrors. If the text has not yet been translated into LANGUAGE, changes to the source-language row are reflected here.
• USER_NAME (VARCHAR2(240)) — the translated, displayable name of the stylesheet.
• DESCRIPTION (VARCHAR2(2000)) — translated description of the stylesheet.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns recording audit/ownership details.
• ZD_EDITION_NAME (VARCHAR2(30)) — editioning column supporting the online patching/editioning model introduced in EBS 12.2.

The surrogate primary key is BNE_STYLESHEETS_TL_PK on (APPLICATION_ID, STYLESHEET_CODE, LANGUAGE). The business-key candidate documented is the unique index BNE_STYLESHEETS_TL_UK1 on (APPLICATION_ID, STYLESHEET_CODE, LANGUAGE, ZD_EDITION_NAME). Both indexes reside in APPS_TS_TX_IDX, while the table data defaults to APPS_TS_TX_DATA with PCTFREE 10.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include verifying that translated names exist for a given language, identifying untranslated rows (where SOURCE_LANG equals a fallback language), and joining translated metadata to the base stylesheet definition. A representative query is:

• SELECT t.STYLESHEET_CODE, t.LANGUAGE, t.USER_NAME, t.DESCRIPTION FROM BNE.BNE_STYLESHEETS_TL t WHERE t.APPLICATION_ID = :app_id AND t.LANGUAGE = USERENV('LANG');
• Detect missing translations: SELECT b.STYLESHEET_CODE FROM BNE.BNE_STYLESHEETS_B b WHERE NOT EXISTS (SELECT 1 FROM BNE.BNE_STYLESHEETS_TL t WHERE t.APPLICATION_ID = b.APPLICATION_ID AND t.STYLESHEET_CODE = b.STYLESHEET_CODE AND t.LANGUAGE = 'US');
• List all languages available for a stylesheet: SELECT LANGUAGE, USER_NAME FROM BNE.BNE_STYLESHEETS_TL WHERE APPLICATION_ID = :app_id AND STYLESHEET_CODE = :code;

These patterns support localization audits, upgrade verification, and user-interface metadata reporting.

Related Objects

The most significant related objects, based on the documented join columns and BNE schema conventions, include:

• BNE_STYLESHEETS_B — base stylesheet definitions; joined on APPLICATION_ID and STYLESHEET_CODE.
• FND_APPLICATIONS — application master; joined on APPLICATION_ID.
• FND_USER — creator/updater; joined via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — login audit reference via LAST_UPDATE_LOGIN.
• FND_LANGUAGES — language validation via the LANGUAGE column.

Because the object is classified as standalone with no additional FK links documented, these relationships reflect the FK and business-key structure provided rather than a broader dependency graph.