Results for “ibc_labels_tl”

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

Overview

IBC_LABELS_TL is the translation (language) table within the IBC – Content Manager product in Oracle EBS 12.1.1 and 12.2.2. It stores the multilingual, translatable attributes of label definitions used by the Content Manager subsystem, most notably the displayable label name and description for each supported language. The "_TL" suffix identifies it as the language-dependent companion to the base table, IBC_LABELS_B, which holds the language-independent (base) definition of each label. Together the two tables form a standard Oracle Applications translation pair keyed on the LABEL_CODE business identifier.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table is best treated as a descriptive satellite attached to the base label hub/link represented by IBC_LABELS_B, carrying the language-specific descriptive payload (label name, description) rather than defining new business entities of its own.

Key Information Stored

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

• LABEL_CODE – The business identifier of the label; the primary join key to IBC_LABELS_B.
• LANGUAGE – The language code identifying the translation for a given row; combined with LABEL_CODE this forms the primary key IBC_LABELS_TL_PK.
• LABEL_NAME – The translated, user-facing name of the label in the given language.
• DESCRIPTION – The translated descriptive text for the label.
• SOURCE_LANG – The source language from which the translation originates.
• ZD_EDITION_NAME – The edition identifier supporting Oracle's edition-based redefinition (EBR) model; combined with LABEL_CODE and LANGUAGE in unique index IBC_LABELS_TL_U1.
• SECURITY_GROUP_ID – Associates the row with a security group; foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle "WHO" audit columns tracking row provenance.

The surrogate primary key is IBC_LABELS_TL_PK (LABEL_CODE, LANGUAGE). The business-key candidate, captured by unique index IBC_LABELS_TL_U1, extends this to include ZD_EDITION_NAME, accommodating multiple editions of the same logical label.

Common Use Cases and Queries

Typical uses include populating LOVs and display fields with the correct translated label for a session's language, and joining translation rows to their base definitions. A common pattern retrieves the translated name for a known label:

• SELECT tl.label_name FROM ibc_labels_tl tl WHERE tl.label_code = :p_code AND tl.language = USERENV('LANG');
• Reporting all labels requiring a specific locale: SELECT label_code, label_name FROM ibc_labels_tl WHERE language = :lang;
• Auditing translation completeness by comparing IBC_LABELS_B rows against available translations in IBC_LABELS_TL.

Note that because the table is EBR-aware, queries should generally filter on the correct edition (via ZD_EDITION_NAME) when the database is running in an editioning configuration.

Related Objects

• IBC_LABELS_B – The base (language-independent) label table; joined on LABEL_CODE (IBC_LABELS_TL.LABEL_CODE → IBC_LABELS_B).
• FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID for security-group partitioning.
• IBC_LABELS_TL_PK – Primary key constraint on (LABEL_CODE, LANGUAGE).
• IBC_LABELS_TL_U1 – Unique index on (LABEL_CODE, LANGUAGE, ZD_EDITION_NAME).
• Other IBC – Content Manager tables and the Oracle Application Object Library (FND) language and security-group infrastructure that provide LANGUAGE and SECURITY_GROUP_ID values.