Results for “tree_root_id”

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

Overview

JTF_NAV_TREE_ROOTS_B is the base table in the JTF (CRM Foundation) schema that stores the tree root definition for each navigation "view by" configuration in Oracle EBS. It is a core metadata component of the Oracle CRM Foundation navigation framework, which governs how hierarchical navigators (such as the CRM Resource Manager, Territory Manager, and various self-service trees) organize and render their top-level root nodes. Each row represents a distinct tree root, and the table acts as the anchor point from which node types, translated names, and view-by attributes are resolved at runtime.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. That is offered as a modeling suggestion rather than a definitive architectural statement: the table carries a single surrogate key (TREE_ROOT_ID), a small set of descriptive attributes, and inbound references from related tables, which is consistent with hub-like behavior at the center of the navigation relationship graph.

Key Information Stored

The table is documented with 11 columns in the 12.2.2 physical schema. The most significant are:

• TREE_ROOT_ID — the surrogate primary key, enforced by JTF_NAV_TREE_ROOTS_B_PK, uniquely identifying each tree root.
• ROOT_VALUE — the business identifier for the root; together with ZD_EDITION_NAME it forms the unique index JTF_NAV_TREE_ROOTS_B_U2.
• VIEWBY_ID — foreign key to JTF_NAV_VIEWBYS_B, associating the root with a specific "view by" dimension.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling row-level security visibility.
• SEQUENCE_NUMBER — orders roots within a view-by grouping.
• ZD_EDITION_NAME — editioning column supporting online patching in 12.2.x; with TREE_ROOT_ID it forms unique index JTF_NAV_TREE_ROOTS_B_U1.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Note that TREE_ROOT_ID functions both as surrogate PK and as a business-key component in U1; ROOT_VALUE is the primary business-key candidate via U2.

Common Use Cases and Queries

Typical usage includes on-site diagnosis of navigation failures, populating translated root names, and reporting on navigator configuration. A common join retrieves roots with their view-by context:

SELECT r.TREE_ROOT_ID, r.ROOT_VALUE, v.VIEWBY_NAME, r.SEQUENCE_NUMBER
FROM JTF_NAV_TREE_ROOTS_B r, JTF_NAV_VIEWBYS_B v
WHERE r.VIEWBY_ID = v.VIEWBY_ID;

To display localized root labels, join the translation table on TREE_ROOT_ID:

SELECT b.TREE_ROOT_ID, t.TREE_ROOT_NAME
FROM JTF_NAV_TREE_ROOTS_B b, JTF_NAV_TREE_ROOTS_TL t
WHERE b.TREE_ROOT_ID = t.TREE_ROOT_ID
AND t.LANGUAGE = USERENV('LANG');

Security-filtered reporting should additionally constrain SECURITY_GROUP_ID against FND_SECURITY_GROUPS to respect the active responsibility's group.

Related Objects

The principal dependent and referenced objects are:

• JTF_NAV_TREE_ROOTS_TL — translation table keyed on TREE_ROOT_ID; stores language-specific root names.
• JTF_NAV_NODE_TYPES — references TREE_ROOT_ID, defining node types belonging to each root.
• JTF_NAV_VIEWBYS_B — parent of VIEWBY_ID; defines the view-by grouping.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; drives row-level security.

These four represent the primary join surface for both runtime navigation resolution and administrative reporting queries against the JTF navigation framework.