Results for “jtf_objects_b_n1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF.JTF_OBJECTS_B is a foundational seed-data table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the JTF schema and stored in the APPS_TS_SEED tablespace. It stores the canonical definitions of "objects," which in EBS terminology represent business entities, modules, or metadata-driven views that other application modules reference by a short alphanumeric code. Rather than holding a foreign-key surrogate, this table exposes OBJECT_CODE as its primary key (constraint JTF_OBJECTS_B_PK) and as the unique-index candidate JTF_OBJECTS_B_U1, making the table a classic reference or lookup "hub."

Heuristically, the mined FK topology classifies JTF_OBJECTS_B as hub-leaning in a Data Vault sense: its key is referenced by dozens of downstream tables (Service, Contracts, Tasks, Notes, Interaction History, iPayment, and others) while it references only two upstream lookup tables (FND_APPLICATION and FND_SECURITY_GROUPS). This makes it a natural business-key hub for any Data Vault or dimensional model that must integrate cross-module EBS entities.

Key Information Stored

The table carries 48 documented columns. The most operationally significant are:

• OBJECT_CODE (VARCHAR2(30)) — Business key; the unique identifier for each object. It is the column behind both JTF_OBJECTS_B_U1 and the PK constraint.
• APPLICATION_ID — FK to FND_APPLICATION; identifies the owning EBS application. Indexed non-uniquely via JTF_OBJECTS_B_N1.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS; supports multi-org/security partitioning.
• OBJECT_FUNCTION, OBJECT_PARAMETERS — Internal form/function name and any runtime parameters used by the EBS framework.
• SELECT_ID, SELECT_NAME, SELECT_DETAILS — Define the columns returned when an object is resolved dynamically (e.g., a concatenated list of display attributes).
• FROM_TABLE, WHERE_CLAUSE, ORDER_BY_CLAUSE, INACTIVE_CLAUSE — The metadata that drives metadata-driven queries and list-of-values (LOV) behavior.
• SEEDED_FLAG — Distinguishes Oracle-delivered seed rows from customer-defined objects.
• URL, LAUNCH_METHOD, WEB_FUNCTION_ID, WEB_FUNCTION_NAME, WEB_FUNCTION_PARAMETERS, OA_WEB_FUNCTION_NAME, OA_WEB_FUNCTION_PARAMETERS — Web/HTML launch configuration for the object.
• START_DATE_ACTIVE, END_DATE_ACTIVE — Date-range activation controls.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Concurrency control and auditing.

Note: in the 12.2.2 documented physical schema, JTF_OBJECTS_B_U1 is rendered as (OBJECT_CODE, ZD_EDITION_NAME), reflecting the Edition-Based Redefinition (EBR) column added in 12.2.

Common Use Cases and Queries

Because the primary key is a short code, most access patterns are lookups by OBJECT_CODE or filters by APPLICATION_ID. Typical scenarios include:

• Determining which module owns a given object code when resolving a cross-module link.
• Driving dynamic LOVs and metadata queries using FROM_TABLE, SELECT_NAME, WHERE_CLAUSE, and ORDER_BY_CLAUSE.
• Validating customer-defined objects against SEEDED_FLAG.

Representative SQL:

SELECT o.object_code, o.object_function, a.application_name
FROM   jtf.jtf_objects_b o,
       fnd_application   a
WHERE  o.application_id = a.application_id
AND    o.seeded_flag   = 'Y';

SELECT child.table_name, child.column_name
FROM   all_cons_columns parent,
       all_constraints  fk,
       all_constraints  child
WHERE  parent.constraint_name = 'JTF_OBJECTS_B_PK'
AND    fk.r_constraint_name   = parent.constraint_name
AND    fk.constraint_name     = child.constraint_name;

Reporting uses include auditing which modules consume a given object type, tracing link integrity in Service/Contracts, and generating inventories of seeded versus custom objects.

Related Objects

JTF_OBJECTS_B is referenced by a wide array of EBS tables. The most significant include:

• JTF_OBJECTS_TL — Translations table joined on OBJECT_CODE; supplies language-dependent descriptions.
• CS_INCIDENT_LINKS — Joins on OBJECT_TYPE and SUBJECT_TYPE in Service incident-to-object links.
• JTF_NOTES_B — Joins on SOURCE_OBJECT_CODE; anchors note attachment to business entities.
• JTF_TASKS_B — Joins on SOURCE_OBJECT_TYPE_CODE; ties tasks to source objects.
• JTF_OBJECT_USAGES — Joins on OBJECT_CODE; records per-application usage of an object.
• OKC_* tables (e.g., OKC_K_ITEMS, OKC_RULES_B, OKC_CONTACTS) — Join on JTOT_OBJECT1_CODE / JTOT_OBJECT2_CODE / JTOT_OBJECT3_CODE for Contracts Core linkages.
• IBY_TANGIBLE — Joins on SOURCE_OBJECT_TYPE_CODE for iPayment integration.
• FND_APPLICATION and FND_SECURITY_GROUPS — Upstream lookups referenced by APPLICATION_ID and SECURITY_GROUP_ID respectively.

Together these relationships establish JTF_OBJECTS_B as a central integration hub across Service, Contracts, Tasks, Notes, and Payment modules in Oracle EBS.