Search Results jtf_custom_grids_u2

Overview

JTF.JTF_CUSTOM_GRIDS is a table in the Oracle E-Business Suite 12.1.1 and 12.2.2 applications schema (JTF, part of the CRM Foundation / Technology stack) that stores end-user personalizations applied to data-bound grid and table regions rendered through the JTF grid framework. Each row represents a named customization set — column ordering, sorting, row height, filtering logic, and visibility — that a user has saved against a specific grid data source. The table is registered in FND Design Data as JTF.JTF_CUSTOM_GRIDS and resides in the APPS_TS_TX_DATA tablespace with indexes in APPS_TS_TX_IDX. The object carries a VALID status in the ETRM 12.2.2 documentation and 16 documented columns. Note the standard Oracle restriction: this object is for internal use only and is not supported for direct access outside standard Oracle Applications programs.

From a heuristic Data Vault modeling perspective, the table leans toward a satellite classification. It holds descriptive, user-specific attributes (customization name, sort columns, where-clause text, row height, public flag) that qualify a parent business concept — the grid data source — rather than acting as an independent hub or a link between two hubs.

Key Information Stored

The table's surrogate primary key is CUSTOM_GRID_ID (NUMBER), enforced by unique index JTF_CUSTOM_GRIDS_U1. A second unique index, JTF_CUSTOM_GRIDS_U2, defines the business-key candidate: the combination of CREATED_BY, LANGUAGE, GRID_DATASOURCE_NAME, and CUSTOM_GRID_NAME. The remaining important columns are:

• GRID_DATASOURCE_NAME (VARCHAR2, 30) — identifies the meta-data set (grid region) to which the customization applies; this is the join key to the grid definition tables.
• CUSTOM_GRID_NAME (VARCHAR2, 80) — the user-defined label for the customization, unique within a data source and user.
• LANGUAGE — language of the customization row, part of the business key.
• CREATED_BY (NUMBER, 15) — the user who owns the customization (FK to FND_USER.USER_ID); part of the business key.
• GRID_SORT_COL_ALIAS1 / 2 / 3 (VARCHAR2, 30) — the first, second, and third columns the user selected for query sorting.
• WHERE_CLAUSE (VARCHAR2, 2000) — optional filter predicate applied by the end user.
• PUBLIC_FLAG — 'T' or 'F', indicating whether the customization is shared with all users; indexed by JTF_CUSTOM_GRIDS_N1.
• DEFAULT_ROW_HEIGHT (NUMBER) — the default number of display lines per row.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, supporting multi-org / data-security partitioning.
• Standard WHO columns — CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The primary use case is troubleshooting and auditing user personalizations for JTF-based grids: which named customizations exist, whether they are public, and what filters or sort orders they impose. Reporting queries typically join to FND_USER to resolve the owner and to the grid definition tables to reconcile data sources. For example, listing public customizations for a data source:

• SELECT cg.CUSTOM_GRID_ID, cg.CUSTOM_GRID_NAME, cg.WHERE_CLAUSE, cg.PUBLIC_FLAG FROM JTF.JTF_CUSTOM_GRIDS cg WHERE cg.GRID_DATASOURCE_NAME = :ds AND cg.PUBLIC_FLAG = 'T';
• SELECT cg.CUSTOM_GRID_NAME, u.USER_NAME, cg.CREATION_DATE FROM JTF.JTF_CUSTOM_GRIDS cg JOIN FND_USER u ON u.USER_ID = cg.CREATED_BY WHERE cg.LANGUAGE = 'US';

These patterns are useful for identifying orphaned customizations, diagnosing slow grid queries caused by expansive WHERE_CLAUSE predicates, and auditing which users have created shared (public) personalizations.

Related Objects

JTF_CUSTOM_GRIDS sits at the center of the JTF personalization sub-model. The most significant related objects and join columns are:

• JTF_GRID_DATASOURCES_B and JTF_GRID_COLS_B — referenced through GRID_DATASOURCE_NAME; they define the meta-data and columns that a customization targets.
• JTF_CUSTOM_GRID_COLS — references CUSTOM_GRID_ID; stores per-column settings within a customization.
• JTF_CUSTOM_BIND_VALUES — references CUSTOM_GRID_ID; holds bind variable values for parameterized customizations.
• JTF_DEF_CUSTOM_GRIDS — references CUSTOM_GRID_ID; denotes the default customization for a data source.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for data-security resolution.
• FND_USER — joined via CREATED_BY to resolve the owner of each customization.

Collectively these relationships confirm the table's role as a satellite-like store of user personalization data anchored to grid data-source hubs.