Search Results jtf_object_usages_u1

Overview

JTF.JTF_OBJECT_USAGES is a foundational table in the Oracle E-Business Suite JTT (Applications Technology) schema, delivered across 12.1.1 and 12.2.2. It functions as the intersection, or association, table linking records in JTF_OBJECTS to the users or consumers of those objects. As the ETRM documentation states, it represents the "Intersection Table between JTF_OBJECTS and Objects User," meaning it records which object types (identified by OBJECT_CODE) are available to, associated with, or consumed by a given user or functional context (identified by OBJECT_USER_CODE).

The table resides in the APPS_TS_SEED tablespace, consistent with seed and setup data that supports the Oracle Applications Framework. Its Data Vault classification, mined heuristically from the foreign-key structure, is satellite-leaning. This suggests that the table is best modeled as an attribute-bearing satellite surrounding a core reference — here the OBJECT_CODE reference to JTF_OBJECTS_B — capturing the usage relationships and descriptive flexfield attributes that extend the base object definition.

Key Information Stored

The surrogate primary key, OBJECT_USAGE_ID, uniquely identifies each usage association and is enforced through the primary key constraint JTF_OBJECT_USAGES_PK. In 12.2.2 the unique index JTF_OBJECT_USAGES_U1 is documented over OBJECT_USAGE_ID together with ZD_EDITION_NAME, reflecting the editioning columns used to support Online Patching. Two nonunique indexes, OBJECT_USAGES_N1 on OBJECT_CODE and JTF_OBJECT_USAGES_N2 on OBJECT_USER_CODE, support the principal access paths.

• OBJECT_CODE — the object type identifier; a foreign key to JTF.JTF_OBJECTS_B.
• OBJECT_USER_CODE — the Oracle Applications internal function name of a form, defining the consumer of the object.
• SEEDED_FLAG — indicates whether the object type is pre-defined (seeded) by Oracle.
• OBJECT_VERSION_NUMBER — sequential lock-control number used with the HTML user interface.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row-level access.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield segments for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — edition column supporting 12.2 Online Patching.

Common Use Cases and Queries

This table is queried when diagnosing which object types are exposed to a specific function or user context, and when validating seeded versus custom object registrations. A typical join retrieves the usage and underlying object definition:

SELECT ou.OBJECT_USAGE_ID, ou.OBJECT_CODE, ou.OBJECT_USER_CODE, ou.SEEDED_FLAG
FROM JTF.JTF_OBJECT_USAGES ou, JTF.JTF_OBJECTS_B ob
WHERE ou.OBJECT_CODE = ob.OBJECT_CODE;

Reporting use cases include auditing all usages tied to a given form or function (filtering on OBJECT_USER_CODE), identifying custom, non-seeded registrations (SEEDED_FLAG), and extracting descriptive flexfield values from the ATTRIBUTE columns. The nonunique indexes N1 and N2 make these filtered queries efficient.

Related Objects

• JTF.JTF_OBJECTS_B — referenced via OBJECT_CODE; the base object definition table.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; controls access scoping.
• FND_USER — indirect relationship through the WHO columns CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — indirect relationship through LAST_UPDATE_LOGIN.
• JTF.JTF_OBJECT_USAGES_PK and unique index JTF_OBJECT_USAGES_U1 — the constraint and index the user searched for, enforcing uniqueness on OBJECT_USAGE_ID (and ZD_EDITION_NAME).