Search Results dir_node_code




Overview

IBC_CITEMS_V is a VALID database view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the IBC – Content Manager product module, the component responsible for managing published content, content types, directory structures, and versioned content items within Oracle iStore and related self-service applications. The view consolidates content item master data with type translations, directory node definitions, and content item version details into a single denormalized result set, which makes it suitable for reporting, concurrent program extraction, and integration interfaces that must retrieve a content item together with its versioning and localization context.

The object is exposed in the ETRM repository as a VIEW and is a frequent reference point for administrators and developers searching for the column VERSION_STATUS, which is surfaced here from the underlying version table. Because the view already joins the language (TL) and base (B) tables, consumers avoid writing the multi-table join logic themselves.

Underlying Base Objects

The view is defined over six referenced base objects, all accessed through APPS synonyms: IBC_CITEM_VERSIONS_B, IBC_CITEM_VERSIONS_TL, IBC_CONTENT_ITEMS, IBC_CONTENT_TYPES_TL, IBC_DIRECTORY_NODES_B, and IBC_DIRECTORY_NODES_TL. The join pattern follows standard Oracle EBS multilingual conventions: the "_B" tables hold language-independent rows, while the "_TL" tables hold translated names and descriptions keyed by LANGUAGE.

IBC_CONTENT_ITEMS supplies the core content item record and its workflow-related flags. IBC_CITEM_VERSIONS_B and IBC_CITEM_VERSIONS_TL supply the version row, including the version number and status. IBC_CONTENT_TYPES_TL and IBC_DIRECTORY_NODES_B/_TL provide the content type name and directory node code/name used to classify and locate the item. Column aliases in the view text (for example CITEM_ID, REF_CODE, VERSION_STATUS, DIR_NODE_CODE) provide the public interface used by dependent objects.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting on content item versions by status, identifying items pending translation, auditing locked content, and feeding integration processes that publish content to external repositories.

Sample query listing content item versions and their status:

SELECT citem_id, ref_code, name, version, version_status, language, start_date, end_date FROM apps.ibc_citems_v WHERE version_status = 'PUBLISHED' ORDER BY citem_id, version;

Sample query identifying items requiring translation:

SELECT citem_id, name, ctype_name, dir_node_name FROM apps.ibc_citems_v WHERE trans_required = 'Y' AND language = USERENV('LANG');

Sample query auditing locked content items:

SELECT citem_id, name, locked_by, item_status FROM apps.ibc_citems_v WHERE locked_by IS NOT NULL;