Results for “content_item_name”

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

Overview

IBC_CITEM_VERSIONS_TL is a language-striped (translation) table in the Oracle E-Business Suite Content Manager module (product code IBC). It stores the translated, language-dependent descriptive attributes of content item versions whose language-independent definition resides in the base table IBC_CITEM_VERSIONS_B. The table is owned by the IBC schema and is registered with VALID status in both Oracle EBS 12.1.1 and 12.2.2, with a documented physical schema of 19 columns in the ETRM 12.2.2 reference.

In Data Vault modeling terms, the FK structure mined from the metadata suggests a satellite-leaning classification: the table hangs off IBC_CITEM_VERSIONS_B via CITEM_VERSION_ID and carries descriptive, context-dependent text rather than acting as an independent hub of business entities. It should therefore be treated as an attribute satellite keyed by a hub/link in the version model, not as a standalone entity. The table also participates in a lineage path to the attachment and security subsystems through FND_LOBS and FND_SECURITY_GROUPS.

Key Information Stored

The documented primary key is the constraint IBC_CITEM_VERSION_LANGS_PK, defined on (CITEM_VERSION_ID, LANGUAGE). CITEM_VERSION_ID is the surrogate/foreign identifier linking back to the base version row in IBC_CITEM_VERSIONS_B, and LANGUAGE identifies the translation row. A second documented unique index, IBC_CITEM_VERSIONS_TL_U1, extends this key to (CITEM_VERSION_ID, LANGUAGE, ZD_EDITION_NAME), which is the strongest business-key candidate in the table and reflects the multi-tenant/edition striping used by later 12.2.x deployments.

The principal descriptive columns are CONTENT_ITEM_NAME, DESCRIPTION, ATTACHMENT_FILE_NAME, DEFAULT_RENDITION_MIME_TYPE, and CITEM_TRANSLATION_STATUS, which together describe the localized presentation of a content version. SOURCE_LANG records the originating language for translation workflows. Attachment handling is supported by ATTACHMENT_FILE_ID and ATTRIBUTE_FILE_ID, both of which are foreign keys to FND_LOBS, with ATTACHMENT_ATTRIBUTE_CODE distinguishing the attachment's purpose. Standard EBS audit columns are present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. SECURITY_GROUP_ID ties the row to an FND_SECURITY_GROUPS record for access control, and TEXTIDX supports text indexing/search. ZD_EDITION_NAME supports edition-based redefinition.

Common Use Cases and Queries

Typical reporting scenarios include retrieving the localized name and description of a content version for a specific language, auditing which translations exist for a given version, and tracing attachment files used by localized content. A standard pattern joins the base table to the translation table:

• SELECT b.citem_version_id, tl.language, tl.content_item_name, tl.description FROM ibc.ibc_citem_versions_b b, ibc.ibc_citem_versions_tl tl WHERE b.citem_version_id = tl.citem_version_id AND tl.language = 'US';
• Attachment lineage: join ATTACHMENT_FILE_ID or ATTRIBUTE_FILE_ID to FND_LOBS to resolve the physical file for a localized rendition.
• Translation coverage: group by CITEM_VERSION_ID and compare against the set of required languages, filtering on CITEM_TRANSLATION_STATUS to expose incomplete translations.
• Security-scoped extracts: constrain rows by SECURITY_GROUP_ID when reporting for a specific operating unit or security group.

The common search term "prp_comp_style_ctntvers" corresponds to the dependent table PRP_COMP_STYLE_CTNTVERS, which references this table on (CITEM_VERSION_ID, LANGUAGE) and is the object most frequently joined for style/content-version composition reporting.

Related Objects

• IBC_CITEM_VERSIONS_B — base (language-independent) version table; join on CITEM_VERSION_ID.
• PRP_COMP_STYLE_CTNTVERS — references CITEM_VERSION_ID and LANGUAGE; the primary dependent object for style/content-version relationships.
• FND_LOBS — referenced twice, via ATTACHMENT_FILE_ID and ATTRIBUTE_FILE_ID, for file storage.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for row-level security scoping.
• IBC_CITEM_VERSIONS_TL_U1 — unique index on (CITEM_VERSION_ID, LANGUAGE, ZD_EDITION_NAME), the key candidate for edition-aware queries.

Because the table is language-striped, any query that omits LANGUAGE or filters incorrectly will return duplicate or missing rows; the primary key columns should always be included in join predicates.