Search Results jtf_nav_tree_roots_b_u2




Overview

JTF.JTF_NAV_TREE_ROOTS_B is the base (language-independent) definition table for navigation tree roots in the Oracle E-Business Suite Framework (JTF) navigation layer. It stores the highest-level anchor points from which navigational tree structures are rendered for a given "view-by" context. In Oracle EBS 12.1.1 and 12.2.2 this object is owned by the JTF schema, carries a status of VALID, and resides in the APPS_TS_SEED tablespace, signalling that its contents are treated as seed or setup data rather than high-volume transactional data. FND Design Data identifies it as JTF.JTF_NAV_TREE_ROOTS_B.

The presence of a ZD_EDITION_NAME column and its inclusion in both unique indexes indicates the table participates in the Edition-Based Redefinition (EBR) / online patching model introduced with EBS 12.2, while remaining compatible with 12.1.1 installations. The ETRM metadata classifies this object heuristically as hub-leaning within a Data Vault modelling perspective — that is, a modelling suggestion that TREE_ROOT_ID behaves as a durable business key anchored at the centre of the navigation domain, with associated descriptive and language data distributed into dependent satellites and translation tables.

Key Information Stored

The table contains eleven documented columns. The most significant are:

The distinction between the surrogate key (TREE_ROOT_ID) and the business-key candidates (TREE_ROOT_ID plus ZD_EDITION_NAME, and ROOT_VALUE plus ZD_EDITION_NAME) is central to correct joins and to avoiding duplication during data migration.

Common Use Cases and Queries

Typical use cases include reporting on the set of navigation roots exposed for each view-by, validating seed data after patching or cloning, and tracing the parentage of navigation node types back to their root. A representative extraction query follows:

  • SELECT TREE_ROOT_ID, ROOT_VALUE, VIEWBY_ID, SEQUENCE_NUMBER FROM JTF.JTF_NAV_TREE_ROOTS_B ORDER BY VIEWBY_ID, SEQUENCE_NUMBER;
  • Joining to translations to resolve display text: SELECT B.TREE_ROOT_ID, T.ROOT_VALUE, B.SEQUENCE_NUMBER FROM JTF.JTF_NAV_TREE_ROOTS_B B, JTF.JTF_NAV_TREE_ROOTS_TL T WHERE B.TREE_ROOT_ID = T.TREE_ROOT_ID AND T.LANGUAGE = USERENV('LANG');
  • Filtering roots by view-by context: ... WHERE VIEWBY_ID = :p_viewby_id;

Because the table is flagged Oracle Internal Use Only, direct DML should be avoided; query and reporting access is appropriate, while maintenance should occur through standard Oracle Applications programs and supported concurrent processes.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

  • JTF.JTF_NAV_VIEWBYS_B — Referenced by VIEWBY_ID; defines the view-by contexts grouping the roots.
  • JTF.JTF_NAV_TREE_ROOTS_TL — References TREE_ROOT_ID; holds the language-specific translations of root values.
  • JTF.JTF_NAV_NODE_TYPES — References TREE_ROOT_ID; associates navigation node types with their root.
  • FND.FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for VPD-enabled hosting.
  • FND.FND_USER — Referenced by the WHO columns CREATED_BY and LAST_UPDATED_BY.
  • FND.FND_LOGINS — Referenced by LAST_UPDATE_LOGIN.

Together these objects form the navigation definition and translation hierarchy anchored at JTF_NAV_TREE_ROOTS_B, with JTF_NAV_TREE_ROOTS_TL and JTF_NAV_NODE_TYPES functioning as dependent child entities linked through the TREE_ROOT_ID surrogate key.