Search Results jtf_custom_grids_pk

Overview

JTF_CUSTOM_GRIDS is a table in the JTF (CRM Foundation) schema that stores user-named sets of grid customizations, commonly referred to in Oracle Applications as "Folders." A Folder is a saved personalization of a tabular region — the choice of visible columns, their ordering, sort sequence, and filtering criteria — persisted so that a user can recall a preferred layout rather than reconfiguring it interactively each session. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the metadata backbone for the folder framework that appears throughout CRM and self-service forms, including the Applications Dashboard infrastructure.

From a Data Vault modeling perspective, the table's FK structure is characterized as satellite-leaning. That classification is a heuristic suggestion rather than a functional designation: JTF_CUSTOM_GRIDS behaves primarily as a descriptive detail set whose rows hang off reusable grid definitions and user identities, rather than as an independent hub of business events or a link that resolves many-to-many associations. Modelers using this structure within a dimensional or Data Vault warehouse would typically treat it as an extension of a GRID_DATASOURCE hub keyed by user and language.

Key Information Stored

The surrogate primary key is CUSTOM_GRID_ID, populated by the sequence behind the JTF_CUSTOM_GRIDS_PK constraint; it is also enforced as a unique index (JTF_CUSTOM_GRIDS_U1). The natural business key is captured by JTF_CUSTOM_GRIDS_U2, a composite unique index over CREATED_BY, LANGUAGE, GRID_DATASOURCE_NAME, and CUSTOM_GRID_NAME. This combination asserts that a named folder is unique per creator and per language for a given grid datasource — the implication being that folders are personal, not global, by default.

The most operationally significant columns are:

• GRID_DATASOURCE_NAME — identifies the grid definition against which the folder applies; the central join key to JTF_GRID_DATASOURCES_B and JTF_GRID_COLS_B.
• CUSTOM_GRID_NAME — the user-visible folder name.
• CREATED_BY — the owning user or responsibility that created the folder.
• LANGUAGE — the language context in which the folder name and configuration apply.
• PUBLIC_FLAG — distinguishes folders shared with a wider audience from private ones.
• WHERE_CLAUSE — the stored filter predicate applied to the datasource when the folder is opened.
• GRID_SORT_COL_ALIAS1, GRID_SORT_COL_ALIAS2, GRID_SORT_COL_ALIAS3 — the ordered sort columns, each keyed back to alias values in JTF_GRID_COLS_B.
• DEFAULT_ROW_HEIGHT — presentation attribute controlling row rendering.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-tenant or restricted data access.
• Standard audit columns: CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Folder administration and diagnostics are the dominant scenarios. A support analyst troubleshooting "my folder disappeared" typically queries by creator and datasource:

• SELECT CUSTOM_GRID_ID, CUSTOM_GRID_NAME, GRID_DATASOURCE_NAME, PUBLIC_FLAG FROM JTF.JTF_CUSTOM_GRIDS WHERE CREATED_BY = :user_id;
• Identifying shared folders for a grid: filter on PUBLIC_FLAG = 'Y' joined to JTF_GRID_DATASOURCES_B on GRID_DATASOURCE_NAME to resolve the datasource display name.
• Reporting folder adoption: count rows grouped by GRID_DATASOURCE_NAME and LANGUAGE to see which regions attract the most personalization.
• Reconstructing a saved layout: join to JTF_CUSTOM_GRID_COLS on CUSTOM_GRID_ID for column membership and to JTF_CUSTOM_BIND_VALUES for bound parameter values, then correlate the three GRID_SORT_COL_ALIAS* columns to establish sort order.

Because WHERE_CLAUSE is stored as text, it should be inspected but never executed without review. Migration scripts that move folders between environments generally key on the four-column business key rather than on CUSTOM_GRID_ID, since IDs are environment-specific.

Related Objects

The following objects participate directly in the folder framework and are joined on documented keys:

• JTF_GRID_DATASOURCES_B — the parent grid definition; joined on GRID_DATASOURCE_NAME.
• JTF_GRID_COLS_B — defines available columns and valid sort aliases; joined on GRID_DATASOURCE_NAME together with the GRID_SORT_COL_ALIAS columns.
• JTF_CUSTOM_GRID_COLS — child table holding the column set for each folder; joined on CUSTOM_GRID_ID.
• JTF_CUSTOM_BIND_VALUES — child table holding bound values for folder parameters; joined on CUSTOM_GRID_ID.
• JTF_DEF_CUSTOM_GRIDS — associates default folders with grid contexts; joined on CUSTOM_GRID_ID.
• FND_SECURITY_GROUPS — security grouping referenced through SECURITY_GROUP_ID.

Application logic interacting with these tables is exposed through the JTF folder APIs and the OA Framework personalization layer, which resolve folder metadata at runtime rather than requiring direct DML against JTF_CUSTOM_GRIDS.