Results for “jtf_mon_sstat”

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

Overview

JTF_MON_SSTAT is a reporting view in the Oracle E-Business Suite CRM Foundation (JTF) module that consolidates session-level activity logging data into a single queryable structure. Its name reflects its function as a monitoring (MON) session statistics (SSTAT) view. The view joins raw activity log entries against a session lookup table to produce a combined result set containing session identifiers, page identifiers, timestamps, and the application security context (user, application, and responsibility) under which each activity was recorded. In the context of Oracle EBS 12.1.1 and 12.2.2, this view supports diagnostic and monitoring reporting rather than transactional processing, providing administrators and support teams with visibility into how CRM Foundation sessions navigate application pages over time. Because it surfaces the SESSION_NAME column, it is a natural entry point for users searching by session name to trace activity recorded against a named session.

Underlying Base Objects

According to the documented view text, JTF_MON_SSTAT is defined over two sources. The first is an inline view (aliased HIT) that selects SESKEY, PAGE_ID, START_TIME, USER_ID, APP_ID, and RESP_ID from the base table JTF_MON_ACT_LOG. The second is the lookup table JTF_MON_SES_LOOKUP (aliased SNAME), which supplies the SESSION_NAME and SESSION_ID values. The two sources are joined on the common SESKEY column, so each row in the activity log is enriched with the human-readable session name and session identifier held in the lookup table. This design separates the high-volume activity log from the descriptive session metadata, allowing the view to present a denormalized, reporting-friendly result set. The ETRM metadata notes that the view is not implemented in the reference database and that no base objects are separately documented, so the authoritative definition remains the view text itself.

Key Columns

• SESKEY — The session key used to join the activity log to the session lookup table; acts as the correlation identifier between the two sources.
• SESSION_NAME — The descriptive name of the session, retrieved from JTF_MON_SES_LOOKUP. This is the column most relevant to searches for "session_name".
• SESSION_ID — The numeric session identifier associated with the session key.
• PAGE_ID — Identifies the application page or function visited during the logged activity.
• START_TIME — The timestamp at which the logged activity began.
• USER_ID — The application user who generated the activity.
• APP_ID — The application (product) context in which the activity occurred.
• RESP_ID — The responsibility under which the user was operating at the time of the activity.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting session behavior, auditing page access by user or responsibility, and reporting on session activity within a time window. The following examples illustrate standard queries.

• Retrieve all activity for a named session:

  SELECT seskey, session_name, session_id, page_id, start_time,
         user_id, app_id, resp_id
  FROM   jtf_mon_sstat
  WHERE  session_name = :p_session_name
  ORDER  BY start_time;

• List activity by user and responsibility within a period:

  SELECT session_name, page_id, start_time
  FROM   jtf_mon_sstat
  WHERE  user_id = :p_user_id
  AND    start_time BETWEEN :p_from AND :p_to;

• Summarize activity counts per session:

  SELECT session_name, COUNT(*) activity_count
  FROM   jtf_mon_sstat
  GROUP  BY session_name
  ORDER  BY activity_count DESC;

These queries are read-only and intended for diagnostic reporting; because the view derives from activity log data, results reflect whatever monitoring records have been captured by the CRM Foundation instrumentation in the environment.