Results for “content_type_code”

50+ results




Overview
Explore in AI Chat

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

Overview

IBC_CONTENT_TYPES_TL is a translation (TL) table within the IBC Content Manager product of Oracle E-Business Suite, holding language-specific descriptive text for content type definitions. In Oracle EBS, content types categorize the kinds of content managed by IBC — such as documents, images, or other managed assets — and this table supplies the human-readable names and descriptions in each installed language. The base, language-independent attributes of a content type reside in the companion table IBC_CONTENT_TYPES_B; the "_TL" suffix indicates that this object stores translatable columns and joins to the base table on the CONTENT_TYPE_CODE business key.

The ETRM Data Vault classification for this table, mined heuristically from its foreign-key structure, is satellite-leaning. This means the table is best modeled as a satellite attached to its parent content type entity, carrying descriptive, non-key attributes that vary by language rather than introducing new relationships of its own.

Key Information Stored

The table is owned by the IBC schema and contains twelve documented columns. The most significant are:

  • CONTENT_TYPE_CODE — the business identifier of the content type; forms part of the primary key and the foreign key to IBC_CONTENT_TYPES_B.
  • LANGUAGE — the language code for the translated row; also part of the primary key.
  • CONTENT_TYPE_NAME — the translated display name of the content type.
  • DESCRIPTION — the translated longer description.
  • SOURCE_LANG — the source language from which the translation was derived.
  • SECURITY_GROUP_ID — the security group that governs access to the row, referencing FND_SECURITY_GROUPS.
  • ZD_EDITION_NAME — the edition label supporting Oracle's edition-based redefinition feature.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit and "WHO" columns tracking row creation and modification.

The primary key is IBC_CONTENT_TYPES_TL_PK, defined on (CONTENT_TYPE_CODE, LANGUAGE). A unique index, IBC_CONTENT_TYPES_TL_U1, is defined on (CONTENT_TYPE_CODE, LANGUAGE, ZD_EDITION_NAME) and serves as the business-key candidate. The foreign key IBC_CONTENT_TYPES_TL.CONTENT_TYPE_CODE references IBC_CONTENT_TYPES_B, anchoring each translated row to its base definition.

Common Use Cases and Queries

Typical usage centers on multilingual reporting and content-type lookups. A common pattern joins the translation table to the base table to retrieve display values for a specific language, for example:

  • Listing all content types with their English names: SELECT b.content_type_code, t.content_type_name FROM ibc_content_types_b b, ibc_content_types_tl t WHERE b.content_type_code = t.content_type_code AND t.language = 'US';
  • Producing a bilingual comparison to audit missing translations across languages.
  • Feeding pick-lists and value-set lookups in IBC Content Manager forms and concurrent programs.
  • Verifying translation coverage by comparing row counts per LANGUAGE against SOURCE_LANG.

Because the table carries SECURITY_GROUP_ID, reporting queries should respect the operating security group filter to return only authorized rows.

Related Objects

  • IBC_CONTENT_TYPES_B — the base table holding language-independent attributes; joined on CONTENT_TYPE_CODE.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for row-level security.
  • IBC_CONTENT_TYPES_TL_PK and IBC_CONTENT_TYPES_TL_U1 — the defining primary key and unique business-key indexes.
  • Other IBC Content Manager tables — content definitions and relationships that reference content types via CONTENT_TYPE_CODE.
  • FND_LANGUAGES — the reference table for the LANGUAGE and SOURCE_LANG values.