Results for “jtf_diagnostic_stats”

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

Overview

JTF_DIAGNOSTIC_STATS is a table in the JTF schema (CRM Foundation product) that stores statistical information about historical test executions within the Oracle E-Business Suite diagnostic framework. It is a transactional store rather than a configuration table: each row captures the aggregate outcome of repeated executions of a named diagnostic test, including run counts, failure counts, and the timestamps and sequence identifiers associated with the most recent execution and the most recent failure. It is present and valid in both EBS 12.1.1 and 12.2.2, with 18 documented columns in the 12.2.2 physical schema.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as standalone. That classification is a modeling suggestion only: the table behaves as a self-contained fact or satellite-like record keyed by an application/group/test-class triple, with no parent hub tables feeding it through foreign keys other than the security group reference. It therefore does not require link-table decomposition in a vault model, but it carries a natural business key that makes it a candidate for a single hub with an attached satellite holding the mutable counters.

Key Information Stored

The surrogate primary key is SEQUENCE, backed by the sequence-driven constraint JTF_DIAGNOSTIC_STATS_PK1. The business-key candidate is the unique index JTF_DIAG_STATS_UK1 defined over APPNAME, GROUPNAME, and TESTCLASSNAME, which together identify a specific diagnostic test within an application and functional group.

• APPNAME, GROUPNAME, TESTCLASSNAME — the identifying triple for the diagnostic test being tracked; these form the unique business key.
• TOTALRUN — cumulative count of executions recorded for this test.
• TOTALFAIL — cumulative count of failed executions, supporting failure-rate reporting.
• LASTEXECUTIONTIME — timestamp of the most recent execution.
• LASTSTATUS — outcome of the most recent execution.
• LASTREPORTSEQUENCEID — pointer to the report or log record produced by the most recent run.
• LASTFAILURETIME — timestamp of the most recent failure.
• LASTFAILURESEQUENCEID — pointer to the failure detail record for the most recent failure.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified each row and when.

Common Use Cases and Queries

Typical usage centers on diagnostic health reporting: identifying tests with the highest failure ratios, detecting tests that have stopped running, and correlating failures to their report sequences. A representative query for the worst offenders is:

• SELECT appname, groupname, testclassname, totalrun, totalfail, ROUND(totalfail/DECODE(totalrun,0,1,totalrun)*100,2) pct_fail FROM jtf.jtf_diagnostic_stats WHERE totalfail > 0 ORDER BY pct_fail DESC;
• SELECT * FROM jtf.jtf_diagnostic_stats WHERE laststatus <> 'SUCCESS' AND lastexecutiontime > SYSDATE - 7;
• SELECT s.appname, s.testclassname, s.lastfailuresequenceid FROM jtf.jtf_diagnostic_stats s WHERE s.security_group_id = :gid;

Because the table retains aggregates rather than individual run history, it is best used as a summary layer; detailed execution history resides in the referenced report and failure records. The search term "Dynatrace Error Counts.xlsx" suggests a parallel requirement — extracting comparable error-count metrics for external monitoring tools. A view or extract over TOTALRUN, TOTALFAIL, LASTSTATUS, and LASTFAILURETIME maps naturally to such a spreadsheet or APM feed.

Related Objects

• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; joins on SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• JTF_DIAGNOSTIC_STATS_PK1 — the primary key constraint enforcing SEQUENCE uniqueness.
• JTF_DIAG_STATS_UK1 — unique index over APPNAME, GROUPNAME, TESTCLASSNAME.
• JTF_DIAGNOSTIC_STATS_SEQ — the sequence supplying the SEQUENCE surrogate key.
• Report and failure detail records referenced by LASTREPORTSEQUENCEID and LASTFAILURESEQUENCEID, which resolve to the diagnostic report store maintained by the JTF diagnostic framework.