Search Results jtf_grid_datasources_vl




Overview
Explore in AI Chat

Overview

The view APPS.JTF_GRID_DATASOURCES_VL is a multilingual (MLS) validation view within the Oracle E-Business Suite CRM Foundation (JTF) product family. It exposes the translation-independent and translation-dependent attributes of grid data sources configured for use by the JTF grid infrastructure, which underlies many CRM and self-service user interface components in EBS 12.1.1 and 12.2.2. The view presents a joined, language-filtered record set so that applications and reports can retrieve a grid data source definition together with its user-facing title in the session's active language. It is a reporting and integration convenience layer: rather than querying the base and translation tables separately and applying a language filter manually, consumers read from a single validated object whose status is VALID in the APPS schema.

As an MLS view, JTF_GRID_DATASOURCES_VL is not a physical table and stores no data of its own. Its role is to abstract the underlying base and translation tables and enforce the standard language resolution rule, supplying the correct translated title text based on the user's session language. This makes it suitable for ad-hoc reporting, data extraction, and integration queries that need grid metadata while respecting Oracle's translation model.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two objects, both referenced as synonyms in the APPS schema:

The view's SELECT joins these two relations on GRID_DATASOURCE_NAME and restricts the translation row with T.LANGUAGE = USERENV('LANG'), ensuring that only the record matching the current language is returned. The body of the view aliases the base table as B and the translation table as T, concatenating the base and translated columns into the final projected result set. Because the join returns a single combined row per grid data source for the active language, callers do not need to manage the language dimension themselves.

Key Columns

The view projects the following columns, drawn from the base and translation tables:

Common Use Cases and Queries

Typical scenarios include auditing configured grid data sources, verifying translation accuracy, and documenting the runtime view and fetch parameters used by JTF grids. A basic query lists the identifier, title, and backing view:

SELECT GRID_DATASOURCE_NAME, TITLE_TEXT, DB_VIEW_NAME, MAX_QUERIED_ROWS, FETCH_SIZE
FROM   APPS.JTF_GRID_DATASOURCES_VL;

To obtain the filter and presentation settings for a specific data source, constrain on the name:

SELECT GRID_DATASOURCE_NAME, TITLE_TEXT, WHERE_CLAUSE,
       ALT_COLOR_CODE, ALT_COLOR_INTERVAL, DEFAULT_ROW_HEIGHT
FROM   APPS.JTF_GRID_DATASOURCES_VL
WHERE  GRID_DATASOURCE_NAME = :p_name;

Because the view applies USERENV('LANG') automatically, running these queries under a given session language returns the corresponding translated title without further filtering. Note that the underlying objects are referenced as synonyms owned by APPS, so the view should be queried from an APPS context or with appropriate privileges.