Results for “ibc_directory_nodes_vl”

30 results




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

Overview

The IBC_DIRECTORY_NODES_VL view is a public, language-sensitive (VL) reporting object owned by the APPS schema within the Oracle E-Business Suite IBC – Content Manager product. It exposes the logical hierarchy of directory nodes used by Content Manager to organize uploaded content, folders, and documents. In the EBS data model, directory nodes form the navigable tree that users traverse when browsing the Content Manager repository; each node represents a folder or organizational container. Because the view follows Oracle's standard "_VL" (translated view) convention, it returns descriptive attributes in the session's current language, determined by USERENV('LANG'). This makes it the preferred interface for reports, concurrent programs, and integrations that must present directory names and descriptions in the end user's own language. The view is documented as VALID in both the 12.1.1 and 12.2.2 releases, and its definition is stable across those versions. The user search term "directory_node_code" maps directly to one of its exposed columns, which is significant because that column is the business-facing identifier used in lookups and external references.

Underlying Base Objects

The view is defined over two base tables, both referenced through APPS-owned synonyms:

  • IBC_DIRECTORY_NODES_B — the "B" (base) table holding language-independent data such as the primary key, the directory node code, node type, WHO/audit columns, and object version.
  • IBC_DIRECTORY_NODES_TL — the "TL" (translated) table holding language-specific attributes, principally the directory node name and description.

As shown in the view text, the two tables are joined on DIRECTORY_NODE_ID with an additional filter T.LANGUAGE = USERENV('LANG'). The B table supplies the transactional and identifying columns, while the TL table supplies the localized text. This two-table pattern (B + TL joined in a VL view) is the standard Oracle translation model and is used throughout IBC.

Key Columns

  • ROW_ID — the ROWID of the base-table row, useful for direct row addressing.
  • DIRECTORY_NODE_ID — the surrogate primary key that uniquely identifies each directory node and links the B and TL records.
  • DIRECTORY_NODE_CODE — the user-visible code for the node; this is the column most often referenced in lookups and is typically the value users search for when they query by node code.
  • NODE_TYPE — classifies the node (for example, folder versus other node categories).
  • DIRECTORY_NODE_NAME — the translated, display name of the node, sourced from the TL table.
  • DESCRIPTION — the translated description text.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • OBJECT_VERSION_NUMBER — optimistic-locking version stamp used by the OAF framework.
  • SECURITY_GROUP_ID — the security group that scopes the record in a multi-org/multi-group environment.

Common Use Cases and Queries

The view is typically used to resolve a directory node code to its localized name, to feed content-management reports, or to validate a node before mapping uploaded content. A common requirement is to retrieve the display name for a known code:

SELECT directory_node_id, directory_node_code, directory_node_name, description FROM apps.ibc_directory_nodes_vl WHERE directory_node_code = :p_node_code;

To list all nodes of a given type for a reporting or integration program:

SELECT directory_node_code, directory_node_name, node_type FROM apps.ibc_directory_nodes_vl WHERE node_type = :p_node_type ORDER BY directory_node_name;

For audit or data-governance queries, the WHO columns can be selected to trace when nodes were last maintained. Because the view is language-sensitive, the same query returns text in the language of the executing session, so API and concurrent-program callers should be aware that USERENV('LANG') governs the returned name and description; if a specific language is required, the session's NLS_LANGUAGE must be set accordingly or the underlying TL table queried directly with an explicit LANGUAGE predicate.