Search Results jtf_grid_cols_b




Overview
Explore in AI Chat

Overview

JTF_GRID_COLS_B is a metadata repository table in the JTF (CRM Foundation) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the definition of each column exposed by a spreadtable UI component — the interactive, sortable, resizable grid region used throughout CRM and self-service applications. Each row describes one column belonging to a named grid data source, capturing the physical database column it maps to, its display characteristics, sortability, validation behavior, and formatting rules. The table therefore acts as the runtime blueprint consulted by the JTF grid rendering engine when constructing a spreadtable at page execution time.

Because it is the foundation table (the "_B" suffix) for a translatable entity, JTF_GRID_COLS_B holds language-independent attribute definitions, while JTF_GRID_COLS_TL holds the translated column prompts and headers. ETRM classifies the table heuristically as hub-leaning within a Data Vault model, since it anchors a durable business key and is referenced by multiple dependent objects; this is a modeling suggestion rather than a physical EBS constraint.

Key Information Stored

The primary key is defined by JTF_GRID_COLS_B_PK, a composite of GRID_DATASOURCE_NAME and GRID_COL_ALIAS. A unique index, JTF_GRID_COLS_B_U1, extends this business key with ZD_EDITION_NAME to support edition-based redefinition. The most significant columns include:

Common Use Cases and Queries

The most common requirement is to enumerate the columns configured for a specific grid. For example:

  • SELECT GRID_COL_ALIAS, DB_COL_NAME, DISPLAY_SEQ, VISIBLE_FLAG FROM JTF.GRID_COLS_B WHERE GRID_DATASOURCE_NAME = :ds ORDER BY DISPLAY_SEQ;

Administrators and developers use this to diagnose why a column is missing, misordered, or non-sortable in a CRM or iSupport grid. A second scenario is auditing formatting and validation: joining to JTF_OBJECTS_B via VALIDATION_OBJECT_CODE reveals which validation logic governs a column. A third is reproducing the translatable prompt for a column by joining to JTF_GRID_COLS_TL on GRID_DATASOURCE_NAME and GRID_COL_ALIAS, restricted by LANGUAGE. Reporting queries frequently combine the base table with JTF_CUSTOM_GRID_COLS to distinguish seeded columns from customer-personalized ones, which is valuable during upgrades from 12.1.1 to 12.2.2 when metadata drift must be reconciled.

Related Objects

The table participates in a dense metadata web. The most significant relationships, with join columns, are:

  • JTF_GRID_DATASOURCES_B — parent data source; joined on GRID_DATASOURCE_NAME.
  • JTF_GRID_COLS_TL — translated prompts; joined on GRID_DATASOURCE_NAME and GRID_COL_ALIAS.
  • JTF_OBJECTS_B — validation entity; joined on VALIDATION_OBJECT_CODE.
  • FND_SECURITY_GROUPS — security grouping; joined on SECURITY_GROUP_ID.
  • JTF_CUSTOM_GRID_COLS — customer column personalizations; joined on GRID_DATASOURCE_NAME and GRID_COL_ALIAS.
  • JTF_GRID_SORT_COLS — default sort definitions; joined on GRID_DATASOURCE_NAME and the sort alias columns.
  • JTF_CUSTOM_GRIDS — saved grid layouts; joined on GRID_DATASOURCE_NAME and sort alias columns.

Together these objects form the JTF spreadtable metadata model, with JTF_GRID_COLS_B serving as the central definition point for column-level behavior.