Search Results dequeue_wait_interval




Overview

JTF_FM_SERVICE is an Oracle EBS APPS-owned view in the CRM Foundation (JTF) product, classified as VALID in the E-Business Suite data dictionary. It presents information about the fulfillment servers registered within the Oracle CRM Foundation fulfillment management infrastructure. In EBS 12.1.1 and 12.2.2, this view is a reporting-oriented, security-reduced representation of its underlying storage table, exposing one filtered row set over the server configuration and runtime state records maintained by the fulfillment engine.

The view's role is primarily diagnostic, administrative, and integration-related. Fulfillment servers dispatch and process messages from request, response, error, and dispatcher queues, and this view surfaces the operational metadata used to monitor and configure them: server identity, startup/shutdown times, current status, worker thread thresholds, queue names, and e-mail account parameters. The SERVICE_DESCRIPTION column, which the user searched for, carries the human-readable description of each fulfillment server, complementing the technical SERVER_NAME identifier.

Underlying Base Objects

According to the documented ETRM metadata, JTF_FM_SERVICE is defined over a single referenced base object, JTF_FM_SERVICE_ALL, which is exposed as a SYNONYM. All columns listed in the view text originate from JTF_FM_SERVICE_ALL; the view performs a straightforward projection of that table's columns without the _ALL multi-org filter typically applied elsewhere in the schema.

The _ALL suffix in Oracle EBS conventionally denotes a table with an ORG_ID column supporting multiple operating units. Consistent with this convention, JTF_FM_SERVICE_ALL includes ORG_ID, and the view therefore exposes ORG_ID and operational columns such as F_DELETEDFLAG and OBJECT_VERSION_NUMBER directly. The view does not aggregate or join additional tables; its role is to provide a stable, named interface over the base table for reporting and query.

Key Columns

Common Use Cases and Queries

Typical scenarios include identifying fulfillment servers by description, auditing server configuration, and reviewing queue or thread settings before troubleshooting mail or dispatching failures.

  • Searching by description:
    SELECT server_id, server_name, service_description, status
    FROM   apps.jtf_fm_service
    WHERE  UPPER(service_description) LIKE UPPER('%email%')
    AND    NVL(f_deletedflag,'N') = 'N';
  • Listing active servers and their operational status:
    SELECT server_name, status, startup_time, optimum_wrkr_thrds, max_wrkr_thrds
    FROM   apps.jtf_fm_service
    WHERE  status = 'RUNNING';
  • Reviewing queue configuration for a specific server:
    SELECT server_name, dispatcher_queue_name, request_queue_name,
           error_queue_name, response_queue_name
    FROM   apps.jtf_fm_service
    WHERE  server_name = :p_server_name;
  • Auditing e-mail integration settings:
    SELECT server_name, imap_host, imap_port, from_address, enable_bounceback
    FROM   apps.jtf_fm_service
    WHERE  NVL(f_deletedflag,'N') = 'N';

Because the view reads directly from JTF_FM_SERVICE_ALL without additional filtering, queries should generally restrict on ORG_ID where operating-unit separation is required, and on F_DELETEDFLAG to exclude logically deleted server definitions.