Search Results jtf_object_usages




Overview
Explore in AI Chat

Overview

JTF_OBJECT_USAGES is a CRM Foundation (JTF) intersection table that links records in JTF_OBJECTS to the applications, users, or subsystems that consume them. Its stated purpose is to allow other Oracle E-Business Suite modules to "hook" to object usages, providing an extensible registration point for associating a registered JTF object with a particular consumer code. The table resides in the JTF schema and is marked VALID in the ETRM 12.2.2 documentation, with the same definition applying to the 12.1.1 code line.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning. The table behaves less like a pure many-to-many link and more like a descriptive satellite that hangs off JTF_OBJECTS_B via OBJECT_CODE, carrying context and attribute payload rather than merely establishing a binary relationship between two hubs.

Key Information Stored

The documented physical schema contains 28 columns. The most significant are:

Business-key candidates are documented in the unique index JTF_OBJECT_USAGES_U1, which covers (OBJECT_USAGE_ID, ZD_EDITION_NAME). Note that this duplicates the surrogate key and serves primarily the edition-aware uniqueness requirement rather than a true business key.

Common Use Cases and Queries

Typical uses include discovering which applications depend on a given JTF object, driving seeded-versus-custom reporting, and auditing attribute extensions across modules. A standard join pattern is:

  • SELECT u.object_usage_id, o.object_code, o.object_name, u.object_user_code, u.seeded_flag FROM jtf_object_usages u, jtf_objects_b o WHERE u.object_code = o.object_code;
  • Filter by consumer: WHERE u.object_user_code = :user_code.
  • Security-scoped reporting: SELECT u.object_usage_id, u.object_code FROM jtf_object_usages u WHERE u.security_group_id = :sgid.
  • Seeded inventory: WHERE u.seeded_flag = 'Y' to list Oracle-delivered hooks.
  • Extensibility audit: select ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for rows where ATTRIBUTE_CATEGORY IS NOT NULL.
  • Edition-aware queries on 12.2 should include WHERE u.zd_edition_name = 'ORA$BASE' (or the appropriate edition) to avoid cross-edition duplicates.

Related Objects

  • JTF_OBJECTS_B — referenced via JTF_OBJECT_USAGES.OBJECT_CODE; the primary parent of the usage row.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs visibility of the usage record.
  • JTF_OBJECT_USAGES_PK — the primary key index on OBJECT_USAGE_ID.
  • JTF_OBJECT_USAGES_U1 — unique index on (OBJECT_USAGE_ID, ZD_EDITION_NAME).
  • JTF_OBJECTS_TL — translated names/descriptions for the parent object, useful for reporting joins.
  • FND_APPLICATION / FND_USER — contextual lookups for OBJECT_USER_CODE value meanings.
  • JTF_OBJECTS_VL / JTF_OBJECTS_V — the standard views commonly joined for object description display.