Results for “bne_interface_cols_tl_uk1”

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

Overview

BNE.BNE_INTERFACE_COLS_TL is the translation (TL) table for the interface column metadata maintained in the Oracle E-Business Suite ETRM (Enterprise Transaction Repository Model) layer. It stores the language-specific prompts, hints, and help text that accompany each interface column defined in the base table BNE.BNE_INTERFACE_COLS_B. Because ETRM interface definitions drive the runtime rendering of user-facing setup and transaction pages, this table ensures that the same interface column can present different display text in each installed language without altering the underlying column definition.

The object resides in the BNE schema, is owned under FND Design Data as BNE.BNE_INTERFACE_COLS_TL, and is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10. One row is required for each interface column in each installed language. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone; it therefore functions most naturally as a satellite joined to its base entity rather than as a hub or link. No foreign-key dependencies were mined, which reinforces its role as a descriptive translation satellite surrounding the base interface column record.

Key Information Stored

The table carries fifteen documented columns. The composite primary key, BNE_INTERFACE_COLS_TL_PK, is defined over INTERFACE_CODE, SEQUENCE_NUM, APPLICATION_ID, and LANGUAGE, providing the unique identity of each translated row. A second unique index, BNE_INTERFACE_COLS_TL_UK1, overlaps this key with the columns APPLICATION_ID, INTERFACE_CODE, SEQUENCE_NUM, and LANGUAGE, extended by ZD_EDITION_NAME in the 12.2.2 physical schema. Because the primary key already guarantees uniqueness on the same business attributes, this unique index functions as a redundant business-key candidate and is the object referenced when users search for bne_interface_cols_tl_uk1.

The most important descriptive columns are:

• APPLICATION_ID — application identifier and foreign key to FND_APPLICATIONS.APPLICATION_ID.
• INTERFACE_CODE — unique code identifying the entity for the given application.
• SEQUENCE_NUM — unique number identifying the interface column.
• LANGUAGE — the language in which the prompts are stored.
• SOURCE_LANG — the language the text mirrors; untranslated rows reflect changes made to the source-language row.
• PROMPT_LEFT — the left-aligned display prompt, up to 240 characters.
• PROMPT_ABOVE — the above-field display prompt, up to 240 characters.
• USER_HINT and USER_HELP_TEXT — user-facing guidance, each up to 2000 characters.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on confirming that every interface column has a corresponding translated prompt in each installed language, and on extracting prompts for documentation or localization reviews. A representative query joining the translation table to the base table follows:

• SELECT b.interface_code, b.sequence_num, t.language, t.prompt_left, t.prompt_above FROM bne.bne_interface_cols_b b, bne.bne_interface_cols_tl t WHERE b.application_id = t.application_id AND b.interface_code = t.interface_code AND b.sequence_num = t.sequence_num AND t.language = USERENV('LANG');
• Detecting missing translations by comparing distinct interface columns in the base table with rows present in the TL table for a target language.
• Auditing modification history using LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recently changed prompts.
• Extracting prompt text for user documentation or translation workbooks.

Because the prompts are stored per language, development teams are advised to query with the correct LANGUAGE value rather than assuming a single set of display strings.

Related Objects

The following objects are most closely associated with BNE_INTERFACE_COLS_TL:

• BNE.BNE_INTERFACE_COLS_B — the base table holding the untranslated interface column definition; joined on APPLICATION_ID, INTERFACE_CODE, and SEQUENCE_NUM.
• FND_APPLICATIONS — referenced via APPLICATION_ID.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.
• Other BNE interface metadata tables (for example, BNE_INTERFACE_TL and BNE_INTERFACE_COLS_B) that follow the same TL pattern and are maintained through the same ETRM setup pages.

These relationships make the table a supporting translation satellite within the BNE interface configuration model rather than a standalone transactional entity.