Search Results jtf_rs_resource_values_u1

Overview

JTF.JTF_RS_RESOURCE_VALUES is a transactional table in the Oracle E-Business Suite (EBS) Resource Manager (JTF_RS) schema. It stores the parameter values that are associated with resources, allowing administrators and applications to attach arbitrary name/value metadata to a resource record. Each row links a resource (RESOURCE_ID) to a parameter definition (RESOURCE_PARAM_ID) and stores the corresponding value (VALUE) together with an application-specific grouping discriminator (VALUE_TYPE). The table is owned by the JTF schema, carries a status of VALID, and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as a link — it connects the resource entity (JTF_RS_RESOURCE_EXTNS) to the resource parameter definition (JTF_RS_RESOURCE_PARAMS) while carrying descriptive payload. Modelers treating the JTF resource domain as a Data Vault should therefore view JTF_RS_RESOURCE_VALUES as a link table with dependent attributes rather than as a pure hub or satellite.

Key Information Stored

The table has 28 documented columns. The most significant are:

• RESOURCE_PARAM_VALUE_ID – Numeric surrogate primary key (JTF_RS_RESOURCE_VALUES_PK). This is the column behind the user's search term, since it is the leading column of the unique index JTF_RS_RESOURCE_VALUES_U1.
• RESOURCE_ID – Foreign key to JTF_RS_RESOURCE_EXTNS identifying the resource that owns the value.
• RESOURCE_PARAM_ID – Foreign key to JTF_RS_RESOURCE_PARAMS identifying the parameter being populated.
• VALUE – VARCHAR2(255) holding the actual parameter value for this resource/parameter combination.
• VALUE_TYPE – VARCHAR2(30) grouping value; the metadata notes it permits application-specific grouping, e.g. CCT associating middleware configuration with values.
• OBJECT_VERSION_NUMBER – Sequential number used for optimistic database locking.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS supporting multi-org/security-group data segregation.
• Standard WHO columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for auditability.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY – Descriptive flexfield segments available for customer extensibility.

The business key is represented by the unique index JTF_RS_RESOURCE_VALUES_U2 on (RESOURCE_ID, RESOURCE_PARAM_ID, VALUE_TYPE), which enforces one value per resource/parameter/value-type combination. The surrogate PK (U1) exists alongside this natural key. Two unique indexes — U1 and U2 — both reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical scenarios involve retrieving the configured parameters for a resource, checking whether a specific value is set, or reporting on which resources use a given parameter.

• Retrieve values for a resource:

  SELECT rpv.resource_param_value_id, rpv.resource_param_id, rp.param_name?, rpv.value, rpv.value_type
  FROM   jtf.jtf_rs_resource_values rpv
  WHERE  rpv.resource_id = :resource_id;

• Locate a resource by parameter value:

  SELECT resource_id, value, value_type
  FROM   jtf.jtf_rs_resource_values
  WHERE  resource_param_id = :param_id
  AND    value = :value;

• Confirm uniqueness of the business key using U2 columns (RESOURCE_ID, RESOURCE_PARAM_ID, VALUE_TYPE).
• Report parameters grouped by VALUE_TYPE to distinguish, for example, CCT middleware configuration values from other application groupings.
• Audit changes by joining to FND_USER through CREATED_BY / LAST_UPDATED_BY.

Because the surrogate PK and both unique indexes are populated outside the table's own constraints, direct DML should be exercised cautiously; standard EBS practice is to modify resource parameters through the Resource Manager APIs rather than inserting rows manually.

Related Objects

JTF_RS_RESOURCE_VALUES participates in several documented foreign key relationships:

• JTF.JTF_RS_RESOURCE_EXTNS – referenced via RESOURCE_ID, the parent resource entity.
• JTF.JTF_RS_RESOURCE_PARAMS – referenced via RESOURCE_PARAM_ID, defining the parameter that the value populates.
• FND_SECURITY_GROUPS – referenced via SECURITY_GROUP_ID for security-group segregation.
• FND_USER – the WHO columns CREATED_BY and LAST_UPDATED_BY point to this table.
• FND_LOGINS – LAST_UPDATE_LOGIN references this table for session attribution.

In practice, queries against JTF_RS_RESOURCE_VALUES are almost always joined to JTF_RS_RESOURCE_EXTNS on RESOURCE_ID and to JTF_RS_RESOURCE_PARAMS on RESOURCE_PARAM_ID, since the value column is meaningful only in conjunction with its parameter definition and owning resource.