Search Results jtf_message_objects




Overview
Explore in AI Chat

Overview

JTF_MESSAGE_OBJECTS is a CRM Foundation (JTF) repository table that stores business object metadata used by the Oracle E-Business Suite Message Dictionary and object-generation framework. It defines the business entities, actions, and message modes that the JTF messaging infrastructure can address, together with the SQL fragments and DTD references required to instantiate or resolve those objects at runtime. In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the JTF schema and is documented as a "business objects store" in the ETRM repository.

The table carries 21 documented columns and is keyed by the composite primary key JTF_MESSAGE_OBJECTS_PK on (PRODUCT_CODE, BUS_OBJ_CODE, ACTION_CODE). The heuristic Data Vault classification mined from the foreign-key structure is standalone; from a modeling perspective this suggests the table behaves as an independent hub-like reference set rather than a dependent satellite, with no documented foreign-key parent or child relationships. In 12.2.x the table includes the ZD_EDITION_NAME column, indicating that it participates in the Edition-Based Redefinition (EBR) model introduced with Online Patching.

Key Information Stored

The most significant columns are:

  • PRODUCT_CODE, BUS_OBJ_CODE, ACTION_CODE — the composite business key forming JTF_MESSAGE_OBJECTS_PK, identifying the product, business object, and action combination being defined.
  • BUS_OBJ_ID — surrogate identifier for the business object row; the two SYS_IL... unique indexes documented (on column ordinals 6 and 8) are LOB/functional indexes rather than classic unique constraints, so the composite PK remains the authoritative business-key candidate.
  • BUS_OBJ_NAME — human-readable name of the business object.
  • BUS_OBJ_SQL — SQL text used to resolve or populate the object, typically a query fragment executed by the messaging engine.
  • OBJ_GENERATOR — the generator routine or package responsible for producing the object payload.
  • BUS_OBJ_DTD — DTD reference (stored in a LOB column) describing the XML structure of the message payload.
  • MSG_MODE — the messaging mode associated with the object definition.
  • ACTIVE_FLAG — enables or disables the definition.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns.
  • ATTRIBUTE1–ATTRIBUTE5 — the standard DFF/descriptive flexfield context columns.
  • ZD_EDITION_NAME — EBR edition marker, present in 12.2.x.

Common Use Cases and Queries

Typical uses include auditing which business objects are enabled for a given product, tracing which generator and DTD back a message payload, and diagnosing messaging failures caused by missing or inactive definitions.

  • List all active objects for a product: SELECT BUS_OBJ_CODE, ACTION_CODE, BUS_OBJ_NAME FROM JTF.JTF_MESSAGE_OBJECTS WHERE PRODUCT_CODE = :p AND ACTIVE_FLAG = 'Y';
  • Locate the DTD and generator for a specific object: SELECT OBJ_GENERATOR, BUS_OBJ_DTD FROM JTF.JTF_MESSAGE_OBJECTS WHERE PRODUCT_CODE=:p AND BUS_OBJ_CODE=:b AND ACTION_CODE=:a;
  • Find recently modified definitions: SELECT * FROM JTF.JTF_MESSAGE_OBJECTS WHERE LAST_UPDATE_DATE > SYSDATE-30;
  • Reporting on coverage of business objects by product and action, and identifying gaps where ACTIVE_FLAG='N' but definitions still exist.

Related Objects

The heuristic FK mining classifies JTF_MESSAGE_OBJECTS as standalone, so no hard parent/child constraints are documented. Practically, it is referenced by the JTF messaging and Message Dictionary components, including JTF_MESSAGES, JTF_MESSAGE_ATTRIBUTES, JTF_MESSAGE_MAPS, and the JTF_MSG_* generator packages. Join columns follow the composite key (PRODUCT_CODE, BUS_OBJ_CODE, ACTION_CODE) shared with those tables. Application code and concurrent programs that invoke the object generator also depend on the OBJ_GENERATOR and BUS_OBJ_SQL values retrieved from this table.