Search Results bind_variable_name




Overview

JTF_CUSTOM_BIND_VALUES is a table owned by the JTF schema (CRM Foundation) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the bind variable values that back end-user customizations of filtering criteria applied to a SpreadTable user interface component. In practical terms, when a user personalizes the filter conditions of a spreadtable-based CRM page, the resulting parameter values are persisted here, keyed to a specific custom grid definition. The table therefore acts as a configuration store for runtime filter bindings rather than as a transactional or operational record.

The ETRM metadata classifies this object heuristically as satellite-leaning in a Data Vault sense. This should be read as a modeling suggestion: JTF_CUSTOM_BIND_VALUES behaves like an attribute-bearing satellite attached to the JTF_CUSTOM_GRIDS hub, carrying descriptive bind-variable values that depend on a parent grid identity rather than defining an independent business entity or a many-to-many association.

Key Information Stored

The primary key is JTF_CUSTOM_BIND_VALUES_PK, defined on the composite of CUSTOM_GRID_ID and BIND_VARIABLE_NAME. A unique index, JTF_CUSTOM_BIND_VALUES_U1, mirrors the same two columns, making them the business-key candidates as well as the physical key. The table contains twelve documented columns; the most significant are listed below.

Common Use Cases and Queries

The principal use case is diagnosing and reporting on end-user filter personalizations for CRM spreadtables. Administrators may need to enumerate the bind variables configured for a given custom grid, or to identify which value column is populated for each datatype. Because the table is a satellite to JTF_CUSTOM_GRIDS, joins typically start from the parent grid.

  • Listing all bind variables for a grid: SELECT BIND_VARIABLE_NAME, BIND_VARIABLE_DATATYPE FROM JTF.JTF_CUSTOM_BIND_VALUES WHERE CUSTOM_GRID_ID = :grid_id;
  • Retrieving resolved values while reconciling datatype to the correct value column, using CASE logic across the char, number, and date value columns.
  • Auditing change history by filtering on LAST_UPDATED_BY and LAST_UPDATE_DATE to trace recent personalization changes.
  • Security-scoped reporting by restricting results on SECURITY_GROUP_ID.
  • Cleanup or impact analysis when a JTF_CUSTOM_GRIDS record is removed, since the child bind values are dependent.

Related Objects

  • JTF_CUSTOM_GRIDS — Parent table referenced via JTF_CUSTOM_BIND_VALUES.CUSTOM_GRID_ID → JTF_CUSTOM_GRIDS. The primary dependency for this satellite.
  • FND_SECURITY_GROUPS — Referenced via JTF_CUSTOM_BIND_VALUES.SECURITY_GROUP_ID, providing the security-group context for each bind value.
  • JTF_CUSTOM_BIND_VALUES_PK / JTF_CUSTOM_BIND_VALUES_U1 — The primary key constraint and its backing unique index on (CUSTOM_GRID_ID, BIND_VARIABLE_NAME).

Beyond these documented relationships, the SpreadTable personalization framework and related JTF custom-grid metadata objects consume these bind values at runtime when rendering and filtering customized UI components.