Search Results jtf_custom_grid_cols




Overview
Explore in AI Chat

Overview

JTF_CUSTOM_GRID_COLS is a CRM Foundation (JTF) transactional table that stores end-user personalizations applied at the individual column level within a spreadtable UI component. Where the parent table JTF_CUSTOM_GRIDS captures the user's saved grid definition (the customized layout as a whole), JTF_CUSTOM_GRID_COLS persists the fine-grained attributes of each column inside that grid: whether the column is visible, its default sort direction, its display sequence, its rendered width, and its user-defined label. This table is therefore central to the Oracle EBS "personalization" or "saved view" feature used across CRM applications such as Oracle Sales, Oracle TeleSales, Oracle Service, and other modules built on the JTF/Applications Technology UI stack.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object heuristically as a link: it associates a grid customization (via CUSTOM_GRID_ID) with a specific datasource column (via GRID_DATASOURCE_NAME and GRID_COL_ALIAS), and it additionally carries a security-group reference. In practice the table behaves as a dependent child of JTF_CUSTOM_GRIDS with an overlaid satellite-like payload of display attributes.

Key Information Stored

The primary key, enforced by the unique index JTF_CUSTOM_GRID_COLS_PK / JTF_CUSTOM_GRID_COLS_U1, is the composite business key (CUSTOM_GRID_ID, GRID_DATASOURCE_NAME, GRID_COL_ALIAS). This triple uniquely identifies one customized column within one grid, and the same three columns are the documented FK join columns to the parent grid and to the base column definitions.

Common Use Cases and Queries

Typical uses include diagnosing why a user's saved grid displays unexpected columns or order, migrating personalizations between environments, and reporting on how widely specific columns are hidden or re-sequenced. A representative query joining the child to its parent and base definitions:

  • SELECT c.custom_grid_id, c.grid_datasource_name, c.grid_col_alias, c.visible_flag, c.display_seq, c.display_hsize, c.sort_asc_by_default_flag, c.label_text FROM jtf_custom_grid_cols c WHERE c.custom_grid_id = :p_grid_id ORDER BY c.display_seq;
  • Hidden-column audit: SELECT grid_col_alias, COUNT(*) FROM jtf_custom_grid_cols WHERE visible_flag = 'N' GROUP BY grid_col_alias ORDER BY 2 DESC;
  • Join to base metadata: SELECT b.column_name, c.label_text, c.display_seq FROM jtf_custom_grid_cols c, jtf_grid_cols_b b WHERE c.grid_datasource_name = b.datasource_name AND c.grid_col_alias = b.col_alias;
  • Security-group-filtered extraction for migration: SELECT * FROM jtf_custom_grid_cols WHERE security_group_id = :sgid AND last_update_date > :since;

Related Objects

The most significant related objects, drawn from the documented FK relationships:

  • JTF_CUSTOM_GRIDS — parent grid personalization; join on CUSTOM_GRID_ID.
  • JTF_GRID_COLS_B — base column catalog; join on GRID_DATASOURCE_NAME and GRID_COL_ALIAS.
  • FND_SECURITY_GROUPS — security-group scoping; join on SECURITY_GROUP_ID.
  • JTF_CUSTOM_GRID_COLS_PK / _U1 — the composite unique indexes that enforce one row per customized column.
  • JTF_GRID_COLS_TL — translated column labels typically consulted alongside JTF_GRID_COLS_B for base label resolution.
  • FND_USER — indirectly referenced through CREATED_BY / LAST_UPDATED_BY for personalization ownership reporting.

Together these objects form the metadata backbone of JTF spreadtable personalization, and JTF_CUSTOM_GRID_COLS is the authoritative store of per-column user preferences within that model.