Search Results jtf_nav_tabs_b




Overview
Explore in AI Chat

Overview

JTF_NAV_TABS_B is the base table in the JTF (CRM Foundation) schema that stores the navigator tab definitions used by Oracle E-Business Suite's CRM navigation framework. Each row represents a single tab rendered within the Navigator, associated with a specific application context identified by APPLICATION_ID. Because the Navigator is a shared infrastructure component, this table underpins the menu strips displayed in CRM modules such as Oracle TeleSales, Oracle iSupport, and Oracle Marketing, and it may also be referenced by other products that surface tab-based navigation.

Physically, the object resides in the JTF schema and is designated VALID. Its primary key is enforced by the constraint JTF_NAV_TABS_B_PK on the TAB_ID column. Under the heuristic Data Vault classification mined from the foreign-key structure, the table is described as hub-leaning. In modeling terms, this suggests that JTF_NAV_TABS_B behaves as a hub-like entity: TAB_ID serves as the stable business key anchor for a set of tab identities, to which descriptive attributes and translations attach. The classification is a suggestion rather than an Oracle-mandated designation.

Key Information Stored

The Oracle 12.2.2 documented schema lists thirteen columns. The most operationally significant are summarized below.

  • TAB_ID — The surrogate primary key and the principal identity column. It is the value propagated to dependent child tables and is the join key throughout the model.
  • TAB_VALUE — The functional/code value for the tab. It participates in the unique business-key candidate JTF_NAV_TABS_B_U2.
  • NAVIGATOR_TYPE — Distinguishes the flavor or category of navigator the tab belongs to, allowing multiple navigator presentations to coexist.
  • APPLICATION_ID — The Oracle application that owns or displays the tab. Together with NAVIGATOR_TYPE, it controls which tabs appear for a given session context.
  • ICON_NAME — The icon associated with the tab, used during rendering.
  • SEQUENCE_NUMBER — Determines display ordering of tabs within the navigator.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting data-level access partitioning.
  • ZD_EDITION_NAME — The editioning column introduced for online patching (EBS 12.2.x). It appears in both unique indexes and separates the run-edition from the patch-edition copy of a row.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS WHO-column auditing.

Two unique indexes act as business-key candidates: JTF_NAV_TABS_B_U1 (TAB_ID, ZD_EDITION_NAME) and JTF_NAV_TABS_B_U2 (TAB_VALUE, ZD_EDITION_NAME). The U1 index confirms TAB_ID as the primary business identifier under editioning; U2 implies that TAB_VALUE must be unique within an edition.

Common Use Cases and Queries

Typical usage includes diagnosing why a tab does not render, reordering tabs, and auditing configuration across applications. A representative query joining the base and translation tables is:

  • SELECT b.tab_id, b.tab_value, b.navigator_type, b.sequence_number, t.user_tab_name FROM jtf_nav_tabs_b b, jtf_nav_tabs_tl t WHERE b.tab_id = t.tab_id AND t.language = USERENV('LANG') ORDER BY b.sequence_number;
  • Filtering by application: SELECT * FROM jtf_nav_tabs_b WHERE application_id = :app_id ORDER BY sequence_number;
  • Checking uniqueness of a code before configuration: SELECT tab_value, count(*) FROM jtf_nav_tabs_b GROUP BY tab_value HAVING count(*) > 1;
  • Auditing editioned rows: SELECT tab_id, zd_edition_name FROM jtf_nav_tabs_b WHERE zd_edition_name IS NOT NULL;

These patterns support reporting on navigator composition, upgrade validation, and troubleshooting of order-of-display issues.

Related Objects

  • JTF_NAV_TABS_TL — The translation (language) table. Its TAB_ID column carries a foreign key back to JTF_NAV_TABS_B, making it the principal dependent object for multilingual tab names.
  • FND_SECURITY_GROUPS — Referenced by JTF_NAV_TABS_B.SECURITY_GROUP_ID, providing the grouping used for data-level security filtering.
  • FND_APPLICATION — The logical parent implied by APPLICATION_ID, though not documented as a formal foreign key, used to resolve the owning product.
  • JTF_NAV_TABS_B_PK — The primary key constraint that anchors the hub-style identity of TAB_ID.
  • FND languages / FND_LANGUAGES — Used with the TL table to resolve the USERENV('LANG') join for translated tab labels.

Administrators configuring Navigator content should treat JTF_NAV_TABS_B as the master definition and JTF_NAV_TABS_TL as its localized companion, ensuring that both remain synchronized during any patching or configuration activity.