Search Results predicate_alias




Overview
Explore in AI Chat

Overview

JTF_OBJECTS_B is a CRM Foundation (JTF) reference table that stores the details of objects (modules) known to the Oracle E-Business Suite. In practice, it functions as a central registry of object types — such as resources, tasks, notes, service requests, and contracts — that other applications reference whenever they need to associate records, links, notes, or work items with a specific business object. The table resides in the JTF schema, carries a VALID status in 12.1.1 and 12.2.2, and is dated by standard WHO audit columns.

From a data modeling perspective, the documented foreign-key structure classifies JTF_OBJECTS_B as hub-leaning. This is a heuristic suggestion rather than an enforced construct: the table holds a stable set of object definitions keyed by a single business identifier, and is referenced by a very large number of downstream tables. It is therefore best modeled as a hub (or reference/lookup dimension) around which satellites such as JTF_OBJECTS_TL provide descriptive attributes.

Key Information Stored

The table contains 48 documented columns. The primary key is JTF_OBJECTS_B_PK, defined on OBJECT_CODE, which is the surrogate-level identifier and the value most foreign tables join against. A unique index, JTF_OBJECTS_B_U1, is defined on (OBJECT_CODE, ZD_EDITION_NAME), making OBJECT_CODE the business-key candidate once the edition column is considered.

Common Use Cases and Queries

Because JTF_OBJECTS_B is a lookup table, most usage centers on resolving an OBJECT_CODE to its owning application or launch definition, or on validating the set of object types permitted for a given linking table.

  • Resolving an object to its application:
    SELECT o.object_code, o.object_function, a.application_name
    FROM jtf_objects_b o
    JOIN fnd_application a ON a.application_id = o.application_id;
  • Listing active, non-seeded object types:
    SELECT object_code, fnd_obj_name
    FROM jtf_objects_b
    WHERE seeded_flag = 'N'
    AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
  • Locating launch definitions for a web-enabled object:
    SELECT object_code, web_function_name, oa_web_function_name
    FROM jtf_objects_b WHERE url IS NOT NULL;
  • Reconciling link tables against the registry, for example joining CS_KB_ELEMENT_LINKS.OBJECT_CODE back to JTF_OBJECTS_B to identify orphaned or unregistered object codes.

Typical reporting scenarios include auditing which objects are exposed as note or work-item types, verifying translated descriptions via JTF_OBJECTS_TL, and troubleshooting LOV or navigation failures where an object code has been inactivated.

Related Objects

JTF_OBJECTS_B is referenced by an extensive set of dependent tables, confirming its role as a shared hub for CRM, Service, Contracts, and Lease Management modules.