Search Results jtf_nav_viewbys_b_pk

Overview

JTF_NAV_VIEWBYS_B is the base table in the JTF (CRM Foundation) schema that stores the view-by definitions associated with each navigation tab in the Oracle E-Business Suite. Within the Oracle EBS 12.1.1 and 12.2.2 navigational framework, tabs present users with configurable "view by" options — grouping or filtering criteria such as Customer, Status, or Date — that shape how records are displayed on a page. This table holds the master (base) records for those view-by entries, while translated and descriptive attributes are stored in the companion _TL table.

The table carries a heuristic Data Vault classification of hub-leaning. In Data Vault modeling terms, JTF_NAV_VIEWBYS_B behaves like a hub: it anchors a stable business key (VIEWBY_VALUE) surrounded by descriptive and auditing attributes, with relationships to other structures flowing outward through foreign keys. This classification is a modeling suggestion derived from the FK topology rather than a physical constraint enforced by EBS.

Key Information Stored

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

• VIEWBY_ID — The surrogate primary key (JTF_NAV_VIEWBYS_B_PK) uniquely identifying each view-by record.
• VIEWBY_VALUE — The internal value or code representing the view-by criterion; a business-key candidate via unique index JTF_NAV_VIEWBYS_B_U2.
• TAB_ID — The navigation tab to which this view-by belongs, linking the view-by to its owning tab.
• SEQUENCE_NUMBER — Controls the display order of the view-by relative to others on the same tab.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or security-group partitioning.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2, participating in both unique indexes (U1 on VIEWBY_ID plus ZD_EDITION_NAME; U2 on VIEWBY_VALUE plus ZD_EDITION_NAME).
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard WHO-column tracking.

The composite unique indexes U1 and U2 identify the true business-key candidates: VIEWBY_ID and VIEWBY_VALUE, each scoped by ZD_EDITION_NAME. The surrogate VIEWBY_ID should be distinguished from VIEWBY_VALUE, which carries the user-facing or semantic identity of the view-by.

Common Use Cases and Queries

Primary use cases center on reconstructing and auditing tab navigation configuration, diagnosing missing or misordered view-bys, and building reporting extracts of navigation metadata. A typical query retrieves all view-bys for a given tab in display order:

• SELECT VIEWBY_ID, VIEWBY_VALUE, SEQUENCE_NUMBER FROM JTF.JTF_NAV_VIEWBYS_B WHERE TAB_ID = :tab_id ORDER BY SEQUENCE_NUMBER;
• Joining to the translation table to obtain display labels: SELECT b.VIEWBY_ID, b.VIEWBY_VALUE, t.VIEWBY_NAME FROM JTF_NAV_VIEWBYS_B b, JTF_NAV_VIEWBYS_TL t WHERE b.VIEWBY_ID = t.VIEWBY_ID;
• Security-group scoped analysis to confirm which view-bys are visible to a given group via SECURITY_GROUP_ID.
• Health checks enumerating view-bys that lack a translation row or reference an inactive tab.

Related Objects

• JTF_NAV_VIEWBYS_TL — Translation table; joins on VIEWBY_ID for language-specific view-by names and descriptions.
• JTF_NAV_TREE_ROOTS_B — References this table through VIEWBY_ID, anchoring tree-root structures to their view-by.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security-group partitioning.
• JTF_NAV_TABS_B — The tab base table relating through TAB_ID, defining the parent tab of each view-by.
• JTF_NAV_VIEWBYS_B_PK / U1 / U2 — Primary key and unique indexes enforcing identity and editioning constraints.