Search Results jtf_custom_bind_values_u1

Overview

JTF.JTF_CUSTOM_BIND_VALUES is a transactional configuration table in the Oracle E-Business Suite JTF schema (part of the CRM Foundation / Application Foundation product family). It stores the resolved runtime values of bind variables that are referenced in the WHERE clause of a user-defined custom grid query. When an administrator or end user defines a custom grid over a particular business entity, the query can be parameterized with bind variables. The definitions of those bind variables—and the concrete values assigned to them for each grid—are persisted in this table.

Under the supplied ETRM metadata, the object is classified as satellite-leaning using a heuristic Data Vault model. Interpreted as a modeling suggestion, this indicates the table behaves primarily as a descriptive dependent of a parent hub/link: its rows describe attributes (the values) that qualify a customization context rather than acting as an independent business entity in their own right. The dependency is anchored by the foreign key CUSTOM_GRID_ID referencing JTF.JTF_CUSTOM_GRIDS.

The object is documented with 12 columns in the ETRM 12.2.2 physical schema, is marked VALID, and resides in the APPS_TS_TX_DATA tablespace (PCT Free 10). Note the standard Oracle EBS restriction: this object is intended for access by Oracle Applications programs, not for direct customer DML.

Key Information Stored

The two most significant columns form the business-key candidate and the core identity of each row:

• CUSTOM_GRID_ID (NUMBER) — the unique customization identifier. This is the leading column of the composite unique index JTF_CUSTOM_BIND_VALUES_U1 and of the primary key.
• BIND_VARIABLE_NAME (VARCHAR2(30)) — the exact name of the bind variable as specified in the query's WHERE clause. It is the second column of both the unique index and primary key.
• BIND_VARIABLE_DATATYPE (VARCHAR2(30)) — the declared datatype of the bind variable, which determines which value column holds the effective data.
• BIND_VARIABLE_CHAR_VALUE (VARCHAR2(2000)) — used when the datatype is character (C).
• BIND_VARIABLE_NUMBER_VALUE (NUMBER) — used when the datatype is numeric (N).
• BIND_VARIABLE_DATE_VALUE (DATE) — used when the datatype is date (D).

Regarding keys, the documented primary key is JTF_CUSTOM_BIND_VALUES_PK (CUSTOM_GRID_ID, BIND_VARIABLE_NAME). The documented unique index JTF_CUSTOM_BIND_VALUES_U1 covers the same two columns (CUSTOM_GRID_ID, BIND_VARIABLE_NAME) in the APPS_TS_TX_IDX tablespace. Because the metadata does not expose a surrogate sequence-derived single-column key, the composite of grid identifier plus bind name is effectively the natural business key enforcing one value per bind variable per grid. The remaining columns—CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and SECURITY_GROUP_ID—are standard WHO audit and Multi-Org/VPD security columns.

Common Use Cases and Queries

This table is typically consulted to reconstruct or debug the effective filter applied by a saved custom grid. A common pattern joins the bind values back to their parent grid definition:

• Retrieve all bind variables for a given grid — filter on CUSTOM_GRID_ID to list every parameter and its value, useful when diagnosing why a grid returns unexpected rows.
• Type-aware value extraction — use a CASE on BIND_VARIABLE_DATATYPE to return the correct value column (C→char, N→number, D→date), since only one value column is populated per row.
• Change auditing — report on LAST_UPDATED_BY and LAST_UPDATE_DATE to identify who recently altered a grid's parameter values.
• Duplicate detection — the unique index JTF_CUSTOM_BIND_VALUES_U1 guarantees uniqueness on (CUSTOM_GRID_ID, BIND_VARIABLE_NAME), so grouping on those columns should never yield duplicates.

A representative query joining back to the parent grid would be: SELECT v.CUSTOM_GRID_ID, v.BIND_VARIABLE_NAME, v.BIND_VARIABLE_DATATYPE, v.BIND_VARIABLE_CHAR_VALUE, v.BIND_VARIABLE_NUMBER_VALUE, v.BIND_VARIABLE_DATE_VALUE FROM JTF.JTF_CUSTOM_BIND_VALUES v WHERE v.CUSTOM_GRID_ID = :grid_id;

Related Objects

The following objects are the most significant relationships documented in the metadata:

• JTF.JTF_CUSTOM_GRIDS — referenced by the foreign key JTF_CUSTOM_BIND_VALUES.CUSTOM_GRID_ID → JTF_CUSTOM_GRIDS. This is the dominant parent, providing the customization header this table's rows qualify.
• FND_SECURITY_GROUPS — referenced by the foreign key CUSTOM_BIND_VALUES.SECURITY_GROUP_ID → FND_SECURITY_GROUPS, supporting VPD-enabled role/security-group hosting.
• FND_USER — implied by the WHO columns CREATED_BY and LAST_UPDATED_BY (foreign key to FND_USER.USER_ID).
• FND_LOGINS — implied by LAST_UPDATE_LOGIN (foreign key to FND_LOGINS.LOGIN_ID).
• JTF_CUSTOM_BIND_VALUES_U1 — the unique index over (CUSTOM_GRID_ID, BIND_VARIABLE_NAME), the principal access path for lookups by grid.
• JTF_CUSTOM_BIND_VALUES_PK — the primary key constraint enforcing row identity on the same two columns.

Collectively these relationships position the table as a detail satellite beneath the custom-grid definition hierarchy, with standard audit and security-group dependencies layered on top.