Results for “ibc_citem_versions_vl”

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

Overview

IBC_CITEM_VERSIONS_VL is a language-enabled (translated) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the IBC — Content Manager product module, which provides the repository and versioning infrastructure used by Oracle iSetup, iLearning, and other content-driven applications to store and retrieve managed content items. The view exposes version-level records for content items, combining descriptive, translatable attributes with the transactional and audit attributes of each version.

The "_VL" suffix indicates that the view implements Oracle's standard translation pattern: it joins a base table holding language-independent, operational data with a translation table holding language-dependent descriptive text, filtered by the session language. This makes the view the primary, supported access point for reporting, forms, and integration interfaces that need to present content item version information in the user's language. Because it resolves the language join automatically, developers and report authors do not need to write their own translation logic.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• IBC_CITEM_VERSIONS_B — the base table storing language-independent version data, including surrogate keys, status, effective dates, and standard WHO/audit columns.
• IBC_CITEM_VERSIONS_TL — the translation table storing language-dependent descriptive attributes such as the content item name, attachment file name, description, and rendition MIME type.

The join is performed on CITEM_VERSION_ID, with the translation side restricted by the condition T.LANGUAGE = USERENV('LANG'), so each query returns exactly one row per version for the current session language. The view is reported as VALID in the ETRM 12.2.2 metadata, and the same definition applies in 12.1.1, where no structural difference in these objects is documented.

Key Columns

The view exposes the union of the identifying, descriptive, and audit columns from both base tables. Principal columns include:

• ROW_ID — the ROWID of the base table row (IBC_CITEM_VERSIONS_B), useful for direct-row addressing.
• CITEM_VERSION_ID — the primary key of the content item version and the join key between the base and translation tables.
• CONTENT_ITEM_ID — identifies the parent content item to which the version belongs.
• VERSION_NUMBER — the ordinal version number assigned to this iteration of the content item.
• CITEM_VERSION_STATUS — the lifecycle status of the version (for example, draft, active, or obsolete).
• START_DATE / END_DATE — the effective date range during which the version is valid.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle "WHO" audit columns.
• OBJECT_VERSION_NUMBER — the optimistic locking token used by the associated forms and APIs.
• SECURITY_GROUP_ID — the security grouping identifier used by the content repository.
• ATTRIBUTE_FILE_ID, ATTACHMENT_FILE_ID, ATTACHMENT_ATTRIBUTE_CODE — references linking the version to its stored attribute and attachment files.
• CONTENT_ITEM_NAME, ATTACHMENT_FILE_NAME, DESCRIPTION — translated descriptive attributes from the _TL table.
• DEFAULT_RENDITION_MIME_TYPE — the MIME type of the default rendition served for the version.

Common Use Cases and Queries

Typical uses of this view include building reports on content item version history, locating the current active version of a content item, and joining version data to attachment or file repositories. A representative query listing all versions of a content item is:

• SELECT citem_version_id, content_item_id, version_number, citem_version_status, start_date, end_date, content_item_name FROM ibc_citem_versions_vl WHERE content_item_id = :p_content_item_id ORDER BY version_number;
• SELECT citem_version_id, version_number, attachment_file_name, default_rendition_mime_type FROM ibc_citem_versions_vl WHERE citem_version_status = 'ACTIVE' AND SYSDATE BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE);
• SELECT c.content_item_name, v.version_number, v.last_updated_by, v.last_update_date FROM ibc_citem_versions_vl v JOIN ibc_content_items_vl c ON c.content_item_id = v.content_item_id ORDER BY c.content_item_name, v.version_number;

Because the view already filters the translation table by USERENV('LANG'), queries should not add their own language predicates. In integration scenarios, the view is commonly read-only and is best consumed through APPS rather than its underlying base tables, ensuring consistent language resolution and full audit visibility.