Results for “jtf_mon_act_log”

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

Overview

JTF_MON_ACT_LOG is a CRM Foundation (JTF) monitoring table that records activity events within the Oracle E-Business Suite monitoring framework. It captures discrete actions performed by users against application pages, sessions, and middle-tier instances, forming the raw event log consumed by the JTF monitoring and diagnostics infrastructure. In Oracle EBS 12.1.1 and 12.2.2, this table is delivered as part of the CRM Foundation schema and is populated by the monitoring instrumentation rather than by end-user transactional flows.

The ETRM metadata notes that the object is "Not implemented in this database," meaning it may not be created or populated in every environment depending on whether CRM monitoring components have been deployed. Its heuristic Data Vault classification is satellite-leaning: the table behaves primarily as a descriptive satellite attached to a set of lookup hubs (MID, PAGE_ID, SESKEY, USER_ID), with the ACCESSKEY surrogate acting as the record identifier. It should therefore be modeled as an event/activity satellite rather than as a true hub or link.

Key Information Stored

The documented columns are limited to the primary key, the foreign keys, and the dependent attribute table linkage. The most significant items are:

• ACCESSKEY — Primary key (JTF_ACCESSKEY_PKY); surrogate identifier uniquely identifying each activity log entry.
• MID — Foreign key to JTF_MON_MID_LOOKUP, identifying the middle-tier / monitoring instance that generated the activity.
• PAGE_ID — Foreign key to JTF_MON_PNAME_LOOKUP, resolving the application page or function against which the activity was recorded.
• SESKEY — Foreign key to JTF_MON_SES_LOOKUP, tying the activity to a specific user session.
• USER_ID — Foreign key to JTF_MON_UNAME_LOOKUP, identifying the user who performed the monitored activity.

Beyond the primary key, these four FK columns are the strongest business-key candidates because they jointly describe the "who, what session, what page, and which server" context of each logged action. The ETRM metadata does not enumerate additional descriptive columns; any further attributes should be confirmed against the deployed table definition with a DESCRIBE or ALL_TAB_COLUMNS query.

Common Use Cases and Queries

Typical usage focuses on monitoring, usage auditing, and diagnostics. Analysts join the log to its lookup tables to produce human-readable activity reports:

• Activity volume by middle tier: aggregated counts grouped by MID to spot load imbalance or failing nodes.
• User activity trails: filtering by USER_ID and SESKEY to reconstruct what a given session accessed.
• Page popularity reporting: grouping by PAGE_ID to identify heavily accessed CRM pages.
• Session correlation: joining to JTF_MON_SES_LOOKUP for session start/end context.
• Attribute-level detail: joining to JTF_MON_DATA_ATTR via ACCESSKEY for extended parameters captured with the activity.

A representative pattern resolves the lookups in one pass:

SELECT a.ACCESSKEY, u.USER_NAME, p.PAGE_NAME, s.SESSION_START, a.MID
FROM JTF_MON_ACT_LOG a, JTF_MON_UNAME_LOOKUP u, JTF_MON_PNAME_LOOKUP p, JTF_MON_SES_LOOKUP s
WHERE a.USER_ID = u.USER_ID AND a.PAGE_ID = p.PAGE_ID AND a.SESKEY = s.SESKEY;

Because the table can grow rapidly, queries should always constrain by date range or by the lookup keys rather than scanning the full log.

Related Objects

The following objects are the most significant dependencies based on the documented FK and PK relationships:

• JTF_MON_MID_LOOKUP — referenced via JTF_MON_ACT_LOG.MID; resolves the monitoring instance.
• JTF_MON_PNAME_LOOKUP — referenced via JTF_MON_ACT_LOG.PAGE_ID; resolves page/function names.
• JTF_MON_SES_LOOKUP — referenced via JTF_MON_ACT_LOG.SESKEY; resolves user sessions.
• JTF_MON_UNAME_LOOKUP — referenced via JTF_MON_ACT_LOG.USER_ID; resolves user identities.
• JTF_MON_DATA_ATTR — references this table via ACCESSKEY; stores extended attribute values associated with each activity record.

Together these objects form the CRM monitoring data model, with JTF_MON_ACT_LOG at the center of the event stream and the four lookup tables supplying the descriptive context.