Results for “jtf_diagnostic_app”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_DIAGNOSTIC_APP is a registration table owned by the JTF (CRM Foundation) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the applications that are registered with the diagnostic framework, including the HTML platform, which the framework treats as a pseudo application. In practical terms, the table acts as the master roster of participating applications so that the diagnostic infrastructure can enumerate, identify, and target those applications at runtime when diagnostic tests, checklists, or troubleshooting routines are executed.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling perspective. This is a modeling suggestion rather than a physical constraint: because the table has no downstream dependents and only a single outbound reference, it is best modeled as a hub-like reference set (an application registry) rather than as a link or satellite. The registration records are low-volume, slowly changing, and semantically independent of transactional data.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • SEQUENCE — The surrogate primary key, enforced through the JTF_DIAGNOSTIC_APP_PK1 constraint and populated from a sequence. It provides a system-generated, stable identifier for each registered application row.
  • APPID — The business identifier of the registered application. Together with ZD_EDITION_NAME, it forms the unique business-key candidate JTF_DIAGNOSTIC_APP_UK1, meaning an application and edition combination must be unique.
  • ZD_EDITION_NAME — The edition qualifier that distinguishes versions of the same application registry entry. This supports Oracle's Edition-Based Redefinition (EBR) model, allowing multiple editions of registration data to coexist.
  • SECURITY_GROUP_ID — The security grouping identifier, which references FND_SECURITY_GROUPS. It controls row-level visibility in a multi-tenant or multi-organization deployment.
  • OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO columns that capture audit information: who created and last modified the row, when, and through which login session.

Common Use Cases and Queries

The principal use case is enumerating the applications available to the diagnostic framework. Administrators and support engineers query this table to confirm which applications are registered and visible in a given environment, and to troubleshoot diagnostic sessions that fail to launch.

A typical query lists registered applications together with audit information:

  • SELECT appid, zd_edition_name, created_by, creation_date FROM jtf.jtf_diagnostic_app ORDER BY appid;
  • SELECT a.appid, g.security_group_name FROM jtf.jtf_diagnostic_app a, fnd_security_groups g WHERE a.security_group_id = g.security_group_id;

Reporting patterns generally join to FND_SECURITY_GROUPS to resolve the owning security group, filter by ZD_EDITION_NAME to isolate the active edition, and restrict to rows whose OBJECT_VERSION_NUMBER reflects the current record. Because the table is small and quasi-static, it is frequently used as a lookup or validation set rather than as a fact source.

Related Objects

The documented foreign key identifies FND_SECURITY_GROUPS as the primary related object, joined on SECURITY_GROUP_ID. The related objects most likely to be significant are:

  • FND_SECURITY_GROUPS — Referenced through JTF_DIAGNOSTIC_APP.SECURITY_GROUP_ID; supplies the security group definition governing row visibility.
  • JTF_DIAGNOSTIC_APP (primary key JTF_DIAGNOSTIC_APP_PK1) — Referenced by any diagnostic framework child tables keyed on the application registration surrogate.
  • FND_APPLICATION — The Oracle Applications registry; APPID values typically correspond to application short names registered in FND_APPLICATION.
  • JTF_DIAGNOSTIC_* framework tables — Diagnostic test, checklist, and execution tables that consume the registered application list at runtime.
  • FND_LOOKUPS — Commonly joined when translating registration status or diagnostic categories into display values.
  • ZD_EDITION_NAME / EBR edition views — Editioning views in the JTF schema that project the correct edition-specific rows.

No additional foreign keys beyond the SECURITY_GROUP_ID reference are documented, confirming the table's standalone classification.