Results for “bne_perf_statistics_tl”

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

Overview

BNE_PERF_STATISTICS_TL is a translation (TL) table owned by the BNE schema, the product schema for Oracle Web Applications Desktop Integrator (Web ADI). It stores the language-specific definitions of performance statistics captured by the BNE performance framework. Each row represents a single performance statistic definition, or a translation of that definition, in a specific language. The _TL suffix indicates that the descriptive attributes of the statistic are maintained per installed language, while language-independent attributes are retained in the corresponding base table.

The object is essential for any diagnostic or monitoring activity that depends on rendering statistic names and descriptions in the user's session language. BNE uses performance statistics to instrument desktop integration operations such as uploads, downloads, and journal imports, and the translated definitions are what surface to end users in the Web ADI interface.

From a Data Vault modeling perspective, the metadata classifies this object as standalone, meaning the heuristic FK analysis found no inbound or outbound foreign keys to other documented tables. In Data Vault terms, a standalone design suggests this is best treated as a satellite (or a language-dependent reference/dimension table) rather than a hub or a link, because its primary key is a composite business key rather than a surrogate identifier. The modeling suggestion is therefore to preserve it as a descriptive satellite keyed by STATISTIC_CODE plus LANGUAGE.

Key Information Stored

The table contains ten documented columns in the 12.2.2 ETRM physical schema. The most significant are:

• STATISTIC_CODE — the business identifier for the performance statistic. Combined with LANGUAGE it forms the primary key constraint BNE_PERF_STATISTICS_TL_PK and is also the leading column of the unique index BNE_PERF_STATISTICS_TL_UK1.
• LANGUAGE — the NLS language code for the row's translation. Also part of both the primary key and the unique index.
• SOURCE_LANG — the language from which the row was originally loaded, used by the translation infrastructure to identify the source of translated content.
• ZD_EDITION_NAME — the editioning column added in EBS 12.2 for Online Patching (Edition-Based Redefinition). It participates in the unique index BNE_PERF_STATISTICS_TL_UK1 (STATISTIC_CODE, LANGUAGE, ZD_EDITION_NAME), making the business key edition-aware.
• USER_NAME — typically the last-updated-by user context or the owner of the statistic definition.
• CREATED_BY / CREATION_DATE — standard WHO audit columns recording creation context and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_LOGIN / LAST_UPDATE_DATE — standard WHO audit columns recording the most recent update, the login of the updating session, and the update timestamp.

No separate surrogate ID column is documented; identity is expressed through the composite business key. Note that the base (non-TL) table holds the language-independent attributes, with the underlying key being STATISTIC_CODE and LANGUAGE as well.

Common Use Cases and Queries

The most frequent use case is joining the translation table to the base statistic table to retrieve the display name and description in the current session language, defaulting to the base language when no translation exists. A typical pattern is:

• Selecting statistic metadata: SELECT statistic_code, language, source_lang, last_update_date FROM bne.bne_perf_statistics_tl WHERE language = USERENV('LANG');
• Reporting on coverage: identifying statistics that have not been translated into a target language by comparing the base table's key set against the TL rows for that LANGUAGE.
• DI/ETL extraction: using STATISTIC_CODE + LANGUAGE as the natural key when loading into an external warehouse or a Power BI dataset. The ZD_EDITION_NAME column should be filtered to the active edition in 12.2 environments.
• Audit reporting: querying CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace when a statistic definition or translation was introduced or modified.

Because the table is low-volume and reference-oriented, it is well suited to being cached or replicated to reporting platforms rather than queried directly during transaction processing.

Related Objects

The ETRM metadata records no FK relationships for this table, so the relationship list below is inferred from naming conventions and the BNE performance framework rather than declared constraints:

• BNE_PERF_STATISTICS — the base table holding language-independent statistic attributes; joined on STATISTIC_CODE.
• BNE_PERF_STATISTICS_TL_PK — the primary key constraint enforcing STATISTIC_CODE + LANGUAGE uniqueness.
• BNE_PERF_STATISTICS_TL_UK1 — the unique index on STATISTIC_CODE, LANGUAGE, ZD_EDITION_NAME.
• FND_LANGUAGES — provides the valid values for LANGUAGE and SOURCE_LANG.
• BNE_PERF_* dependent objects such as performance snapshot or metric tables that reference STATISTIC_CODE at load time.
• FND_APPLICATION / BNE product metadata — supplies the owning application context used by the Desktop Integrator performance dashboards.

Consumers should always join through STATISTIC_CODE and LANGUAGE, and in 12.2 include the ZD_EDITION_NAME predicate to respect editioning.