Search Results ibc_directory_nodes_tl




Overview
Explore in AI Chat

Overview

The IBC_DIRECTORY_NODES_TL table is a core component of the Content Manager (IBC) module within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. As a translation table (denoted by the '_TL' suffix), its primary function is to store multilingual information for directory nodes. These nodes form the hierarchical structure of the content repository, organizing digital assets such as documents, images, and other managed content. The table enables the EBS application to present directory names and descriptions in the language of the user's session, supporting global deployments. It operates in conjunction with its base table, IBC_DIRECTORY_NODES_B, which holds non-translatable, language-independent attributes.

Key Information Stored

The table's structure is designed to manage translated text for each directory node across multiple installed languages. Its primary key is a composite of DIRECTORY_NODE_ID and LANGUAGE, ensuring a unique translation record per node per language. The DIRECTORY_NODE_ID column is a foreign key that links each translation row to a specific directory node defined in the IBC_DIRECTORY_NODES_B table. The LANGUAGE column stores the language code (e.g., 'US' for American English) for the translation. While the specific column list is not detailed in the provided metadata, typical translation tables in EBS include columns such as NODE_NAME and DESCRIPTION to hold the translated textual attributes. Additional standard columns like CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are also invariably present for auditing.

Common Use Cases and Queries

This table is queried whenever the Content Manager interface renders the content directory tree in a user's session language. Common operational and reporting scenarios include generating a list of all directory nodes with their translated names for a specific language, or identifying nodes missing translations for a critical language. A typical query to retrieve translated node information would join this table with its base table.

  • Sample Query: To fetch the active directory structure in the current session language, a developer might use: SELECT b.PARENT_DIRECTORY_NODE_ID, tl.NODE_NAME FROM ibc_directory_nodes_b b, ibc_directory_nodes_tl tl WHERE b.directory_node_id = tl.directory_node_id AND tl.language = USERENV('LANG') ORDER BY b.ORDER_OF_LEVEL;
  • Data Fix: Administrators may run update statements on this table to correct translated text for a specific node and language, ensuring the DIRECTORY_NODE_ID and LANGUAGE conditions are precisely specified in the WHERE clause.

Related Objects

The IBC_DIRECTORY_NODES_TL table has a direct and essential relationship with the IBC_DIRECTORY_NODES_B table, as defined by its foreign key constraint. The DIRECTORY_NODE_ID column in the TL table references the DIRECTORY_NODE_ID in the B table. This relationship is foundational; a directory node must exist in the base table before translations can be entered. The table is also intrinsically linked to the broader Content Manager data model, which includes objects for content items (IBC_CONTENT_ITEMS_B/TL), categories, and permissions. Any application programming interface (API) or user interface (UI) process that creates, updates, or displays directory nodes will interact with this translation table, typically via the standard Oracle Translation Table architecture.