Search Results jtf_grid_datasources_b_pk

Overview

JTF_GRID_DATASOURCES_B is a CRM Foundation (JTF) metadata table that stores the definitions used to initialize, configure, and render "spreadtable" (spreadsheet-style) user interface components within Oracle E-Business Suite. Each row describes a grid data source — the view, query constraints, and display characteristics that the JTF grid framework applies when constructing a grid at runtime. The table is the base table of a translated entity: the language-independent attributes reside here, while translatable text is held in JTF_GRID_DATASOURCES_TL. This base/translation split confirms that the table functions as the anchor or master record for a self-contained metadata cluster.

Under the heuristic Data Vault classification mined from the foreign key structure, JTF_GRID_DATASOURCES_B is hub-leaning. In Data Vault modeling terms it behaves as a hub: its primary key, GRID_DATASOURCE_NAME, is a stable business key, and the tables that surround it (column definitions, sort columns, custom grid definitions) act as satellites and links that carry descriptive and relational detail. This classification is a modeling suggestion only; the physical implementation remains third-normal-form within the JTF schema.

Key Information Stored

The surrogate primary key is defined by constraint JTF_GRID_DATASOURCES_B_PK, which is backed by the unique index JTF_GRID_DATASOURCES_B_U1 on (GRID_DATASOURCE_NAME, ZD_EDITION_NAME). GRID_DATASOURCE_NAME is therefore the effective business key — a name-based identifier consumed throughout the JTF grid framework — while ZD_EDITION_NAME supports edition-based redefinition in the 12.2.2 schema.

• GRID_DATASOURCE_NAME — the named identifier for the data source; referenced by every dependent grid metadata table.
• DB_VIEW_NAME — the database view from which the grid retrieves its rows and columns.
• APPLICATION_ID — the owning application, validated against FND_APPLICATION, used to scope the data source by product.
• WHERE_CLAUSE — an optional predicate applied to the base view to filter grid content.
• MAX_QUERIED_ROWS and FETCH_SIZE — controls governing result-set limiting and array fetch behavior for performance management.
• DEFAULT_ROW_HEIGHT — the default rendered height of grid rows.
• ALT_COLOR_CODE and ALT_COLOR_INTERVAL — banded-row shading configuration for readability.
• SECURITY_GROUP_ID — the security grouping, validated against FND_SECURITY_GROUPS, used for access isolation.
• Standard WHO audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Administrators and developers query this table when diagnosing grid behavior, cloning grid definitions between environments, or auditing which data sources belong to a given application. A typical lookup joins the base definition to its translations:

• Identify all grid data sources owned by a product: SELECT grid_datasource_name, db_view_name FROM jtf_grid_datasources_b WHERE application_id = :app_id;
• Retrieve display and performance settings for a specific grid: SELECT db_view_name, where_clause, max_queried_rows, fetch_size FROM jtf_grid_datasources_b WHERE grid_datasource_name = :name;
• Obtain translatable prompts and titles via the TL table: SELECT b.grid_datasource_name, t.* FROM jtf_grid_datasources_b b, jtf_grid_datasources_tl t WHERE b.grid_datasource_name = t.grid_datasource_name AND t.language = USERENV('LANG');

Reporting use cases include inventorying all customized versus seeded grids (by joining JTF_CUSTOM_GRIDS and JTF_DEF_CUSTOM_GRIDS) and version-control extraction of grid metadata for migration packages.

Related Objects

• JTF_GRID_DATASOURCES_TL — translation table joined on GRID_DATASOURCE_NAME; supplies language-specific display text.
• JTF_GRID_COLS_B — column definitions for each data source, joined on GRID_DATASOURCE_NAME.
• JTF_GRID_SORT_COLS — default sort columns, joined on GRID_DATASOURCE_NAME.
• JTF_DEF_CUSTOM_GRIDS — seeded custom grid definitions referencing GRID_DATASOURCE_NAME.
• JTF_CUSTOM_GRIDS — user-defined custom grids referencing GRID_DATASOURCE_NAME.
• IEU_UWQ_NODE_DS — Universal Work Queue node data sources referencing DATASOURCE_NAME.
• FND_APPLICATION — parent application, joined via APPLICATION_ID.
• FND_SECURITY_GROUPS — security group validation via SECURITY_GROUP_ID.