Search Results jtf_nav_node_types_v




Overview
Explore in AI Chat

Overview

JTF_NAV_NODE_TYPES_V is a documented view owned by the APPS schema within the JTF – CRM Foundation product module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The view is recorded in ETRM as VALID and is described simply as a "view on the base table." Functionally, it exposes the metadata that defines node types used by the Oracle CRM Foundation navigator infrastructure. Each node type represents a configurable category of navigable item within a CRM tree — for example, a folder, a form-launching node, or a static parent node. Because it joins node type definitions to their owning tree roots, the view provides a denormalized, business-friendly perspective used by reporting, integration, and diagnostic activities. Rather than querying the underlying definition table and the tree root translation table separately, consumers obtain node type attributes together with the root key in a single, read-only result set. This makes the view well suited to ad hoc queries, data extracts, and integration routines that must resolve how a given navigator tree is composed without directly manipulating the base tables.

Underlying Base Objects

The view is defined over two documented referenced objects:

  • JTF_NAV_NODE_TYPES (exposed through a synonym) — the primary base table holding the node type definitions, including the flow, parent page, primary key, and icon metadata columns.
  • JTF_NAV_TREE_ROOTS_VL (a view) — the translated tree root view, supplying the ROOT_VALUE used to derive the ROOT_KEY column.

The two objects are joined on TREE_ROOT_ID, so every node type is presented alongside the root key of the tree to which it belongs. Aliasing in the view text uses NT for the node types source and TR for the tree roots source, consistent with the documented view SQL. Because JTF_NAV_TREE_ROOTS_VL is itself a translated (VL) view, the joined result may reflect language-specific root values depending on session locale settings.

Key Columns

The view exposes the following documented columns:

Common Use Cases and Queries

Typical scenarios include auditing navigator configuration, identifying which node types belong to a particular tree, and resolving form-launch parameters for integration. A representative query joining node types to a specific root is:

  • SELECT node_type_id, root_key, node_type, form_name FROM jtf_nav_node_types_v WHERE root_key = :p_root_key;
  • SELECT node_type, icon_name, static_child_flag FROM jtf_nav_node_types_v ORDER BY node_type;

Consultants frequently use the view to verify that custom node types have been registered correctly after a tree root migration or patch application, since the ROOT_KEY mapping confirms whether a node type is anchored to the expected tree.