Results for “bne_queries_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BNE_QUERIES_TL is a translation table owned by the BNE schema (Web Applications Desktop Integrator) in Oracle EBS 12.1.1 and 12.2.2. It stores language-specific, translatable attributes for the rows defined in BNE_QUERIES_B, the base table that holds query definitions used by Web ADI and related BNE components. In the standard EBS multilingual model, the _TL table carries the user-facing text (names, descriptions and prompt strings) for every supported language, while the _B table stores language-independent columns such as the owning application and query code.
From a Data Vault modeling perspective, the FK metadata classifies this object heuristically as standalone. BNE_QUERIES_TL therefore can be treated as a descriptive satellite attached to the BNE_QUERIES_B business key; it holds context and translation attributes rather than relationships to other entities, and no dependent links are implied by its constraints.
Key Information Stored
The table exposes 11 documented columns. The primary key, enforced by BNE_QUERIES_TL_PK, is the composite (APPLICATION_ID, QUERY_CODE, LANGUAGE), making the surrogate identifier in practice a concatenation of the parent business key plus the language discriminator. A second unique index, BNE_QUERIES_TL_UK1, extends this to (APPLICATION_ID, QUERY_CODE, LANGUAGE, ZD_EDITION_NAME), which is the business-key candidate that also accounts for the editioning/ZD_EDITION_NAME column introduced in later EBS releases.
- APPLICATION_ID — owning application identifier; part of the primary key and the parent link to BNE_QUERIES_B.
- QUERY_CODE — the query's short code; the core business identifier shared with the base table.
- LANGUAGE — language code of the translated row; the third component of the PK.
- SOURCE_LANG — the source language the current translation was derived from, used in the MLS language-derivation logic.
- USER_NAME — the user-facing name of the query in the given language.
- ZD_EDITION_NAME — editioning column used in 12.2 editions-based architecture; also part of the UK1 business key.
- CREATED_BY, CREATION_DATE — standard WHO columns recording creation audit information.
- LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO columns capturing the most recent modification audit trail.
Note that columns such as DESCRIPTION and prompt text typically reside in the _TL table; the documented metadata above only confirms the columns listed. Reporters should verify additional text columns in the dictionary before relying on them.
Common Use Cases and Queries
The most frequent use is to resolve the display name of a query in a specific language when the base row in BNE_QUERIES_B is already known. A representative join pattern is:
SELECT b.QUERY_CODE, t.USER_NAME, t.LANGUAGE FROM BNE.BNE_QUERIES_B b JOIN BNE.BNE_QUERIES_TL t ON t.APPLICATION_ID = b.APPLICATION_ID AND t.QUERY_CODE = b.QUERY_CODE WHERE t.LANGUAGE = USERENV('LANG');- Auditing translation coverage: count distinct LANGUAGE values per QUERY_CODE to detect queries missing a required translation.
- Extracting the source language lineage with
WHERE t.SOURCE_LANG = 'US'to reconcile translated and original text. - Reporting on WHO audit columns to identify when a translation was last maintained.
Related Objects
- BNE_QUERIES_B — base table; join on (APPLICATION_ID, QUERY_CODE).
- BNE_QUERIES_TL_PK — primary key constraint (APPLICATION_ID, QUERY_CODE, LANGUAGE).
- BNE_QUERIES_TL_UK1 — unique index (APPLICATION_ID, QUERY_CODE, LANGUAGE, ZD_EDITION_NAME).
- BNE_QUERIES (and related BNE query/parameter objects) — higher-level containers that reference the query definition.
- FND_APPLICATION — resolves APPLICATION_ID to an application name for reporting.
- FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG codes.
- BNE_QUERY_PARAMETERS_TL / BNE_QUERY_PARAMETERS_B — sibling translation/base tables for the parameters of each query, joined via the same query code.
-
Translations for BNE_QUERIES_B
-
Translations for BNE_QUERIES_B
-
SYNONYM: APPS.BNE_QUERIES_TL 12.1.1
-
SYNONYM: APPS.BNE_QUERIES_TL 12.2.2
-
TABLE: BNE.BNE_QUERIES_TL 12.1.1
-
TABLE: BNE.BNE_QUERIES_TL 12.2.2
-
VIEW: BNE.BNE_QUERIES_TL# 12.2.2
-
View: BNE_QUERIES_VL 12.2.2
BNE_QUERIES_VL is a standard translation view over the BNE_QUERIES entity.
APPS.BNE_QUERIES_VL·↳ BNE_QUERIES_B·↳ BNE_QUERIES_TL·Explore BNE module →
-
View: BNE_QUERIES_VL 12.1.1
BNE_QUERIES_VL is a standard translation view over the BNE_QUERIES entity.
APPS.BNE_QUERIES_VL·↳ BNE_QUERIES_B·↳ BNE_QUERIES_TL·Explore BNE module →
-
VIEW: BNE.BNE_QUERIES_TL# 12.2.2
-
VIEW: APPS.BNE_QUERIES_VL 12.2.2
-
VIEW: APPS.BNE_QUERIES_VL 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
VIEW: APPS.BNE_QUERIES_VL 12.1.1
-
VIEW: APPS.BNE_QUERIES_VL 12.2.2