Results for “ibc_directory_nodes_tl”

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

Overview

IBC_DIRECTORY_NODES_TL is a translation (TL) table owned by the IBC schema, which supports the Oracle E-Business Suite Content Manager module (product short name IBC). As its name and ETRM description indicate, the table stores translated information about directory nodes — the named and described entries that make up the hierarchical folder structure used to organize content items managed by Content Manager. In Oracle EBS, virtually every user-facing catalog, folder, or library construct employs the standard language-pair design: a base table holds language-independent attributes and identity, while an accompanying _TL table holds the language-dependent text columns such as name and description, one row per installed language.

From a data-modeling perspective, the relationship metadata classifies this object as satellite-leaning. Under a Data Vault interpretation, the language-specific descriptive attributes (name and description) behave as a satellite dependent on the base entity IBC_DIRECTORY_NODES_B, keyed by the directory node identity plus language. This is a heuristic suggestion rather than a physical implementation, but it accurately reflects the dependency of every _TL row on a single parent row in the _B table.

Key Information Stored

The table’s primary key is IBC_DIRECTORY_NODES_TL_PK, composed of DIRECTORY_NODE_ID and LANGUAGE. DIRECTORY_NODE_ID is the foreign key and surrogate identifier of the node, while LANGUAGE identifies the language of the translated text. The documented unique index IBC_DIRECTORY_NODES_TL_U1 (DIRECTORY_NODE_ID, LANGUAGE, ZD_EDITION_NAME) is the business-key candidate; ZD_EDITION_NAME supports Oracle’s edition-based redefinition feature and permits multiple edition-specific versions of the same logical row.

• DIRECTORY_NODE_ID — surrogate identifier linking the translation to its base record in IBC_DIRECTORY_NODES_B.
• LANGUAGE — the language code for this translation row.
• SOURCE_LANG — the language from which the text was translated, used by the translation framework for change detection.
• DIRECTORY_NODE_NAME — the translated display name of the directory node.
• DESCRIPTION — the translated descriptive text for the node.
• SECURITY_GROUP_ID — the security group (operating unit) that owns the row, referencing FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — edition identifier for edition-based redefinition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified each translation row and when.

Common Use Cases and Queries

The primary use case is multilingual presentation of the Content Manager directory hierarchy: joining the base table to the translation table, filtered by the session language, produces the folder labels shown in the user interface and in reports. A typical query joins on the node identifier and constrains the language:

• SELECT b.directory_node_id, t.directory_node_name, t.description FROM ibc.ibc_directory_nodes_b b, ibc.ibc_directory_nodes_tl t WHERE b.directory_node_id = t.directory_node_id AND t.language = USERENV('LANG')
• Translation-completeness audits that compare installed languages against rows present in the _TL table to detect untranslated nodes.
• Reconciliation of SOURCE_LANG against LANGUAGE to identify outdated translations after source text changes.
• Security-scoped reporting joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID.

Related Objects

The most significant related objects, derived from the documented foreign-key relationships, are:

• IBC_DIRECTORY_NODES_B — the base table; joined on DIRECTORY_NODE_ID. All language-independent attributes and the node’s structural position live here.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID to scope rows to an operating unit or security group.
• IBC_DIRECTORY_NODES_TL_PK / IBC_DIRECTORY_NODES_TL_U1 — the primary and unique indexes that enforce identity and edition-aware uniqueness.
• FND_LANGUAGES — the underlying language definition source that constrains valid values for LANGUAGE and SOURCE_LANG.
• Content Manager translation APIs and concurrent programs — the standard EBS translation and editioning utilities that populate and maintain rows in this table.