Search Results jtf_fm_service_all




Overview
Explore in AI Chat

Overview

JTF_FM_SERVICE_ALL is a CRM Foundation (JTF) table that stores configuration and runtime information about fulfillment servers. Fulfillment servers act as the processing engines within the Oracle EBS fulfillment management and workflow infrastructure, consuming messages from request queues, dispatching work to worker threads, and returning results to response queues. In this capacity, the table functions as the master registry of server instances, their queue assignments, thread thresholds, and email or IMAP integration settings.

Based on the documented foreign key structure, the ETRM metadata classifies this object as hub-leaning. This is a heuristic Data Vault modeling suggestion: SERVER_ID serves as the durable, unique business key around which related transactional or descriptive records (such as dispatcher rows in JTF_FM_DISPATCHERS) can be organized. In practice, this means JTF_FM_SERVICE_ALL is best treated as a reference or master hub table rather than a transactional fact table.

Key Information Stored

The primary key is defined by the constraint JTF_FM_SERVICE_ALL_PK, which is enforced on SERVER_ID. Note that a unique index, JTF_FM_SERVICE_ALL_U1, is defined on the composite of (SERVER_ID, ZD_EDITION_NAME), indicating that the business-key candidate for this table includes the editioning column used in Oracle EBS 12.2 multi-tenant data model. Among the 46 documented columns, the most operationally significant are:

Common Use Cases and Queries

Administrators and technical consultants typically query this table to audit server configuration, diagnose queue blockage, or review email integration metadata. A frequent pattern is listing all active servers with their queue assignments:

  • SELECT server_id, server_name, status, dispatcher_queue_name, request_queue_name FROM jtf.jtf_fm_service_all WHERE status = 'A';
  • Identifying servers with unusually high thread thresholds or low dequeue wait intervals that may indicate misconfiguration or performance risk.
  • Joining to JTF_FM_DISPATCHERS to correlate servers with their dispatched message loads.
  • Reviewing IMAP and email settings for troubleshooting bounceback or inbound mail processing failures.
  • Security-group-filtered reporting by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

The following objects are the most significant relationship points for this table, based on the documented FK metadata:

  • JTF_FM_DISPATCHERS — references JTF_FM_SERVICE_ALL.SERVER_ID via the column SERVER_ID (documented twice, indicating multiple relationship definitions). This is the primary child table for server dispatch activity.
  • FND_SECURITY_GROUPS — referenced by this table's SECURITY_GROUP_ID foreign key, governing row-level security filtering.

Beyond the documented foreign keys, the SERVER_ID and queue-name columns are referenced by fulfillment manager runtime processes and concurrent programs that manage server startup, shutdown, and worker thread lifecycle. Any query joining fulfillment dispatcher diagnostics should treat JTF_FM_SERVICE_ALL as the hub, with JTF_FM_DISPATCHERS as the dependent activity table.